Lines Matching refs:and

1 The input protocol uses a map of types and codes to express input device values
2 to userspace. This document describes the types and codes and how and when they
9 input event encompassing a type, code, and value.
13 input subsystem; drivers do not need to maintain the state and may attempt to
17 class/input/event*/device/capabilities/, and the properties of a device are
49   - Used to turn LEDs on devices on and off.
61   - A special type for power button and switch input.
76   - Used to synchronize and separate events into packets of input data changes
78     the REL_X and REL_Y values for one motion, then emit a SYN_REPORT. The next
79     motion will emit more REL_X and REL_Y values and send another SYN_REPORT.
85   - Used to synchronize and separate touch events. See the
90     Client should ignore all events up to and including next SYN_REPORT
91     event and query the device (using EVIOCG* ioctls) to obtain its
100 events have a value of 2. In general, KEY_<name> is used for keyboard keys, and
106   - These codes are used in conjunction with input trackpads, tablets, and
108     When an event occurs and a tool is used, the corresponding BTN_TOOL_<name>
111     trackpads, tablets, and touchscreens should use at least one BTN_TOOL_<name>
121     example, a pen tablet may set BTN_TOOL_PEN to 1 and BTN_TOUCH to 0 while the
127 Note: Historically a touch device with BTN_TOOL_FINGER and BTN_TOUCH was
131 future, this distinction will be deprecated and the device properties ioctl
135   - These codes denote one, two, three, and four finger interaction on a
136     trackpad or touchscreen. For example, if the user uses two fingers and moves
139     Note that all BTN_TOOL_<name> codes and the BTN_TOUCH code are orthogonal in
160   - These codes are used for vertical and horizontal scroll wheels,
173     proximity of the device and while the value of the BTN_TOUCH code is 0. If
187 the current switch state. This ensures that the device, kernel, and userspace
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
226 EV_FF events are used to initialize a force feedback capable device and to cause
245 transformations, such as scaling, flipping and rotating). Non-direct input
251 on the screen and thus requires use of an on-screen pointer to trace user's
256 considered undefined and the device type should be deduced in the
263 set. Common in clickpad notebooks and macbooks from 2009 and onwards.
271 Some touchpads, most common between 2008 and 2011, can detect the presence
273 number of contacts and a rectangular shape is known. For such
299 Directional axes on this device (absolute and/or relative x, y, z) represent
301 regular directional axes and accelerometer axes on the same event node.
305 The guidelines below ensure proper single-touch and multi-finger functionality.
313 further buttons of the device. REL_WHEEL and REL_HWHEEL should be used to report
348 For new hardware, both INPUT_PROP_DIRECT and INPUT_PROP_POINTER should be set.