Kconfig 13 KB

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