Kconfig 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678
  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_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"
  57. default y
  58. select SERIO
  59. select SERIO_LIBPS2
  60. select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO
  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_CLPS711X
  124. tristate "CLPS711X Keypad support"
  125. depends on OF_GPIO && (ARCH_CLPS711X || COMPILE_TEST)
  126. select INPUT_MATRIXKMAP
  127. select INPUT_POLLDEV
  128. help
  129. Say Y here to enable the matrix keypad on the Cirrus Logic
  130. CLPS711X CPUs.
  131. To compile this driver as a module, choose M here: the
  132. module will be called clps711x-keypad.
  133. config KEYBOARD_LKKBD
  134. tristate "DECstation/VAXstation LK201/LK401 keyboard"
  135. select SERIO
  136. help
  137. Say Y here if you want to use a LK201 or LK401 style serial
  138. keyboard. This keyboard is also useable on PCs if you attach
  139. it with the inputattach program. The connector pinout is
  140. described within lkkbd.c.
  141. To compile this driver as a module, choose M here: the
  142. module will be called lkkbd.
  143. config KEYBOARD_EP93XX
  144. tristate "EP93xx Matrix Keypad support"
  145. depends on ARCH_EP93XX
  146. select INPUT_MATRIXKMAP
  147. help
  148. Say Y here to enable the matrix keypad on the Cirrus EP93XX.
  149. To compile this driver as a module, choose M here: the
  150. module will be called ep93xx_keypad.
  151. config KEYBOARD_GPIO
  152. tristate "GPIO Buttons"
  153. depends on GPIOLIB
  154. help
  155. This driver implements support for buttons connected
  156. to GPIO pins of various CPUs (and some other chips).
  157. Say Y here if your device has buttons connected
  158. directly to such GPIO pins. Your board-specific
  159. setup logic must also provide a platform device,
  160. with configuration data saying which GPIOs are used.
  161. To compile this driver as a module, choose M here: the
  162. module will be called gpio_keys.
  163. config KEYBOARD_GPIO_POLLED
  164. tristate "Polled GPIO buttons"
  165. depends on GPIOLIB
  166. select INPUT_POLLDEV
  167. help
  168. This driver implements support for buttons connected
  169. to GPIO pins that are not capable of generating interrupts.
  170. Say Y here if your device has buttons connected
  171. directly to such GPIO pins. Your board-specific
  172. setup logic must also provide a platform device,
  173. with configuration data saying which GPIOs are used.
  174. To compile this driver as a module, choose M here: the
  175. module will be called gpio_keys_polled.
  176. config KEYBOARD_TCA6416
  177. tristate "TCA6416/TCA6408A Keypad Support"
  178. depends on I2C
  179. help
  180. This driver implements basic keypad functionality
  181. for keys connected through TCA6416/TCA6408A IO expanders.
  182. Say Y here if your device has keys connected to
  183. TCA6416/TCA6408A IO expander. Your board-specific setup logic
  184. must also provide pin-mask details(of which TCA6416 pins
  185. are used for keypad).
  186. If enabled the entire TCA6416 device will be managed through
  187. this driver.
  188. To compile this driver as a module, choose M here: the
  189. module will be called tca6416_keypad.
  190. config KEYBOARD_TCA8418
  191. tristate "TCA8418 Keypad Support"
  192. depends on I2C
  193. select INPUT_MATRIXKMAP
  194. help
  195. This driver implements basic keypad functionality
  196. for keys connected through TCA8418 keypad decoder.
  197. Say Y here if your device has keys connected to
  198. TCA8418 keypad decoder.
  199. If enabled the complete TCA8418 device will be managed through
  200. this driver.
  201. To compile this driver as a module, choose M here: the
  202. module will be called tca8418_keypad.
  203. config KEYBOARD_MATRIX
  204. tristate "GPIO driven matrix keypad support"
  205. depends on GPIOLIB
  206. select INPUT_MATRIXKMAP
  207. help
  208. Enable support for GPIO driven matrix keypad.
  209. To compile this driver as a module, choose M here: the
  210. module will be called matrix_keypad.
  211. config KEYBOARD_HIL_OLD
  212. tristate "HP HIL keyboard support (simple driver)"
  213. depends on GSC || HP300
  214. default y
  215. help
  216. The "Human Interface Loop" is a older, 8-channel USB-like
  217. controller used in several Hewlett Packard models. This driver
  218. was adapted from the one written for m68k/hp300, and implements
  219. support for a keyboard attached to the HIL port, but not for
  220. any other types of HIL input devices like mice or tablets.
  221. However, it has been thoroughly tested and is stable.
  222. If you want full HIL support including support for multiple
  223. keyboards, mice, and tablets, you have to enable the
  224. "HP System Device Controller i8042 Support" in the input/serio
  225. submenu.
  226. config KEYBOARD_HIL
  227. tristate "HP HIL keyboard/pointer support"
  228. depends on GSC || HP300
  229. default y
  230. select HP_SDC
  231. select HIL_MLC
  232. select SERIO
  233. help
  234. The "Human Interface Loop" is a older, 8-channel USB-like
  235. controller used in several Hewlett Packard models.
  236. This driver implements support for HIL-keyboards and pointing
  237. devices (mice, tablets, touchscreens) attached
  238. to your machine, so normally you should say Y here.
  239. config KEYBOARD_HP6XX
  240. tristate "HP Jornada 6xx keyboard"
  241. depends on SH_HP6XX
  242. select INPUT_POLLDEV
  243. help
  244. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  245. support the built-in keyboard.
  246. To compile this driver as a module, choose M here: the
  247. module will be called jornada680_kbd.
  248. config KEYBOARD_HP7XX
  249. tristate "HP Jornada 7xx keyboard"
  250. depends on SA1100_JORNADA720_SSP && SA1100_SSP
  251. help
  252. Say Y here if you have a HP Jornada 710/720/728 and want to
  253. support the built-in keyboard.
  254. To compile this driver as a module, choose M here: the
  255. module will be called jornada720_kbd.
  256. config KEYBOARD_LM8323
  257. tristate "LM8323 keypad chip"
  258. depends on I2C
  259. depends on LEDS_CLASS
  260. help
  261. If you say yes here you get support for the National Semiconductor
  262. LM8323 keypad controller.
  263. To compile this driver as a module, choose M here: the
  264. module will be called lm8323.
  265. config KEYBOARD_LM8333
  266. tristate "LM8333 keypad chip"
  267. depends on I2C
  268. select INPUT_MATRIXKMAP
  269. help
  270. If you say yes here you get support for the National Semiconductor
  271. LM8333 keypad controller.
  272. To compile this driver as a module, choose M here: the
  273. module will be called lm8333.
  274. config KEYBOARD_LOCOMO
  275. tristate "LoCoMo Keyboard Support"
  276. depends on SHARP_LOCOMO
  277. help
  278. Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
  279. To compile this driver as a module, choose M here: the
  280. module will be called locomokbd.
  281. config KEYBOARD_LPC32XX
  282. tristate "LPC32XX matrix key scanner support"
  283. depends on ARCH_LPC32XX && OF
  284. select INPUT_MATRIXKMAP
  285. help
  286. Say Y here if you want to use NXP LPC32XX SoC key scanner interface,
  287. connected to a key matrix.
  288. To compile this driver as a module, choose M here: the
  289. module will be called lpc32xx-keys.
  290. config KEYBOARD_MAPLE
  291. tristate "Maple bus keyboard"
  292. depends on SH_DREAMCAST && MAPLE
  293. help
  294. Say Y here if you have a Dreamcast console running Linux and have
  295. a keyboard attached to its Maple bus.
  296. To compile this driver as a module, choose M here: the
  297. module will be called maple_keyb.
  298. config KEYBOARD_MAX7359
  299. tristate "Maxim MAX7359 Key Switch Controller"
  300. depends on I2C
  301. help
  302. If you say yes here you get support for the Maxim MAX7359 Key
  303. Switch Controller chip. This providers microprocessors with
  304. management of up to 64 key switches
  305. To compile this driver as a module, choose M here: the
  306. module will be called max7359_keypad.
  307. config KEYBOARD_MCS
  308. tristate "MELFAS MCS Touchkey"
  309. depends on I2C
  310. help
  311. Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
  312. chip in your system.
  313. If unsure, say N.
  314. To compile this driver as a module, choose M here: the
  315. module will be called mcs_touchkey.
  316. config KEYBOARD_MPR121
  317. tristate "Freescale MPR121 Touchkey"
  318. depends on I2C
  319. help
  320. Say Y here if you have Freescale MPR121 touchkey controller
  321. chip in your system.
  322. If unsure, say N.
  323. To compile this driver as a module, choose M here: the
  324. module will be called mpr121_touchkey.
  325. config KEYBOARD_IMX
  326. tristate "IMX keypad support"
  327. depends on ARCH_MXC
  328. select INPUT_MATRIXKMAP
  329. help
  330. Enable support for IMX keypad port.
  331. To compile this driver as a module, choose M here: the
  332. module will be called imx_keypad.
  333. config KEYBOARD_NEWTON
  334. tristate "Newton keyboard"
  335. select SERIO
  336. help
  337. Say Y here if you have a Newton keyboard on a serial port.
  338. To compile this driver as a module, choose M here: the
  339. module will be called newtonkbd.
  340. config KEYBOARD_NOMADIK
  341. tristate "ST-Ericsson Nomadik SKE keyboard"
  342. depends on (ARCH_NOMADIK || ARCH_U8500)
  343. select INPUT_MATRIXKMAP
  344. help
  345. Say Y here if you want to use a keypad provided on the SKE controller
  346. used on the Ux500 and Nomadik platforms
  347. To compile this driver as a module, choose M here: the
  348. module will be called nmk-ske-keypad.
  349. config KEYBOARD_NSPIRE
  350. tristate "TI-NSPIRE built-in keyboard"
  351. depends on ARCH_NSPIRE && OF
  352. select INPUT_MATRIXKMAP
  353. help
  354. Say Y here if you want to use the built-in keypad on TI-NSPIRE.
  355. To compile this driver as a module, choose M here: the
  356. module will be called nspire-keypad.
  357. config KEYBOARD_TEGRA
  358. tristate "NVIDIA Tegra internal matrix keyboard controller support"
  359. depends on ARCH_TEGRA && OF
  360. select INPUT_MATRIXKMAP
  361. help
  362. Say Y here if you want to use a matrix keyboard connected directly
  363. to the internal keyboard controller on Tegra SoCs.
  364. To compile this driver as a module, choose M here: the
  365. module will be called tegra-kbc.
  366. config KEYBOARD_OPENCORES
  367. tristate "OpenCores Keyboard Controller"
  368. depends on HAS_IOMEM
  369. help
  370. Say Y here if you want to use the OpenCores Keyboard Controller
  371. http://www.opencores.org/project,keyboardcontroller
  372. To compile this driver as a module, choose M here; the
  373. module will be called opencores-kbd.
  374. config KEYBOARD_PXA27x
  375. tristate "PXA27x/PXA3xx keypad support"
  376. depends on PXA27x || PXA3xx || ARCH_MMP
  377. select INPUT_MATRIXKMAP
  378. help
  379. Enable support for PXA27x/PXA3xx keypad controller.
  380. To compile this driver as a module, choose M here: the
  381. module will be called pxa27x_keypad.
  382. config KEYBOARD_PXA930_ROTARY
  383. tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
  384. depends on CPU_PXA930 || CPU_PXA935
  385. help
  386. Enable support for PXA930/PXA935 Enhanced Rotary Controller.
  387. To compile this driver as a module, choose M here: the
  388. module will be called pxa930_rotary.
  389. config KEYBOARD_PMIC8XXX
  390. tristate "Qualcomm PMIC8XXX keypad support"
  391. depends on MFD_PM8XXX
  392. select INPUT_MATRIXKMAP
  393. help
  394. Say Y here if you want to enable the driver for the PMIC8XXX
  395. keypad provided as a reference design from Qualcomm. This is intended
  396. to support upto 18x8 matrix based keypad design.
  397. To compile this driver as a module, choose M here: the module will
  398. be called pmic8xxx-keypad.
  399. config KEYBOARD_SAMSUNG
  400. tristate "Samsung keypad support"
  401. depends on HAVE_CLK
  402. select INPUT_MATRIXKMAP
  403. help
  404. Say Y here if you want to use the keypad on your Samsung mobile
  405. device.
  406. To compile this driver as a module, choose M here: the
  407. module will be called samsung-keypad.
  408. config KEYBOARD_GOLDFISH_EVENTS
  409. depends on GOLDFISH
  410. tristate "Generic Input Event device for Goldfish"
  411. help
  412. Say Y here to get an input event device for the Goldfish virtual
  413. device emulator.
  414. To compile this driver as a module, choose M here: the
  415. module will be called goldfish-events.
  416. config KEYBOARD_STOWAWAY
  417. tristate "Stowaway keyboard"
  418. select SERIO
  419. help
  420. Say Y here if you have a Stowaway keyboard on a serial port.
  421. Stowaway compatible keyboards like Dicota Input-PDA keyboard
  422. are also supported by this driver.
  423. To compile this driver as a module, choose M here: the
  424. module will be called stowaway.
  425. config KEYBOARD_ST_KEYSCAN
  426. tristate "STMicroelectronics keyscan support"
  427. depends on ARCH_STI || COMPILE_TEST
  428. select INPUT_MATRIXKMAP
  429. help
  430. Say Y here if you want to use a keypad attached to the keyscan block
  431. on some STMicroelectronics SoC devices.
  432. To compile this driver as a module, choose M here: the
  433. module will be called st-keyscan.
  434. config KEYBOARD_SUNKBD
  435. tristate "Sun Type 4 and Type 5 keyboard"
  436. select SERIO
  437. help
  438. Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
  439. connected either to the Sun keyboard connector or to an serial
  440. (RS-232) port via a simple adapter.
  441. To compile this driver as a module, choose M here: the
  442. module will be called sunkbd.
  443. config KEYBOARD_SH_KEYSC
  444. tristate "SuperH KEYSC keypad support"
  445. depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
  446. help
  447. Say Y here if you want to use a keypad attached to the KEYSC block
  448. on SuperH processors such as sh7722 and sh7343.
  449. To compile this driver as a module, choose M here: the
  450. module will be called sh_keysc.
  451. config KEYBOARD_STMPE
  452. tristate "STMPE keypad support"
  453. depends on MFD_STMPE
  454. select INPUT_MATRIXKMAP
  455. help
  456. Say Y here if you want to use the keypad controller on STMPE I/O
  457. expanders.
  458. To compile this driver as a module, choose M here: the module will be
  459. called stmpe-keypad.
  460. config KEYBOARD_DAVINCI
  461. tristate "TI DaVinci Key Scan"
  462. depends on ARCH_DAVINCI_DM365
  463. help
  464. Say Y to enable keypad module support for the TI DaVinci
  465. platforms (DM365).
  466. To compile this driver as a module, choose M here: the
  467. module will be called davinci_keyscan.
  468. config KEYBOARD_OMAP
  469. tristate "TI OMAP keypad support"
  470. depends on ARCH_OMAP1
  471. select INPUT_MATRIXKMAP
  472. help
  473. Say Y here if you want to use the OMAP keypad.
  474. To compile this driver as a module, choose M here: the
  475. module will be called omap-keypad.
  476. config KEYBOARD_OMAP4
  477. tristate "TI OMAP4+ keypad support"
  478. depends on OF || ARCH_OMAP2PLUS
  479. select INPUT_MATRIXKMAP
  480. help
  481. Say Y here if you want to use the OMAP4+ keypad.
  482. To compile this driver as a module, choose M here: the
  483. module will be called omap4-keypad.
  484. config KEYBOARD_SPEAR
  485. tristate "ST SPEAR keyboard support"
  486. depends on PLAT_SPEAR
  487. select INPUT_MATRIXKMAP
  488. help
  489. Say Y here if you want to use the SPEAR keyboard.
  490. To compile this driver as a module, choose M here: the
  491. module will be called spear-keboard.
  492. config KEYBOARD_TC3589X
  493. tristate "TC3589X Keypad support"
  494. depends on MFD_TC3589X
  495. select INPUT_MATRIXKMAP
  496. help
  497. Say Y here if you want to use the keypad controller on
  498. TC35892/3 I/O expander.
  499. To compile this driver as a module, choose M here: the
  500. module will be called tc3589x-keypad.
  501. config KEYBOARD_TWL4030
  502. tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
  503. depends on TWL4030_CORE
  504. select INPUT_MATRIXKMAP
  505. help
  506. Say Y here if your board use the keypad controller on
  507. TWL4030 family chips. It's safe to say enable this
  508. even on boards that don't use the keypad controller.
  509. To compile this driver as a module, choose M here: the
  510. module will be called twl4030_keypad.
  511. config KEYBOARD_XTKBD
  512. tristate "XT keyboard"
  513. select SERIO
  514. help
  515. Say Y here if you want to use the old IBM PC/XT keyboard (or
  516. compatible) on your system. This is only possible with a
  517. parallel port keyboard adapter, you cannot connect it to the
  518. keyboard port on a PC that runs Linux.
  519. To compile this driver as a module, choose M here: the
  520. module will be called xtkbd.
  521. config KEYBOARD_W90P910
  522. tristate "W90P910 Matrix Keypad support"
  523. depends on ARCH_W90X900
  524. select INPUT_MATRIXKMAP
  525. help
  526. Say Y here to enable the matrix keypad on evaluation board
  527. based on W90P910.
  528. To compile this driver as a module, choose M here: the
  529. module will be called w90p910_keypad.
  530. config KEYBOARD_CROS_EC
  531. tristate "ChromeOS EC keyboard"
  532. select INPUT_MATRIXKMAP
  533. depends on MFD_CROS_EC
  534. help
  535. Say Y here to enable the matrix keyboard used by ChromeOS devices
  536. and implemented on the ChromeOS EC. You must enable one bus option
  537. (MFD_CROS_EC_I2C or MFD_CROS_EC_SPI) to use this.
  538. To compile this driver as a module, choose M here: the
  539. module will be called cros_ec_keyb.
  540. config KEYBOARD_CAP1106
  541. tristate "Microchip CAP1106 touch sensor"
  542. depends on OF && I2C
  543. select REGMAP_I2C
  544. help
  545. Say Y here to enable the CAP1106 touch sensor driver.
  546. To compile this driver as a module, choose M here: the
  547. module will be called cap1106.
  548. endif