diff options
| author | Ioan-Adrian Ratiu <adi@adirat.com> | 2016-09-27 20:41:38 +0200 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2016-10-10 10:52:00 +0200 |
| commit | e15944099870f374ca7efc62f98cf23ba272ef43 (patch) | |
| tree | 143de2a9a03a73bf91b6fd29ad0e8c157d92b819 /drivers/ras | |
| parent | HID: hid-led: fix issue with transfer buffer not being dma capable (diff) | |
| download | linux-e15944099870f374ca7efc62f98cf23ba272ef43.tar.xz linux-e15944099870f374ca7efc62f98cf23ba272ef43.zip | |
HID: hid-dr: add input mapping for axis selection
Commit 79346d620e9d ("HID: input: force generic axis to be mapped to their
user space axis") made mapping generic axes to their userspace equivalents
mandatory and some lower end gamepads which were depending on the previous
behaviour suffered severe regressions because they were reusing axes and
expecting hid-input to multiplex their map to the respective userspace axis
by always searching for and using the next available axis.
One solution is to add a hid quirk for this type of "previous" behaviour in
hid-input to bypass the new axes policy in favour of the old one, but since
only one hardware vendor seems to be affected negatively we're better off
making and exception and mapping in the driver for now; if more vendors or
drivers turn out to experience the problem we should reconsider the quirk
solution.
Signed-off-by: Ioan-Adrian Ratiu <adi@adirat.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/ras')
0 files changed, 0 insertions, 0 deletions