summaryrefslogtreecommitdiff
path: root/drivers/hid/hid-debug.c
diff options
context:
space:
mode:
authorChase Douglas <chase.douglas@ubuntu.com>2010-08-30 13:27:45 -0400
committerJiri Kosina <jkosina@suse.cz>2010-09-08 12:04:03 +0200
commit1debfb3315d95ab5ce328e307bd115b4400685fb (patch)
treea95b278e7a86d1a2688ec67476558fcac744b2bd /drivers/hid/hid-debug.c
parent816651a7d4a32664261e5f9f88ad0d558faed4cc (diff)
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>
Diffstat (limited to 'drivers/hid/hid-debug.c')
-rw-r--r--drivers/hid/hid-debug.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/hid/hid-debug.c b/drivers/hid/hid-debug.c
index 850d02a7a925..adff4efdc169 100644
--- a/drivers/hid/hid-debug.c
+++ b/drivers/hid/hid-debug.c
@@ -570,6 +570,8 @@ void hid_debug_event(struct hid_device *hdev, char *buf)
buf[i];
list->tail = (list->tail + i) % HID_DEBUG_BUFSIZE;
}
+
+ wake_up_interruptible(&hdev->debug_wait);
}
EXPORT_SYMBOL_GPL(hid_debug_event);