summaryrefslogtreecommitdiffstats
path: root/drivers/hid/uhid.c
diff options
context:
space:
mode:
authorDavid Herrmann <dh.herrmann@gmail.com>2013-07-15 19:10:12 +0200
committerJiri Kosina <jkosina@suse.cz>2013-07-31 11:02:02 +0200
commit50c9d75b6f01a337aab728511bc1d2a0a3d7b800 (patch)
tree87f3ef456925f5bb0b65222a09b47a47fbc1d9c5 /drivers/hid/uhid.c
parentHID: uhid: use generic hidinput_input_event() (diff)
downloadlinux-50c9d75b6f01a337aab728511bc1d2a0a3d7b800.tar.xz
linux-50c9d75b6f01a337aab728511bc1d2a0a3d7b800.zip
HID: input: generic hidinput_input_event handler
The hidinput_input_event() callback converts input events written from userspace into HID reports and sends them to the device. We currently implement this in every HID transport driver, even though most of them do the same. This provides a generic hidinput_input_event() implementation which is mostly copied from usbhid. It uses a delayed worker to allow multiple LED events to be collected into a single output event. We use the custom ->request() transport driver callback to allow drivers to adjust the outgoing report and handle the request asynchronously. If no custom ->request() callback is available, we fall back to the generic raw output report handler (which is synchronous). Drivers can still provide custom hidinput_input_event() handlers (see logitech-dj) if the generic implementation doesn't fit their needs. Signed-off-by: David Herrmann <dh.herrmann@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/hid/uhid.c')
0 files changed, 0 insertions, 0 deletions