xref: /linux-6.15/drivers/input/joystick/Kconfig (revision 4f73bc4d) 
1#
2# Joystick driver configuration
3#
4menuconfig 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
15if INPUT_JOYSTICK
16
17config 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
34config 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
44config 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
54config 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
63config 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
73config 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
83config 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
93config 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
103config 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
113config 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
123config 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
133source "drivers/input/joystick/iforce/Kconfig"
134
135if TTY
136
137config JOYSTICK_WARRIOR
138	tristate "Logitech WingMan Warrior joystick"
139	select SERIO
140	help
141	  Say Y here if you have a Logitech WingMan Warrior joystick connected
142	  to your computer's serial port.
143
144	  To compile this driver as a module, choose M here: the
145	  module will be called warrior.
146
147config JOYSTICK_MAGELLAN
148	tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers"
149	select SERIO
150	help
151	  Say Y here if you have a Magellan or Space Mouse 6DOF controller
152	  connected to your computer's serial port.
153
154	  To compile this driver as a module, choose M here: the
155	  module will be called magellan.
156
157config JOYSTICK_SPACEORB
158	tristate "SpaceTec SpaceOrb/Avenger 6dof controllers"
159	select SERIO
160	help
161	  Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
162	  controller connected to your computer's serial port.
163
164	  To compile this driver as a module, choose M here: the
165	  module will be called spaceorb.
166
167config JOYSTICK_SPACEBALL
168	tristate "SpaceTec SpaceBall 6dof controllers"
169	select SERIO
170	help
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.
174
175	  To compile this driver as a module, choose M here: the
176	  module will be called spaceball.
177
178config JOYSTICK_STINGER
179	tristate "Gravis Stinger gamepad"
180	select SERIO
181	help
182	  Say Y here if you have a Gravis Stinger connected to one of your
183	  serial ports.
184
185	  To compile this driver as a module, choose M here: the
186	  module will be called stinger.
187
188config JOYSTICK_TWIDJOY
189	tristate "Twiddler as a joystick"
190	select SERIO
191	help
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.
194
195	  To compile this driver as a module, choose M here: the
196	  module will be called twidjoy.
197
198config JOYSTICK_ZHENHUA
199	tristate "5-byte Zhenhua RC transmitter"
200	select SERIO
201	help
202	  Say Y here if you have a Zhen Hua PPM-4CH transmitter which is
203	  supplied with a ready to fly micro electric indoor helicopters
204	  such as EasyCopter, Lama, MiniCopter, DragonFly or Jabo and want
205	  to use it via serial cable as a joystick.
206
207	  To compile this driver as a module, choose M here: the
208	  module will be called zhenhua.
209
210endif # TTY
211
212config JOYSTICK_DB9
213	tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads"
214	depends on PARPORT
215	help
216	  Say Y here if you have a Sega Master System gamepad, Sega Genesis
217	  gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
218	  Commodore, Amstrad CPC joystick connected to your parallel port.
219	  For more information on how to use the driver please read
220	  <file:Documentation/input/joystick-parport.txt>.
221
222	  To compile this driver as a module, choose M here: the
223	  module will be called db9.
224
225config JOYSTICK_GAMECON
226	tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads"
227	depends on PARPORT
228	select INPUT_FF_MEMLESS
229	---help---
230	  Say Y here if you have a Nintendo Entertainment System gamepad,
231	  Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
232	  Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
233	  Commodore, Amstrad CPC joystick connected to your parallel port.
234	  For more information on how to use the driver please read
235	  <file:Documentation/input/joystick-parport.txt>.
236
237	  To compile this driver as a module, choose M here: the
238	  module will be called gamecon.
239
240config JOYSTICK_TURBOGRAFX
241	tristate "Multisystem joysticks via TurboGraFX device"
242	depends on PARPORT
243	help
244	  Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
245	  and want to use it with Multisystem -- Atari, Amiga, Commodore,
246	  Amstrad CPC joystick. For more information on how to use the driver
247	  please read <file:Documentation/input/joystick-parport.txt>.
248
249	  To compile this driver as a module, choose M here: the
250	  module will be called turbografx.
251
252config JOYSTICK_AMIGA
253	tristate "Amiga joysticks"
254	depends on AMIGA
255	help
256	  Say Y here if you have an Amiga with a digital joystick connected
257	  to it.
258
259	  To compile this driver as a module, choose M here: the
260	  module will be called amijoy.
261
262config JOYSTICK_AS5011
263	tristate "Austria Microsystem AS5011 joystick"
264	depends on I2C
265	help
266	  Say Y here if you have an AS5011 digital joystick connected to your
267	  system.
268
269	  To compile this driver as a module, choose M here: the
270	  module will be called as5011.
271
272config JOYSTICK_JOYDUMP
273	tristate "Gameport data dumper"
274	select GAMEPORT
275	help
276	  Say Y here if you want to dump data from your joystick into the system
277	  log for debugging purposes. Say N if you are making a production
278	  configuration or aren't sure.
279
280	  To compile this driver as a module, choose M here: the
281	  module will be called joydump.
282
283config JOYSTICK_XPAD
284	tristate "X-Box gamepad support"
285	depends on USB_ARCH_HAS_HCD
286	select USB
287	help
288	  Say Y here if you want to use the X-Box pad with your computer.
289	  Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
290	  and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
291
292	  For information about how to connect the X-Box pad to USB, see
293	  <file:Documentation/input/xpad.txt>.
294
295	  To compile this driver as a module, choose M here: the
296	  module will be called xpad.
297
298config JOYSTICK_XPAD_FF
299	bool "X-Box gamepad rumble support"
300	depends on JOYSTICK_XPAD && INPUT
301	select INPUT_FF_MEMLESS
302	---help---
303	  Say Y here if you want to take advantage of xbox 360 rumble features.
304
305config JOYSTICK_XPAD_LEDS
306	bool "LED Support for Xbox360 controller 'BigX' LED"
307	depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD)
308	---help---
309	  This option enables support for the LED which surrounds the Big X on
310	  XBox 360 controller.
311
312config JOYSTICK_WALKERA0701
313	tristate "Walkera WK-0701 RC transmitter"
314	depends on HIGH_RES_TIMERS && PARPORT
315	help
316	  Say Y or M here if you have a Walkera WK-0701 transmitter which is
317	  supplied with a ready to fly Walkera helicopters such as HM36,
318	  HM37, HM60 and want to use it via parport as a joystick. More
319	  information is available: <file:Documentation/input/walkera0701.txt>
320
321	  To compile this driver as a module, choose M here: the
322	  module will be called walkera0701.
323
324config JOYSTICK_MAPLE
325	tristate "Dreamcast control pad"
326	depends on MAPLE
327	help
328	  Say Y here if you have a SEGA Dreamcast and want to use your
329	  controller as a joystick.
330
331	  Most Dreamcast users will say Y.
332
333	  To compile this as a module choose M here: the module will be called
334	  maplecontrol.
335
336endif
337