summaryrefslogtreecommitdiff
path: root/libevdev/libevdev.c
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2013-06-28 12:51:16 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2013-06-28 12:51:16 +1000
commit6482f9ad2a5d356a902e36fa8b01c4a7370ee0b9 (patch)
tree9a5eff82ca490d3badbb44f0dcf39fd9e79eacba /libevdev/libevdev.c
parent9ddd477f624bb6b1cf60663c9b682f113b877996 (diff)
downloadlibevdev-6482f9ad2a5d356a902e36fa8b01c4a7370ee0b9.tar.gz
Add a FIXME to log a warning message
When a sync is complete and the first event is a SYN_DROPPED again, we have a problem. Log that so that the process can print a warning. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'libevdev/libevdev.c')
-rw-r--r--libevdev/libevdev.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/libevdev/libevdev.c b/libevdev/libevdev.c
index 5dd6bdb..fd3d3c7 100644
--- a/libevdev/libevdev.c
+++ b/libevdev/libevdev.c
@@ -552,6 +552,8 @@ int libevdev_next_event(struct libevdev *dev, unsigned int flags, struct input_e
* event in the queue from the previous read.
*/
+ /* FIXME: if the first event after syncing is a SYN_DROPPED, log this */
+
/* Always read in some more events. Best case this smoothes over a potential SYN_DROPPED,
worst case we don't read fast enough and end up with SYN_DROPPED anyway */
rc = read_more_events(dev);