Dirga Yuza
f2361469e4
This fixes an incomplete mapping introduced in PR #39769 for the Acer Nitro 5 AN515-58. The previous PR mapped the physical keyboard backlight keys (scancodes `0xef` and `0xf0`) to `kbdillumup` and `kbdillumdown` to prevent them from dropping screen brightness. However, the embedded controller on this Acer model only emits "make" (press) scancodes and fails to emit "break" (release) scancodes for these specific keys. Without a release event, the input subsystem registers the keys as continously held down (auto-repeat). In desktop environments like KDE Plasma, pressing the key once causes the brightness UI slider to get stuck in an infinite adjustment loop. This issue is previously unnoticed as this model did not expose any keyboard backlight control. The fix is done by prepending the `!` (force-release) flag to the keycodes. This instructs `evdev` to synthesize a key release event. The fix is verified locally on an Acer Nitro AN515-58. `evtest` now correctly reports `value 1` immediately followed by `value` 0, and KDE Plasma brightness OSD no longer gets stuck. Signed-off-by: Dirga Yuza <dirgayuza123@gmail.com>
Files in this directory specify a description of hardware devices, in the form of mappings from modalias-like keys (which identify specific hardware devices) to udev properties. Files in this directory are not read by udev directly. Instead, man:systemd-hwdb(8) compiles them into a binary database. See man:hwdb(7) for an overview of the configuration file format, and man:systemd-udevd.service(8) for a description of the udev daemon. Use 'systemd-analyze cat-config udev/hwdb.d' to display the effective config.