linux-toradex.git/include/linux/hid.h, branch v2.6.29

headers_check fix: linux/hid.h

2009-01-30T18:20:37+00:00

fix the following 'make headers_check' warnings:

  usr/include/linux/hid.h:69: extern's make no sense in userspace
  usr/include/linux/hid.h:76: extern's make no sense in userspace

Signed-off-by: Jaswinder Singh Rajput

HID: avoid sparse warning in HID_COMPAT_LOAD_DRIVER

2009-01-04T00:00:53+00:00

Impact: include a prototype for the exported function in the macro

Fix about 20 of this warnings:

  drivers/hid/hid-a4tech.c:162:1: warning: symbol 'hid_compat_a4tech' was not declared. Should it be static?

Signed-off-by: Hannes Eder 
Signed-off-by: Jiri Kosina

HID: add dynids facility

2009-01-04T00:00:52+00:00

Allow adding new devices to the hid drivers on the fly without
a need of kernel recompilation.

Now, one can test a driver e.g. by:
echo 0003:045E:00F0.0003 > ../generic-usb/unbind
echo 0003 045E 00F0 > new_id
from some driver subdir.

Signed-off-by: Jiri Slaby 
Signed-off-by: Jiri Kosina

HID: move usbhid flags to usbhid.h

2009-01-04T00:00:51+00:00

Move usbhid specific flags from global hid.h into local usbhid.h.

Signed-off-by: Jiri Slaby 
Signed-off-by: Jiri Kosina

HID: fix oops during suspend of unbound HID devices

2008-10-27T14:06:01+00:00

Usbhid structure is allocated on start invoked only from probe
of some driver. When there is no driver, the structure is null
and causes null-dereference oopses.

Fix it by allocating the structure on probe and disconnect of
the device itself. Also make sure we won't race between start
and resume or stop and suspend respectively.

References: http://bugzilla.kernel.org/show_bug.cgi?id=11827

Signed-off-by: Jiri Slaby 
Cc: Johannes Berg 
Cc: Andreas Schwab 
Signed-off-by: Jiri Kosina

HID: add hid_type to general hid struct

2008-10-22T12:45:11+00:00

Add type to the hid structure to distinguish to which device type
(now only mouse) we are talking to. Needed for per device type ignore
list support.

Note: this patch leaves the type as unknown for bluetooth devices,
there is not support for this in the hidp code.

Signed-off-by: Jiri Slaby 
Signed-off-by: Jiri Kosina

HID: fix a lockup regression when using force feedback on a PID device

2008-10-14T21:51:02+00:00

Commit 8006479c9b75fb6594a7b746af3d7f1fbb68f18f introduced a spinlock in
input_dev->event_lock, which is locked when handling input events.
However, the hid-pidff driver sleeps when handling events as it waits for
reports being sent to the device before changing the report contents
again.
This causes a system lockup when trying to use force feedback with a PID
device, a regression introduced in 2.6.24 and 2.6.23.15.

Fix it by extracting the raw report data from struct hid_report
immediately when hid_submit_report() is called, therefore allowing
drivers to change the contents of struct hid_report immediately without
affecting the already-queued transfer.

In hid-pidff, re-add the removed usbhid_wait_io() to
pidff_erase_effect() instead, to prevent a full report queue from causing
the submission to fail, thus not freeing up device memory.
pidff_erase_effect() is not called while dev->event_lock is held.

Signed-off-by: Anssi Hannula 
Signed-off-by: Jiri Kosina

HID: remove hid-ff

2008-10-14T21:51:01+00:00

hid-ff.c now calls only pidff (generic driver), the special ones are now
in separate drivers. Invoke pidff on all non-special directly.

Signed-off-by: Jiri Slaby 
Signed-off-by: Jiri Kosina

HID: move zeroplus FF processing

2008-10-14T21:51:01+00:00

Signed-off-by: Jiri Slaby 
Signed-off-by: Jiri Kosina

HID: move thrustmaster FF processing

2008-10-14T21:51:00+00:00

Signed-off-by: Jiri Slaby 
Signed-off-by: Jiri Kosina