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

Add libevdev_event_value_get_name() to resolve ABS_MT_TOOL_TYPE values

2018-07-09T01:57:57+00:00

ABS_MT_TOOL_TYPE values are an enum, not a numerical value like all other
axes. So let's allow converting those values to string.

Fixes https://gitlab.freedesktop.org/libevdev/libevdev/issues/1

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

Update struct input_event

2018-04-12T05:23:22+00:00

The struct input_event is not y2038 safe.
Update the struct according to the kernel patch:
https://lkml.org/lkml/2018/1/6/324

Signed-off-by: Deepa Dinamani 
Reviewed-by: Peter Hutterer 
Signed-off-by: Peter Hutterer

When changing the fd, reset our grab state to ungrabbed

2017-12-13T00:01:58+00:00

Previously, calling grabbing a device after changing the fd was a no-op
because libevdev's grab state didn't match the fd:

libevdev_grab(LIBEVDEV_GRAB);
  .. fd is grabbed
  .. internal state is 'grabbed'
libevdev_change_fd();
  .. new fd is ungrabbed
  .. internal state is 'grabbed'
libevdev_grab(LIBEVDEV_GRAB);
  .. argument matches internal state and we exit without grabbing the device

Signed-off-by: Peter Hutterer

Fix an indentation issues

2017-04-24T23:27:16+00:00

Signed-off-by: Peter Hutterer

Don't bother sanitizing disabled event codes

2016-08-17T07:43:32+00:00

Filter them immediately instead of passing them on and relying on the actual
event handling code to filter them.

Reproducer: if EV_ABS is disabled on an Apple MagicMouse we still get events
passed into sanitize_event(). But the code handling EV_ABS events doesn't
update the state, so we end up complaining about double tracking IDs, even
though that is not actually correct.

https://bugzilla.redhat.com/show_bug.cgi?id=1361325

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

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