1 # SPDX-License-Identifier: GPL-2.0-only
3 # Joystick driver configuration
5 menuconfig INPUT_JOYSTICK
6 bool "Joysticks/Gamepads"
8 If you have a joystick, 6dof controller, gamepad, steering wheel,
9 weapon control system or something like that you can say Y here
10 and the list of supported devices will be displayed. This option
11 doesn't affect the kernel.
13 Please read the file <file:Documentation/input/joydev/joystick.rst> which
14 contains more information.
18 config JOYSTICK_ANALOG
19 tristate "Classic PC analog joysticks and gamepads"
22 Say Y here if you have a joystick that connects to the PC
23 gameport. In addition to the usual PC analog joystick, this driver
24 supports many extensions, including joysticks with throttle control,
25 with rudders, additional hats and buttons compatible with CH
26 Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or
27 Saitek Cyborg joysticks.
29 Please read the file <file:Documentation/input/joydev/joystick.rst> which
30 contains more information.
32 To compile this driver as a module, choose M here: the
33 module will be called analog.
36 tristate "Assassin 3D and MadCatz Panther devices"
39 Say Y here if you have an FPGaming or MadCatz controller using the
40 A3D protocol over the PC gameport.
42 To compile this driver as a module, choose M here: the
43 module will be called a3d.
46 tristate "Simple joystick connected over ADC"
50 Say Y here if you have a simple joystick connected over ADC.
52 To compile this driver as a module, choose M here: the
53 module will be called adc-joystick.
56 tristate "Logitech ADI digital joysticks and gamepads"
58 depends on ADI!=m # avoid module name conflict
60 Say Y here if you have a Logitech controller using the ADI
61 protocol over the PC gameport.
63 To compile this driver as a module, choose M here: the
64 module will be called adi.
67 tristate "Creative Labs Blaster Cobra gamepad"
70 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
72 To compile this driver as a module, choose M here: the
73 module will be called cobra.
76 tristate "Genius Flight2000 Digital joysticks and gamepads"
79 Say Y here if you have a Genius Flight2000 or MaxFighter digitally
80 communicating joystick or gamepad.
82 To compile this driver as a module, choose M here: the
83 module will be called gf2k.
86 tristate "Gravis GrIP joysticks and gamepads"
89 Say Y here if you have a Gravis controller using the GrIP protocol
92 To compile this driver as a module, choose M here: the
93 module will be called grip.
95 config JOYSTICK_GRIP_MP
96 tristate "Gravis GrIP MultiPort"
99 Say Y here if you have the original Gravis GrIP MultiPort, a hub
100 that connects to the gameport and you connect gamepads to it.
102 To compile this driver as a module, choose M here: the
103 module will be called grip_mp.
105 config JOYSTICK_GUILLEMOT
106 tristate "Guillemot joysticks and gamepads"
109 Say Y here if you have a Guillemot joystick using a digital
110 protocol over the PC gameport.
112 To compile this driver as a module, choose M here: the
113 module will be called guillemot.
115 config JOYSTICK_INTERACT
116 tristate "InterAct digital joysticks and gamepads"
119 Say Y here if you have an InterAct gameport or joystick
120 communicating digitally over the gameport.
122 To compile this driver as a module, choose M here: the
123 module will be called interact.
125 config JOYSTICK_SIDEWINDER
126 tristate "Microsoft SideWinder digital joysticks and gamepads"
129 Say Y here if you have a Microsoft controller using the Digital
130 Overdrive protocol over PC gameport.
132 To compile this driver as a module, choose M here: the
133 module will be called sidewinder.
136 tristate "ThrustMaster DirectConnect joysticks and gamepads"
139 Say Y here if you have a ThrustMaster controller using the
140 DirectConnect (BSP) protocol over the PC gameport.
142 To compile this driver as a module, choose M here: the
143 module will be called tmdc.
145 source "drivers/input/joystick/iforce/Kconfig"
147 config JOYSTICK_WARRIOR
148 tristate "Logitech WingMan Warrior joystick"
151 Say Y here if you have a Logitech WingMan Warrior joystick connected
152 to your computer's serial port.
154 To compile this driver as a module, choose M here: the
155 module will be called warrior.
157 config JOYSTICK_MAGELLAN
158 tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers"
161 Say Y here if you have a Magellan or Space Mouse 6DOF controller
162 connected to your computer's serial port.
164 To compile this driver as a module, choose M here: the
165 module will be called magellan.
167 config JOYSTICK_SPACEORB
168 tristate "SpaceTec SpaceOrb/Avenger 6dof controllers"
171 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
172 controller connected to your computer's serial port.
174 To compile this driver as a module, choose M here: the
175 module will be called spaceorb.
177 config JOYSTICK_SPACEBALL
178 tristate "SpaceTec SpaceBall 6dof controllers"
181 Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX
182 controller connected to your computer's serial port. For the
183 SpaceBall 4000 USB model, use the USB HID driver.
185 To compile this driver as a module, choose M here: the
186 module will be called spaceball.
188 config JOYSTICK_STINGER
189 tristate "Gravis Stinger gamepad"
192 Say Y here if you have a Gravis Stinger connected to one of your
195 To compile this driver as a module, choose M here: the
196 module will be called stinger.
198 config JOYSTICK_TWIDJOY
199 tristate "Twiddler as a joystick"
202 Say Y here if you have a Handykey Twiddler connected to your
203 computer's serial port and want to use it as a joystick.
205 To compile this driver as a module, choose M here: the
206 module will be called twidjoy.
208 config JOYSTICK_ZHENHUA
209 tristate "5-byte Zhenhua RC transmitter"
213 Say Y here if you have a Zhen Hua PPM-4CH transmitter which is
214 supplied with a ready to fly micro electric indoor helicopters
215 such as EasyCopter, Lama, MiniCopter, DragonFly or Jabo and want
216 to use it via serial cable as a joystick.
218 To compile this driver as a module, choose M here: the
219 module will be called zhenhua.
222 tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads"
225 Say Y here if you have a Sega Master System gamepad, Sega Genesis
226 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
227 Commodore, Amstrad CPC joystick connected to your parallel port.
228 For more information on how to use the driver please read
229 <file:Documentation/input/devices/joystick-parport.rst>.
231 To compile this driver as a module, choose M here: the
232 module will be called db9.
234 config JOYSTICK_GAMECON
235 tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads"
237 select INPUT_FF_MEMLESS
239 Say Y here if you have a Nintendo Entertainment System gamepad,
240 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
241 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
242 Commodore, Amstrad CPC joystick connected to your parallel port.
243 For more information on how to use the driver please read
244 <file:Documentation/input/devices/joystick-parport.rst>.
246 To compile this driver as a module, choose M here: the
247 module will be called gamecon.
249 config JOYSTICK_TURBOGRAFX
250 tristate "Multisystem joysticks via TurboGraFX device"
253 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
254 and want to use it with Multisystem -- Atari, Amiga, Commodore,
255 Amstrad CPC joystick. For more information on how to use the driver
256 please read <file:Documentation/input/devices/joystick-parport.rst>.
258 To compile this driver as a module, choose M here: the
259 module will be called turbografx.
261 config JOYSTICK_AMIGA
262 tristate "Amiga joysticks"
265 Say Y here if you have an Amiga with a digital joystick connected
268 To compile this driver as a module, choose M here: the
269 module will be called amijoy.
271 config JOYSTICK_AS5011
272 tristate "Austria Microsystem AS5011 joystick"
275 Say Y here if you have an AS5011 digital joystick connected to your
278 To compile this driver as a module, choose M here: the
279 module will be called as5011.
281 config JOYSTICK_JOYDUMP
282 tristate "Gameport data dumper"
285 Say Y here if you want to dump data from your joystick into the system
286 log for debugging purposes. Say N if you are making a production
287 configuration or aren't sure.
289 To compile this driver as a module, choose M here: the
290 module will be called joydump.
293 tristate "X-Box gamepad support"
294 depends on USB_ARCH_HAS_HCD
297 Say Y here if you want to use the X-Box pad with your computer.
298 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
299 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
301 For information about how to connect the X-Box pad to USB, see
302 <file:Documentation/input/devices/xpad.rst>.
304 To compile this driver as a module, choose M here: the
305 module will be called xpad.
307 config JOYSTICK_XPAD_FF
308 bool "X-Box gamepad rumble support"
309 depends on JOYSTICK_XPAD && INPUT
310 select INPUT_FF_MEMLESS
312 Say Y here if you want to take advantage of xbox 360 rumble features.
314 config JOYSTICK_XPAD_LEDS
315 bool "LED Support for Xbox360 controller 'BigX' LED"
316 depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD)
318 This option enables support for the LED which surrounds the Big X on
321 config JOYSTICK_WALKERA0701
322 tristate "Walkera WK-0701 RC transmitter"
323 depends on HIGH_RES_TIMERS && PARPORT
325 Say Y or M here if you have a Walkera WK-0701 transmitter which is
326 supplied with a ready to fly Walkera helicopters such as HM36,
327 HM37, HM60 and want to use it via parport as a joystick. More
328 information is available: <file:Documentation/input/devices/walkera0701.rst>
330 To compile this driver as a module, choose M here: the
331 module will be called walkera0701.
333 config JOYSTICK_MAPLE
334 tristate "Dreamcast control pad"
337 Say Y here if you have a SEGA Dreamcast and want to use your
338 controller as a joystick.
340 Most Dreamcast users will say Y.
342 To compile this as a module choose M here: the module will be called
345 config JOYSTICK_PSXPAD_SPI
346 tristate "PlayStation 1/2 joypads via SPI interface"
349 Say Y here if you wish to connect PlayStation 1/2 joypads
352 To compile this driver as a module, choose M here: the
353 module will be called psxpad-spi.
355 config JOYSTICK_PSXPAD_SPI_FF
356 bool "PlayStation 1/2 joypads force feedback (rumble) support"
357 depends on JOYSTICK_PSXPAD_SPI
358 select INPUT_FF_MEMLESS
360 Say Y here if you want to take advantage of PlayStation 1/2
361 joypads rumble features.
363 To drive rumble motor a dedicated power supply is required.
366 tristate "PhoenixRC Flight Controller Adapter"
367 depends on USB_ARCH_HAS_HCD
370 Say Y here if you want to use the PhoenixRC Flight Controller Adapter.
372 To compile this driver as a module, choose M here: the
373 module will be called pxrc.
375 config JOYSTICK_FSIA6B
376 tristate "FlySky FS-iA6B RC Receiver"
379 Say Y here if you use a FlySky FS-i6 RC remote control along with the
380 FS-iA6B RC receiver as a joystick input device.
382 To compile this driver as a module, choose M here: the
383 module will be called fsia6b.