delta/libevdev.git/libevdev/libevdev.c, branch libevdev-1.4.5

Fix invalid absinfo range values reported by certain mtk soc

2015-08-24T06:26:00+00:00

This change will only affect certain touch screens, for which the driver
integration code does not provide meaningful values for the allowed range
of ABS_MT_TRACKING_IDs. The reported range [0, 0] will be overwritten with
[-1, 0xFFFF]

Signed-off-by: Andreas Pokorny 

[Changed from INT_MAX to 0xFFFF to match the kernel, add device name to log
message]

Signed-off-by: Peter Hutterer

Accept LIBEVDEV_READ_FLAG_BLOCKING as valid flag

2015-04-08T02:48:43+00:00

https://bugs.freedesktop.org/show_bug.cgi?id=89798

Signed-off-by: Peter Hutterer 
Reviewed-by: Benjamin Tissoires

ABS_MAX counts as MT axis for the event queue

2015-03-23T04:02:15+00:00

Signed-off-by: Peter Hutterer

cosmetic: fix a comment

2015-03-23T04:01:58+00:00

Signed-off-by: Peter Hutterer

cosmetic: fix a couple of duplicate/missing empty lines

2015-03-03T22:41:33+00:00

Signed-off-by: Peter Hutterer

Remove superfluous linebreak in an error message

2014-11-17T22:17:56+00:00

Signed-off-by: Peter Hutterer

Fix a confusing comment

2014-11-17T01:26:29+00:00

Signed-off-by: Peter Hutterer

Rename symbols leaking from static library to avoid name clashes

2014-08-20T06:43:58+00:00

The static library currently leaks log_msg and log_priority. Both are too
generic, so rename them, with a leading underscore to hint they're supposed to
be private.

Signed-off-by: Peter Hutterer

Add per-device log handlers

2014-06-05T05:16:06+00:00

The global log handler isn't a good choice for a low-level library. In the
caser of the X server, both evdev and synaptics are now using the libevdev but
are loaded from the same server process. Thus, there's only one log handler,
but evdev and synaptics don't talk to each other (a bit childish, I know).

Add a per-device log handler that overrides the global log handler, and fall
back to the global log handler if no device log handler is set. The log
macros take care of that automatically, especially as we can't do per-device
log handlers for the uinput code.

Note that we use the same struct for the global and device logging, so in each
instance one of the two function pointers is NULL. Suicide triggers are in
place in case we mess that up.

This also makes libevdev_new_from_fd() a bit less useful since we can't set
the log handler beforehand.

Signed-off-by: Peter Hutterer 
Reviewed-by: David Herrmann

Drain all events before synchronizing after SYN_DROPPED

2014-04-23T22:17:01+00:00

The kernel ring buffer drops all events on SYN_DROPPED, but then continues to
fill up again. So by the time we read the events, the kernel's client buffer is
essentially like this:
  SYN_DROPPED, ev1, ev2, ev3, ...., evN

The kernel's device state represents the device after evN, and that is what
the ioctls return. For EV_KEY, EV_SND, EV_LED and EV_SW the kernel removes
potential duplicates from the client buffer [1], it doesn't do so for EV_ABS.

So we can't actually sync while there are events on the wire because the
events represent an earlier state. So simply discard all events in the kernel
buffer, synchronize, and then start processing again. We lose some granularity
but at least the events are correct.

[1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/input/evdev.c?id=483180281f0ac60d1138710eb21f4b9961901294

Signed-off-by: Peter Hutterer