ABS_RESERVED was added to 4.20 for that reason, to keep that event code
reserved so we can't use it for anything else (and thus mess up the fake MT
detection).
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
dev->fd = fd;
- /* devices with ABS_MT_SLOT - 1 aren't MT devices,
+ /* devices with ABS_RESERVED aren't MT devices,
see the documentation for multitouch-related
functions for more details */
- if (!libevdev_has_event_code(dev, EV_ABS, ABS_MT_SLOT - 1) &&
+ if (!libevdev_has_event_code(dev, EV_ABS, ABS_RESERVED) &&
libevdev_has_event_code(dev, EV_ABS, ABS_MT_SLOT)) {
const struct input_absinfo *abs_info;
* meaning, matching the axis names in linux/input.h. Some devices merely
* export a number of axes beyond the available axis list. For those
* devices, the multitouch information is invalid. Specifically, if a device
- * provides the ABS_MT_SLOT axis AND also the (ABS_MT_SLOT - 1) axis, the
+ * provides the ABS_MT_SLOT axis AND also the ABS_RESERVED axis, the
* device is not treated as multitouch device. No slot information is
* available and the ABS_MT axis range for these devices is treated as all
* other EV_ABS axes.