fdo-mirrors/libevdev
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/libevdev/libevdev.git synced 2026-05-09 08:18:07 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Split the SYN_DROPPED page into a few sections

Browse source 
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Peter Hutterer 2014-04-07 14:26:31 +10:00
parent be87068a9b
commit c44e510acd
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
libevdev/libevdev.h
View file

@ -162,6 +162,9 @@ extern "C" {
* *
* This page describes how libevdev handles SYN_DROPPED events. * This page describes how libevdev handles SYN_DROPPED events.
* *
* Receiving SYN_DROPPED events
* ============================
*
* The kernel sends evdev events separated by an event of type EV_SYN and * The kernel sends evdev events separated by an event of type EV_SYN and
* code SYN_REPORT. Such an event marks the end of a frame of hardware * code SYN_REPORT. Such an event marks the end of a frame of hardware
* events. The number of events between SYN_REPORT events is arbitrary and * events. The number of events between SYN_REPORT events is arbitrary and
@ -209,6 +212,9 @@ extern "C" {
* * discard all events until including the next SYN_REPORT * * discard all events until including the next SYN_REPORT
* These event are part of incomplete event frames. * These event are part of incomplete event frames.
* *
* Synchronizing the state of the device
* =====================================
*
* The handling of the device after a SYN_DROPPED depends on the available * The handling of the device after a SYN_DROPPED depends on the available
* event codes. For all event codes of type EV_REL, no handling is * event codes. For all event codes of type EV_REL, no handling is
* necessary, there is no state attached. For all event codes of type * necessary, there is no state attached. For all event codes of type
@ -271,6 +277,9 @@ extern "C" {
* Note the terminating ABS_MT_SLOT event, this indicates that the kernel * Note the terminating ABS_MT_SLOT event, this indicates that the kernel
* currently has slot 1 active. * currently has slot 1 active.
* *
* Synchronizing ABS_MT_TRACKING_ID
* ================================
*
* The event code ABS_MT_TRACKING_ID is used to denote the start and end of * The event code ABS_MT_TRACKING_ID is used to denote the start and end of
* a touch point within a slot. An ABS_MT_TRACKING_ID of zero or greater * a touch point within a slot. An ABS_MT_TRACKING_ID of zero or greater
* denotes the start of a touchpoint, an ABS_MT_TRACKING_ID of -1 denotes * denotes the start of a touchpoint, an ABS_MT_TRACKING_ID of -1 denotes