Kconfig 18 KB

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