Lines Matching full:codes

1 .. _input-event-codes:
4 Input event codes
8 The input protocol uses a map of types and codes to express input device values
9 to userspace. This document describes the types and codes and how and when they
19 of event codes have changed. However, the state is maintained within the Linux
30 Event types are groupings of codes under a logical input construct. Each
31 type has a set of applicable codes to be used in generating events. See the
32 Codes section for details on valid codes for each type.
86 Event codes
89 Event codes define the precise type of event.
130 A few EV_KEY codes have special meanings:
134   - These codes are used in conjunction with input trackpads, tablets, and
149     certain value. BTN_TOUCH may be combined with BTN_TOOL_<name> codes. For
165   - These codes denote one, two, three, and four finger interaction on a
169     Note that all BTN_TOOL_<name> codes and the BTN_TOUCH code are orthogonal in
172     codes should have a value of 1 during any synchronization frame.
174 Note: Historically some drivers emitted multiple of the finger count codes with
178 be used to emit these codes. Please see multi-touch-protocol.txt for details.
185 space is unknown. If the absolute position is known, EV_ABS codes should be used
186 instead of EV_REL codes.
188 A few EV_REL codes have special meanings:
192   - These codes are used for vertical and horizontal scroll wheels,
196     see REL_WHEEL_HI_RES. These event codes are legacy codes and
220 A few EV_ABS codes have special meanings:
259 A few EV_MSC codes have special meaning:
424 BTN_{0,1,2,etc} are good generic codes for unlabeled buttons. Do not use