summaryrefslogtreecommitdiffstats
path: root/drivers/hid/hid-gfrm.c
diff options
context:
space:
mode:
authorBenjamin Tissoires <benjamin.tissoires@redhat.com>2017-12-08 15:28:18 +0100
committerJiri Kosina <jkosina@suse.cz>2018-04-17 14:08:54 +0200
commit190d7f02ce8ef6774a69d3ec18c288c8a9601a4e (patch)
tree4953de950ebd7fa3aaf9cd4e4c94fc1c34aa59f3 /drivers/hid/hid-gfrm.c
parente8403b493fd5180e351ca67eb66406d95dadcd0b (diff)
downloadlinux-190d7f02ce8ef6774a69d3ec18c288c8a9601a4e.tar.bz2
HID: input: do not increment usages when a duplicate is found
This is something that bothered us from a long time. When hid-input doesn't know how to map a usage, it uses *_MISC. But there is something else which increments the usage if the evdev code is already used. This leads to few issues: - some devices may have their ABS_X mapped to ABS_Y if they export a bad set of usages (see the DragonRise joysticks IIRC -> fixed in a specific HID driver) - *_MISC + N might (will) conflict with other defined axes (my Logitech H800 exports some multitouch axes because of that) - this prevents to freely add some new evdev usages, because "hey, my headset will now report ABS_COFFEE, and it's not coffee capable". So let's try to kill this nonsense, and hope we won't break too many devices. I my headset case, the ABS_MISC axes are created because of some proprietary usages, so we might not break that many devices. For backward compatibility, a quirk HID_QUIRK_INCREMENT_USAGE_ON_DUPLICATE is created and can be applied to any device that needs this behavior. Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Acked-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/hid/hid-gfrm.c')
0 files changed, 0 insertions, 0 deletions