Kconfig 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760
  1. #
  2. # Input core configuration
  3. #
  4. menuconfig INPUT_KEYBOARD
  5. bool "Keyboards"
  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_ADC
  13. tristate "ADC Ladder Buttons"
  14. depends on IIO
  15. select INPUT_POLLDEV
  16. help
  17. This driver implements support for buttons connected
  18. to an ADC using a resistor ladder.
  19. Say Y here if your device has such buttons connected to an ADC. Your
  20. board-specific setup logic must also provide a configuration data
  21. for mapping voltages to buttons.
  22. To compile this driver as a module, choose M here: the
  23. module will be called adc_keys.
  24. config KEYBOARD_ADP5520
  25. tristate "Keypad Support for ADP5520 PMIC"
  26. depends on PMIC_ADP5520
  27. help
  28. This option enables support for the keypad scan matrix
  29. on Analog Devices ADP5520 PMICs.
  30. To compile this driver as a module, choose M here: the module will
  31. be called adp5520-keys.
  32. config KEYBOARD_ADP5588
  33. tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
  34. depends on I2C
  35. help
  36. Say Y here if you want to use a ADP5588/87 attached to your
  37. system I2C bus.
  38. To compile this driver as a module, choose M here: the
  39. module will be called adp5588-keys.
  40. config KEYBOARD_ADP5589
  41. tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander"
  42. depends on I2C
  43. help
  44. Say Y here if you want to use a ADP5585/ADP5589 attached to your
  45. system I2C bus.
  46. To compile this driver as a module, choose M here: the
  47. module will be called adp5589-keys.
  48. config KEYBOARD_AMIGA
  49. tristate "Amiga keyboard"
  50. depends on AMIGA
  51. help
  52. Say Y here if you are running Linux on any AMIGA and have a keyboard
  53. attached.
  54. To compile this driver as a module, choose M here: the
  55. module will be called amikbd.
  56. config ATARI_KBD_CORE
  57. bool
  58. config KEYBOARD_ATARI
  59. tristate "Atari keyboard"
  60. depends on ATARI
  61. select ATARI_KBD_CORE
  62. help
  63. Say Y here if you are running Linux on any Atari and have a keyboard
  64. attached.
  65. To compile this driver as a module, choose M here: the
  66. module will be called atakbd.
  67. config KEYBOARD_ATKBD
  68. tristate "AT keyboard"
  69. default y
  70. select SERIO
  71. select SERIO_LIBPS2
  72. select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO
  73. select SERIO_GSCPS2 if GSC
  74. help
  75. Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
  76. you'll need this, unless you have a different type keyboard (USB, ADB
  77. or other). This also works for AT and PS/2 keyboards connected over a
  78. PS/2 to serial converter.
  79. If unsure, say Y.
  80. To compile this driver as a module, choose M here: the
  81. module will be called atkbd.
  82. config KEYBOARD_ATKBD_HP_KEYCODES
  83. bool "Use HP keyboard scancodes"
  84. depends on PARISC && KEYBOARD_ATKBD
  85. default y
  86. help
  87. Say Y here if you have a PA-RISC machine and want to use an AT or
  88. PS/2 keyboard, and your keyboard uses keycodes that are specific to
  89. PA-RISC keyboards.
  90. Say N if you use a standard keyboard.
  91. config KEYBOARD_ATKBD_RDI_KEYCODES
  92. bool "Use PrecisionBook keyboard scancodes"
  93. depends on KEYBOARD_ATKBD_HP_KEYCODES
  94. default n
  95. help
  96. If you have an RDI PrecisionBook, say Y here if you want to use its
  97. built-in keyboard (as opposed to an external keyboard).
  98. The PrecisionBook has five keys that conflict with those used by most
  99. AT and PS/2 keyboards. These are as follows:
  100. PrecisionBook Standard AT or PS/2
  101. F1 F12
  102. Left Ctrl Left Alt
  103. Caps Lock Left Ctrl
  104. Right Ctrl Caps Lock
  105. Left 102nd key (the key to the right of Left Shift)
  106. If you say N here, and use the PrecisionBook keyboard, then each key
  107. in the left-hand column will be interpreted as the corresponding key
  108. in the right-hand column.
  109. If you say Y here, and use an external keyboard, then each key in the
  110. right-hand column will be interpreted as the key shown in the
  111. left-hand column.
  112. config KEYBOARD_QT1070
  113. tristate "Atmel AT42QT1070 Touch Sensor Chip"
  114. depends on I2C
  115. help
  116. Say Y here if you want to use Atmel AT42QT1070 QTouch
  117. Sensor chip as input device.
  118. To compile this driver as a module, choose M here:
  119. the module will be called qt1070
  120. config KEYBOARD_QT2160
  121. tristate "Atmel AT42QT2160 Touch Sensor Chip"
  122. depends on I2C
  123. help
  124. If you say yes here you get support for Atmel AT42QT2160 Touch
  125. Sensor chip as a keyboard input.
  126. This driver can also be built as a module. If so, the module
  127. will be called qt2160.
  128. config KEYBOARD_CLPS711X
  129. tristate "CLPS711X Keypad support"
  130. depends on OF_GPIO && (ARCH_CLPS711X || COMPILE_TEST)
  131. select INPUT_MATRIXKMAP
  132. select INPUT_POLLDEV
  133. help
  134. Say Y here to enable the matrix keypad on the Cirrus Logic
  135. CLPS711X CPUs.
  136. To compile this driver as a module, choose M here: the
  137. module will be called clps711x-keypad.
  138. config KEYBOARD_DLINK_DIR685
  139. tristate "D-Link DIR-685 touchkeys support"
  140. depends on I2C
  141. default ARCH_GEMINI
  142. help
  143. If you say yes here you get support for the D-Link DIR-685
  144. touchkeys.
  145. To compile this driver as a module, choose M here: the
  146. module will be called dlink-dir685-touchkeys.
  147. config KEYBOARD_LKKBD
  148. tristate "DECstation/VAXstation LK201/LK401 keyboard"
  149. select SERIO
  150. help
  151. Say Y here if you want to use a LK201 or LK401 style serial
  152. keyboard. This keyboard is also useable on PCs if you attach
  153. it with the inputattach program. The connector pinout is
  154. described within lkkbd.c.
  155. To compile this driver as a module, choose M here: the
  156. module will be called lkkbd.
  157. config KEYBOARD_EP93XX
  158. tristate "EP93xx Matrix Keypad support"
  159. depends on ARCH_EP93XX
  160. select INPUT_MATRIXKMAP
  161. help
  162. Say Y here to enable the matrix keypad on the Cirrus EP93XX.
  163. To compile this driver as a module, choose M here: the
  164. module will be called ep93xx_keypad.
  165. config KEYBOARD_GPIO
  166. tristate "GPIO Buttons"
  167. depends on GPIOLIB || COMPILE_TEST
  168. help
  169. This driver implements support for buttons connected
  170. to GPIO pins of various CPUs (and some other chips).
  171. Say Y here if your device has buttons connected
  172. directly to such GPIO pins. Your board-specific
  173. setup logic must also provide a platform device,
  174. with configuration data saying which GPIOs are used.
  175. To compile this driver as a module, choose M here: the
  176. module will be called gpio_keys.
  177. config KEYBOARD_GPIO_POLLED
  178. tristate "Polled GPIO buttons"
  179. depends on GPIOLIB
  180. select INPUT_POLLDEV
  181. help
  182. This driver implements support for buttons connected
  183. to GPIO pins that are not capable of generating interrupts.
  184. Say Y here if your device has buttons connected
  185. directly to such GPIO pins. Your board-specific
  186. setup logic must also provide a platform device,
  187. with configuration data saying which GPIOs are used.
  188. To compile this driver as a module, choose M here: the
  189. module will be called gpio_keys_polled.
  190. config KEYBOARD_TCA6416
  191. tristate "TCA6416/TCA6408A Keypad Support"
  192. depends on I2C
  193. help
  194. This driver implements basic keypad functionality
  195. for keys connected through TCA6416/TCA6408A IO expanders.
  196. Say Y here if your device has keys connected to
  197. TCA6416/TCA6408A IO expander. Your board-specific setup logic
  198. must also provide pin-mask details(of which TCA6416 pins
  199. are used for keypad).
  200. If enabled the entire TCA6416 device will be managed through
  201. this driver.
  202. To compile this driver as a module, choose M here: the
  203. module will be called tca6416_keypad.
  204. config KEYBOARD_TCA8418
  205. tristate "TCA8418 Keypad Support"
  206. depends on I2C
  207. select INPUT_MATRIXKMAP
  208. help
  209. This driver implements basic keypad functionality
  210. for keys connected through TCA8418 keypad decoder.
  211. Say Y here if your device has keys connected to
  212. TCA8418 keypad decoder.
  213. If enabled the complete TCA8418 device will be managed through
  214. this driver.
  215. To compile this driver as a module, choose M here: the
  216. module will be called tca8418_keypad.
  217. config KEYBOARD_MATRIX
  218. tristate "GPIO driven matrix keypad support"
  219. depends on GPIOLIB || COMPILE_TEST
  220. select INPUT_MATRIXKMAP
  221. help
  222. Enable support for GPIO driven matrix keypad.
  223. To compile this driver as a module, choose M here: the
  224. module will be called matrix_keypad.
  225. config KEYBOARD_HIL_OLD
  226. tristate "HP HIL keyboard support (simple driver)"
  227. depends on GSC || HP300
  228. default y
  229. help
  230. The "Human Interface Loop" is a older, 8-channel USB-like
  231. controller used in several Hewlett Packard models. This driver
  232. was adapted from the one written for m68k/hp300, and implements
  233. support for a keyboard attached to the HIL port, but not for
  234. any other types of HIL input devices like mice or tablets.
  235. However, it has been thoroughly tested and is stable.
  236. If you want full HIL support including support for multiple
  237. keyboards, mice, and tablets, you have to enable the
  238. "HP System Device Controller i8042 Support" in the input/serio
  239. submenu.
  240. config KEYBOARD_HIL
  241. tristate "HP HIL keyboard/pointer support"
  242. depends on GSC || HP300
  243. default y
  244. select HP_SDC
  245. select HIL_MLC
  246. select SERIO
  247. help
  248. The "Human Interface Loop" is a older, 8-channel USB-like
  249. controller used in several Hewlett Packard models.
  250. This driver implements support for HIL-keyboards and pointing
  251. devices (mice, tablets, touchscreens) attached
  252. to your machine, so normally you should say Y here.
  253. config KEYBOARD_HP6XX
  254. tristate "HP Jornada 6xx keyboard"
  255. depends on SH_HP6XX
  256. select INPUT_POLLDEV
  257. help
  258. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  259. support the built-in keyboard.
  260. To compile this driver as a module, choose M here: the
  261. module will be called jornada680_kbd.
  262. config KEYBOARD_HP7XX
  263. tristate "HP Jornada 7xx keyboard"
  264. depends on SA1100_JORNADA720_SSP && SA1100_SSP
  265. help
  266. Say Y here if you have a HP Jornada 710/720/728 and want to
  267. support the built-in keyboard.
  268. To compile this driver as a module, choose M here: the
  269. module will be called jornada720_kbd.
  270. config KEYBOARD_LM8323
  271. tristate "LM8323 keypad chip"
  272. depends on I2C
  273. depends on LEDS_CLASS
  274. help
  275. If you say yes here you get support for the National Semiconductor
  276. LM8323 keypad controller.
  277. To compile this driver as a module, choose M here: the
  278. module will be called lm8323.
  279. config KEYBOARD_LM8333
  280. tristate "LM8333 keypad chip"
  281. depends on I2C
  282. select INPUT_MATRIXKMAP
  283. help
  284. If you say yes here you get support for the National Semiconductor
  285. LM8333 keypad controller.
  286. To compile this driver as a module, choose M here: the
  287. module will be called lm8333.
  288. config KEYBOARD_LOCOMO
  289. tristate "LoCoMo Keyboard Support"
  290. depends on SHARP_LOCOMO
  291. help
  292. Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
  293. To compile this driver as a module, choose M here: the
  294. module will be called locomokbd.
  295. config KEYBOARD_LPC32XX
  296. tristate "LPC32XX matrix key scanner support"
  297. depends on ARCH_LPC32XX && OF
  298. select INPUT_MATRIXKMAP
  299. help
  300. Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
  301. connected to a key matrix.
  302. To compile this driver as a module, choose M here: the
  303. module will be called lpc32xx-keys.
  304. config KEYBOARD_MAPLE
  305. tristate "Maple bus keyboard"
  306. depends on SH_DREAMCAST && MAPLE
  307. help
  308. Say Y here if you have a Dreamcast console running Linux and have
  309. a keyboard attached to its Maple bus.
  310. To compile this driver as a module, choose M here: the
  311. module will be called maple_keyb.
  312. config KEYBOARD_MAX7359
  313. tristate "Maxim MAX7359 Key Switch Controller"
  314. select INPUT_MATRIXKMAP
  315. depends on I2C
  316. help
  317. If you say yes here you get support for the Maxim MAX7359 Key
  318. Switch Controller chip. This providers microprocessors with
  319. management of up to 64 key switches
  320. To compile this driver as a module, choose M here: the
  321. module will be called max7359_keypad.
  322. config KEYBOARD_MCS
  323. tristate "MELFAS MCS Touchkey"
  324. depends on I2C
  325. help
  326. Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
  327. chip in your system.
  328. If unsure, say N.
  329. To compile this driver as a module, choose M here: the
  330. module will be called mcs_touchkey.
  331. config KEYBOARD_MPR121
  332. tristate "Freescale MPR121 Touchkey"
  333. depends on I2C
  334. help
  335. Say Y here if you have Freescale MPR121 touchkey controller
  336. chip in your system.
  337. If unsure, say N.
  338. To compile this driver as a module, choose M here: the
  339. module will be called mpr121_touchkey.
  340. config KEYBOARD_SNVS_PWRKEY
  341. tristate "IMX SNVS Power Key Driver"
  342. depends on SOC_IMX6SX
  343. depends on OF
  344. help
  345. This is the snvs powerkey driver for the Freescale i.MX application
  346. processors that are newer than i.MX6 SX.
  347. To compile this driver as a module, choose M here; the
  348. module will be called snvs_pwrkey.
  349. config KEYBOARD_IMX
  350. tristate "IMX keypad support"
  351. depends on ARCH_MXC
  352. select INPUT_MATRIXKMAP
  353. help
  354. Enable support for IMX keypad port.
  355. To compile this driver as a module, choose M here: the
  356. module will be called imx_keypad.
  357. config KEYBOARD_NEWTON
  358. tristate "Newton keyboard"
  359. select SERIO
  360. help
  361. Say Y here if you have a Newton keyboard on a serial port.
  362. To compile this driver as a module, choose M here: the
  363. module will be called newtonkbd.
  364. config KEYBOARD_NOMADIK
  365. tristate "ST-Ericsson Nomadik SKE keyboard"
  366. depends on (ARCH_NOMADIK || ARCH_U8500)
  367. select INPUT_MATRIXKMAP
  368. help
  369. Say Y here if you want to use a keypad provided on the SKE controller
  370. used on the Ux500 and Nomadik platforms
  371. To compile this driver as a module, choose M here: the
  372. module will be called nmk-ske-keypad.
  373. config KEYBOARD_NSPIRE
  374. tristate "TI-NSPIRE built-in keyboard"
  375. depends on ARCH_NSPIRE && OF
  376. select INPUT_MATRIXKMAP
  377. help
  378. Say Y here if you want to use the built-in keypad on TI-NSPIRE.
  379. To compile this driver as a module, choose M here: the
  380. module will be called nspire-keypad.
  381. config KEYBOARD_TEGRA
  382. tristate "NVIDIA Tegra internal matrix keyboard controller support"
  383. depends on ARCH_TEGRA && OF
  384. select INPUT_MATRIXKMAP
  385. help
  386. Say Y here if you want to use a matrix keyboard connected directly
  387. to the internal keyboard controller on Tegra SoCs.
  388. To compile this driver as a module, choose M here: the
  389. module will be called tegra-kbc.
  390. config KEYBOARD_OPENCORES
  391. tristate "OpenCores Keyboard Controller"
  392. depends on HAS_IOMEM
  393. help
  394. Say Y here if you want to use the OpenCores Keyboard Controller
  395. http://www.opencores.org/project,keyboardcontroller
  396. To compile this driver as a module, choose M here; the
  397. module will be called opencores-kbd.
  398. config KEYBOARD_PXA27x
  399. tristate "PXA27x/PXA3xx keypad support"
  400. depends on PXA27x || PXA3xx || ARCH_MMP
  401. select INPUT_MATRIXKMAP
  402. help
  403. Enable support for PXA27x/PXA3xx keypad controller.
  404. To compile this driver as a module, choose M here: the
  405. module will be called pxa27x_keypad.
  406. config KEYBOARD_PXA930_ROTARY
  407. tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
  408. depends on CPU_PXA930 || CPU_PXA935
  409. help
  410. Enable support for PXA930/PXA935 Enhanced Rotary Controller.
  411. To compile this driver as a module, choose M here: the
  412. module will be called pxa930_rotary.
  413. config KEYBOARD_PMIC8XXX
  414. tristate "Qualcomm PMIC8XXX keypad support"
  415. depends on MFD_PM8XXX
  416. select INPUT_MATRIXKMAP
  417. help
  418. Say Y here if you want to enable the driver for the PMIC8XXX
  419. keypad provided as a reference design from Qualcomm. This is intended
  420. to support upto 18x8 matrix based keypad design.
  421. To compile this driver as a module, choose M here: the module will
  422. be called pmic8xxx-keypad.
  423. config KEYBOARD_SAMSUNG
  424. tristate "Samsung keypad support"
  425. depends on HAVE_CLK
  426. select INPUT_MATRIXKMAP
  427. help
  428. Say Y here if you want to use the keypad on your Samsung mobile
  429. device.
  430. To compile this driver as a module, choose M here: the
  431. module will be called samsung-keypad.
  432. config KEYBOARD_GOLDFISH_EVENTS
  433. depends on GOLDFISH || COMPILE_TEST
  434. tristate "Generic Input Event device for Goldfish"
  435. help
  436. Say Y here to get an input event device for the Goldfish virtual
  437. device emulator.
  438. To compile this driver as a module, choose M here: the
  439. module will be called goldfish-events.
  440. config KEYBOARD_STOWAWAY
  441. tristate "Stowaway keyboard"
  442. select SERIO
  443. help
  444. Say Y here if you have a Stowaway keyboard on a serial port.
  445. Stowaway compatible keyboards like Dicota Input-PDA keyboard
  446. are also supported by this driver.
  447. To compile this driver as a module, choose M here: the
  448. module will be called stowaway.
  449. config KEYBOARD_ST_KEYSCAN
  450. tristate "STMicroelectronics keyscan support"
  451. depends on ARCH_STI || COMPILE_TEST
  452. select INPUT_MATRIXKMAP
  453. help
  454. Say Y here if you want to use a keypad attached to the keyscan block
  455. on some STMicroelectronics SoC devices.
  456. To compile this driver as a module, choose M here: the
  457. module will be called st-keyscan.
  458. config KEYBOARD_SUNKBD
  459. tristate "Sun Type 4 and Type 5 keyboard"
  460. select SERIO
  461. help
  462. Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
  463. connected either to the Sun keyboard connector or to an serial
  464. (RS-232) port via a simple adapter.
  465. To compile this driver as a module, choose M here: the
  466. module will be called sunkbd.
  467. config KEYBOARD_SH_KEYSC
  468. tristate "SuperH KEYSC keypad support"
  469. depends on ARCH_SHMOBILE || COMPILE_TEST
  470. help
  471. Say Y here if you want to use a keypad attached to the KEYSC block
  472. on SuperH processors such as sh7722 and sh7343.
  473. To compile this driver as a module, choose M here: the
  474. module will be called sh_keysc.
  475. config KEYBOARD_STMPE
  476. tristate "STMPE keypad support"
  477. depends on MFD_STMPE
  478. depends on OF
  479. select INPUT_MATRIXKMAP
  480. help
  481. Say Y here if you want to use the keypad controller on STMPE I/O
  482. expanders.
  483. To compile this driver as a module, choose M here: the module will be
  484. called stmpe-keypad.
  485. config KEYBOARD_SUN4I_LRADC
  486. tristate "Allwinner sun4i low res adc attached tablet keys support"
  487. depends on ARCH_SUNXI
  488. help
  489. This selects support for the Allwinner low res adc attached tablet
  490. keys found on Allwinner sunxi SoCs.
  491. To compile this driver as a module, choose M here: the
  492. module will be called sun4i-lradc-keys.
  493. config KEYBOARD_DAVINCI
  494. tristate "TI DaVinci Key Scan"
  495. depends on ARCH_DAVINCI_DM365
  496. help
  497. Say Y to enable keypad module support for the TI DaVinci
  498. platforms (DM365).
  499. To compile this driver as a module, choose M here: the
  500. module will be called davinci_keyscan.
  501. config KEYBOARD_IPAQ_MICRO
  502. tristate "Buttons on Micro SoC (iPaq h3100,h3600,h3700)"
  503. depends on MFD_IPAQ_MICRO
  504. help
  505. Say Y to enable support for the buttons attached to
  506. Micro peripheral controller on iPAQ h3100/h3600/h3700
  507. To compile this driver as a module, choose M here: the
  508. module will be called ipaq-micro-keys.
  509. config KEYBOARD_OMAP
  510. tristate "TI OMAP keypad support"
  511. depends on ARCH_OMAP1
  512. select INPUT_MATRIXKMAP
  513. help
  514. Say Y here if you want to use the OMAP keypad.
  515. To compile this driver as a module, choose M here: the
  516. module will be called omap-keypad.
  517. config KEYBOARD_OMAP4
  518. tristate "TI OMAP4+ keypad support"
  519. depends on OF || ARCH_OMAP2PLUS
  520. select INPUT_MATRIXKMAP
  521. help
  522. Say Y here if you want to use the OMAP4+ keypad.
  523. To compile this driver as a module, choose M here: the
  524. module will be called omap4-keypad.
  525. config KEYBOARD_SPEAR
  526. tristate "ST SPEAR keyboard support"
  527. depends on PLAT_SPEAR
  528. select INPUT_MATRIXKMAP
  529. help
  530. Say Y here if you want to use the SPEAR keyboard.
  531. To compile this driver as a module, choose M here: the
  532. module will be called spear-keboard.
  533. config KEYBOARD_TC3589X
  534. tristate "TC3589X Keypad support"
  535. depends on MFD_TC3589X
  536. select INPUT_MATRIXKMAP
  537. help
  538. Say Y here if you want to use the keypad controller on
  539. TC35892/3 I/O expander.
  540. To compile this driver as a module, choose M here: the
  541. module will be called tc3589x-keypad.
  542. config KEYBOARD_TM2_TOUCHKEY
  543. tristate "TM2 touchkey support"
  544. depends on I2C
  545. depends on LEDS_CLASS
  546. help
  547. Say Y here to enable device driver for tm2-touchkey with
  548. LED control for the Exynos5433 TM2 board.
  549. To compile this driver as a module, choose M here.
  550. module will be called tm2-touchkey.
  551. config KEYBOARD_TWL4030
  552. tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
  553. depends on TWL4030_CORE
  554. select INPUT_MATRIXKMAP
  555. help
  556. Say Y here if your board use the keypad controller on
  557. TWL4030 family chips. It's safe to say enable this
  558. even on boards that don't use the keypad controller.
  559. To compile this driver as a module, choose M here: the
  560. module will be called twl4030_keypad.
  561. config KEYBOARD_XTKBD
  562. tristate "XT keyboard"
  563. select SERIO
  564. help
  565. Say Y here if you want to use the old IBM PC/XT keyboard (or
  566. compatible) on your system. This is only possible with a
  567. parallel port keyboard adapter, you cannot connect it to the
  568. keyboard port on a PC that runs Linux.
  569. To compile this driver as a module, choose M here: the
  570. module will be called xtkbd.
  571. config KEYBOARD_W90P910
  572. tristate "W90P910 Matrix Keypad support"
  573. depends on ARCH_W90X900
  574. select INPUT_MATRIXKMAP
  575. help
  576. Say Y here to enable the matrix keypad on evaluation board
  577. based on W90P910.
  578. To compile this driver as a module, choose M here: the
  579. module will be called w90p910_keypad.
  580. config KEYBOARD_CROS_EC
  581. tristate "ChromeOS EC keyboard"
  582. select INPUT_MATRIXKMAP
  583. depends on MFD_CROS_EC
  584. help
  585. Say Y here to enable the matrix keyboard used by ChromeOS devices
  586. and implemented on the ChromeOS EC. You must enable one bus option
  587. (CROS_EC_I2C or CROS_EC_SPI) to use this.
  588. To compile this driver as a module, choose M here: the
  589. module will be called cros_ec_keyb.
  590. config KEYBOARD_CAP11XX
  591. tristate "Microchip CAP11XX based touch sensors"
  592. depends on OF && I2C
  593. select REGMAP_I2C
  594. help
  595. Say Y here to enable the CAP11XX touch sensor driver.
  596. To compile this driver as a module, choose M here: the
  597. module will be called cap11xx.
  598. config KEYBOARD_BCM
  599. tristate "Broadcom keypad driver"
  600. depends on OF && HAVE_CLK
  601. select INPUT_MATRIXKMAP
  602. default ARCH_BCM_CYGNUS
  603. help
  604. Say Y here if you want to use Broadcom keypad.
  605. To compile this driver as a module, choose M here: the
  606. module will be called bcm-keypad.
  607. config KEYBOARD_MTK_PMIC
  608. tristate "MediaTek PMIC keys support"
  609. depends on MFD_MT6397
  610. help
  611. Say Y here if you want to use the pmic keys (powerkey/homekey).
  612. To compile this driver as a module, choose M here: the
  613. module will be called pmic-keys.
  614. endif