Map Pocket EVO AYA SPACE, =, LC and RC buttons - #169
Open
jesherman wants to merge 1 commit into
Open
Conversation
These four buttons are wired to SoC GPIOs rather than to the controller MCU, so they never appear on the fake-Xbox-360 pad and were unmapped. They arrive instead on their own gpio-keys node, which the kernel only creates once the device tree declares it. Kept out of the existing gpio-keys node deliberately: InputPlumber grabs the source devices it manages, so sharing that node would swallow volume up. The device tree emits F13-F16 rather than AYANEO's stock KEY_A, KEY_EQUAL, KEY_LEFT and KEY_RIGHTSHIFT. Those type real characters, so any moment InputPlumber is not grabbing the node - desktop mode, a service restart - they would leak into whatever has focus. Only AYA SPACE is bound to a fixed action, since QuickAccess is the one thing Steam Input cannot bind. The other three become paddles so they stay remappable per game. Needs the matching aya-keys node in qcs8550-ayaneo-pocketevo.dts; until that lands nothing matches "aya-keys" and this config is inert. Verified on hardware by patching the DTB in place and reading the emulated Steam Controller's HID reports: AYA SPACE opens QAM, and =, LC and RC report as L5, L4 and R4.
Contributor
Author
|
Kernel half is up: virtudude/armada-packages#14 — it adds the Merge order matters slightly: this PR is inert until that node exists, and that node is inert until Both halves verified together on hardware: AYA SPACE opens QAM, and =, LC and RC report as L5, L4 and R4. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These four buttons are wired to SoC GPIOs rather than to the controller MCU, so they never appear on the fake-Xbox-360 pad and were unmapped. They arrive instead on their own gpio-keys node, which the kernel only creates once the device tree declares it.
Kept out of the existing gpio-keys node deliberately: InputPlumber grabs the source devices it manages, so sharing that node would swallow volume up.
The device tree emits F13-F16 rather than AYANEO's stock KEY_A, KEY_EQUAL, KEY_LEFT and KEY_RIGHTSHIFT. Those type real characters, so any moment InputPlumber is not grabbing the node - desktop mode, a service restart - they would leak into whatever has focus.
Only AYA SPACE is bound to a fixed action, since QuickAccess is the one thing Steam Input cannot bind. The other three become paddles so they stay remappable per game.
Needs the matching aya-keys node in qcs8550-ayaneo-pocketevo.dts; until that lands nothing matches "aya-keys" and this config is inert.
Verified on hardware by patching the DTB in place and reading the emulated Steam Controller's HID reports: AYA SPACE opens QAM, and =, LC and RC report as L5, L4 and R4.