Lines Matching +full:not +full:- +full:used
1 .. _input-event-codes:
10 may be used.
14 used to separate input events into packets of input data changes occurring at
20 input subsystem; drivers do not need to maintain the state and may attempt to
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.
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 ------
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>
141 touchscreens should export only one BTN_TOOL_<name> at a time. To not break
142 existing userspace, it is recommended to not switch tool in one EV_SYN frame
148 BTN_TOUCH is used for touch contact. While an input tool is determined to be
155 pen is hovering over but not touching the tablet surface.
165 EVIOCGPROP, defined in linux/input.h, will be used to convey the device type.
169 - These codes denote one, two, three, and four finger interaction on a
182 be used to emit these codes. Please see multi-touch-protocol.txt for details.
185 ------
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,
198 physical size of which varies by device. For high-resolution wheels
199 this may be an approximation based on the high-resolution scroll events,
206 - High-resolution scroll wheel data. The accumulated value 120 represents
207 movement by one detent. For devices that do not provide high-resolution
209 high-resolution scrolling, the value may be a fraction of 120.
211 If a vertical scroll wheel supports high-resolution scrolling, this code
213 and REL_HWHEEL may be an approximation based on the high-resolution
214 scroll events. There is no guarantee that the high-resolution data
219 ------
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
233 - BTN_TOOL_<name> should be set to 1 when the tool comes into detectable
240 - Used to describe the state of a multi-value profile switch. An event is
246 - Used to describe multitouch input events. Please see
247 multi-touch-protocol.txt for details.
251 - For touch devices, many devices converted contact size into pressure.
253 pressure and contact size are directly related. This is not the case
259 pressure data is in arbitrary units. If the resolution is non-zero, the
265 -----
268 used to denote when a laptop lid is closed.
276 not need to keep the state of the switch at any time.
279 ------
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
293 unknown. If the device does not provide this information, the driver must
294 not provide it to user space.
297 ------
299 EV_LED events are used for input and output to set and query the state of
303 ------
305 EV_REP events are used for specifying autorepeating events.
308 ------
310 EV_SND events are used for sending sound commands to simple sound output
314 -----
316 EV_FF events are used to initialize a force feedback capable device and to cause
320 ------
322 EV_PWR events are a special type of event used specifically for power
323 management. Its usage is not well defined. To be addressed later.
334 --------------------------------------
337 directly mapped to screen coordinates (not taking into account trivial
338 transformations, such as scaling, flipping and rotating). Non-direct input
339 devices require non-trivial transformation, such as absolute to relative
341 drawing tablets; non-direct devices: touchpads, mice.
343 The INPUT_PROP_POINTER property indicates that the device is not transposed
344 on the screen and thus requires use of an on-screen pointer to trace user's
345 movements. Typical pointer devices: touchpads, tablets, mice; non-pointer
353 --------------------
364 ------------------
376 If INPUT_PROP_SEMI_MT is not set, the device is assumed to be a true MT
380 -----------------------
383 device but do not have physical buttons associated with the trackstick
385 visual/haptic areas for left, middle, right buttons intended to be used
389 accordingly. This property does not affect kernel behavior.
390 The kernel does not provide button emulation for such devices but treats
394 ------------------------
400 All other axes retain their meaning. A device must not mix
406 The guidelines below ensure proper single-touch and multi-finger functionality.
407 For multi-touch functionality, see the multi-touch-protocol.rst document for
411 ----
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
419 ------------
422 used to report when a touch is active on the screen.
423 BTN_{MOUSE,LEFT,MIDDLE,RIGHT} must not be reported as the result of touch
429 ---------
435 location of the touch. BTN_TOUCH should be used to report when a touch is active
436 on the trackpad. Where multi-finger support is available, BTN_TOOL_<name> should
437 be used to report the number of touches active on the trackpad.
442 -------
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}.
449 BTN_{0,1,2,etc} are good generic codes for unlabeled buttons. Do not use