Kconfig - OpenGrok cross reference for /openbmc/linux/drivers/input/joystick/Kconfig

1 # SPDX-License-Identifier: GPL-2.0-only
7 	depends on !UML
11 	  and the list of supported devices will be displayed. This option
12 	  doesn't affect the kernel.
14 	  Please read the file <file:Documentation/input/joydev/joystick.rst> which
23 	  Say Y here if you have a joystick that connects to the PC
24 	  gameport. In addition to the usual PC analog joystick, this driver
30 	  Please read the file <file:Documentation/input/joydev/joystick.rst> which
33 	  To compile this driver as a module, choose M here: the
40 	  Say Y here if you have an FPGaming or MadCatz controller using the
41 	  A3D protocol over the PC gameport.
43 	  To compile this driver as a module, choose M here: the
48 	depends on IIO
54 	  To compile this driver as a module, choose M here: the
55 	  module will be called adc-joystick.
60 	depends on ADI!=m # avoid module name conflict
62 	  Say Y here if you have a Logitech controller using the ADI
63 	  protocol over the PC gameport.
65 	  To compile this driver as a module, choose M here: the
74 	  To compile this driver as a module, choose M here: the
84 	  To compile this driver as a module, choose M here: the
91 	  Say Y here if you have a Gravis controller using the GrIP protocol
92 	  over the PC gameport.
94 	  To compile this driver as a module, choose M here: the
101 	  Say Y here if you have the original Gravis GrIP MultiPort, a hub
102 	  that connects to the gameport and you connect gamepads to it.
104 	  To compile this driver as a module, choose M here: the
112 	  protocol over the PC gameport.
114 	  To compile this driver as a module, choose M here: the
122 	  communicating digitally over the gameport.
124 	  To compile this driver as a module, choose M here: the
131 	  Say Y here if you have a Microsoft controller using the Digital
134 	  To compile this driver as a module, choose M here: the
141 	  Say Y here if you have a ThrustMaster controller using the
142 	  DirectConnect (BSP) protocol over the PC gameport.
144 	  To compile this driver as a module, choose M here: the
156 	  To compile this driver as a module, choose M here: the
166 	  To compile this driver as a module, choose M here: the
176 	  To compile this driver as a module, choose M here: the
184 	  controller connected to your computer's serial port. For the
185 	  SpaceBall 4000 USB model, use the USB HID driver.
187 	  To compile this driver as a module, choose M here: the
197 	  To compile this driver as a module, choose M here: the
207 	  To compile this driver as a module, choose M here: the
211 	tristate "5-byte Zhenhua RC transmitter"
215 	  Say Y here if you have a Zhen Hua PPM-4CH transmitter which is
216 	  supplied with a ready to fly micro electric indoor helicopters
220 	  To compile this driver as a module, choose M here: the
225 	depends on PARPORT
228 	  gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
230 	  For more information on how to use the driver please read
231 	  <file:Documentation/input/devices/joystick-parport.rst>.
233 	  To compile this driver as a module, choose M here: the
238 	depends on PARPORT
243 	  Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
245 	  For more information on how to use the driver please read
246 	  <file:Documentation/input/devices/joystick-parport.rst>.
248 	  To compile this driver as a module, choose M here: the
253 	depends on PARPORT
255 	  Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
256 	  and want to use it with Multisystem -- Atari, Amiga, Commodore,
257 	  Amstrad CPC joystick. For more information on how to use the driver
258 	  please read <file:Documentation/input/devices/joystick-parport.rst>.
260 	  To compile this driver as a module, choose M here: the
265 	depends on AMIGA
270 	  To compile this driver as a module, choose M here: the
275 	depends on I2C
280 	  To compile this driver as a module, choose M here: the
287 	  Say Y here if you want to dump data from your joystick into the system
291 	  To compile this driver as a module, choose M here: the
296 	depends on USB_ARCH_HAS_HCD
303 	  For information about how to connect the Xbox pad to USB, see
306 	  To compile this driver as a module, choose M here: the
311 	depends on JOYSTICK_XPAD && INPUT
317 	bool "LED Support for the Xbox 360 controller Guide button"
318 	depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD)
320 	  This option enables support for the LED which surrounds the Big X on
324 	tristate "Walkera WK-0701 RC transmitter"
325 	depends on HIGH_RES_TIMERS && PARPORT
327 	  Say Y or M here if you have a Walkera WK-0701 transmitter which is
328 	  supplied with a ready to fly Walkera helicopters such as HM36,
332 	  To compile this driver as a module, choose M here: the
337 	depends on MAPLE
344 	  To compile this as a module choose M here: the module will be called
349 	depends on SPI
354 	  To compile this driver as a module, choose M here: the
355 	  module will be called psxpad-spi.
359 	depends on JOYSTICK_PSXPAD_SPI
369 	depends on USB_ARCH_HAS_HCD
372 	  Say Y here if you want to use the PhoenixRC Flight Controller Adapter.
374 	  To compile this driver as a module, choose M here: the
379 	depends on I2C
381 	  Say Y here if you want to use the SparkFun Qwiic Joystick.
383 	  To compile this driver as a module, choose M here: the
384 	  module will be called qwiic-joystick.
387 	tristate "FlySky FS-iA6B RC Receiver"
390 	  Say Y here if you use a FlySky FS-i6 RC remote control along with the
391 	  FS-iA6B RC receiver as a joystick input device.
393 	  To compile this driver as a module, choose M here: the
398 	depends on MACH_NINTENDO64
400 	  Say Y here if you want enable support for the four
401 	  built-in controller ports on the Nintendo 64 console.
405 	depends on INPUT && I2C
406 	depends on HAS_IOMEM
409 	  Say Y here if you want to enable the driver for the
410 	  the Raspberry Pi Sense HAT.
412 	  To compile this driver as a module, choose M here: the