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