Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525
  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/TCA6408A Keypad Support"
  161. depends on I2C
  162. help
  163. This driver implements basic keypad functionality
  164. for keys connected through TCA6416/TCA6408A IO expanders.
  165. Say Y here if your device has keys connected to
  166. TCA6416/TCA6408A 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 entire TCA6416 device will be managed through
  170. this driver.
  171. To compile this driver as a module, choose M here: the
  172. module will be called tca6416_keypad.
  173. config KEYBOARD_MATRIX
  174. tristate "GPIO driven matrix keypad support"
  175. depends on GENERIC_GPIO
  176. help
  177. Enable support for GPIO driven matrix keypad.
  178. To compile this driver as a module, choose M here: the
  179. module will be called matrix_keypad.
  180. config KEYBOARD_HIL_OLD
  181. tristate "HP HIL keyboard support (simple driver)"
  182. depends on GSC || HP300
  183. default y
  184. help
  185. The "Human Interface Loop" is a older, 8-channel USB-like
  186. controller used in several Hewlett Packard models. This driver
  187. was adapted from the one written for m68k/hp300, and implements
  188. support for a keyboard attached to the HIL port, but not for
  189. any other types of HIL input devices like mice or tablets.
  190. However, it has been thoroughly tested and is stable.
  191. If you want full HIL support including support for multiple
  192. keyboards, mice, and tablets, you have to enable the
  193. "HP System Device Controller i8042 Support" in the input/serio
  194. submenu.
  195. config KEYBOARD_HIL
  196. tristate "HP HIL keyboard/pointer support"
  197. depends on GSC || HP300
  198. default y
  199. select HP_SDC
  200. select HIL_MLC
  201. select SERIO
  202. help
  203. The "Human Interface Loop" is a older, 8-channel USB-like
  204. controller used in several Hewlett Packard models.
  205. This driver implements support for HIL-keyboards and pointing
  206. devices (mice, tablets, touchscreens) attached
  207. to your machine, so normally you should say Y here.
  208. config KEYBOARD_HP6XX
  209. tristate "HP Jornada 6xx keyboard"
  210. depends on SH_HP6XX
  211. select INPUT_POLLDEV
  212. help
  213. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  214. support the built-in keyboard.
  215. To compile this driver as a module, choose M here: the
  216. module will be called jornada680_kbd.
  217. config KEYBOARD_HP7XX
  218. tristate "HP Jornada 7xx keyboard"
  219. depends on SA1100_JORNADA720_SSP && SA1100_SSP
  220. help
  221. Say Y here if you have a HP Jornada 710/720/728 and want to
  222. support the built-in keyboard.
  223. To compile this driver as a module, choose M here: the
  224. module will be called jornada720_kbd.
  225. config KEYBOARD_LM8323
  226. tristate "LM8323 keypad chip"
  227. depends on I2C
  228. depends on LEDS_CLASS
  229. help
  230. If you say yes here you get support for the National Semiconductor
  231. LM8323 keypad controller.
  232. To compile this driver as a module, choose M here: the
  233. module will be called lm8323.
  234. config KEYBOARD_LOCOMO
  235. tristate "LoCoMo Keyboard Support"
  236. depends on SHARP_LOCOMO
  237. help
  238. Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
  239. To compile this driver as a module, choose M here: the
  240. module will be called locomokbd.
  241. config KEYBOARD_MAPLE
  242. tristate "Maple bus keyboard"
  243. depends on SH_DREAMCAST && MAPLE
  244. help
  245. Say Y here if you have a Dreamcast console running Linux and have
  246. a keyboard attached to its Maple bus.
  247. To compile this driver as a module, choose M here: the
  248. module will be called maple_keyb.
  249. config KEYBOARD_MAX7359
  250. tristate "Maxim MAX7359 Key Switch Controller"
  251. depends on I2C
  252. help
  253. If you say yes here you get support for the Maxim MAX7359 Key
  254. Switch Controller chip. This providers microprocessors with
  255. management of up to 64 key switches
  256. To compile this driver as a module, choose M here: the
  257. module will be called max7359_keypad.
  258. config KEYBOARD_MCS
  259. tristate "MELFAS MCS Touchkey"
  260. depends on I2C
  261. help
  262. Say Y here if you have the MELFAS MCS5000/5080 touchkey controller
  263. chip in your system.
  264. If unsure, say N.
  265. To compile this driver as a module, choose M here: the
  266. module will be called mcs_touchkey.
  267. config KEYBOARD_IMX
  268. tristate "IMX keypad support"
  269. depends on ARCH_MXC
  270. help
  271. Enable support for IMX keypad port.
  272. To compile this driver as a module, choose M here: the
  273. module will be called imx_keypad.
  274. config KEYBOARD_NEWTON
  275. tristate "Newton keyboard"
  276. select SERIO
  277. help
  278. Say Y here if you have a Newton keyboard on a serial port.
  279. To compile this driver as a module, choose M here: the
  280. module will be called newtonkbd.
  281. config KEYBOARD_NOMADIK
  282. tristate "ST-Ericsson Nomadik SKE keyboard"
  283. depends on PLAT_NOMADIK
  284. help
  285. Say Y here if you want to use a keypad provided on the SKE controller
  286. used on the Ux500 and Nomadik platforms
  287. To compile this driver as a module, choose M here: the
  288. module will be called nmk-ske-keypad.
  289. config KEYBOARD_OPENCORES
  290. tristate "OpenCores Keyboard Controller"
  291. help
  292. Say Y here if you want to use the OpenCores Keyboard Controller
  293. http://www.opencores.org/project,keyboardcontroller
  294. To compile this driver as a module, choose M here; the
  295. module will be called opencores-kbd.
  296. config KEYBOARD_PXA27x
  297. tristate "PXA27x/PXA3xx keypad support"
  298. depends on PXA27x || PXA3xx || ARCH_MMP
  299. help
  300. Enable support for PXA27x/PXA3xx keypad controller.
  301. To compile this driver as a module, choose M here: the
  302. module will be called pxa27x_keypad.
  303. config KEYBOARD_PXA930_ROTARY
  304. tristate "PXA930/PXA935 Enhanced Rotary Controller Support"
  305. depends on CPU_PXA930 || CPU_PXA935
  306. help
  307. Enable support for PXA930/PXA935 Enhanced Rotary Controller.
  308. To compile this driver as a module, choose M here: the
  309. module will be called pxa930_rotary.
  310. config KEYBOARD_SAMSUNG
  311. tristate "Samsung keypad support"
  312. depends on SAMSUNG_DEV_KEYPAD
  313. help
  314. Say Y here if you want to use the Samsung keypad.
  315. To compile this driver as a module, choose M here: the
  316. module will be called samsung-keypad.
  317. config KEYBOARD_STOWAWAY
  318. tristate "Stowaway keyboard"
  319. select SERIO
  320. help
  321. Say Y here if you have a Stowaway keyboard on a serial port.
  322. Stowaway compatible keyboards like Dicota Input-PDA keyboard
  323. are also supported by this driver.
  324. To compile this driver as a module, choose M here: the
  325. module will be called stowaway.
  326. config KEYBOARD_SUNKBD
  327. tristate "Sun Type 4 and Type 5 keyboard"
  328. select SERIO
  329. help
  330. Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
  331. connected either to the Sun keyboard connector or to an serial
  332. (RS-232) port via a simple adapter.
  333. To compile this driver as a module, choose M here: the
  334. module will be called sunkbd.
  335. config KEYBOARD_SH_KEYSC
  336. tristate "SuperH KEYSC keypad support"
  337. depends on SUPERH || ARCH_SHMOBILE
  338. help
  339. Say Y here if you want to use a keypad attached to the KEYSC block
  340. on SuperH processors such as sh7722 and sh7343.
  341. To compile this driver as a module, choose M here: the
  342. module will be called sh_keysc.
  343. config KEYBOARD_STMPE
  344. tristate "STMPE keypad support"
  345. depends on MFD_STMPE
  346. help
  347. Say Y here if you want to use the keypad controller on STMPE I/O
  348. expanders.
  349. To compile this driver as a module, choose M here: the module will be
  350. called stmpe-keypad.
  351. config KEYBOARD_DAVINCI
  352. tristate "TI DaVinci Key Scan"
  353. depends on ARCH_DAVINCI_DM365
  354. help
  355. Say Y to enable keypad module support for the TI DaVinci
  356. platforms (DM365).
  357. To compile this driver as a module, choose M here: the
  358. module will be called davinci_keyscan.
  359. config KEYBOARD_OMAP
  360. tristate "TI OMAP keypad support"
  361. depends on (ARCH_OMAP1 || ARCH_OMAP2)
  362. help
  363. Say Y here if you want to use the OMAP keypad.
  364. To compile this driver as a module, choose M here: the
  365. module will be called omap-keypad.
  366. config KEYBOARD_OMAP4
  367. tristate "TI OMAP4 keypad support"
  368. depends on ARCH_OMAP4
  369. help
  370. Say Y here if you want to use the OMAP4 keypad.
  371. To compile this driver as a module, choose M here: the
  372. module will be called omap4-keypad.
  373. config KEYBOARD_SPEAR
  374. tristate "ST SPEAR keyboard support"
  375. depends on PLAT_SPEAR
  376. help
  377. Say Y here if you want to use the SPEAR keyboard.
  378. To compile this driver as a module, choose M here: the
  379. module will be called spear-keboard.
  380. config KEYBOARD_TC3589X
  381. tristate "TC3589X Keypad support"
  382. depends on MFD_TC3589X
  383. help
  384. Say Y here if you want to use the keypad controller on
  385. TC35892/3 I/O expander.
  386. To compile this driver as a module, choose M here: the
  387. module will be called tc3589x-keypad.
  388. config KEYBOARD_TNETV107X
  389. tristate "TI TNETV107X keypad support"
  390. depends on ARCH_DAVINCI_TNETV107X
  391. help
  392. Say Y here if you want to use the TNETV107X keypad.
  393. To compile this driver as a module, choose M here: the
  394. module will be called tnetv107x-keypad.
  395. config KEYBOARD_TWL4030
  396. tristate "TI TWL4030/TWL5030/TPS659x0 keypad support"
  397. depends on TWL4030_CORE
  398. help
  399. Say Y here if your board use the keypad controller on
  400. TWL4030 family chips. It's safe to say enable this
  401. even on boards that don't use the keypad controller.
  402. To compile this driver as a module, choose M here: the
  403. module will be called twl4030_keypad.
  404. config KEYBOARD_XTKBD
  405. tristate "XT keyboard"
  406. select SERIO
  407. help
  408. Say Y here if you want to use the old IBM PC/XT keyboard (or
  409. compatible) on your system. This is only possible with a
  410. parallel port keyboard adapter, you cannot connect it to the
  411. keyboard port on a PC that runs Linux.
  412. To compile this driver as a module, choose M here: the
  413. module will be called xtkbd.
  414. config KEYBOARD_W90P910
  415. tristate "W90P910 Matrix Keypad support"
  416. depends on ARCH_W90X900
  417. help
  418. Say Y here to enable the matrix keypad on evaluation board
  419. based on W90P910.
  420. To compile this driver as a module, choose M here: the
  421. module will be called w90p910_keypad.
  422. endif