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 "Logitech ADI digital joysticks and gamepads"
48 depends on ADI!=m # avoid module name conflict
50 Say Y here if you have a Logitech controller using the ADI
51 protocol over the PC gameport.
53 To compile this driver as a module, choose M here: the
54 module will be called adi.
57 tristate "Creative Labs Blaster Cobra gamepad"
60 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
62 To compile this driver as a module, choose M here: the
63 module will be called cobra.
66 tristate "Genius Flight2000 Digital joysticks and gamepads"
69 Say Y here if you have a Genius Flight2000 or MaxFighter digitally
70 communicating joystick or gamepad.
72 To compile this driver as a module, choose M here: the
73 module will be called gf2k.
76 tristate "Gravis GrIP joysticks and gamepads"
79 Say Y here if you have a Gravis controller using the GrIP protocol
82 To compile this driver as a module, choose M here: the
83 module will be called grip.
85 config JOYSTICK_GRIP_MP
86 tristate "Gravis GrIP MultiPort"
89 Say Y here if you have the original Gravis GrIP MultiPort, a hub
90 that connects to the gameport and you connect gamepads to it.
92 To compile this driver as a module, choose M here: the
93 module will be called grip_mp.
95 config JOYSTICK_GUILLEMOT
96 tristate "Guillemot joysticks and gamepads"
99 Say Y here if you have a Guillemot joystick using a digital
100 protocol over the PC gameport.
102 To compile this driver as a module, choose M here: the
103 module will be called guillemot.
105 config JOYSTICK_INTERACT
106 tristate "InterAct digital joysticks and gamepads"
109 Say Y here if you have an InterAct gameport or joystick
110 communicating digitally over the gameport.
112 To compile this driver as a module, choose M here: the
113 module will be called interact.
115 config JOYSTICK_SIDEWINDER
116 tristate "Microsoft SideWinder digital joysticks and gamepads"
119 Say Y here if you have a Microsoft controller using the Digital
120 Overdrive protocol over PC gameport.
122 To compile this driver as a module, choose M here: the
123 module will be called sidewinder.
126 tristate "ThrustMaster DirectConnect joysticks and gamepads"
129 Say Y here if you have a ThrustMaster controller using the
130 DirectConnect (BSP) protocol over the PC gameport.
132 To compile this driver as a module, choose M here: the
133 module will be called tmdc.
135 source "drivers/input/joystick/iforce/Kconfig"
137 config JOYSTICK_WARRIOR
138 tristate "Logitech WingMan Warrior joystick"
141 Say Y here if you have a Logitech WingMan Warrior joystick connected
142 to your computer's serial port.
144 To compile this driver as a module, choose M here: the
145 module will be called warrior.
147 config JOYSTICK_MAGELLAN
148 tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers"
151 Say Y here if you have a Magellan or Space Mouse 6DOF controller
152 connected to your computer's serial port.
154 To compile this driver as a module, choose M here: the
155 module will be called magellan.
157 config JOYSTICK_SPACEORB
158 tristate "SpaceTec SpaceOrb/Avenger 6dof controllers"
161 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
162 controller connected to your computer's serial port.
164 To compile this driver as a module, choose M here: the
165 module will be called spaceorb.
167 config JOYSTICK_SPACEBALL
168 tristate "SpaceTec SpaceBall 6dof controllers"
171 Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX
172 controller connected to your computer's serial port. For the
173 SpaceBall 4000 USB model, use the USB HID driver.
175 To compile this driver as a module, choose M here: the
176 module will be called spaceball.
178 config JOYSTICK_STINGER
179 tristate "Gravis Stinger gamepad"
182 Say Y here if you have a Gravis Stinger connected to one of your
185 To compile this driver as a module, choose M here: the
186 module will be called stinger.
188 config JOYSTICK_TWIDJOY
189 tristate "Twiddler as a joystick"
192 Say Y here if you have a Handykey Twiddler connected to your
193 computer's serial port and want to use it as a joystick.
195 To compile this driver as a module, choose M here: the
196 module will be called twidjoy.
198 config JOYSTICK_ZHENHUA
199 tristate "5-byte Zhenhua RC transmitter"
203 Say Y here if you have a Zhen Hua PPM-4CH transmitter which is
204 supplied with a ready to fly micro electric indoor helicopters
205 such as EasyCopter, Lama, MiniCopter, DragonFly or Jabo and want
206 to use it via serial cable as a joystick.
208 To compile this driver as a module, choose M here: the
209 module will be called zhenhua.
212 tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads"
215 Say Y here if you have a Sega Master System gamepad, Sega Genesis
216 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
217 Commodore, Amstrad CPC joystick connected to your parallel port.
218 For more information on how to use the driver please read
219 <file:Documentation/input/devices/joystick-parport.rst>.
221 To compile this driver as a module, choose M here: the
222 module will be called db9.
224 config JOYSTICK_GAMECON
225 tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads"
227 select INPUT_FF_MEMLESS
229 Say Y here if you have a Nintendo Entertainment System gamepad,
230 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
231 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
232 Commodore, Amstrad CPC joystick connected to your parallel port.
233 For more information on how to use the driver please read
234 <file:Documentation/input/devices/joystick-parport.rst>.
236 To compile this driver as a module, choose M here: the
237 module will be called gamecon.
239 config JOYSTICK_TURBOGRAFX
240 tristate "Multisystem joysticks via TurboGraFX device"
243 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
244 and want to use it with Multisystem -- Atari, Amiga, Commodore,
245 Amstrad CPC joystick. For more information on how to use the driver
246 please read <file:Documentation/input/devices/joystick-parport.rst>.
248 To compile this driver as a module, choose M here: the
249 module will be called turbografx.
251 config JOYSTICK_AMIGA
252 tristate "Amiga joysticks"
255 Say Y here if you have an Amiga with a digital joystick connected
258 To compile this driver as a module, choose M here: the
259 module will be called amijoy.
261 config JOYSTICK_AS5011
262 tristate "Austria Microsystem AS5011 joystick"
265 Say Y here if you have an AS5011 digital joystick connected to your
268 To compile this driver as a module, choose M here: the
269 module will be called as5011.
271 config JOYSTICK_JOYDUMP
272 tristate "Gameport data dumper"
275 Say Y here if you want to dump data from your joystick into the system
276 log for debugging purposes. Say N if you are making a production
277 configuration or aren't sure.
279 To compile this driver as a module, choose M here: the
280 module will be called joydump.
283 tristate "X-Box gamepad support"
284 depends on USB_ARCH_HAS_HCD
287 Say Y here if you want to use the X-Box pad with your computer.
288 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
289 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
291 For information about how to connect the X-Box pad to USB, see
292 <file:Documentation/input/devices/xpad.rst>.
294 To compile this driver as a module, choose M here: the
295 module will be called xpad.
297 config JOYSTICK_XPAD_FF
298 bool "X-Box gamepad rumble support"
299 depends on JOYSTICK_XPAD && INPUT
300 select INPUT_FF_MEMLESS
302 Say Y here if you want to take advantage of xbox 360 rumble features.
304 config JOYSTICK_XPAD_LEDS
305 bool "LED Support for Xbox360 controller 'BigX' LED"
306 depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD)
308 This option enables support for the LED which surrounds the Big X on
311 config JOYSTICK_WALKERA0701
312 tristate "Walkera WK-0701 RC transmitter"
313 depends on HIGH_RES_TIMERS && PARPORT
315 Say Y or M here if you have a Walkera WK-0701 transmitter which is
316 supplied with a ready to fly Walkera helicopters such as HM36,
317 HM37, HM60 and want to use it via parport as a joystick. More
318 information is available: <file:Documentation/input/devices/walkera0701.rst>
320 To compile this driver as a module, choose M here: the
321 module will be called walkera0701.
323 config JOYSTICK_MAPLE
324 tristate "Dreamcast control pad"
327 Say Y here if you have a SEGA Dreamcast and want to use your
328 controller as a joystick.
330 Most Dreamcast users will say Y.
332 To compile this as a module choose M here: the module will be called
335 config JOYSTICK_PSXPAD_SPI
336 tristate "PlayStation 1/2 joypads via SPI interface"
339 Say Y here if you wish to connect PlayStation 1/2 joypads
342 To compile this driver as a module, choose M here: the
343 module will be called psxpad-spi.
345 config JOYSTICK_PSXPAD_SPI_FF
346 bool "PlayStation 1/2 joypads force feedback (rumble) support"
347 depends on JOYSTICK_PSXPAD_SPI
348 select INPUT_FF_MEMLESS
350 Say Y here if you want to take advantage of PlayStation 1/2
351 joypads rumble features.
353 To drive rumble motor a dedicated power supply is required.
356 tristate "PhoenixRC Flight Controller Adapter"
357 depends on USB_ARCH_HAS_HCD
360 Say Y here if you want to use the PhoenixRC Flight Controller Adapter.
362 To compile this driver as a module, choose M here: the
363 module will be called pxrc.
365 config JOYSTICK_FSIA6B
366 tristate "FlySky FS-iA6B RC Receiver"
369 Say Y here if you use a FlySky FS-i6 RC remote control along with the
370 FS-iA6B RC receiver as a joystick input device.
372 To compile this driver as a module, choose M here: the
373 module will be called fsia6b.