linux.git/drivers/input/joystick, branch v4.14-rc4

Merge branch 'next' into for-linus

2017-09-15T16:52:21+00:00

Prepare second round of input updates for 4.14 merge window.

Input: xpad - validate USB endpoint type during probe

2017-09-12T18:45:59+00:00

We should only see devices with interrupt endpoints. Ignore any other
endpoints that we find, so we don't send try to send them interrupt URBs
and trigger a WARN down in the USB stack.

Reported-by: Andrey Konovalov 
Tested-by: Andrey Konovalov 
Cc:  # c01b5e7464f0 Input: xpad - don't depend on endpoint order
Signed-off-by: Cameron Gutman 
Signed-off-by: Dmitry Torokhov

Input: adi - make array seq static, reduces object code size

2017-09-04T16:28:15+00:00

Don't populate the array seq on the stack, instead make it static.
Makes the object code smaller by over 170 bytes:

Before:
   text	   data	    bss	    dec	    hex	filename
  13227	   3232	      0	  16459	   404b	drivers/input/joystick/adi.o

After:
   text	   data	    bss	    dec	    hex	filename
  12957	   3328	      0	  16285	   3f9d	drivers/input/joystick/adi.o

Signed-off-by: Colin Ian King 
Signed-off-by: Dmitry Torokhov

Merge branch 'next' into for-linus

2017-09-04T16:22:54+00:00

Prepare input updates for 4.14 merge window.

Input: xpad - fix PowerA init quirk for some gamepad models

2017-08-31T18:55:11+00:00

The PowerA gamepad initialization quirk worked with the PowerA
wired gamepad I had around (0x24c6:0x543a), but a user reported [0]
that it didn't work for him, even though our gamepads shared the
same vendor and product IDs.

When I initially implemented the PowerA quirk, I wanted to avoid
actually triggering the rumble action during init. My tests showed
that my gamepad would work correctly even if it received a rumble
of 0 intensity, so that's what I went with.

Unfortunately, this apparently isn't true for all models (perhaps
a firmware difference?). This non-working gamepad seems to require
the real magic rumble packet that the Microsoft driver sends, which
actually vibrates the gamepad. To counteract this effect, I still
send the old zero-rumble PowerA quirk packet which cancels the
rumble effect before the motors can spin up enough to vibrate.

[0]: https://github.com/paroj/xpad/issues/48#issuecomment-313904867

Reported-by: Kyle Beauchamp 
Tested-by: Kyle Beauchamp 
Fixes: 81093c9848a7 ("Input: xpad - support some quirky Xbox One pads")
Cc: stable@vger.kernel.org # v4.12
Signed-off-by: Cameron Gutman 
Signed-off-by: Dmitry Torokhov

Input: zhenhua - constify serio_device_id

2017-08-19T00:14:17+00:00

serio_device_id are not supposed to change at runtime. All functions
working with serio_device_id provided by  work with
const serio_device_id. So mark the non-const structs as const.

Signed-off-by: Arvind Yadav 
Signed-off-by: Dmitry Torokhov

Input: warrior - constify serio_device_id

2017-08-19T00:14:16+00:00

serio_device_id are not supposed to change at runtime. All functions
working with serio_device_id provided by  work with
const serio_device_id. So mark the non-const structs as const.

Signed-off-by: Arvind Yadav 
Signed-off-by: Dmitry Torokhov

Input: twidjoy - constify serio_device_id

2017-08-19T00:14:15+00:00

serio_device_id are not supposed to change at runtime. All functions
working with serio_device_id provided by  work with
const serio_device_id. So mark the non-const structs as const.

Signed-off-by: Arvind Yadav 
Signed-off-by: Dmitry Torokhov

Input: stinger - constify serio_device_id

2017-08-19T00:14:14+00:00

serio_device_id are not supposed to change at runtime. All functions
working with serio_device_id provided by  work with
const serio_device_id. So mark the non-const structs as const.

Signed-off-by: Arvind Yadav 
Signed-off-by: Dmitry Torokhov

Input: spaceorb - constify serio_device_id

2017-08-19T00:14:12+00:00

serio_device_id are not supposed to change at runtime. All functions
working with serio_device_id provided by  work with
const serio_device_id. So mark the non-const structs as const.

Signed-off-by: Arvind Yadav 
Signed-off-by: Dmitry Torokhov