Documentation/input/input.rst

12 Input subsystem is a collection of drivers that is designed to support
14 drivers/input, although quite a few live in drivers/hid and
18 loaded before any other of the input modules - it serves as a way of
32 a simulated PS/2 interface to GPM and X, and so on.
49 will be available as a character device on major 13, minor 63::
100 	crw-r--r--   1 root     root      13,  65 Apr  1 10:50 event1
101 	crw-r--r--   1 root     root      13,  66 Apr  1 10:50 event2
102 	crw-r--r--   1 root     root      13,  67 Apr  1 10:50 event3
106 range. If there are more than 32 input devices in a system, additional
112 ``keyboard`` is in-kernel input handler and is a part of VT code. It
118 ``mousedev`` is a hack to make legacy programs that use mouse input
120 a PS/2-style (a la /dev/psaux) mouse device available to the
128 	crw-r--r--   1 root     root      13,  35 Apr  1 10:50 mouse3
131 	crw-r--r--   1 root     root      13,  62 Apr  1 10:50 mouse30
132 	crw-r--r--   1 root     root      13,  63 Apr  1 10:50 mice
134 Each ``mouse`` device is assigned to a single mouse or digitizer, except
144 via a virtual PS/2 mouse and thus needs to be scaled
145 accordingly. These values won't be used if you use a mouse only.
150 these. You'll need ImPS/2 if you want to make use of a wheel on a USB
161 	crw-r--r--   1 root     root      13,   0 Apr  1 10:50 js0
162 	crw-r--r--   1 root     root      13,   1 Apr  1 10:50 js1
163 	crw-r--r--   1 root     root      13,   2 Apr  1 10:50 js2
164 	crw-r--r--   1 root     root      13,   3 Apr  1 10:50 js3
179 whole suite. It handles all HID devices, and because there is a very
195 detects everything automatically and when a HID device is inserted, it
198 However, because the devices vary wildly, you might happen to have a
206 other use when the big usbhid wouldn't be a good choice, there is the
207 usbmouse driver. It handles USB mice only. It uses a simpler HIDBP
215 Much like usbmouse, this module talks to keyboards with a simplified
234 A driver for I-Force joysticks and wheels, both over USB and RS232.
236 Corp. considers the protocol a trade secret and won't disclose a word
242 Typing a couple keys on the keyboard should be enough to check that
243 a keyboard works and is correctly connected to the kernel keyboard
246 Doing a ``cat /dev/input/mouse0`` (c, 13, 32) will verify that a mouse
260 /dev/input/eventX devices, and you'll always get a whole number of input
261 events on a read. Their layout is::
271 Type is for example EV_REL for relative movement, EV_KEY for a keypress or
274 ``code`` is event code, for example REL_X or KEY_BACKSPACE, again a complete
277 ``value`` is the value the event carries. Either a relative change for