summaryrefslogtreecommitdiff
path: root/drivers/input/keyboard/omap4-keypad.c
diff options
context:
space:
mode:
authorCameron Gutman <aicommander@gmail.com>2017-04-10 20:43:04 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2017-04-10 20:45:14 -0700
commit81093c9848a781b85163d06de92ef8f84528cf6a (patch)
tree4a98d49a601cf21fa0334e02114f3ca34bac382e /drivers/input/keyboard/omap4-keypad.c
parentc5cb37d0d62c58320f0a86777b738fb28272245b (diff)
downloadlwn-81093c9848a781b85163d06de92ef8f84528cf6a.tar.gz
lwn-81093c9848a781b85163d06de92ef8f84528cf6a.zip
Input: xpad - support some quirky Xbox One pads
There are several quirky Xbox One pads that depend on initialization packets that the Microsoft pads don't require. To deal with these, I've added a mechanism for issuing device-specific initialization packets using a VID/PID-based quirks list. For the initial set of init quirks, I have added quirk handling from Valve's Steam Link xpad driver[0] and the 360Controller project[1] for macOS to enable some new pads to work properly. This should enable full functionality on the following quirky pads: 0x0e6f:0x0165 - Titanfall 2 gamepad (previously fully non-functional) 0x0f0d:0x0067 - Hori Horipad (analog sticks previously non-functional) 0x24c6:0x541a - PowerA Xbox One pad (previously fully non-functional) 0x24c6:0x542a - PowerA Xbox One pad (previously fully non-functional) 0x24c6:0x543a - PowerA Xbox One pad (previously fully non-functional) [0]: https://github.com/ValveSoftware/steamlink-sdk/blob/master/kernel/drivers/input/joystick/xpad.c [1]: https://github.com/360Controller/360Controller Signed-off-by: Cameron Gutman <aicommander@gmail.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input/keyboard/omap4-keypad.c')
0 files changed, 0 insertions, 0 deletions