Lines Matching refs:input
1 The input protocol uses a map of types and codes to express input device values
5 A single hardware event generates multiple input events. Each input event
7 used to separate input events into packets of input data changes occurring at
9 input event encompassing a type, code, and value.
11 The input protocol is a stateful protocol. Events are emitted only when values
13 input subsystem; drivers do not need to maintain the state and may attempt to
15 event code values using the EVIOCG* ioctls defined in linux/input.h. The event
17 class/input/event*/device/capabilities/, and the properties of a device are
18 provided in class/input/event*/device/properties.
22 Event types are groupings of codes under a logical input construct. Each
43 - Used to describe miscellaneous input data that do not fit into other types.
46 - Used to describe binary state input switches.
58 - Used to send force feedback commands to an input device.
61 - A special type for power button and switch input.
76 - Used to synchronize and separate events into packets of input data changes
106 - These codes are used in conjunction with input trackpads, tablets, and
110 with the input device, the BTN_TOOL_<name> code should be reset to 0. All
115 BTN_TOUCH is used for touch contact. While an input tool is determined to be
132 EVIOCGPROP, defined in linux/input.h, will be used to convey the device type.
174 the input device may be used freely in three dimensions, consider ABS_Z
178 - Used to describe multitouch input events. Please see
190 Upon resume, if the switch state is the same as before suspend, then the input
196 EV_MSC events are used for input and output events that do not fall under other
212 EV_LED events are used for input and output to set and query the state of
236 Normally, userspace sets up an input device based on the data it emits,
245 transformations, such as scaling, flipping and rotating). Non-direct input
247 transformation for touchpads. Typical direct input devices: touchscreens,