Documentation/input/event-codes.rst

10 may be used.
14 used to separate input events into packets of input data changes occurring at
31 type has a set of applicable codes to be used in generating events. See the
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.
84   - Used to receive force feedback device status.
99   - Used to synchronize and separate events into packets of input data changes
110   - Used to synchronize and separate touch events. See the
115   - Used to indicate buffer overrun in the evdev client's event queue.
123 EV_KEY events take the form KEY_<name> or BTN_<name>. For example, KEY_A is used
127 events have a value of 2. In general, KEY_<name> is used for keyboard keys, and
128 BTN_<name> is used for other types of momentary switch events.
134   - These codes are used in conjunction with input trackpads, tablets, and
135     touchscreens. These devices may be used with fingers, pens, or other tools.
136     When an event occurs and a tool is used, the corresponding BTN_TOOL_<name>
148     BTN_TOUCH is used for touch contact. While an input tool is determined to be
165 EVIOCGPROP, defined in linux/input.h, will be used to convey the device type.
182 be used to emit these codes. Please see multi-touch-protocol.txt for details.
189 space is unknown. If the absolute position is known, EV_ABS codes should be used
196   - These codes are used for vertical and horizontal scroll wheels,
228   - Used to describe the distance of a tool from an interaction surface. This
231     the input device may be used freely in three dimensions, consider ABS_Z
240   - Used to describe the state of a multi-value profile switch.  An event is
246   - Used to describe multitouch input events. Please see
268 used to denote when a laptop lid is closed.
281 EV_MSC events are used for input and output events that do not fall under other
288   - Used to report the number of microseconds since the last reset. This event
299 EV_LED events are used for input and output to set and query the state of
305 EV_REP events are used for specifying autorepeating events.
310 EV_SND events are used for sending sound commands to simple sound output
316 EV_FF events are used to initialize a force feedback capable device and to cause
322 EV_PWR events are a special type of event used specifically for power
385 visual/haptic areas for left, middle, right buttons intended to be used
413 REL_{X,Y} must be reported when the mouse moves. BTN_LEFT must be used to report
414 the primary button press. BTN_{MIDDLE,RIGHT,4,5,etc.} should be used to report
415 further buttons of the device. REL_WHEEL and REL_HWHEEL should be used to report
422 used to report when a touch is active on the screen.
435 location of the touch. BTN_TOUCH should be used to report when a touch is active
437 be used to report the number of touches active on the trackpad.
446 should be used to report when the tool is in contact with the tablet.
447 BTN_{STYLUS,STYLUS2} should be used to report buttons on the tool itself. Any
448 button may be used for buttons on the tablet except BTN_{MOUSE,LEFT}.