blob: a11ff74a5127019cb6f367d07ffae32429ccf37e [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Input device configuration
3#
4
5menu "Input device support"
Heiko Carstensd7222602013-02-13 13:29:01 -08006 depends on !UML
Linus Torvalds1da177e2005-04-16 15:20:36 -07007
8config INPUT
David Rientjes6a108a12011-01-20 14:44:16 -08009 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
Linus Torvalds1da177e2005-04-16 15:20:36 -070010 default y
Dmitry Torokhov36203c42009-12-04 10:22:23 -080011 help
Linus Torvalds1da177e2005-04-16 15:20:36 -070012 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
Anssi Hannula7d928a22006-07-19 01:40:30 -040028config INPUT_FF_MEMLESS
29 tristate "Support for memoryless force-feedback devices"
Dmitry Torokhov36203c42009-12-04 10:22:23 -080030 help
Anssi Hannula7d928a22006-07-19 01:40:30 -040031 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
Dmitry Torokhov893e7c22007-06-13 01:49:58 -040041config 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
Dmitry Torokhov36203c42009-12-04 10:22:23 -080054config 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
Dmitry Torokhov19328112012-05-10 22:37:08 -070067config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070080comment "Userland interfaces"
81
82config INPUT_MOUSEDEV
Tom Gundersendfaaed082013-10-31 00:44:49 -070083 tristate "Mouse interface"
Linus Torvalds1da177e2005-04-16 15:20:36 -070084 default y
Dmitry Torokhov36203c42009-12-04 10:22:23 -080085 help
Linus Torvalds1da177e2005-04-16 15:20:36 -070086 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
97config INPUT_MOUSEDEV_PSAUX
98 bool "Provide legacy /dev/psaux device"
99 default y
100 depends on INPUT_MOUSEDEV
Dmitry Torokhov36203c42009-12-04 10:22:23 -0800101 help
Linus Torvalds1da177e2005-04-16 15:20:36 -0700102 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
109config 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
119config 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
129config INPUT_JOYDEV
130 tristate "Joystick interface"
Dmitry Torokhov36203c42009-12-04 10:22:23 -0800131 help
Linus Torvalds1da177e2005-04-16 15:20:36 -0700132 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700142config 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
151config INPUT_EVBUG
152 tristate "Event debugging"
Dmitry Torokhov36203c42009-12-04 10:22:23 -0800153 help
Linus Torvalds1da177e2005-04-16 15:20:36 -0700154 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
Richard Purdiee17bb1d2008-01-30 16:33:59 -0500165config INPUT_APMPOWER
David Rientjes6a108a12011-01-20 14:44:16 -0800166 tristate "Input Power Event -> APM Bridge" if EXPERT
Richard Purdiee17bb1d2008-01-30 16:33:59 -0500167 depends on INPUT && APM_EMULATION
Dmitry Torokhov36203c42009-12-04 10:22:23 -0800168 help
Richard Purdiee17bb1d2008-01-30 16:33:59 -0500169 Say Y here if you want suspend key events to trigger a user
170 requested suspend through APM. This is useful on embedded
Matt LaPlante692105b2009-01-26 11:12:25 +0100171 systems where such behaviour is desired without userspace
Richard Purdiee17bb1d2008-01-30 16:33:59 -0500172 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700177comment "Input Device Drivers"
178
179source "drivers/input/keyboard/Kconfig"
180
181source "drivers/input/mouse/Kconfig"
182
183source "drivers/input/joystick/Kconfig"
184
Dmitry Torokhov4104d132007-05-07 16:16:29 -0400185source "drivers/input/tablet/Kconfig"
186
Linus Torvalds1da177e2005-04-16 15:20:36 -0700187source "drivers/input/touchscreen/Kconfig"
188
189source "drivers/input/misc/Kconfig"
190
191endif
192
193menu "Hardware I/O ports"
194
195source "drivers/input/serio/Kconfig"
196
197source "drivers/input/gameport/Kconfig"
198
199endmenu
200
201endmenu
202