Apply the "NO_LIMITED_CONTROLLER_CONNECT" fix to atmega16u2 too (and …

[purdeaandrei]

Description

I noticed while browsing code, that this modifier macro is applied only to the atmega32u2 mcu,
however looking at LUFA code it is something that applies to all Series 2 and Xmega AVRs too.

Looking at LUFA code this macro is tested for in very few places, and looks like it is only tested
in the case of MCUs for which it matters, so it's okay for it to be indiscriminately defined.

So looking at what keyboards we have I found we have two atmega16u2 keyboards in our keyboards folder:

• sixkeyboard
• xd004/v1

These keyboards are most likely benefited by this change.

Tested by @SidneyBovet

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).
  Tested by @SidneyBovet

[purdeaandrei]

@SidneyBovet @M0les @jackhumbert Sorry for the ping. Any chance you could test this change with the above mentioned keyboards? I am pinging you because you have contributed to the above mentioned two keyboards in git history.

[SidneyBovet]

Hey there, happy to help. I tried with my xd004/v1 and it does work as highlighted in tmk/tmk_keyboard#361, i.e. it could wake up my Windows 10 from sleep (and I tested without the changes, it does not). Needless to say it flashed and behaved just fine.

Great change as far as I am concerned!

[purdeaandrei]

Hey there, happy to help. I tried with my xd004/v1 and it does work as highlighted in tmk/tmk_keyboard#361, i.e. it could wake up my Windows 10 from sleep (and I tested without the changes, it does not). Needless to say it flashed and behaved just fine.

Great change as far as I am concerned!

Thanks! I have updated the PR description to say it's now tested.

@qmk/collaborators please review

[drashna]

Thanks!