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