mirror of
https://github.com/systemd/systemd.git
synced 2025-02-03 17:47:28 +03:00
1642b7b3ac
The function `builtin-input_id` incorrectly identifies the ASRock LED Controller as an input device due to the presence of buttons and axis. To fix this we add a new rule in `hwdb.d/60-input-id.hwdb`. The properties have been set to empty instead of `0` because some programs might check if the value is set at all instead of checking its value, as discussed in #32773. The device has no real keys. The devices is controlled by i2c interface and some settings in UEFI, and it provides an header to connect LED strips and similar devices. I suppose it's possible that ASRock intended to connect devices with buttons for controlling LEDs to it, but: (i) the controller itself does not have key, (ii) to my knowledge no such device exists. So I think we can unset that property as well. On a sidenote, unsetting those properties does not affect the i2c interface, OpenRGB still interacts normally with the device. Fixes #32773.
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.