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

Note that libevdev_free() does not close the fd

2015-06-29T02:23:34+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

doc: add the prefixing * to all @code doxygen sections

2014-11-17T23:05:16+00:00

These were removed in (7da329b) because for some reason they got copied into
the output. That was either a buggy doxygen or just some other problem. Add
them again, makes it much easier to read the header file.

Signed-off-by: Peter Hutterer

doc: fix slightly confusing code/type comments

2014-08-27T21:54:22+00:00

Signed-off-by: Ran Benita 
Signed-off-by: Peter Hutterer

Add some minimal documentation about static linking

2014-08-25T00:12:37+00:00

I can't recommend it, but I can't stop people from doing it, so at least
document the ground rules.

Signed-off-by: Peter Hutterer

Add libevdev_property_from_name()

2014-08-19T22:43:15+00:00

12717d79 "Add libevdev_event_type/code_from_name() resolvers" added the
lookup functions for types and codes, this commit adds the missing ones for
input properties.

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

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

Mark the log functions with the printf format attribute

2014-06-05T05:15:12+00:00

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

Document that we need uinput in the kernel for the test suite

2014-05-22T05:07:59+00:00

Signed-off-by: Peter Hutterer

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