Lines Matching +full:system +full:- +full:on +full:- +full:a +full:- +full:chip
1 # SPDX-License-Identifier: GPL-2.0-only
9 Say Y here, and a list of supported keyboards will be displayed.
18 depends on IIO
21 to an ADC using a resistor ladder.
24 board-specific setup logic must also provide a configuration data
27 To compile this driver as a module, choose M here: the
32 depends on PMIC_ADP5520
35 on Analog Devices ADP5520 PMICs.
37 To compile this driver as a module, choose M here: the module will
38 be called adp5520-keys.
42 depends on I2C
44 Say Y here if you want to use a ADP5588/87 attached to your
45 system I2C bus.
47 To compile this driver as a module, choose M here: the
48 module will be called adp5588-keys.
52 depends on I2C
54 Say Y here if you want to use a ADP5585/ADP5589 attached to your
55 system I2C bus.
57 To compile this driver as a module, choose M here: the
58 module will be called adp5589-keys.
62 depends on AMIGA
64 Say Y here if you are running Linux on any AMIGA and have a keyboard
67 To compile this driver as a module, choose M here: the
75 depends on ACPI && EFI
76 depends on SPI
77 depends on X86 || COMPILE_TEST
78 depends on LEDS_CLASS
81 Say Y here if you are running Linux on any Apple MacBook8,1 or later,
88 To compile this driver as a module, choose M here: the
93 depends on ATARI
96 Say Y here if you are running Linux on any Atari and have a keyboard
99 To compile this driver as a module, choose M here: the
110 Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
111 you'll need this, unless you have a different type keyboard (USB, ADB
112 or other). This also works for AT and PS/2 keyboards connected over a
117 To compile this driver as a module, choose M here: the
122 depends on PARISC && KEYBOARD_ATKBD
125 Say Y here if you have a PA-RISC machine and want to use an AT or
127 PA-RISC keyboards.
129 Say N if you use a standard keyboard.
133 depends on KEYBOARD_ATKBD_HP_KEYCODES
137 built-in keyboard (as opposed to an external keyboard).
151 in the left-hand column will be interpreted as the corresponding key
152 in the right-hand column.
155 right-hand column will be interpreted as the key shown in the
156 left-hand column.
159 tristate "Microchip AT42QT1050 Touch Sensor Chip"
160 depends on I2C
164 Sensor chip as input device.
166 To compile this driver as a module, choose M here:
170 tristate "Atmel AT42QT1070 Touch Sensor Chip"
171 depends on I2C
174 Sensor chip as input device.
176 To compile this driver as a module, choose M here:
180 tristate "Atmel AT42QT2160 Touch Sensor Chip"
181 depends on I2C
184 Sensor chip as a keyboard input.
186 This driver can also be built as a module. If so, the module
191 depends on OF_GPIO && (ARCH_CLPS711X || COMPILE_TEST)
194 Say Y here to enable the matrix keypad on the Cirrus Logic
197 To compile this driver as a module, choose M here: the
198 module will be called clps711x-keypad.
201 tristate "D-Link DIR-685 touchkeys support"
202 depends on I2C
205 If you say yes here you get support for the D-Link DIR-685
208 To compile this driver as a module, choose M here: the
209 module will be called dlink-dir685-touchkeys.
215 Say Y here if you want to use a LK201 or LK401 style serial
216 keyboard. This keyboard is also useable on PCs if you attach
220 To compile this driver as a module, choose M here: the
225 depends on ARCH_EP93XX || COMPILE_TEST
228 Say Y here to enable the matrix keypad on the Cirrus EP93XX.
230 To compile this driver as a module, choose M here: the
235 depends on GPIOLIB || COMPILE_TEST
241 directly to such GPIO pins. Your board-specific
242 setup logic must also provide a platform device,
245 To compile this driver as a module, choose M here: the
250 depends on GPIOLIB
256 directly to such GPIO pins. Your board-specific
257 setup logic must also provide a platform device,
260 To compile this driver as a module, choose M here: the
265 depends on I2C
271 TCA6416/TCA6408A IO expander. Your board-specific setup logic
272 must also provide pin-mask details(of which TCA6416 pins
278 To compile this driver as a module, choose M here: the
283 depends on I2C
295 To compile this driver as a module, choose M here: the
300 depends on GPIOLIB || COMPILE_TEST
305 To compile this driver as a module, choose M here: the
310 depends on GSC || HP300
313 The "Human Interface Loop" is a older, 8-channel USB-like
316 support for a keyboard attached to the HIL port, but not for
322 "HP System Device Controller i8042 Support" in the input/serio
327 depends on GSC || HP300
333 The "Human Interface Loop" is a older, 8-channel USB-like
335 This driver implements support for HIL-keyboards and pointing
341 depends on SH_HP6XX
343 Say Y here if you have a HP Jornada 620/660/680/690 and want to
344 support the built-in keyboard.
346 To compile this driver as a module, choose M here: the
351 depends on SA1100_JORNADA720_SSP && SA1100_SSP
353 Say Y here if you have a HP Jornada 710/720/728 and want to
354 support the built-in keyboard.
356 To compile this driver as a module, choose M here: the
360 tristate "LM8323 keypad chip"
361 depends on I2C
362 depends on LEDS_CLASS
367 To compile this driver as a module, choose M here: the
371 tristate "LM8333 keypad chip"
372 depends on I2C
378 To compile this driver as a module, choose M here: the
383 depends on SHARP_LOCOMO
385 Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA
387 To compile this driver as a module, choose M here: the
392 depends on ARCH_LPC32XX && OF
396 connected to a key matrix.
398 To compile this driver as a module, choose M here: the
399 module will be called lpc32xx-keys.
403 depends on SH_DREAMCAST && MAPLE
405 Say Y here if you have a Dreamcast console running Linux and have
406 a keyboard attached to its Maple bus.
408 To compile this driver as a module, choose M here: the
414 depends on I2C
417 Switch Controller chip. This providers microprocessors with
420 To compile this driver as a module, choose M here: the
425 depends on I2C
428 chip in your system.
432 To compile this driver as a module, choose M here: the
437 depends on I2C
440 chip in your system.
444 To compile this driver as a module, choose M here: the
449 depends on ARCH_MXC || COMPILE_TEST
450 depends on OF
455 To compile this driver as a module, choose M here; the
460 depends on ARCH_MXC
465 To compile this driver as a module, choose M here: the
470 depends on IMX_SCU
472 This is the system controller key driver for NXP i.MX SoCs with
473 system controller inside.
475 To compile this driver as a module, choose M here: the
482 Say Y here if you have a Newton keyboard on a serial port.
484 To compile this driver as a module, choose M here: the
488 tristate "ST-Ericsson Nomadik SKE keyboard"
489 depends on (ARCH_NOMADIK || ARCH_U8500)
492 Say Y here if you want to use a keypad provided on the SKE controller
493 used on the Ux500 and Nomadik platforms
495 To compile this driver as a module, choose M here: the
496 module will be called nmk-ske-keypad.
499 tristate "TI-NSPIRE built-in keyboard"
500 depends on ARCH_NSPIRE && OF
503 Say Y here if you want to use the built-in keypad on TI-NSPIRE.
505 To compile this driver as a module, choose M here: the
506 module will be called nspire-keypad.
510 depends on ARCH_TEGRA && OF
513 Say Y here if you want to use a matrix keyboard connected directly
514 to the internal keyboard controller on Tegra SoCs.
516 To compile this driver as a module, choose M here: the
517 module will be called tegra-kbc.
521 depends on HAS_IOMEM
526 To compile this driver as a module, choose M here; the
527 module will be called opencores-kbd.
531 depends on PXA27x || PXA3xx || ARCH_MMP
536 To compile this driver as a module, choose M here: the
541 depends on CPU_PXA930 || CPU_PXA935
545 To compile this driver as a module, choose M here: the
550 depends on MFD_PM8XXX
554 keypad provided as a reference design from Qualcomm. This is intended
557 To compile this driver as a module, choose M here: the module will
558 be called pmic8xxx-keypad.
562 depends on HAVE_CLK
565 Say Y here if you want to use the keypad on your Samsung mobile
568 To compile this driver as a module, choose M here: the
569 module will be called samsung-keypad.
572 depends on GOLDFISH || COMPILE_TEST
578 To compile this driver as a module, choose M here: the
579 module will be called goldfish-events.
585 Say Y here if you have a Stowaway keyboard on a serial port.
586 Stowaway compatible keyboards like Dicota Input-PDA keyboard
589 To compile this driver as a module, choose M here: the
594 depends on ARCH_STI || COMPILE_TEST
597 Say Y here if you want to use a keypad attached to the keyscan block
598 on some STMicroelectronics SoC devices.
600 To compile this driver as a module, choose M here: the
601 module will be called st-keyscan.
607 Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
609 (RS-232) port via a simple adapter.
611 To compile this driver as a module, choose M here: the
616 depends on ARCH_SHMOBILE || COMPILE_TEST
618 Say Y here if you want to use a keypad attached to the KEYSC block
619 on SuperH processors such as sh7722 and sh7343.
621 To compile this driver as a module, choose M here: the
626 depends on MFD_STMPE
627 depends on OF
630 Say Y here if you want to use the keypad controller on STMPE I/O
633 To compile this driver as a module, choose M here: the module will be
634 called stmpe-keypad.
638 depends on ARCH_SUNXI
641 keys found on Allwinner sunxi SoCs.
643 To compile this driver as a module, choose M here: the
644 module will be called sun4i-lradc-keys.
648 depends on ARCH_DAVINCI_DM365
653 To compile this driver as a module, choose M here: the
657 tristate "Buttons on Micro SoC (iPaq h3100,h3600,h3700)"
658 depends on MFD_IPAQ_MICRO
661 Micro peripheral controller on iPAQ h3100/h3600/h3700
663 To compile this driver as a module, choose M here: the
664 module will be called ipaq-micro-keys.
668 depends on MFD_IQS62X
671 IQS621, IQS622, IQS624 and IQS625 multi-function sensors.
673 To compile this driver as a module, choose M here: the module will
674 be called iqs62x-keys.
678 depends on ARCH_OMAP1
683 To compile this driver as a module, choose M here: the
684 module will be called omap-keypad.
688 depends on OF || ARCH_OMAP2PLUS
693 To compile this driver as a module, choose M here: the
694 module will be called omap4-keypad.
698 depends on PLAT_SPEAR
703 To compile this driver as a module, choose M here: the
704 module will be called spear-keyboard.
708 depends on MFD_TC3589X
711 Say Y here if you want to use the keypad controller on
714 To compile this driver as a module, choose M here: the
715 module will be called tc3589x-keypad.
719 depends on I2C
720 depends on LEDS_CLASS
722 Say Y here to enable device driver for tm2-touchkey with
725 To compile this driver as a module, choose M here.
726 module will be called tm2-touchkey.
730 depends on TWL4030_CORE
733 Say Y here if your board use the keypad controller on
735 even on boards that don't use the keypad controller.
737 To compile this driver as a module, choose M here: the
745 compatible) on your system. This is only possible with a
747 keyboard port on a PC that runs Linux.
749 To compile this driver as a module, choose M here: the
755 depends on CROS_EC
758 and implemented on the ChromeOS EC. You must enable one bus option
761 To compile this driver as a module, choose M here: the
766 depends on OF && I2C
771 To compile this driver as a module, choose M here: the
776 depends on OF && HAVE_CLK
782 To compile this driver as a module, choose M here: the
783 module will be called bcm-keypad.
787 depends on MFD_MT6397
791 To compile this driver as a module, choose M here: the
792 module will be called pmic-keys.