Kconfig 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533
  1. #
  2. # Input core configuration
  3. #
  4. menuconfig INPUT_KEYBOARD
  5. bool "Keyboards" if EXPERT || !X86
  6. default y
  7. help
  8. Say Y here, and a list of supported keyboards will be displayed.
  9. This option doesn't affect the kernel.
  10. If unsure, say Y.
  11. if INPUT_KEYBOARD
  12. config KEYBOARD_ADP5520
  13. tristate "Keypad Support for ADP5520 PMIC"
  14. depends on PMIC_ADP5520
  15. help
  16. This option enables support for the keypad scan matrix
  17. on Analog Devices ADP5520 PMICs.
  18. To compile this driver as a module, choose M here: the module will
  19. be called adp5520-keys.
  20. config KEYBOARD_ADP5588
  21. tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
  22. depends on I2C
  23. help
  24. Say Y here if you want to use a ADP5588/87 attached to your
  25. system I2C bus.
  26. To compile this driver as a module, choose M here: the
  27. module will be called adp5588-keys.
  28. config KEYBOARD_AMIGA
  29. tristate "Amiga keyboard"
  30. depends on AMIGA
  31. help
  32. Say Y here if you are running Linux on any AMIGA and have a keyboard
  33. attached.
  34. To compile this driver as a module, choose M here: the
  35. module will be called amikbd.
  36. config ATARI_KBD_CORE
  37. bool
  38. config KEYBOARD_ATARI
  39. tristate "Atari keyboard"
  40. depends on ATARI
  41. select ATARI_KBD_CORE
  42. help
  43. Say Y here if you are running Linux on any Atari and have a keyboard
  44. attached.
  45. To compile this driver as a module, choose M here: the
  46. module will be called atakbd.
  47. config KEYBOARD_ATKBD
  48. tristate "AT keyboard" if EXPERT || !X86
  49. default y
  50. select SERIO
  51. select SERIO_LIBPS2
  52. select SERIO_I8042 if X86
  53. select SERIO_GSCPS2 if GSC
  54. help
  55. Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
  56. you'll need this, unless you have a different type keyboard (USB, ADB
  57. or other). This also works for AT and PS/2 keyboards connected over a
  58. PS/2 to serial converter.
  59. If unsure, say Y.
  60. To compile this driver as a module, choose M here: the
  61. module will be called atkbd.
  62. config KEYBOARD_ATKBD_HP_KEYCODES
  63. bool "Use HP keyboard scancodes"
  64. depends on PARISC && KEYBOARD_ATKBD
  65. default y
  66. help
  67. Say Y here if you have a PA-RISC machine and want to use an AT or
  68. PS/2 keyboard, and your keyboard uses keycodes that are specific to
  69. PA-RISC keyboards.
  70. Say N if you use a standard keyboard.
  71. config KEYBOARD_ATKBD_RDI_KEYCODES
  72. bool "Use PrecisionBook keyboard scancodes"
  73. depends on KEYBOARD_ATKBD_HP_KEYCODES
  74. default n
  75. help
  76. If you have an RDI PrecisionBook, say Y here if you want to use its
  77. built-in keyboard (as opposed to an external keyboard).
  78. The PrecisionBook has five keys that conflict with those used by most
  79. AT and PS/2 keyboards. These are as follows:
  80. PrecisionBook Standard AT or PS/2
  81. F1 F12
  82. Left Ctrl Left Alt
  83. Caps Lock Left Ctrl
  84. Right Ctrl Caps Lock
  85. Left 102nd key (the key to the right of Left Shift)
  86. If you say N here, and use the PrecisionBook keyboard, then each key
  87. in the left-hand column will be interpreted as the corresponding key
  88. in the right-hand column.
  89. If you say Y here, and use an external keyboard, then each key in the
  90. right-hand column will be interpreted as the key shown in the
  91. left-hand column.
  92. config KEYBOARD_QT1070
  93. tristate "Atmel AT42QT1070 Touch Sensor Chip"
  94. depends on I2C
  95. help
  96. Say Y here if you want to use Atmel AT42QT1070 QTouch
  97. Sensor chip as input device.
  98. To compile this driver as a module, choose M here:
  99. the module will be called qt1070
  100. config KEYBOARD_QT2160
  101. tristate "Atmel AT42QT2160 Touch Sensor Chip"
  102. depends on I2C && EXPERIMENTAL
  103. help
  104. If you say yes here you get support for Atmel AT42QT2160 Touch
  105. Sensor chip as a keyboard input.
  106. This driver can also be built as a module. If so, the module
  107. will be called qt2160.
  108. config KEYBOARD_BFIN
  109. tristate "Blackfin BF54x keypad support"
  110. depends on (BF54x && !BF544)
  111. help
  112. Say Y here if you want to use the BF54x keypad.
  113. To compile this driver as a module, choose M here: the
  114. module will be called bf54x-keys.
  115. config KEYBOARD_LKKBD
  116. tristate "DECstation/VAXstation LK201/LK401 keyboard"
  117. select SERIO
  118. help
  119. Say Y here if you want to use a LK201 or LK401 style serial
  120. keyboard. This keyboard is also useable on PCs if you attach
  121. it with the inputattach program. The connector pinout is
  122. described within lkkbd.c.
  123. To compile this driver as a module, choose M here: the
  124. module will be called lkkbd.
  125. config KEYBOARD_EP93XX
  126. tristate "EP93xx Matrix Keypad support"
  127. depends on ARCH_EP93XX
  128. help
  129. Say Y here to enable the matrix keypad on the Cirrus EP93XX.
  130. To compile this driver as a module, choose M here: the
  131. module will be called ep93xx_keypad.
  132. config KEYBOARD_GPIO
  133. tristate "GPIO Buttons"
  134. depends on GENERIC_GPIO
  135. help
  136. This driver implements support for buttons connected
  137. to GPIO pins of various CPUs (and some other chips).
  138. Say Y here if your device has buttons connected
  139. directly to such GPIO pins. Your board-specific
  140. setup logic must also provide a platform device,
  141. with configuration data saying which GPIOs are used.
  142. To compile this driver as a module, choose M here: the
  143. module will be called gpio_keys.
  144. config KEYBOARD_GPIO_POLLED
  145. tristate "Polled GPIO buttons"
  146. depends on GENERIC_GPIO
  147. select INPUT_POLLDEV
  148. help
  149. This driver implements support for buttons connected
  150. to GPIO pins that are not capable of generating interrupts.
  151. Say Y here if your device has buttons connected
  152. directly to such GPIO pins. Your board-specific
  153. setup logic must also provide a platform device,
  154. with configuration data saying which GPIOs are used.
  155. To compile this driver as a module, choose M here: the
  156. module will be called gpio_keys_polled.
  157. config KEYBOARD_TCA6416
  158. tristate "TCA6416/TCA6408A Keypad Support"
  159. depends on I2C
  160. help
  161. This driver implements basic keypad functionality
  162. for keys connected through TCA6416/TCA6408A IO expanders.
  163. Say Y here if your device has keys connected to
  164. TCA6416/TCA6408A IO expander. Your board-specific setup logic
  165. must also provide pin-mask details(of which TCA6416 pins
  166. are used for keypad).
  167. If enabled the entire TCA6416 device will be managed through
  168. this driver.
  169. To compile this driver as a module, choose M here: the
  170. module will be called tca6416_keypad.
  171. config KEYBOARD_MATRIX
  172. tristate "GPIO driven matrix keypad support"
  173. depends on GENERIC_GPIO
  174. help
  175. Enable support for GPIO driven matrix keypad.
  176. To compile this driver as a module, choose M here: the
  177. module will be called matrix_keypad.
  178. config KEYBOARD_HIL_OLD
  179. tristate "HP HIL keyboard support (simple driver)"
  180. depends on GSC || HP300
  181. default y
  182. help
  183. The "Human Interface Loop" is a older, 8-channel USB-like
  184. controller used in several Hewlett Packard models. This driver
  185. was adapted from the one written for m68k/hp300, and implements
  186. support for a keyboard attached to the HIL port, but not for
  187. any other types of HIL input devices like mice or tablets.
  188. However, it has been thoroughly tested and is stable.
  189. If you want full HIL support including support for multiple
  190. keyboards, mice, and tablets, you have to enable the
  191. "HP System Device Controller i8042 Support" in the input/serio
  192. submenu.
  193. config KEYBOARD_HIL
  194. tristate "HP HIL keyboard/pointer support"
  195. depends on GSC || HP300
  196. default y
  197. select HP_SDC
  198. select HIL_MLC
  199. select SERIO
  200. help
  201. The "Human Interface Loop" is a older, 8-channel USB-like
  202. controller used in several Hewlett Packard models.
  203. This driver implements support for HIL-keyboards and pointing
  204. devices (mice, tablets, touchscreens) attached
  205. to your machine, so normally you should say Y here.
  206. config KEYBOARD_HP6XX
  207. tristate "HP Jornada 6xx keyboard"
  208. depends on SH_HP6XX
  209. select INPUT_POLLDEV
  210. help
  211. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  212. support the built-in keyboard.
  213. To compile this driver as a module, choose M here: the
  214. module will be called jornada680_kbd.
  215. config KEYBOARD_HP7XX
  216. tristate "HP Jornada 7xx keyboard"
  217. depends on SA1100_JORNADA720_SSP && SA1100_SSP
  218. help
  219. Say Y here if you have a HP Jornada 710/720/728 and want to
  220. support the built-in keyboard.
  221. To compile this driver as a module, choose M here: the
  222. module will be called jornada720_kbd.
  223. config KEYBOARD_LM8323
  224. tristate "LM8323 keypad chip"
  225. depends on I2C
  226. depends on LEDS_CLASS
  227. help
  228. If you say yes here you get support for the National Semiconductor
  229. LM8323 keypad controller.
  230. To compile this driver as a module, choose M here: the
  231. module will be called lm8323.
  232. config KEYBOARD_LOCOMO
  233. tristate "LoCoMo Keyboard Support"
  234. depends on SHARP_LOCOMO
  235. help
  236. Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
  237. To compile this driver as a module, choose M here: the
  238. module will be called locomokbd.
  239. config KEYBOARD_MAPLE
  240. tristate "Maple bus keyboard"
  241. depends on SH_DREAMCAST && MAPLE
  242. help
  243. Say Y here if you have a Dreamcast console running Linux and have
  244. a keyboard attached to its Maple bus.
  245. To compile this driver as a module, choose M here: the
  246. module will be called maple_keyb.
  247. config KEYBOARD_MAX7359
  248. tristate "Maxim MAX7359 Key Switch Controller"
  249. depends on I2C
  250. help
  251. If you say yes here you get support for the Maxim MAX7359 Key
  252. Switch Controller chip. This providers microprocessors with
  253. management of up to 64 key switches
  254. To compile this driver as a module, choose M here: the
  255. module will be called max7359_keypad.
  256. config KEYBOARD_MCS
  257. tristate "MELFAS MCS Touchkey"
  258. depends on I2C
  259. help
  260. Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
  261. chip in your system.
  262. If unsure, say N.
  263. To compile this driver as a module, choose M here: the
  264. module will be called mcs_touchkey.
  265. config KEYBOARD_IMX
  266. tristate "IMX keypad support"
  267. depends on ARCH_MXC
  268. help
  269. Enable support for IMX keypad port.
  270. To compile this driver as a module, choose M here: the
  271. module will be called imx_keypad.
  272. config KEYBOARD_NEWTON
  273. tristate "Newton keyboard"
  274. select SERIO
  275. help
  276. Say Y here if you have a Newton keyboard on a serial port.
  277. To compile this driver as a module, choose M here: the
  278. module will be called newtonkbd.
  279. config KEYBOARD_NOMADIK
  280. tristate "ST-Ericsson Nomadik SKE keyboard"
  281. depends on PLAT_NOMADIK
  282. help
  283. Say Y here if you want to use a keypad provided on the SKE controller
  284. used on the Ux500 and Nomadik platforms
  285. To compile this driver as a module, choose M here: the
  286. module will be called nmk-ske-keypad.
  287. config KEYBOARD_TEGRA
  288. tristate "NVIDIA Tegra internal matrix keyboard controller support"
  289. depends on ARCH_TEGRA
  290. help
  291. Say Y here if you want to use a matrix keyboard connected directly
  292. to the internal keyboard controller on Tegra SoCs.
  293. To compile this driver as a module, choose M here: the
  294. module will be called tegra-kbc.
  295. config KEYBOARD_OPENCORES
  296. tristate "OpenCores Keyboard Controller"
  297. help
  298. Say Y here if you want to use the OpenCores Keyboard Controller
  299. http://www.opencores.org/project,keyboardcontroller
  300. To compile this driver as a module, choose M here; the
  301. module will be called opencores-kbd.
  302. config KEYBOARD_PXA27x
  303. tristate "PXA27x/PXA3xx keypad support"
  304. depends on PXA27x || PXA3xx || ARCH_MMP
  305. help
  306. Enable support for PXA27x/PXA3xx keypad controller.
  307. To compile this driver as a module, choose M here: the
  308. module will be called pxa27x_keypad.
  309. config KEYBOARD_PXA930_ROTARY
  310. tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
  311. depends on CPU_PXA930 || CPU_PXA935
  312. help
  313. Enable support for PXA930/PXA935 Enhanced Rotary Controller.
  314. To compile this driver as a module, choose M here: the
  315. module will be called pxa930_rotary.
  316. config KEYBOARD_SAMSUNG
  317. tristate "Samsung keypad support"
  318. depends on SAMSUNG_DEV_KEYPAD
  319. help
  320. Say Y here if you want to use the Samsung keypad.
  321. To compile this driver as a module, choose M here: the
  322. module will be called samsung-keypad.
  323. config KEYBOARD_STOWAWAY
  324. tristate "Stowaway keyboard"
  325. select SERIO
  326. help
  327. Say Y here if you have a Stowaway keyboard on a serial port.
  328. Stowaway compatible keyboards like Dicota Input-PDA keyboard
  329. are also supported by this driver.
  330. To compile this driver as a module, choose M here: the
  331. module will be called stowaway.
  332. config KEYBOARD_SUNKBD
  333. tristate "Sun Type 4 and Type 5 keyboard"
  334. select SERIO
  335. help
  336. Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
  337. connected either to the Sun keyboard connector or to an serial
  338. (RS-232) port via a simple adapter.
  339. To compile this driver as a module, choose M here: the
  340. module will be called sunkbd.
  341. config KEYBOARD_SH_KEYSC
  342. tristate "SuperH KEYSC keypad support"
  343. depends on SUPERH || ARCH_SHMOBILE
  344. help
  345. Say Y here if you want to use a keypad attached to the KEYSC block
  346. on SuperH processors such as sh7722 and sh7343.
  347. To compile this driver as a module, choose M here: the
  348. module will be called sh_keysc.
  349. config KEYBOARD_STMPE
  350. tristate "STMPE keypad support"
  351. depends on MFD_STMPE
  352. help
  353. Say Y here if you want to use the keypad controller on STMPE I/O
  354. expanders.
  355. To compile this driver as a module, choose M here: the module will be
  356. called stmpe-keypad.
  357. config KEYBOARD_DAVINCI
  358. tristate "TI DaVinci Key Scan"
  359. depends on ARCH_DAVINCI_DM365
  360. help
  361. Say Y to enable keypad module support for the TI DaVinci
  362. platforms (DM365).
  363. To compile this driver as a module, choose M here: the
  364. module will be called davinci_keyscan.
  365. config KEYBOARD_OMAP
  366. tristate "TI OMAP keypad support"
  367. depends on (ARCH_OMAP1 || ARCH_OMAP2)
  368. help
  369. Say Y here if you want to use the OMAP keypad.
  370. To compile this driver as a module, choose M here: the
  371. module will be called omap-keypad.
  372. config KEYBOARD_OMAP4
  373. tristate "TI OMAP4 keypad support"
  374. depends on ARCH_OMAP4
  375. help
  376. Say Y here if you want to use the OMAP4 keypad.
  377. To compile this driver as a module, choose M here: the
  378. module will be called omap4-keypad.
  379. config KEYBOARD_SPEAR
  380. tristate "ST SPEAR keyboard support"
  381. depends on PLAT_SPEAR
  382. help
  383. Say Y here if you want to use the SPEAR keyboard.
  384. To compile this driver as a module, choose M here: the
  385. module will be called spear-keboard.
  386. config KEYBOARD_TC3589X
  387. tristate "TC3589X Keypad support"
  388. depends on MFD_TC3589X
  389. help
  390. Say Y here if you want to use the keypad controller on
  391. TC35892/3 I/O expander.
  392. To compile this driver as a module, choose M here: the
  393. module will be called tc3589x-keypad.
  394. config KEYBOARD_TNETV107X
  395. tristate "TI TNETV107X keypad support"
  396. depends on ARCH_DAVINCI_TNETV107X
  397. help
  398. Say Y here if you want to use the TNETV107X keypad.
  399. To compile this driver as a module, choose M here: the
  400. module will be called tnetv107x-keypad.
  401. config KEYBOARD_TWL4030
  402. tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
  403. depends on TWL4030_CORE
  404. help
  405. Say Y here if your board use the keypad controller on
  406. TWL4030 family chips. It's safe to say enable this
  407. even on boards that don't use the keypad controller.
  408. To compile this driver as a module, choose M here: the
  409. module will be called twl4030_keypad.
  410. config KEYBOARD_XTKBD
  411. tristate "XT keyboard"
  412. select SERIO
  413. help
  414. Say Y here if you want to use the old IBM PC/XT keyboard (or
  415. compatible) on your system. This is only possible with a
  416. parallel port keyboard adapter, you cannot connect it to the
  417. keyboard port on a PC that runs Linux.
  418. To compile this driver as a module, choose M here: the
  419. module will be called xtkbd.
  420. config KEYBOARD_W90P910
  421. tristate "W90P910 Matrix Keypad support"
  422. depends on ARCH_W90X900
  423. help
  424. Say Y here to enable the matrix keypad on evaluation board
  425. based on W90P910.
  426. To compile this driver as a module, choose M here: the
  427. module will be called w90p910_keypad.
  428. endif