diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2017-02-12 12:33:22 +0100 |
|---|---|---|
| committer | Hans de Goede <hdegoede@redhat.com> | 2017-02-12 12:43:23 +0100 |
| commit | 57bb707d48131f4daad2b1b746eab586eb66b4f3 (patch) | |
| tree | b5bffb062f6b8d223a31992a72cf49785a4be75a /hwdb | |
| parent | 6818c54ca6663c008fad77d2677c61758c7215f5 (diff) | |
rules: Add extended evdev/input match rules for event nodes with the same name
Sometimes a system may have 2 input event nodes with the same name where
we only want to apply keyboard hwdb rules to 1 of the 2 devices.
This problem happens e.g. on devices where the soc_button_array driver is
used (e.g. intel atom based tablets) which registers 2 event nodes with
the name "gpio-keys".
This commit adds a new extended match rule which extends the match to also
check $attr{phys} and $attr{capabilities/ev}, allowing to differentiate
between devices with an identical name.
Suggested-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Diffstat (limited to 'hwdb')
| -rw-r--r-- | hwdb/60-keyboard.hwdb | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/hwdb/60-keyboard.hwdb b/hwdb/60-keyboard.hwdb index c8452f47d0..036f2cc7cc 100644 --- a/hwdb/60-keyboard.hwdb +++ b/hwdb/60-keyboard.hwdb @@ -32,6 +32,15 @@ # driver, <vendor> is the firmware-provided string exported # by the kernel DMI modalias, see /sys/class/dmi/id/modalias # +# - Extended input driver device name, properties and DMI data match: +# evdev:name:<input device name>:phys:<phys>:ev:<ev>:dmi:bvn*:bvr*:bd*:svn<vendor>:pn* +# <input device name> is the name device specified by the +# driver, <phys> is the physical-device-path, "cat +# /sys/class/input/input?/phys", <ev> is the event bitmask, "cat +# /sys/class/input/input?/capabilities/ev" and <vendor> is the +# firmware-provided string exported by the kernel DMI modalias, +# see /sys/class/dmi/id/modalias +# # Scan codes are specified as: # KEYBOARD_KEY_<hex scan code>=<key code identifier> # The scan code should be expressed in hex lowercase. The key codes |