Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514
  1. #
  2. # Input core configuration
  3. #
  4. menuconfig INPUT_KEYBOARD
  5. bool "Keyboards" if EMBEDDED || !X86
  6. default y
  7. help
  8. Say Y here, and a list of supported keyboards will be displayed.
  9. This option doesn't affect the kernel.
  10. If unsure, say Y.
  11. if INPUT_KEYBOARD
  12. config KEYBOARD_AAED2000
  13. tristate "AAED-2000 keyboard"
  14. depends on MACH_AAED2000
  15. select INPUT_POLLDEV
  16. default y
  17. help
  18. Say Y here to enable the keyboard on the Agilent AAED-2000
  19. development board.
  20. To compile this driver as a module, choose M here: the
  21. module will be called aaed2000_kbd.
  22. config KEYBOARD_ADP5520
  23. tristate "Keypad Support for ADP5520 PMIC"
  24. depends on PMIC_ADP5520
  25. help
  26. This option enables support for the keypad scan matrix
  27. on Analog Devices ADP5520 PMICs.
  28. To compile this driver as a module, choose M here: the module will
  29. be called adp5520-keys.
  30. config KEYBOARD_ADP5588
  31. tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
  32. depends on I2C
  33. help
  34. Say Y here if you want to use a ADP5588/87 attached to your
  35. system I2C bus.
  36. To compile this driver as a module, choose M here: the
  37. module will be called adp5588-keys.
  38. config KEYBOARD_AMIGA
  39. tristate "Amiga keyboard"
  40. depends on AMIGA
  41. help
  42. Say Y here if you are running Linux on any AMIGA and have a keyboard
  43. attached.
  44. To compile this driver as a module, choose M here: the
  45. module will be called amikbd.
  46. config ATARI_KBD_CORE
  47. bool
  48. config KEYBOARD_ATARI
  49. tristate "Atari keyboard"
  50. depends on ATARI
  51. select ATARI_KBD_CORE
  52. help
  53. Say Y here if you are running Linux on any Atari and have a keyboard
  54. attached.
  55. To compile this driver as a module, choose M here: the
  56. module will be called atakbd.
  57. config KEYBOARD_ATKBD
  58. tristate "AT keyboard" if EMBEDDED || !X86
  59. default y
  60. select SERIO
  61. select SERIO_LIBPS2
  62. select SERIO_I8042 if X86
  63. select SERIO_GSCPS2 if GSC
  64. help
  65. Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
  66. you'll need this, unless you have a different type keyboard (USB, ADB
  67. or other). This also works for AT and PS/2 keyboards connected over a
  68. PS/2 to serial converter.
  69. If unsure, say Y.
  70. To compile this driver as a module, choose M here: the
  71. module will be called atkbd.
  72. config KEYBOARD_ATKBD_HP_KEYCODES
  73. bool "Use HP keyboard scancodes"
  74. depends on PARISC && KEYBOARD_ATKBD
  75. default y
  76. help
  77. Say Y here if you have a PA-RISC machine and want to use an AT or
  78. PS/2 keyboard, and your keyboard uses keycodes that are specific to
  79. PA-RISC keyboards.
  80. Say N if you use a standard keyboard.
  81. config KEYBOARD_ATKBD_RDI_KEYCODES
  82. bool "Use PrecisionBook keyboard scancodes"
  83. depends on KEYBOARD_ATKBD_HP_KEYCODES
  84. default n
  85. help
  86. If you have an RDI PrecisionBook, say Y here if you want to use its
  87. built-in keyboard (as opposed to an external keyboard).
  88. The PrecisionBook has five keys that conflict with those used by most
  89. AT and PS/2 keyboards. These are as follows:
  90. PrecisionBook Standard AT or PS/2
  91. F1 F12
  92. Left Ctrl Left Alt
  93. Caps Lock Left Ctrl
  94. Right Ctrl Caps Lock
  95. Left 102nd key (the key to the right of Left Shift)
  96. If you say N here, and use the PrecisionBook keyboard, then each key
  97. in the left-hand column will be interpreted as the corresponding key
  98. in the right-hand column.
  99. If you say Y here, and use an external keyboard, then each key in the
  100. right-hand column will be interpreted as the key shown in the
  101. left-hand column.
  102. config KEYBOARD_QT2160
  103. tristate "Atmel AT42QT2160 Touch Sensor Chip"
  104. depends on I2C && EXPERIMENTAL
  105. help
  106. If you say yes here you get support for Atmel AT42QT2160 Touch
  107. Sensor chip as a keyboard input.
  108. This driver can also be built as a module. If so, the module
  109. will be called qt2160.
  110. config KEYBOARD_BFIN
  111. tristate "Blackfin BF54x keypad support"
  112. depends on (BF54x && !BF544)
  113. help
  114. Say Y here if you want to use the BF54x keypad.
  115. To compile this driver as a module, choose M here: the
  116. module will be called bf54x-keys.
  117. config KEYBOARD_LKKBD
  118. tristate "DECstation/VAXstation LK201/LK401 keyboard"
  119. select SERIO
  120. help
  121. Say Y here if you want to use a LK201 or LK401 style serial
  122. keyboard. This keyboard is also useable on PCs if you attach
  123. it with the inputattach program. The connector pinout is
  124. described within lkkbd.c.
  125. To compile this driver as a module, choose M here: the
  126. module will be called lkkbd.
  127. config KEYBOARD_EP93XX
  128. tristate "EP93xx Matrix Keypad support"
  129. depends on ARCH_EP93XX
  130. help
  131. Say Y here to enable the matrix keypad on the Cirrus EP93XX.
  132. To compile this driver as a module, choose M here: the
  133. module will be called ep93xx_keypad.
  134. config KEYBOARD_GPIO
  135. tristate "GPIO Buttons"
  136. depends on GENERIC_GPIO
  137. help
  138. This driver implements support for buttons connected
  139. to GPIO pins of various CPUs (and some other chips).
  140. Say Y here if your device has buttons connected
  141. directly to such GPIO pins. Your board-specific
  142. setup logic must also provide a platform device,
  143. with configuration data saying which GPIOs are used.
  144. To compile this driver as a module, choose M here: the
  145. module will be called gpio_keys.
  146. config KEYBOARD_GPIO_POLLED
  147. tristate "Polled GPIO buttons"
  148. depends on GENERIC_GPIO
  149. select INPUT_POLLDEV
  150. help
  151. This driver implements support for buttons connected
  152. to GPIO pins that are not capable of generating interrupts.
  153. Say Y here if your device has buttons connected
  154. directly to such GPIO pins. Your board-specific
  155. setup logic must also provide a platform device,
  156. with configuration data saying which GPIOs are used.
  157. To compile this driver as a module, choose M here: the
  158. module will be called gpio_keys_polled.
  159. config KEYBOARD_TCA6416
  160. tristate "TCA6416 Keypad Support"
  161. depends on I2C
  162. help
  163. This driver implements basic keypad functionality
  164. for keys connected through TCA6416 IO expander
  165. Say Y here if your device has keys connected to
  166. TCA6416 IO expander. Your board-specific setup logic
  167. must also provide pin-mask details(of which TCA6416 pins
  168. are used for keypad).
  169. If enabled the complete TCA6416 device will be managed through
  170. this driver.
  171. config KEYBOARD_MATRIX
  172. tristate "GPIO driven matrix keypad support"
  173. depends on GENERIC_GPIO
  174. help
  175. Enable support for GPIO driven matrix keypad.
  176. To compile this driver as a module, choose M here: the
  177. module will be called matrix_keypad.
  178. config KEYBOARD_HIL_OLD
  179. tristate "HP HIL keyboard support (simple driver)"
  180. depends on GSC || HP300
  181. default y
  182. help
  183. The "Human Interface Loop" is a older, 8-channel USB-like
  184. controller used in several Hewlett Packard models. This driver
  185. was adapted from the one written for m68k/hp300, and implements
  186. support for a keyboard attached to the HIL port, but not for
  187. any other types of HIL input devices like mice or tablets.
  188. However, it has been thoroughly tested and is stable.
  189. If you want full HIL support including support for multiple
  190. keyboards, mice, and tablets, you have to enable the
  191. "HP System Device Controller i8042 Support" in the input/serio
  192. submenu.
  193. config KEYBOARD_HIL
  194. tristate "HP HIL keyboard/pointer support"
  195. depends on GSC || HP300
  196. default y
  197. select HP_SDC
  198. select HIL_MLC
  199. select SERIO
  200. help
  201. The "Human Interface Loop" is a older, 8-channel USB-like
  202. controller used in several Hewlett Packard models.
  203. This driver implements support for HIL-keyboards and pointing
  204. devices (mice, tablets, touchscreens) attached
  205. to your machine, so normally you should say Y here.
  206. config KEYBOARD_HP6XX
  207. tristate "HP Jornada 6xx keyboard"
  208. depends on SH_HP6XX
  209. select INPUT_POLLDEV
  210. help
  211. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  212. support the built-in keyboard.
  213. To compile this driver as a module, choose M here: the
  214. module will be called jornada680_kbd.
  215. config KEYBOARD_HP7XX
  216. tristate "HP Jornada 7xx keyboard"
  217. depends on SA1100_JORNADA720_SSP && SA1100_SSP
  218. help
  219. Say Y here if you have a HP Jornada 710/720/728 and want to
  220. support the built-in keyboard.
  221. To compile this driver as a module, choose M here: the
  222. module will be called jornada720_kbd.
  223. config KEYBOARD_LM8323
  224. tristate "LM8323 keypad chip"
  225. depends on I2C
  226. depends on LEDS_CLASS
  227. help
  228. If you say yes here you get support for the National Semiconductor
  229. LM8323 keypad controller.
  230. To compile this driver as a module, choose M here: the
  231. module will be called lm8323.
  232. config KEYBOARD_LOCOMO
  233. tristate "LoCoMo Keyboard Support"
  234. depends on SHARP_LOCOMO
  235. help
  236. Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
  237. To compile this driver as a module, choose M here: the
  238. module will be called locomokbd.
  239. config KEYBOARD_MAPLE
  240. tristate "Maple bus keyboard"
  241. depends on SH_DREAMCAST && MAPLE
  242. help
  243. Say Y here if you have a Dreamcast console running Linux and have
  244. a keyboard attached to its Maple bus.
  245. To compile this driver as a module, choose M here: the
  246. module will be called maple_keyb.
  247. config KEYBOARD_MAX7359
  248. tristate "Maxim MAX7359 Key Switch Controller"
  249. depends on I2C
  250. help
  251. If you say yes here you get support for the Maxim MAX7359 Key
  252. Switch Controller chip. This providers microprocessors with
  253. management of up to 64 key switches
  254. To compile this driver as a module, choose M here: the
  255. module will be called max7359_keypad.
  256. config KEYBOARD_MCS
  257. tristate "MELFAS MCS Touchkey"
  258. depends on I2C
  259. help
  260. Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
  261. chip in your system.
  262. If unsure, say N.
  263. To compile this driver as a module, choose M here: the
  264. module will be called mcs_touchkey.
  265. config KEYBOARD_IMX
  266. tristate "IMX keypad support"
  267. depends on ARCH_MXC
  268. help
  269. Enable support for IMX keypad port.
  270. To compile this driver as a module, choose M here: the
  271. module will be called imx_keypad.
  272. config KEYBOARD_NEWTON
  273. tristate "Newton keyboard"
  274. select SERIO
  275. help
  276. Say Y here if you have a Newton keyboard on a serial port.
  277. To compile this driver as a module, choose M here: the
  278. module will be called newtonkbd.
  279. config KEYBOARD_NOMADIK
  280. tristate "ST-Ericsson Nomadik SKE keyboard"
  281. depends on PLAT_NOMADIK
  282. help
  283. Say Y here if you want to use a keypad provided on the SKE controller
  284. used on the Ux500 and Nomadik platforms
  285. To compile this driver as a module, choose M here: the
  286. module will be called nmk-ske-keypad.
  287. config KEYBOARD_OPENCORES
  288. tristate "OpenCores Keyboard Controller"
  289. help
  290. Say Y here if you want to use the OpenCores Keyboard Controller
  291. http://www.opencores.org/project,keyboardcontroller
  292. To compile this driver as a module, choose M here; the
  293. module will be called opencores-kbd.
  294. config KEYBOARD_PXA27x
  295. tristate "PXA27x/PXA3xx keypad support"
  296. depends on PXA27x || PXA3xx || ARCH_MMP
  297. help
  298. Enable support for PXA27x/PXA3xx keypad controller.
  299. To compile this driver as a module, choose M here: the
  300. module will be called pxa27x_keypad.
  301. config KEYBOARD_PXA930_ROTARY
  302. tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
  303. depends on CPU_PXA930 || CPU_PXA935
  304. help
  305. Enable support for PXA930/PXA935 Enhanced Rotary Controller.
  306. To compile this driver as a module, choose M here: the
  307. module will be called pxa930_rotary.
  308. config KEYBOARD_SAMSUNG
  309. tristate "Samsung keypad support"
  310. depends on SAMSUNG_DEV_KEYPAD
  311. help
  312. Say Y here if you want to use the Samsung keypad.
  313. To compile this driver as a module, choose M here: the
  314. module will be called samsung-keypad.
  315. config KEYBOARD_STOWAWAY
  316. tristate "Stowaway keyboard"
  317. select SERIO
  318. help
  319. Say Y here if you have a Stowaway keyboard on a serial port.
  320. Stowaway compatible keyboards like Dicota Input-PDA keyboard
  321. are also supported by this driver.
  322. To compile this driver as a module, choose M here: the
  323. module will be called stowaway.
  324. config KEYBOARD_SUNKBD
  325. tristate "Sun Type 4 and Type 5 keyboard"
  326. select SERIO
  327. help
  328. Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
  329. connected either to the Sun keyboard connector or to an serial
  330. (RS-232) port via a simple adapter.
  331. To compile this driver as a module, choose M here: the
  332. module will be called sunkbd.
  333. config KEYBOARD_SH_KEYSC
  334. tristate "SuperH KEYSC keypad support"
  335. depends on SUPERH || ARCH_SHMOBILE
  336. help
  337. Say Y here if you want to use a keypad attached to the KEYSC block
  338. on SuperH processors such as sh7722 and sh7343.
  339. To compile this driver as a module, choose M here: the
  340. module will be called sh_keysc.
  341. config KEYBOARD_STMPE
  342. tristate "STMPE keypad support"
  343. depends on MFD_STMPE
  344. help
  345. Say Y here if you want to use the keypad controller on STMPE I/O
  346. expanders.
  347. To compile this driver as a module, choose M here: the module will be
  348. called stmpe-keypad.
  349. config KEYBOARD_DAVINCI
  350. tristate "TI DaVinci Key Scan"
  351. depends on ARCH_DAVINCI_DM365
  352. help
  353. Say Y to enable keypad module support for the TI DaVinci
  354. platforms (DM365).
  355. To compile this driver as a module, choose M here: the
  356. module will be called davinci_keyscan.
  357. config KEYBOARD_OMAP
  358. tristate "TI OMAP keypad support"
  359. depends on (ARCH_OMAP1 || ARCH_OMAP2)
  360. help
  361. Say Y here if you want to use the OMAP keypad.
  362. To compile this driver as a module, choose M here: the
  363. module will be called omap-keypad.
  364. config KEYBOARD_OMAP4
  365. tristate "TI OMAP4 keypad support"
  366. depends on ARCH_OMAP4
  367. help
  368. Say Y here if you want to use the OMAP4 keypad.
  369. To compile this driver as a module, choose M here: the
  370. module will be called omap4-keypad.
  371. config KEYBOARD_TC3589X
  372. tristate "TC3589X Keypad support"
  373. depends on MFD_TC3589X
  374. help
  375. Say Y here if you want to use the keypad controller on
  376. TC35892/3 I/O expander.
  377. To compile this driver as a module, choose M here: the
  378. module will be called tc3589x-keypad.
  379. config KEYBOARD_TNETV107X
  380. tristate "TI TNETV107X keypad support"
  381. depends on ARCH_DAVINCI_TNETV107X
  382. help
  383. Say Y here if you want to use the TNETV107X keypad.
  384. To compile this driver as a module, choose M here: the
  385. module will be called tnetv107x-keypad.
  386. config KEYBOARD_TWL4030
  387. tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
  388. depends on TWL4030_CORE
  389. help
  390. Say Y here if your board use the keypad controller on
  391. TWL4030 family chips. It's safe to say enable this
  392. even on boards that don't use the keypad controller.
  393. To compile this driver as a module, choose M here: the
  394. module will be called twl4030_keypad.
  395. config KEYBOARD_XTKBD
  396. tristate "XT keyboard"
  397. select SERIO
  398. help
  399. Say Y here if you want to use the old IBM PC/XT keyboard (or
  400. compatible) on your system. This is only possible with a
  401. parallel port keyboard adapter, you cannot connect it to the
  402. keyboard port on a PC that runs Linux.
  403. To compile this driver as a module, choose M here: the
  404. module will be called xtkbd.
  405. config KEYBOARD_W90P910
  406. tristate "W90P910 Matrix Keypad support"
  407. depends on ARCH_W90X900
  408. help
  409. Say Y here to enable the matrix keypad on evaluation board
  410. based on W90P910.
  411. To compile this driver as a module, choose M here: the
  412. module will be called w90p910_keypad.
  413. endif