Documentation/input/event-codes.rst

1 .. _input-event-codes:
36   - Used as markers to separate events. Events may be separated in time or in
41   - Used to describe state changes of keyboards, buttons, or other key-like
46   - Used to describe relative axis value changes, e.g. moving the mouse 5 units
51   - Used to describe absolute axis value changes, e.g. describing the
56   - Used to describe miscellaneous input data that do not fit into other types.
60   - Used to describe binary state input switches.
64   - Used to turn LEDs on devices on and off.
68   - Used to output sound to devices.
72   - Used for autorepeating devices.
76   - Used to send force feedback commands to an input device.
80   - A special type for power button and switch input.
84   - Used to receive force feedback device status.
92 ------
99   - Used to synchronize and separate events into packets of input data changes
106   - TBD
110   - Used to synchronize and separate touch events. See the
111     multi-touch-protocol.txt document for more information.
115   - Used to indicate buffer overrun in the evdev client's event queue.
121 ------
134   - These codes are used in conjunction with input trackpads, tablets, and
165   - These codes denote one, two, three, and four finger interaction on a
171     for one code from each group. At most only one of these BTN_TOOL_<name>
178 be used to emit these codes. Please see multi-touch-protocol.txt for details.
181 ------
192   - These codes are used for vertical and horizontal scroll wheels,
194     physical size of which varies by device. For high-resolution wheels
195     this may be an approximation based on the high-resolution scroll events,
202   - High-resolution scroll wheel data. The accumulated value 120 represents
203     movement by one detent. For devices that do not provide high-resolution
205     high-resolution scrolling, the value may be a fraction of 120.
207     If a vertical scroll wheel supports high-resolution scrolling, this code
209     and REL_HWHEEL may be an approximation based on the high-resolution
210     scroll events. There is no guarantee that the high-resolution data
215 ------
224   - Used to describe the distance of a tool from an interaction surface. This
229   - BTN_TOOL_<name> should be set to 1 when the tool comes into detectable
236   - Used to describe multitouch input events. Please see
237     multi-touch-protocol.txt for details.
240 -----
254 ------
263   - Used to report the number of microseconds since the last reset. This event
272 ------
278 ------
283 ------
289 -----
295 ------
309 --------------------------------------
313 transformations, such as scaling, flipping and rotating). Non-direct input
314 devices require non-trivial transformation, such as absolute to relative
316 drawing tablets; non-direct devices: touchpads, mice.
319 on the screen and thus requires use of an on-screen pointer to trace user's
320 movements.  Typical pointer devices: touchpads, tablets, mice; non-pointer
328 --------------------
339 ------------------
341 Some touchpads, most common between 2008 and 2011, can detect the presence
344 touchpads, the semi-mt property should be set.
347 bounding box, or just some of them, for instance the two most recent
355 -----------------------
357 Some laptops, most notably the Lenovo 40 series provide a trackstick
360 visual/haptic areas for left, middle, right buttons intended to be used
369 ------------------------
381 The guidelines below ensure proper single-touch and multi-finger functionality.
382 For multi-touch functionality, see the multi-touch-protocol.txt document for
386 ----
389 the primary button press. BTN_{MIDDLE,RIGHT,4,5,etc.} should be used to report
394 ------------
398 BTN_{MOUSE,LEFT,MIDDLE,RIGHT} must not be reported as the result of touch
404 ---------
411 on the trackpad. Where multi-finger support is available, BTN_TOOL_<name> should
417 -------