Kconfig 23 KB

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