blob: 9dea14db724ca1a186f8d7f765b94c28ed0db3a3 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Input device configuration
3#
4
5menu "Input device support"
Martin Schwidefsky9556fb72007-05-10 15:45:58 +02006 depends on !S390
Linus Torvalds1da177e2005-04-16 15:20:36 -07007
8config INPUT
9 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EMBEDDED
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
Anssi Hannula7d928a22006-07-19 01:40:30 -040028config INPUT_FF_MEMLESS
29 tristate "Support for memoryless force-feedback devices"
30 default n
31 ---help---
32 Say Y here if you have memoryless force-feedback input device
33 such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
34 Power 2, or similar. You will also need to enable hardware-specific
35 driver.
36
37 If unsure, say N.
38
39 To compile this driver as a module, choose M here: the
40 module will be called ff-memless.
41
Dmitry Torokhov893e7c22007-06-13 01:49:58 -040042config INPUT_POLLDEV
43 tristate "Polled input device skeleton"
44 help
45 Say Y here if you are using a driver for an input
46 device that periodically polls hardware state. This
47 option is only useful for out-of-tree drivers since
48 in-tree drivers select it automatically.
49
50 If unsure, say N.
51
52 To compile this driver as a module, choose M here: the
53 module will be called input-polldev.
54
Linus Torvalds1da177e2005-04-16 15:20:36 -070055comment "Userland interfaces"
56
57config INPUT_MOUSEDEV
58 tristate "Mouse interface" if EMBEDDED
59 default y
60 ---help---
61 Say Y here if you want your mouse to be accessible as char devices
62 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
63 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
64 programs (including SVGAlib, GPM and X) will be able to use your
65 mouse.
66
67 If unsure, say Y.
68
69 To compile this driver as a module, choose M here: the
70 module will be called mousedev.
71
72config INPUT_MOUSEDEV_PSAUX
73 bool "Provide legacy /dev/psaux device"
74 default y
75 depends on INPUT_MOUSEDEV
76 ---help---
77 Say Y here if you want your mouse also be accessible as char device
78 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
79 the same as the data from /dev/input/mice.
80
81 If unsure, say Y.
82
83
84config INPUT_MOUSEDEV_SCREEN_X
85 int "Horizontal screen resolution"
86 depends on INPUT_MOUSEDEV
87 default "1024"
88 help
89 If you're using a digitizer, or a graphic tablet, and want to use
90 it as a mouse then the mousedev driver needs to know the X window
91 screen resolution you are using to correctly scale the data. If
92 you're not using a digitizer, this value is ignored.
93
94config INPUT_MOUSEDEV_SCREEN_Y
95 int "Vertical screen resolution"
96 depends on INPUT_MOUSEDEV
97 default "768"
98 help
99 If you're using a digitizer, or a graphic tablet, and want to use
100 it as a mouse then the mousedev driver needs to know the X window
101 screen resolution you are using to correctly scale the data. If
102 you're not using a digitizer, this value is ignored.
103
104config INPUT_JOYDEV
105 tristate "Joystick interface"
106 ---help---
107 Say Y here if you want your joystick or gamepad to be
108 accessible as char device 13:0+ - /dev/input/jsX device.
109
110 If unsure, say Y.
111
112 More information is available: <file:Documentation/input/joystick.txt>
113
114 To compile this driver as a module, choose M here: the
115 module will be called joydev.
116
Linus Torvalds1da177e2005-04-16 15:20:36 -0700117config INPUT_EVDEV
118 tristate "Event interface"
119 help
120 Say Y here if you want your input device events be accessible
121 under char device 13:64+ - /dev/input/eventX in a generic way.
122
123 To compile this driver as a module, choose M here: the
124 module will be called evdev.
125
126config INPUT_EVBUG
127 tristate "Event debugging"
128 ---help---
129 Say Y here if you have a problem with the input subsystem and
130 want all events (keypresses, mouse movements), to be output to
131 the system log. While this is useful for debugging, it's also
132 a security threat - your keypresses include your passwords, of
133 course.
134
135 If unsure, say N.
136
137 To compile this driver as a module, choose M here: the
138 module will be called evbug.
139
Richard Purdiee17bb1d2008-01-30 16:33:59 -0500140config INPUT_APMPOWER
141 tristate "Input Power Event -> APM Bridge" if EMBEDDED
142 depends on INPUT && APM_EMULATION
143 ---help---
144 Say Y here if you want suspend key events to trigger a user
145 requested suspend through APM. This is useful on embedded
146 systems where such behviour is desired without userspace
147 interaction. If unsure, say N.
148
149 To compile this driver as a module, choose M here: the
150 module will be called apm-power.
151
Linus Torvalds1da177e2005-04-16 15:20:36 -0700152comment "Input Device Drivers"
153
154source "drivers/input/keyboard/Kconfig"
155
156source "drivers/input/mouse/Kconfig"
157
158source "drivers/input/joystick/Kconfig"
159
Dmitry Torokhov4104d132007-05-07 16:16:29 -0400160source "drivers/input/tablet/Kconfig"
161
Linus Torvalds1da177e2005-04-16 15:20:36 -0700162source "drivers/input/touchscreen/Kconfig"
163
164source "drivers/input/misc/Kconfig"
165
166endif
167
168menu "Hardware I/O ports"
169
170source "drivers/input/serio/Kconfig"
171
172source "drivers/input/gameport/Kconfig"
173
174endmenu
175
176endmenu
177