Skip to content

fix(Ayaneo 3): match the joystick rings LED sys_name by glob - #666

Open
matmartinez wants to merge 1 commit into
ShadowBlip:mainfrom
matmartinez:ayaneo-3-led-glob
Open

fix(Ayaneo 3): match the joystick rings LED sys_name by glob#666
matmartinez wants to merge 1 commit into
ShadowBlip:mainfrom
matmartinez:ayaneo-3-led-glob

Conversation

@matmartinez

Copy link
Copy Markdown

The hid-ayaneo driver just merged in OpenGamingCollective/linux-unstable#3 registers the AYANEO 3 joystick-rings LED with a per-device name (<hid device name>:rgb:joystick_rings, e.g. 0003:1C4F:0002.0003:rgb:joystick_rings) instead of the fixed ayaneo:rgb:joystick_rings this config expects — the prefix was changed to dev_name() during kernel review, since a fixed LED name can collide.

sys_name is matched with glob_match(), so a wildcard prefix keeps this entry working with both the old fixed name and the new per-device one (the composite device is DMI-gated to the AYANEO 3, so the glob can't over-match on other hardware).

Verified on an AYANEO 3 on Bazzite 44 with the merged driver: the LED registers as 0003:1C4F:0002.0003:rgb:joystick_rings and the HID device (and thus the LED path) is recreated on every controller power cycle, which is why matching by exact name is brittle.

Related: ShadowBlip/OpenGamepadUI#528 (magic-modules integration coordination).

The hid-ayaneo driver merged in OpenGamingCollective/linux-unstable#3
registers the joystick rings LED with a per-device name
("<hid dev name>:rgb:joystick_rings", e.g.
"0003:1C4F:0002.0003:rgb:joystick_rings") rather than the fixed
"ayaneo:rgb:joystick_rings", following review feedback there. sys_name
is matched with glob_match(), so a wildcard prefix covers both the old
fixed name and the new per-device one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant