linux-toradex.git/drivers/hid/hid-sony.c, branch v4.0.2

HID: sony: fix uninitialized per-controller spinlock

2015-02-23T12:01:15+00:00

Per-controller spinlock needs to be properly initialized during device probe.

[jkosina@suse.cz: massage changelog]
[jkosina@suse.cz: drop hunk that has already been applied by previous
 patch]
Signed-off-by: Frank Praznik 
Signed-off-by: Jiri Kosina

HID: sony: initialize sony_dev_list_lock properly

2015-02-23T10:15:44+00:00

sony_dev_list_lock spinlock (which was introduced in d2d782fccee ("HID: sony:
Prevent duplicate controller connections") is not being initialized properly.
Fix that.

Reported-by: Pavel Machek 
Signed-off-by: Jiri Kosina

HID: sony: Fix a WARNING shown when rmmod-ing the driver

2015-02-18T20:18:22+00:00

ida_destroy() must be called _after_ all the devices have been
unregistered; otherwise, when calling "rmmod hid_sony" with devices
still plugged in, the following warning would show up because of calls
to ida_simple_remove() on a destroyed ID allocator:

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5509 at lib/idr.c:1052 ida_simple_remove+0x26/0x50()
ida_remove called for id=0 which is not allocated.
Modules linked in: ...
CPU: 0 PID: 5509 Comm: rmmod Not tainted 3.19.0-rc6-ao2 #35
Hardware name: System manufacturer System Product Name/M2N-MX SE, BIOS 0501    03/20/2008
 0000000000000000 ffffffff8176320d ffffffff815b3a88 ffff880036f7fdd8
 ffffffff8106ce01 0000000000000000 ffffffffa07658e0 0000000000000246
 ffff88005077d8b8 ffff88005077d8d0 ffffffff8106ce7a ffffffff81763260
Call Trace:
 [] ? dump_stack+0x40/0x50
 [] ? warn_slowpath_common+0x81/0xb0
 [] ? warn_slowpath_fmt+0x4a/0x50
 [] ? ida_simple_remove+0x26/0x50
 [] ? sony_remove+0x58/0xe0 [hid_sony]
 [] ? hid_device_remove+0x65/0xd0 [hid]
 [] ? __device_release_driver+0x7e/0x100
 [] ? driver_detach+0xa0/0xb0
 [] ? bus_remove_driver+0x55/0xe0
 [] ? hid_unregister_driver+0x2f/0xa0 [hid]
 [] ? SyS_delete_module+0x1bf/0x270
 [] ? do_notify_resume+0x69/0xa0
 [] ? system_call_fastpath+0x16/0x1b
---[ end trace bc794b3d22c30ede ]---

Signed-off-by: Antonio Ospite 
Acked-by: Frank Praznik 
Signed-off-by: Jiri Kosina

HID: sony: Add support for the third-party SMK PS3 Bluetooth Remote

2014-11-20T14:05:27+00:00

Add vid/pid for the SMK branded third-party PS3 Bluetooth remote and enable
support in the hid-sony driver.

Signed-off-by: Frank Praznik 
Signed-off-by: Jiri Kosina

HID: sony: Use kernel allocated buffers for HID reports

2014-11-19T09:23:54+00:00

Replace stack buffers with kernel allocated buffers for sending
and receiving HID reports to prevent issues with DMA transfers
on certain hardware.

Output report buffers are allocated at initialization time to avoid
excessive calls to kmalloc and kfree.

Link: https://bugzilla.kernel.org/show_bug.cgi?id=87991
Signed-off-by: Frank Praznik 
Reviewed-by: Dmitry Torokhov 
Signed-off-by: Jiri Kosina

HID: sony: Update the DualShock 4 touchpad resolution

2014-09-25T09:23:26+00:00

The DualShock 4 touchpad has been measured to have a resolution of
44.86 dots/mm which equates to 1920x942.

Signed-off-by: Frank Praznik 
Signed-off-by: Jiri Kosina

HID: sony: Set touchpad bits in the input_configured callback

2014-09-22T14:04:21+00:00

Set the DualShock4 touchpad bits in the input_configured callback
so that they are registered properly for any input devices created
during hid_hw_start.

Signed-off-by: Frank Praznik 
Signed-off-by: Jiri Kosina

HID: sony: Update file header and correct comments

2014-09-15T11:34:53+00:00

Update the file header and correct an outdated comment block.

Signed-off-by: Frank Praznik 
Signed-off-by: Jiri Kosina

HID: sony: Corrections for the DualShock 4 HID descriptor

2014-09-15T11:34:53+00:00

Fix a few minor issues in the HID descriptor:
 - A 6 bit entry had a logical maximum of 255 when the largest it can be is 63.
 - A logical max value was incorrectly being set to -1 instead of 255.
 - Set the min/max of the gyroscopes to -8192/8191 as that is the range of
   values which represent the true controller orientation.  Any values beyond
   those extents are just noise.

Signed-off-by: Frank Praznik 
Signed-off-by: Jiri Kosina

HID: sony: Set the Sixaxis cable state correctly

2014-09-01T09:20:52+00:00

Bit 3 in byte 31 of the Sixaxis report indicates whether the battery is
charging or not charging as opposed to whether or not the cable is plugged in.
As a result, when connected via USB and fully charged, the power_supply status
is wrongly reported as 'Discharging' instead of 'Full'.

Use the battery level value to set the cable state so that the power status
is reported correctly as that seems to be the only reliable way to determine the
cable status on the Sixaxis.

Signed-off-by: Frank Praznik 
Signed-off-by: Jiri Kosina