| commit | 1debfb3315d95ab5ce328e307bd115b4400685fb | |
| author | Chase Douglas <chase.douglas@ubuntu.com> | |
| Mon, 30 Aug 2010 17:27:45 +0000 (30 13:27 -0400) | ||
| committer | Jiri Kosina <jkosina@suse.cz> | |
| Wed, 8 Sep 2010 10:04:03 +0000 (8 12:04 +0200) | ||
| tree | a95b278e7a86d1a2688ec67476558fcac744b2bd | treesnapshot (tar.gz zip) |
| parent | 816651a7d4a32664261e5f9f88ad0d558faed4cc | commitdiff |
HID: debugfs: wake up reading tasks upon event
Some devices poke the hid core in a way that causes hid_debug_event to
be called, while never calling hid_dump_input. Without this wakeup
addition, tasks reading for hid events through debugfs may never see any
events. It may be that a well written driver doesn't cause this, but
then what's the point of debugfs?
Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Some devices poke the hid core in a way that causes hid_debug_event to
be called, while never calling hid_dump_input. Without this wakeup
addition, tasks reading for hid events through debugfs may never see any
events. It may be that a well written driver doesn't cause this, but
then what's the point of debugfs?
Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
| drivers/hid/hid-debug.c | diffblobblamehistory |