Kconfig 12 KB

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