Split the SYN_DROPPED page into a few sections

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

1 files changed, 9 insertions, 0 deletions

diff --git a/libevdev/libevdev.h b/libevdev/libevdev.h
index bf221fb..31b5c79 100644
--- a/libevdev/libevdev.h
+++ b/libevdev/libevdev.h
@@ -162,6 +162,9 @@ extern "C" {
  *
  * 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
  * 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
@@ -209,6 +212,9 @@ extern "C" {
  * * discard all events until including the next SYN_REPORT
  * 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
  * 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
@@ -271,6 +277,9 @@ extern "C" {
  * Note the terminating ABS_MT_SLOT event, this indicates that the kernel
  * 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
  * 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