Kconfig 23 KB

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