Re: [RFC 3/8] HID: input: generic hidinput_input_event handler

2013-07-31 Thread Jiri Kosina
On Wed, 17 Jul 2013, David Herrmann wrote: + + /* led_work is spawned by input_dev callbacks, but doesn't access the +* parent input_dev at all. Once all input devices are removed, we +* know that led_work will never get restarted, so we can cancel it +*

Re: [RFC 3/8] HID: input: generic hidinput_input_event handler

2013-07-17 Thread David Herrmann
Hi On Tue, Jul 16, 2013 at 10:04 AM, Benjamin Tissoires benjamin.tissoi...@gmail.com wrote: On Mon, Jul 15, 2013 at 7:10 PM, David Herrmann dh.herrm...@gmail.com wrote: The hidinput_input_event() callback converts input events written from userspace into HID reports and sends them to the

Re: [RFC 3/8] HID: input: generic hidinput_input_event handler

2013-07-16 Thread Benjamin Tissoires
On Mon, Jul 15, 2013 at 7:10 PM, David Herrmann dh.herrm...@gmail.com wrote: 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

[RFC 3/8] HID: input: generic hidinput_input_event handler

2013-07-15 Thread David Herrmann
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