Lines Matching full:event

1 .. _input-event-codes:
4 Input event codes
12 A single hardware event generates multiple input events. Each input event
13 contains the new value of a single data item. A special event type, EV_SYN, is
15 the same moment in time. In the following, the term "event" refers to a single
16 input event encompassing a type, code, and value.
19 of event codes have changed. However, the state is maintained within the Linux
22 event code values using the EVIOCG* ioctls defined in linux/input.h. The event
24 class/input/event*/device/capabilities/, and the properties of a device are
25 provided in class/input/event*/device/properties.
27 Event types
30 Event types are groupings of codes under a logical input construct. Each
86 Event codes
89 Event codes define the precise type of event.
94 EV_SYN event values are undefined. Their usage is defined only by when they are
95 sent in the evdev event stream.
115   - Used to indicate buffer overrun in the evdev client's event queue.
117     event and query the device (using EVIOCG* ioctls) to obtain its
124 to represent the 'A' key on a keyboard. When a key is depressed, an event with
125 the key's code is emitted with value 1. When the key is released, an event is
136     When an event occurs and a tool is used, the corresponding BTN_TOOL_<name>
170     purpose. A trackpad event generated by finger touches should generate events
196     see REL_WHEEL_HI_RES. These event codes are legacy codes and
212     event.
225     event should only be emitted while the tool is hovering, meaning in close
263   - Used to report the number of microseconds since the last reset. This event
267     A reset to zero can happen, in which case the time since the last event is
297 EV_PWR events are a special type of event used specifically for power
304 i.e., the event types. In the case of two devices emitting the same event
325 traditional way, using emitted event types.
376 regular directional axes and accelerometer axes on the same event node.