]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blob - drivers/input/joystick/Kconfig
Merge branch 'stable-4.13' of git://git.infradead.org/users/pcmoore/audit
[mirror_ubuntu-bionic-kernel.git] / drivers / input / joystick / Kconfig
1 #
2 # Joystick driver configuration
3 #
4 menuconfig INPUT_JOYSTICK
5 bool "Joysticks/Gamepads"
6 help
7 If you have a joystick, 6dof controller, gamepad, steering wheel,
8 weapon control system or something like that you can say Y here
9 and the list of supported devices will be displayed. This option
10 doesn't affect the kernel.
11
12 Please read the file <file:Documentation/input/joystick.txt> which
13 contains more information.
14
15 if INPUT_JOYSTICK
16
17 config JOYSTICK_ANALOG
18 tristate "Classic PC analog joysticks and gamepads"
19 select GAMEPORT
20 ---help---
21 Say Y here if you have a joystick that connects to the PC
22 gameport. In addition to the usual PC analog joystick, this driver
23 supports many extensions, including joysticks with throttle control,
24 with rudders, additional hats and buttons compatible with CH
25 Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or
26 Saitek Cyborg joysticks.
27
28 Please read the file <file:Documentation/input/joystick.txt> which
29 contains more information.
30
31 To compile this driver as a module, choose M here: the
32 module will be called analog.
33
34 config JOYSTICK_A3D
35 tristate "Assassin 3D and MadCatz Panther devices"
36 select GAMEPORT
37 help
38 Say Y here if you have an FPGaming or MadCatz controller using the
39 A3D protocol over the PC gameport.
40
41 To compile this driver as a module, choose M here: the
42 module will be called a3d.
43
44 config JOYSTICK_ADI
45 tristate "Logitech ADI digital joysticks and gamepads"
46 select GAMEPORT
47 help
48 Say Y here if you have a Logitech controller using the ADI
49 protocol over the PC gameport.
50
51 To compile this driver as a module, choose M here: the
52 module will be called adi.
53
54 config JOYSTICK_COBRA
55 tristate "Creative Labs Blaster Cobra gamepad"
56 select GAMEPORT
57 help
58 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
59
60 To compile this driver as a module, choose M here: the
61 module will be called cobra.
62
63 config JOYSTICK_GF2K
64 tristate "Genius Flight2000 Digital joysticks and gamepads"
65 select GAMEPORT
66 help
67 Say Y here if you have a Genius Flight2000 or MaxFighter digitally
68 communicating joystick or gamepad.
69
70 To compile this driver as a module, choose M here: the
71 module will be called gf2k.
72
73 config JOYSTICK_GRIP
74 tristate "Gravis GrIP joysticks and gamepads"
75 select GAMEPORT
76 help
77 Say Y here if you have a Gravis controller using the GrIP protocol
78 over the PC gameport.
79
80 To compile this driver as a module, choose M here: the
81 module will be called grip.
82
83 config JOYSTICK_GRIP_MP
84 tristate "Gravis GrIP MultiPort"
85 select GAMEPORT
86 help
87 Say Y here if you have the original Gravis GrIP MultiPort, a hub
88 that connects to the gameport and you connect gamepads to it.
89
90 To compile this driver as a module, choose M here: the
91 module will be called grip_mp.
92
93 config JOYSTICK_GUILLEMOT
94 tristate "Guillemot joysticks and gamepads"
95 select GAMEPORT
96 help
97 Say Y here if you have a Guillemot joystick using a digital
98 protocol over the PC gameport.
99
100 To compile this driver as a module, choose M here: the
101 module will be called guillemot.
102
103 config JOYSTICK_INTERACT
104 tristate "InterAct digital joysticks and gamepads"
105 select GAMEPORT
106 help
107 Say Y here if you have an InterAct gameport or joystick
108 communicating digitally over the gameport.
109
110 To compile this driver as a module, choose M here: the
111 module will be called interact.
112
113 config JOYSTICK_SIDEWINDER
114 tristate "Microsoft SideWinder digital joysticks and gamepads"
115 select GAMEPORT
116 help
117 Say Y here if you have a Microsoft controller using the Digital
118 Overdrive protocol over PC gameport.
119
120 To compile this driver as a module, choose M here: the
121 module will be called sidewinder.
122
123 config JOYSTICK_TMDC
124 tristate "ThrustMaster DirectConnect joysticks and gamepads"
125 select GAMEPORT
126 help
127 Say Y here if you have a ThrustMaster controller using the
128 DirectConnect (BSP) protocol over the PC gameport.
129
130 To compile this driver as a module, choose M here: the
131 module will be called tmdc.
132
133 source "drivers/input/joystick/iforce/Kconfig"
134
135 config JOYSTICK_WARRIOR
136 tristate "Logitech WingMan Warrior joystick"
137 select SERIO
138 help
139 Say Y here if you have a Logitech WingMan Warrior joystick connected
140 to your computer's serial port.
141
142 To compile this driver as a module, choose M here: the
143 module will be called warrior.
144
145 config JOYSTICK_MAGELLAN
146 tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers"
147 select SERIO
148 help
149 Say Y here if you have a Magellan or Space Mouse 6DOF controller
150 connected to your computer's serial port.
151
152 To compile this driver as a module, choose M here: the
153 module will be called magellan.
154
155 config JOYSTICK_SPACEORB
156 tristate "SpaceTec SpaceOrb/Avenger 6dof controllers"
157 select SERIO
158 help
159 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
160 controller connected to your computer's serial port.
161
162 To compile this driver as a module, choose M here: the
163 module will be called spaceorb.
164
165 config JOYSTICK_SPACEBALL
166 tristate "SpaceTec SpaceBall 6dof controllers"
167 select SERIO
168 help
169 Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX
170 controller connected to your computer's serial port. For the
171 SpaceBall 4000 USB model, use the USB HID driver.
172
173 To compile this driver as a module, choose M here: the
174 module will be called spaceball.
175
176 config JOYSTICK_STINGER
177 tristate "Gravis Stinger gamepad"
178 select SERIO
179 help
180 Say Y here if you have a Gravis Stinger connected to one of your
181 serial ports.
182
183 To compile this driver as a module, choose M here: the
184 module will be called stinger.
185
186 config JOYSTICK_TWIDJOY
187 tristate "Twiddler as a joystick"
188 select SERIO
189 help
190 Say Y here if you have a Handykey Twiddler connected to your
191 computer's serial port and want to use it as a joystick.
192
193 To compile this driver as a module, choose M here: the
194 module will be called twidjoy.
195
196 config JOYSTICK_ZHENHUA
197 tristate "5-byte Zhenhua RC transmitter"
198 select SERIO
199 select BITREVERSE
200 help
201 Say Y here if you have a Zhen Hua PPM-4CH transmitter which is
202 supplied with a ready to fly micro electric indoor helicopters
203 such as EasyCopter, Lama, MiniCopter, DragonFly or Jabo and want
204 to use it via serial cable as a joystick.
205
206 To compile this driver as a module, choose M here: the
207 module will be called zhenhua.
208
209 config JOYSTICK_DB9
210 tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads"
211 depends on PARPORT
212 help
213 Say Y here if you have a Sega Master System gamepad, Sega Genesis
214 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
215 Commodore, Amstrad CPC joystick connected to your parallel port.
216 For more information on how to use the driver please read
217 <file:Documentation/input/joystick-parport.txt>.
218
219 To compile this driver as a module, choose M here: the
220 module will be called db9.
221
222 config JOYSTICK_GAMECON
223 tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads"
224 depends on PARPORT
225 select INPUT_FF_MEMLESS
226 ---help---
227 Say Y here if you have a Nintendo Entertainment System gamepad,
228 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
229 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
230 Commodore, Amstrad CPC joystick connected to your parallel port.
231 For more information on how to use the driver please read
232 <file:Documentation/input/joystick-parport.txt>.
233
234 To compile this driver as a module, choose M here: the
235 module will be called gamecon.
236
237 config JOYSTICK_TURBOGRAFX
238 tristate "Multisystem joysticks via TurboGraFX device"
239 depends on PARPORT
240 help
241 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
242 and want to use it with Multisystem -- Atari, Amiga, Commodore,
243 Amstrad CPC joystick. For more information on how to use the driver
244 please read <file:Documentation/input/joystick-parport.txt>.
245
246 To compile this driver as a module, choose M here: the
247 module will be called turbografx.
248
249 config JOYSTICK_AMIGA
250 tristate "Amiga joysticks"
251 depends on AMIGA
252 help
253 Say Y here if you have an Amiga with a digital joystick connected
254 to it.
255
256 To compile this driver as a module, choose M here: the
257 module will be called amijoy.
258
259 config JOYSTICK_AS5011
260 tristate "Austria Microsystem AS5011 joystick"
261 depends on I2C
262 help
263 Say Y here if you have an AS5011 digital joystick connected to your
264 system.
265
266 To compile this driver as a module, choose M here: the
267 module will be called as5011.
268
269 config JOYSTICK_JOYDUMP
270 tristate "Gameport data dumper"
271 select GAMEPORT
272 help
273 Say Y here if you want to dump data from your joystick into the system
274 log for debugging purposes. Say N if you are making a production
275 configuration or aren't sure.
276
277 To compile this driver as a module, choose M here: the
278 module will be called joydump.
279
280 config JOYSTICK_XPAD
281 tristate "X-Box gamepad support"
282 depends on USB_ARCH_HAS_HCD
283 select USB
284 help
285 Say Y here if you want to use the X-Box pad with your computer.
286 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
287 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
288
289 For information about how to connect the X-Box pad to USB, see
290 <file:Documentation/input/xpad.txt>.
291
292 To compile this driver as a module, choose M here: the
293 module will be called xpad.
294
295 config JOYSTICK_XPAD_FF
296 bool "X-Box gamepad rumble support"
297 depends on JOYSTICK_XPAD && INPUT
298 select INPUT_FF_MEMLESS
299 ---help---
300 Say Y here if you want to take advantage of xbox 360 rumble features.
301
302 config JOYSTICK_XPAD_LEDS
303 bool "LED Support for Xbox360 controller 'BigX' LED"
304 depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD)
305 ---help---
306 This option enables support for the LED which surrounds the Big X on
307 XBox 360 controller.
308
309 config JOYSTICK_WALKERA0701
310 tristate "Walkera WK-0701 RC transmitter"
311 depends on HIGH_RES_TIMERS && PARPORT
312 help
313 Say Y or M here if you have a Walkera WK-0701 transmitter which is
314 supplied with a ready to fly Walkera helicopters such as HM36,
315 HM37, HM60 and want to use it via parport as a joystick. More
316 information is available: <file:Documentation/input/walkera0701.txt>
317
318 To compile this driver as a module, choose M here: the
319 module will be called walkera0701.
320
321 config JOYSTICK_MAPLE
322 tristate "Dreamcast control pad"
323 depends on MAPLE
324 help
325 Say Y here if you have a SEGA Dreamcast and want to use your
326 controller as a joystick.
327
328 Most Dreamcast users will say Y.
329
330 To compile this as a module choose M here: the module will be called
331 maplecontrol.
332
333 config JOYSTICK_PSXPAD_SPI
334 tristate "PlayStation 1/2 joypads via SPI interface"
335 depends on SPI
336 select INPUT_POLLDEV
337 help
338 Say Y here if you wish to connect PlayStation 1/2 joypads
339 via SPI interface.
340
341 To compile this driver as a module, choose M here: the
342 module will be called psxpad-spi.
343
344 config JOYSTICK_PSXPAD_SPI_FF
345 bool "PlayStation 1/2 joypads force feedback (rumble) support"
346 depends on JOYSTICK_PSXPAD_SPI
347 select INPUT_FF_MEMLESS
348 help
349 Say Y here if you want to take advantage of PlayStation 1/2
350 joypads rumble features.
351
352 To drive rumble motor a dedicated power supply is required.
353
354 endif