Lines Matching refs:codes

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
12 of event codes have changed. However, the state is maintained within the Linux
22 Event types are groupings of codes under a logical input construct. Each
23 type has a set of applicable codes to be used in generating events. See the
24 Codes section for details on valid codes for each type.
66 Event codes:
68 Event codes define the precise type of event.
103 A few EV_KEY codes have special meanings:
106   - These codes are used in conjunction with input trackpads, tablets, and
120     certain value. BTN_TOUCH may be combined with BTN_TOOL_<name> codes. For
135   - These codes denote one, two, three, and four finger interaction on a
139     Note that all BTN_TOOL_<name> codes and the BTN_TOUCH code are orthogonal in
142     codes should have a value of 1 during any synchronization frame.
144 Note: Historically some drivers emitted multiple of the finger count codes with
148 be used to emit these codes. Please see multi-touch-protocol.txt for details.
154 space is unknown. If the absolute position is known, EV_ABS codes should be used
155 instead of EV_REL codes.
157 A few EV_REL codes have special meanings:
160   - These codes are used for vertical and horizontal scroll wheels,
168 A few EV_ABS codes have special meanings:
199 A few EV_MSC codes have special meaning:
344 BTN_{0,1,2,etc} are good generic codes for unlabeled buttons. Do not use