1
2
3
4
5menu "Input device support"
6 depends on !UML
7
8config INPUT
9 tristate "Generic input layer (needed for keyboard, mouse, ...)"
10 default y
11 help
12 Say Y here if you have any input device (mouse, keyboard, tablet,
13 joystick, steering wheel ...) connected to your system and want
14 it to be available to applications. This includes standard PS/2
15 keyboard and mouse.
16
17 Say N here if you have a headless (no monitor, no keyboard) system.
18
19 More information is available: <file:Documentation/input/input.txt>
20
21 If unsure, say Y.
22
23 To compile this driver as a module, choose M here: the
24 module will be called input.
25
26if INPUT
27
28config INPUT_LEDS
29 tristate "Export input device LEDs in sysfs"
30 depends on LEDS_CLASS
31 default INPUT
32 help
33 Say Y here if you would like to export LEDs on input devices
34 as standard LED class devices in sysfs.
35
36 If unsure, say Y.
37
38 To compile this driver as a module, choose M here: the
39 module will be called input-leds.
40
41config INPUT_FF_MEMLESS
42 tristate "Support for memoryless force-feedback devices"
43 help
44 Say Y here if you have memoryless force-feedback input device
45 such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
46 Power 2, or similar. You will also need to enable hardware-specific
47 driver.
48
49 If unsure, say N.
50
51 To compile this driver as a module, choose M here: the
52 module will be called ff-memless.
53
54config INPUT_POLLDEV
55 tristate "Polled input device skeleton"
56 help
57 Say Y here if you are using a driver for an input
58 device that periodically polls hardware state. This
59 option is only useful for out-of-tree drivers since
60 in-tree drivers select it automatically.
61
62 If unsure, say N.
63
64 To compile this driver as a module, choose M here: the
65 module will be called input-polldev.
66
67config INPUT_SPARSEKMAP
68 tristate "Sparse keymap support library"
69 help
70 Say Y here if you are using a driver for an input
71 device that uses sparse keymap. This option is only
72 useful for out-of-tree drivers since in-tree drivers
73 select it automatically.
74
75 If unsure, say N.
76
77 To compile this driver as a module, choose M here: the
78 module will be called sparse-keymap.
79
80config INPUT_MATRIXKMAP
81 tristate "Matrix keymap support library"
82 help
83 Say Y here if you are using a driver for an input
84 device that uses matrix keymap. This option is only
85 useful for out-of-tree drivers since in-tree drivers
86 select it automatically.
87
88 If unsure, say N.
89
90 To compile this driver as a module, choose M here: the
91 module will be called matrix-keymap.
92
93comment "Userland interfaces"
94
95config INPUT_MOUSEDEV
96 tristate "Mouse interface"
97 default y
98 help
99 Say Y here if you want your mouse to be accessible as char devices
100 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
101 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
102 programs (including SVGAlib, GPM and X) will be able to use your
103 mouse.
104
105 If unsure, say Y.
106
107 To compile this driver as a module, choose M here: the
108 module will be called mousedev.
109
110config INPUT_MOUSEDEV_PSAUX
111 bool "Provide legacy /dev/psaux device"
112 default y
113 depends on INPUT_MOUSEDEV
114 help
115 Say Y here if you want your mouse also be accessible as char device
116 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
117 the same as the data from /dev/input/mice.
118
119 If unsure, say Y.
120
121
122config INPUT_MOUSEDEV_SCREEN_X
123 int "Horizontal screen resolution"
124 depends on INPUT_MOUSEDEV
125 default "1024"
126 help
127 If you're using a digitizer, or a graphic tablet, and want to use
128 it as a mouse then the mousedev driver needs to know the X window
129 screen resolution you are using to correctly scale the data. If
130 you're not using a digitizer, this value is ignored.
131
132config INPUT_MOUSEDEV_SCREEN_Y
133 int "Vertical screen resolution"
134 depends on INPUT_MOUSEDEV
135 default "768"
136 help
137 If you're using a digitizer, or a graphic tablet, and want to use
138 it as a mouse then the mousedev driver needs to know the X window
139 screen resolution you are using to correctly scale the data. If
140 you're not using a digitizer, this value is ignored.
141
142config INPUT_JOYDEV
143 tristate "Joystick interface"
144 help
145 Say Y here if you want your joystick or gamepad to be
146 accessible as char device 13:0+ - /dev/input/jsX device.
147
148 If unsure, say Y.
149
150 More information is available: <file:Documentation/input/joystick.txt>
151
152 To compile this driver as a module, choose M here: the
153 module will be called joydev.
154
155config INPUT_EVDEV
156 tristate "Event interface"
157 help
158 Say Y here if you want your input device events be accessible
159 under char device 13:64+ - /dev/input/eventX in a generic way.
160
161 To compile this driver as a module, choose M here: the
162 module will be called evdev.
163
164config INPUT_EVBUG
165 tristate "Event debugging"
166 help
167 Say Y here if you have a problem with the input subsystem and
168 want all events (keypresses, mouse movements), to be output to
169 the system log. While this is useful for debugging, it's also
170 a security threat - your keypresses include your passwords, of
171 course.
172
173 If unsure, say N.
174
175 To compile this driver as a module, choose M here: the
176 module will be called evbug.
177
178config INPUT_APMPOWER
179 tristate "Input Power Event -> APM Bridge" if EXPERT
180 depends on INPUT && APM_EMULATION
181 help
182 Say Y here if you want suspend key events to trigger a user
183 requested suspend through APM. This is useful on embedded
184 systems where such behaviour is desired without userspace
185 interaction. If unsure, say N.
186
187 To compile this driver as a module, choose M here: the
188 module will be called apm-power.
189
190comment "Input Device Drivers"
191
192source "drivers/input/keyboard/Kconfig"
193
194source "drivers/input/mouse/Kconfig"
195
196source "drivers/input/joystick/Kconfig"
197
198source "drivers/input/tablet/Kconfig"
199
200source "drivers/input/touchscreen/Kconfig"
201
202source "drivers/input/misc/Kconfig"
203
204source "drivers/input/rmi4/Kconfig"
205
206endif
207
208menu "Hardware I/O ports"
209
210source "drivers/input/serio/Kconfig"
211
212source "drivers/input/gameport/Kconfig"
213
214endmenu
215
216endmenu
217
218
