Файловый менеджер - Редактировать - /var/www/xthruster/html/wp-content/uploads/flags/input.tar
Назад
mouse/Kconfig 0000644 00000031244 14722071600 0007202 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Mouse driver configuration # menuconfig INPUT_MOUSE bool "Mice" default y help Say Y here, and a list of supported mice will be displayed. This option doesn't affect the kernel. If unsure, say Y. if INPUT_MOUSE config MOUSE_PS2 tristate "PS/2 mouse" default y select SERIO select SERIO_LIBPS2 select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO select SERIO_GSCPS2 if GSC help Say Y here if you have a PS/2 mouse connected to your system. This includes the standard 2 or 3-button PS/2 mouse, as well as PS/2 mice with wheels and extra buttons, Microsoft, Logitech or Genius compatible. Synaptics, ALPS or Elantech TouchPad users might be interested in a specialized Xorg/XFree86 driver at: <http://w1.894.telia.com/~u89404340/touchpad/index.html> and a new version of GPM at: <http://www.geocities.com/dt_or/gpm/gpm.html> <http://xorg.freedesktop.org/archive/individual/driver/> to take advantage of the advanced features of the touchpad. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called psmouse. config MOUSE_PS2_ALPS bool "ALPS PS/2 mouse protocol extension" if EXPERT default y depends on MOUSE_PS2 help Say Y here if you have an ALPS PS/2 touchpad connected to your system. If unsure, say Y. config MOUSE_PS2_BYD bool "BYD PS/2 mouse protocol extension" if EXPERT default y depends on MOUSE_PS2 help Say Y here if you have a BYD PS/2 touchpad connected to your system. If unsure, say Y. config MOUSE_PS2_LOGIPS2PP bool "Logitech PS/2++ mouse protocol extension" if EXPERT default y depends on MOUSE_PS2 help Say Y here if you have a Logitech PS/2++ mouse connected to your system. If unsure, say Y. config MOUSE_PS2_SYNAPTICS bool "Synaptics PS/2 mouse protocol extension" if EXPERT default y depends on MOUSE_PS2 help Say Y here if you have a Synaptics PS/2 TouchPad connected to your system. If unsure, say Y. config MOUSE_PS2_SYNAPTICS_SMBUS bool "Synaptics PS/2 SMbus companion" if EXPERT default y depends on MOUSE_PS2 depends on I2C=y || I2C=MOUSE_PS2 select MOUSE_PS2_SMBUS help Say Y here if you have a Synaptics RMI4 touchpad connected to to an SMBus, but enumerated through PS/2. If unsure, say Y. config MOUSE_PS2_CYPRESS bool "Cypress PS/2 mouse protocol extension" if EXPERT default y depends on MOUSE_PS2 help Say Y here if you have a Cypress PS/2 Trackpad connected to your system. If unsure, say Y. config MOUSE_PS2_LIFEBOOK bool "Fujitsu Lifebook PS/2 mouse protocol extension" if EXPERT default y depends on MOUSE_PS2 && X86 && DMI help Say Y here if you have a Fujitsu B-series Lifebook PS/2 TouchScreen connected to your system. If unsure, say Y. config MOUSE_PS2_TRACKPOINT bool "IBM Trackpoint PS/2 mouse protocol extension" if EXPERT default y depends on MOUSE_PS2 help Say Y here if you have an IBM Trackpoint PS/2 mouse connected to your system. If unsure, say Y. config MOUSE_PS2_ELANTECH bool "Elantech PS/2 protocol extension" depends on MOUSE_PS2 help Say Y here if you have an Elantech PS/2 touchpad connected to your system. This driver exposes some configuration registers via sysfs entries. For further information, see <file:Documentation/input/devices/elantech.rst>. If unsure, say N. config MOUSE_PS2_ELANTECH_SMBUS bool "Elantech PS/2 SMbus companion" if EXPERT default y depends on MOUSE_PS2 && MOUSE_PS2_ELANTECH depends on I2C=y || I2C=MOUSE_PS2 select MOUSE_PS2_SMBUS help Say Y here if you have a Elantech touchpad connected to to an SMBus, but enumerated through PS/2. If unsure, say Y. config MOUSE_PS2_SENTELIC bool "Sentelic Finger Sensing Pad PS/2 protocol extension" depends on MOUSE_PS2 help Say Y here if you have a laptop (such as MSI WIND Netbook) with Sentelic Finger Sensing Pad touchpad. If unsure, say N. config MOUSE_PS2_TOUCHKIT bool "eGalax TouchKit PS/2 protocol extension" depends on MOUSE_PS2 help Say Y here if you have an eGalax TouchKit PS/2 touchscreen connected to your system. If unsure, say N. config MOUSE_PS2_OLPC bool "OLPC PS/2 mouse protocol extension" depends on MOUSE_PS2 && OLPC help Say Y here if you have an OLPC XO-1 laptop (with built-in PS/2 touchpad/tablet device). The manufacturer calls the touchpad an HGPK. If unsure, say N. config MOUSE_PS2_FOCALTECH bool "FocalTech PS/2 mouse protocol extension" if EXPERT default y depends on MOUSE_PS2 help Say Y here if you have a FocalTech PS/2 TouchPad connected to your system. If unsure, say Y. config MOUSE_PS2_VMMOUSE bool "Virtual mouse (vmmouse)" depends on MOUSE_PS2 && X86 && HYPERVISOR_GUEST help Say Y here if you are running under control of VMware hypervisor (ESXi, Workstation or Fusion). Also make sure that when you enable this option, you remove the xf86-input-vmmouse user-space driver or upgrade it to at least xf86-input-vmmouse 13.1.0, which doesn't load in the presence of an in-kernel vmmouse driver. If unsure, say N. config MOUSE_PS2_SMBUS bool depends on MOUSE_PS2 config MOUSE_SERIAL tristate "Serial mouse" select SERIO help Say Y here if you have a serial (RS-232, COM port) mouse connected to your system. This includes Sun, MouseSystems, Microsoft, Logitech and all other compatible serial mice. If unsure, say N. To compile this driver as a module, choose M here: the module will be called sermouse. config MOUSE_APPLETOUCH tristate "Apple USB Touchpad support" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use an Apple USB Touchpad. These are the touchpads that can be found on post-February 2005 Apple Powerbooks (prior models have a Synaptics touchpad connected to the ADB bus). This driver provides a basic mouse driver but can be interfaced with the synaptics X11 driver to provide acceleration and scrolling in X11. For further information, see <file:Documentation/input/devices/appletouch.rst>. To compile this driver as a module, choose M here: the module will be called appletouch. config MOUSE_BCM5974 tristate "Apple USB BCM5974 Multitouch trackpad support" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you have an Apple USB BCM5974 Multitouch trackpad. The BCM5974 is the multitouch trackpad found in the Macbook Air (JAN2008) and Macbook Pro Penryn (FEB2008) laptops. It is also found in the IPhone (2007) and Ipod Touch (2008). This driver provides multitouch functionality together with the synaptics X11 driver. The interface is currently identical to the appletouch interface, for further information, see <file:Documentation/input/devices/appletouch.rst>. To compile this driver as a module, choose M here: the module will be called bcm5974. config MOUSE_CYAPA tristate "Cypress APA I2C Trackpad support" depends on I2C select CRC_ITU_T help This driver adds support for Cypress All Points Addressable (APA) I2C Trackpads, including the ones used in 2012 Samsung Chromebooks. Say Y here if you have a Cypress APA I2C Trackpad. To compile this driver as a module, choose M here: the module will be called cyapa. config MOUSE_ELAN_I2C tristate "ELAN I2C Touchpad support" depends on I2C help This driver adds support for Elan I2C/SMbus Trackpads. Say Y here if you have a ELAN I2C/SMbus Touchpad. To compile this driver as a module, choose M here: the module will be called elan_i2c. config MOUSE_ELAN_I2C_I2C bool "Enable I2C support" depends on MOUSE_ELAN_I2C default y help Say Y here if Elan Touchpad in your system is connected to a standard I2C controller. If unsure, say Y. config MOUSE_ELAN_I2C_SMBUS bool "Enable SMbus support" depends on MOUSE_ELAN_I2C help Say Y here if Elan Touchpad in your system is connected to a SMbus adapter. If unsure, say Y. config MOUSE_INPORT tristate "InPort/MS/ATIXL busmouse" depends on ISA help Say Y here if you have an InPort, Microsoft or ATI XL busmouse. They are rather rare these days. To compile this driver as a module, choose M here: the module will be called inport. config MOUSE_ATIXL bool "ATI XL variant" depends on MOUSE_INPORT help Say Y here if your mouse is of the ATI XL variety. config MOUSE_LOGIBM tristate "Logitech busmouse" depends on ISA help Say Y here if you have a Logitech busmouse. They are rather rare these days. To compile this driver as a module, choose M here: the module will be called logibm. config MOUSE_PC110PAD tristate "IBM PC110 touchpad" depends on ISA help Say Y if you have the IBM PC-110 micro-notebook and want its touchpad supported. To compile this driver as a module, choose M here: the module will be called pc110pad. config MOUSE_AMIGA tristate "Amiga mouse" depends on AMIGA help Say Y here if you have an Amiga and want its native mouse supported by the kernel. To compile this driver as a module, choose M here: the module will be called amimouse. config MOUSE_ATARI tristate "Atari mouse" depends on ATARI select ATARI_KBD_CORE help Say Y here if you have an Atari and want its native mouse supported by the kernel. To compile this driver as a module, choose M here: the module will be called atarimouse. config MOUSE_RISCPC tristate "Acorn RiscPC mouse" depends on ARCH_ACORN help Say Y here if you have the Acorn RiscPC computer and want its native mouse supported. To compile this driver as a module, choose M here: the module will be called rpcmouse. config MOUSE_VSXXXAA tristate "DEC VSXXX-AA/GA mouse and VSXXX-AB tablet" select SERIO help Say Y (or M) if you want to use a DEC VSXXX-AA (hockey puck) or a VSXXX-GA (rectangular) mouse. Theses mice are typically used on DECstations or VAXstations, but can also be used on any box capable of RS232 (with some adaptor described in the source file). This driver also works with the digitizer (VSXXX-AB) DEC produced. config MOUSE_GPIO tristate "GPIO mouse" depends on GPIOLIB || COMPILE_TEST select INPUT_POLLDEV help This driver simulates a mouse on GPIO lines of various CPUs (and some other chips). Say Y here if your device has buttons or a simple joystick connected directly to GPIO lines. Your board-specific setup logic must also provide a platform device and platform data saying which GPIOs are used. To compile this driver as a module, choose M here: the module will be called gpio_mouse. config MOUSE_PXA930_TRKBALL tristate "PXA930 Trackball mouse" depends on CPU_PXA930 || CPU_PXA935 help Say Y here to support PXA930 Trackball mouse. config MOUSE_MAPLE tristate "Maple mouse (for the Dreamcast)" depends on MAPLE help This driver supports the Maple mouse on the SEGA Dreamcast. Most Dreamcast users, who have a mouse, will say Y here. To compile this driver as a module choose M here: the module will be called maplemouse. config MOUSE_SYNAPTICS_I2C tristate "Synaptics I2C Touchpad support" depends on I2C help This driver supports Synaptics I2C touchpad controller on eXeda mobile device. The device will not work the synaptics X11 driver because (i) it reports only relative coordinates and has no capabilities to report absolute coordinates (ii) the eXeda device itself uses Xfbdev as X Server and it does not allow using xf86-input-* drivers. Say y here if you have eXeda device and want to use a Synaptics I2C Touchpad. To compile this driver as a module, choose M here: the module will be called synaptics_i2c. config MOUSE_SYNAPTICS_USB tristate "Synaptics USB device support" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use a Synaptics USB touchpad or pointing stick. While these devices emulate an USB mouse by default and can be used with standard usbhid driver, this driver, together with its X.Org counterpart, allows you to fully utilize capabilities of the device. More information can be found at: <http://jan-steinhoff.de/linux/synaptics-usb.html> To compile this driver as a module, choose M here: the module will be called synaptics_usb. config MOUSE_NAVPOINT_PXA27x tristate "Synaptics NavPoint (PXA27x SSP/SPI)" depends on PXA27x && PXA_SSP help This driver adds support for the Synaptics NavPoint touchpad connected to a PXA27x SSP port in SPI slave mode. The device emulates a mouse; a tap or tap-and-a-half drag gesture emulates the left mouse button. For example, use the xf86-input-evdev driver for an X pointing device. To compile this driver as a module, choose M here: the module will be called navpoint. endif mouse/Makefile 0000644 00000003461 14722071600 0007337 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the mouse drivers. # # Each configuration option enables a list of files. obj-$(CONFIG_MOUSE_AMIGA) += amimouse.o obj-$(CONFIG_MOUSE_APPLETOUCH) += appletouch.o obj-$(CONFIG_MOUSE_ATARI) += atarimouse.o obj-$(CONFIG_MOUSE_BCM5974) += bcm5974.o obj-$(CONFIG_MOUSE_CYAPA) += cyapatp.o obj-$(CONFIG_MOUSE_ELAN_I2C) += elan_i2c.o obj-$(CONFIG_MOUSE_GPIO) += gpio_mouse.o obj-$(CONFIG_MOUSE_INPORT) += inport.o obj-$(CONFIG_MOUSE_LOGIBM) += logibm.o obj-$(CONFIG_MOUSE_MAPLE) += maplemouse.o obj-$(CONFIG_MOUSE_NAVPOINT_PXA27x) += navpoint.o obj-$(CONFIG_MOUSE_PC110PAD) += pc110pad.o obj-$(CONFIG_MOUSE_PS2) += psmouse.o obj-$(CONFIG_MOUSE_PXA930_TRKBALL) += pxa930_trkball.o obj-$(CONFIG_MOUSE_RISCPC) += rpcmouse.o obj-$(CONFIG_MOUSE_SERIAL) += sermouse.o obj-$(CONFIG_MOUSE_SYNAPTICS_I2C) += synaptics_i2c.o obj-$(CONFIG_MOUSE_SYNAPTICS_USB) += synaptics_usb.o obj-$(CONFIG_MOUSE_VSXXXAA) += vsxxxaa.o cyapatp-objs := cyapa.o cyapa_gen3.o cyapa_gen5.o cyapa_gen6.o psmouse-objs := psmouse-base.o synaptics.o focaltech.o psmouse-$(CONFIG_MOUSE_PS2_ALPS) += alps.o psmouse-$(CONFIG_MOUSE_PS2_BYD) += byd.o psmouse-$(CONFIG_MOUSE_PS2_ELANTECH) += elantech.o psmouse-$(CONFIG_MOUSE_PS2_OLPC) += hgpk.o psmouse-$(CONFIG_MOUSE_PS2_LOGIPS2PP) += logips2pp.o psmouse-$(CONFIG_MOUSE_PS2_LIFEBOOK) += lifebook.o psmouse-$(CONFIG_MOUSE_PS2_SENTELIC) += sentelic.o psmouse-$(CONFIG_MOUSE_PS2_TRACKPOINT) += trackpoint.o psmouse-$(CONFIG_MOUSE_PS2_TOUCHKIT) += touchkit_ps2.o psmouse-$(CONFIG_MOUSE_PS2_CYPRESS) += cypress_ps2.o psmouse-$(CONFIG_MOUSE_PS2_VMMOUSE) += vmmouse.o psmouse-$(CONFIG_MOUSE_PS2_SMBUS) += psmouse-smbus.o elan_i2c-objs := elan_i2c_core.o elan_i2c-$(CONFIG_MOUSE_ELAN_I2C_I2C) += elan_i2c_i2c.o elan_i2c-$(CONFIG_MOUSE_ELAN_I2C_SMBUS) += elan_i2c_smbus.o touchscreen/Kconfig 0000644 00000107126 14722071600 0010377 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Touchscreen driver configuration # menuconfig INPUT_TOUCHSCREEN bool "Touchscreens" help Say Y here, and a list of supported touchscreens will be displayed. This option doesn't affect the kernel. If unsure, say Y. if INPUT_TOUCHSCREEN config TOUCHSCREEN_PROPERTIES def_tristate INPUT depends on INPUT config TOUCHSCREEN_88PM860X tristate "Marvell 88PM860x touchscreen" depends on MFD_88PM860X help Say Y here if you have a 88PM860x PMIC and want to enable support for the built-in touchscreen. If unsure, say N. To compile this driver as a module, choose M here: the module will be called 88pm860x-ts. config TOUCHSCREEN_ADS7846 tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens" depends on SPI_MASTER depends on HWMON = n || HWMON help Say Y here if you have a touchscreen interface using the ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller, and your board-specific setup code includes that in its table of SPI devices. If HWMON is selected, and the driver is told the reference voltage on your board, you will also get hwmon interfaces for the voltage (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip. If unsure, say N (but it's safe to say "Y"). To compile this driver as a module, choose M here: the module will be called ads7846. config TOUCHSCREEN_AD7877 tristate "AD7877 based touchscreens" depends on SPI_MASTER help Say Y here if you have a touchscreen interface using the AD7877 controller, and your board-specific initialization code includes that in its table of SPI devices. If unsure, say N (but it's safe to say "Y"). To compile this driver as a module, choose M here: the module will be called ad7877. config TOUCHSCREEN_AD7879 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface" help Say Y here if you want to support a touchscreen interface using the AD7879-1/AD7889-1 controller. You should select a bus connection too. To compile this driver as a module, choose M here: the module will be called ad7879. config TOUCHSCREEN_AD7879_I2C tristate "support I2C bus connection" depends on TOUCHSCREEN_AD7879 && I2C select REGMAP_I2C help Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus. To compile this driver as a module, choose M here: the module will be called ad7879-i2c. config TOUCHSCREEN_AD7879_SPI tristate "support SPI bus connection" depends on TOUCHSCREEN_AD7879 && SPI_MASTER select REGMAP_SPI help Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus. If unsure, say N (but it's safe to say "Y"). To compile this driver as a module, choose M here: the module will be called ad7879-spi. config TOUCHSCREEN_ADC tristate "Generic ADC based resistive touchscreen" depends on IIO select IIO_BUFFER select IIO_BUFFER_CB help Say Y here if you want to use the generic ADC resistive touchscreen driver. If unsure, say N (but it's safe to say "Y"). To compile this driver as a module, choose M here: the module will be called resistive-adc-touch.ko. config TOUCHSCREEN_AR1021_I2C tristate "Microchip AR1020/1021 i2c touchscreen" depends on I2C && OF help Say Y here if you have the Microchip AR1020 or AR1021 touchscreen controller chip in your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called ar1021_i2c. config TOUCHSCREEN_ATMEL_MXT tristate "Atmel mXT I2C Touchscreen" depends on I2C select FW_LOADER help Say Y here if you have Atmel mXT series I2C touchscreen, such as AT42QT602240/ATMXT224, connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called atmel_mxt_ts. config TOUCHSCREEN_ATMEL_MXT_T37 bool "Support T37 Diagnostic Data" depends on TOUCHSCREEN_ATMEL_MXT depends on VIDEO_V4L2=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_V4L2=m) select VIDEOBUF2_VMALLOC help Say Y here if you want support to output data from the T37 Diagnostic Data object using a V4L device. config TOUCHSCREEN_AUO_PIXCIR tristate "AUO in-cell touchscreen using Pixcir ICs" depends on I2C depends on GPIOLIB || COMPILE_TEST help Say Y here if you have a AUO display with in-cell touchscreen using Pixcir ICs. If unsure, say N. To compile this driver as a module, choose M here: the module will be called auo-pixcir-ts. config TOUCHSCREEN_BU21013 tristate "BU21013 based touch panel controllers" depends on I2C help Say Y here if you have a bu21013 touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called bu21013_ts. config TOUCHSCREEN_BU21029 tristate "Rohm BU21029 based touch panel controllers" depends on I2C help Say Y here if you have a Rohm BU21029 touchscreen controller connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called bu21029_ts. config TOUCHSCREEN_CHIPONE_ICN8318 tristate "chipone icn8318 touchscreen controller" depends on GPIOLIB || COMPILE_TEST depends on I2C depends on OF help Say Y here if you have a ChipOne icn8318 based I2C touchscreen. If unsure, say N. To compile this driver as a module, choose M here: the module will be called chipone_icn8318. config TOUCHSCREEN_CHIPONE_ICN8505 tristate "chipone icn8505 touchscreen controller" depends on I2C && ACPI help Say Y here if you have a ChipOne icn8505 based I2C touchscreen. If unsure, say N. To compile this driver as a module, choose M here: the module will be called chipone_icn8505. config TOUCHSCREEN_CY8CTMG110 tristate "cy8ctmg110 touchscreen" depends on I2C depends on GPIOLIB || COMPILE_TEST help Say Y here if you have a cy8ctmg110 capacitive touchscreen on an AAVA device. If unsure, say N. To compile this driver as a module, choose M here: the module will be called cy8ctmg110_ts. config TOUCHSCREEN_CYTTSP_CORE tristate "Cypress TTSP touchscreen" help Say Y here if you have a touchscreen using controller from the Cypress TrueTouch(tm) Standard Product family connected to your system. You will also need to select appropriate bus connection below. If unsure, say N. To compile this driver as a module, choose M here: the module will be called cyttsp_core. config TOUCHSCREEN_CYTTSP_I2C tristate "support I2C bus connection" depends on TOUCHSCREEN_CYTTSP_CORE && I2C help Say Y here if the touchscreen is connected via I2C bus. To compile this driver as a module, choose M here: the module will be called cyttsp_i2c. config TOUCHSCREEN_CYTTSP_SPI tristate "support SPI bus connection" depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER help Say Y here if the touchscreen is connected via SPI bus. To compile this driver as a module, choose M here: the module will be called cyttsp_spi. config TOUCHSCREEN_CYTTSP4_CORE tristate "Cypress TrueTouch Gen4 Touchscreen Driver" help Core driver for Cypress TrueTouch(tm) Standard Product Generation4 touchscreen controllers. Say Y here if you have a Cypress Gen4 touchscreen. If unsure, say N. To compile this driver as a module, choose M here. config TOUCHSCREEN_CYTTSP4_I2C tristate "support I2C bus connection" depends on TOUCHSCREEN_CYTTSP4_CORE && I2C help Say Y here if the touchscreen is connected via I2C bus. To compile this driver as a module, choose M here: the module will be called cyttsp4_i2c. config TOUCHSCREEN_CYTTSP4_SPI tristate "support SPI bus connection" depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER help Say Y here if the touchscreen is connected via SPI bus. To compile this driver as a module, choose M here: the module will be called cyttsp4_spi. config TOUCHSCREEN_DA9034 tristate "Touchscreen support for Dialog Semiconductor DA9034" depends on PMIC_DA903X default y help Say Y here to enable the support for the touchscreen found on Dialog Semiconductor DA9034 PMIC. If unsure, say N. To compile this driver as a module, choose M here: the module will be called da9034-ts. config TOUCHSCREEN_DA9052 tristate "Dialog DA9052/DA9053 TSI" depends on PMIC_DA9052 help Say Y here to support the touchscreen found on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs. If unsure, say N. To compile this driver as a module, choose M here: the module will be called da9052_tsi. config TOUCHSCREEN_DYNAPRO tristate "Dynapro serial touchscreen" select SERIO help Say Y here if you have a Dynapro serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called dynapro. config TOUCHSCREEN_HAMPSHIRE tristate "Hampshire serial touchscreen" select SERIO help Say Y here if you have a Hampshire serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called hampshire. config TOUCHSCREEN_EETI tristate "EETI touchscreen panel support" depends on I2C help Say Y here to enable support for I2C connected EETI touch panels. To compile this driver as a module, choose M here: the module will be called eeti_ts. config TOUCHSCREEN_EGALAX tristate "EETI eGalax multi-touch panel support" depends on I2C && OF help Say Y here to enable support for I2C connected EETI eGalax multi-touch panels. To compile this driver as a module, choose M here: the module will be called egalax_ts. config TOUCHSCREEN_EGALAX_SERIAL tristate "EETI eGalax serial touchscreen" select SERIO help Say Y here to enable support for serial connected EETI eGalax touch panels. To compile this driver as a module, choose M here: the module will be called egalax_ts_serial. config TOUCHSCREEN_EXC3000 tristate "EETI EXC3000 multi-touch panel support" depends on I2C help Say Y here to enable support for I2C connected EETI EXC3000 multi-touch panels. To compile this driver as a module, choose M here: the module will be called exc3000. config TOUCHSCREEN_FUJITSU tristate "Fujitsu serial touchscreen" select SERIO help Say Y here if you have the Fujitsu touchscreen (such as one installed in Lifebook P series laptop) connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called fujitsu-ts. config TOUCHSCREEN_GOODIX tristate "Goodix I2C touchscreen" depends on I2C depends on GPIOLIB || COMPILE_TEST help Say Y here if you have the Goodix touchscreen (such as one installed in Onda v975w tablets) connected to your system. It also supports 5-finger chip models, which can be found on ARM tablets, like Wexler TAB7200 and MSI Primo73. If unsure, say N. To compile this driver as a module, choose M here: the module will be called goodix. config TOUCHSCREEN_HIDEEP tristate "HiDeep Touch IC" depends on I2C help Say Y here if you have a touchscreen using HiDeep. If unsure, say N. To compile this driver as a module, choose M here : the module will be called hideep_ts. config TOUCHSCREEN_ILI210X tristate "Ilitek ILI210X based touchscreen" depends on I2C help Say Y here if you have a ILI210X based touchscreen controller. This driver supports models ILI2102, ILI2102s, ILI2103, ILI2103s and ILI2105. Such kind of chipsets can be found in Amazon Kindle Fire touchscreens. If unsure, say N. To compile this driver as a module, choose M here: the module will be called ili210x. config TOUCHSCREEN_IPROC tristate "IPROC touch panel driver support" depends on ARCH_BCM_IPROC || COMPILE_TEST help Say Y here if you want to add support for the IPROC touch controller to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called bcm_iproc_tsc. config TOUCHSCREEN_S3C2410 tristate "Samsung S3C2410/generic touchscreen input driver" depends on ARCH_S3C24XX || SAMSUNG_DEV_TS depends on S3C_ADC help Say Y here if you have the s3c2410 touchscreen. If unsure, say N. To compile this driver as a module, choose M here: the module will be called s3c2410_ts. config TOUCHSCREEN_S6SY761 tristate "Samsung S6SY761 Touchscreen driver" depends on I2C help Say Y if you have the Samsung S6SY761 driver If unsure, say N To compile this driver as module, choose M here: the module will be called s6sy761. config TOUCHSCREEN_GUNZE tristate "Gunze AHL-51S touchscreen" select SERIO help Say Y here if you have the Gunze AHL-51 touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called gunze. config TOUCHSCREEN_EKTF2127 tristate "Elan eKTF2127 I2C touchscreen" depends on I2C help Say Y here if you have an Elan eKTF2127 touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called ektf2127. config TOUCHSCREEN_ELAN tristate "Elan eKTH I2C touchscreen" depends on I2C help Say Y here if you have an Elan eKTH I2C touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called elants_i2c. config TOUCHSCREEN_ELO tristate "Elo serial touchscreens" select SERIO help Say Y here if you have an Elo serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called elo. config TOUCHSCREEN_WACOM_W8001 tristate "Wacom W8001 penabled serial touchscreen" select SERIO help Say Y here if you have an Wacom W8001 penabled serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called wacom_w8001. config TOUCHSCREEN_WACOM_I2C tristate "Wacom Tablet support (I2C)" depends on I2C help Say Y here if you want to use the I2C version of the Wacom Pen Tablet. If unsure, say N. To compile this driver as a module, choose M here: the module will be called wacom_i2c. config TOUCHSCREEN_LPC32XX tristate "LPC32XX touchscreen controller" depends on ARCH_LPC32XX help Say Y here if you have a LPC32XX device and want to support the built-in touchscreen. To compile this driver as a module, choose M here: the module will be called lpc32xx_ts. config TOUCHSCREEN_MAX11801 tristate "MAX11801 based touchscreens" depends on I2C help Say Y here if you have a MAX11801 based touchscreen controller. If unsure, say N. To compile this driver as a module, choose M here: the module will be called max11801_ts. config TOUCHSCREEN_MCS5000 tristate "MELFAS MCS-5000 touchscreen" depends on I2C help Say Y here if you have the MELFAS MCS-5000 touchscreen controller chip in your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called mcs5000_ts. config TOUCHSCREEN_MMS114 tristate "MELFAS MMS114 touchscreen" depends on I2C help Say Y here if you have the MELFAS MMS114 touchscreen controller chip in your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called mms114. config TOUCHSCREEN_MELFAS_MIP4 tristate "MELFAS MIP4 Touchscreen" depends on I2C help Say Y here if you have a MELFAS MIP4 Touchscreen device. If unsure, say N. To compile this driver as a module, choose M here: the module will be called melfas_mip4. config TOUCHSCREEN_MTOUCH tristate "MicroTouch serial touchscreens" select SERIO help Say Y here if you have a MicroTouch (3M) serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called mtouch. config TOUCHSCREEN_IMX6UL_TSC tristate "Freescale i.MX6UL touchscreen controller" depends on (OF && GPIOLIB) || COMPILE_TEST help Say Y here if you have a Freescale i.MX6UL, and want to use the internal touchscreen controller. If unsure, say N. To compile this driver as a module, choose M here: the module will be called imx6ul_tsc. config TOUCHSCREEN_INEXIO tristate "iNexio serial touchscreens" select SERIO help Say Y here if you have an iNexio serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called inexio. config TOUCHSCREEN_MK712 tristate "ICS MicroClock MK712 touchscreen" help Say Y here if you have the ICS MicroClock MK712 touchscreen controller chip in your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called mk712. config TOUCHSCREEN_HP600 tristate "HP Jornada 6xx touchscreen" depends on SH_HP6XX && SH_ADC help Say Y here if you have a HP Jornada 620/660/680/690 and want to support the built-in touchscreen. To compile this driver as a module, choose M here: the module will be called hp680_ts_input. config TOUCHSCREEN_HP7XX tristate "HP Jornada 7xx touchscreen" depends on SA1100_JORNADA720_SSP help Say Y here if you have a HP Jornada 710/720/728 and want to support the built-in touchscreen. To compile this driver as a module, choose M here: the module will be called jornada720_ts. config TOUCHSCREEN_IPAQ_MICRO tristate "HP iPAQ Atmel Micro ASIC touchscreen" depends on MFD_IPAQ_MICRO help Say Y here to enable support for the touchscreen attached to the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700 If unsure, say N. To compile this driver as a module, choose M here: the module will be called ipaq-micro-ts. config TOUCHSCREEN_HTCPEN tristate "HTC Shift X9500 touchscreen" depends on ISA help Say Y here if you have an HTC Shift UMPC also known as HTC X9500 Clio / Shangrila and want to support the built-in touchscreen. If unsure, say N. To compile this driver as a module, choose M here: the module will be called htcpen. config TOUCHSCREEN_PENMOUNT tristate "Penmount serial touchscreen" select SERIO help Say Y here if you have a Penmount serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called penmount. config TOUCHSCREEN_EDT_FT5X06 tristate "EDT FocalTech FT5x06 I2C Touchscreen support" depends on I2C help Say Y here if you have an EDT "Polytouch" touchscreen based on the FocalTech FT5x06 family of controllers connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called edt-ft5x06. config TOUCHSCREEN_RASPBERRYPI_FW tristate "Raspberry Pi's firmware base touch screen support" depends on RASPBERRYPI_FIRMWARE || (RASPBERRYPI_FIRMWARE=n && COMPILE_TEST) select INPUT_POLLDEV help Say Y here if you have the official Raspberry Pi 7 inch screen on your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called raspberrypi-ts. config TOUCHSCREEN_MIGOR tristate "Renesas MIGO-R touchscreen" depends on (SH_MIGOR || COMPILE_TEST) && I2C help Say Y here to enable MIGO-R touchscreen support. If unsure, say N. To compile this driver as a module, choose M here: the module will be called migor_ts. config TOUCHSCREEN_TOUCHRIGHT tristate "Touchright serial touchscreen" select SERIO help Say Y here if you have a Touchright serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called touchright. config TOUCHSCREEN_TOUCHWIN tristate "Touchwin serial touchscreen" select SERIO help Say Y here if you have a Touchwin serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called touchwin. config TOUCHSCREEN_TI_AM335X_TSC tristate "TI Touchscreen Interface" depends on MFD_TI_AM335X_TSCADC help Say Y here if you have 4/5/8 wire touchscreen controller to be connected to the ADC controller on your TI AM335x SoC. If unsure, say N. To compile this driver as a module, choose M here: the module will be called ti_am335x_tsc. config TOUCHSCREEN_UCB1400 tristate "Philips UCB1400 touchscreen" depends on AC97_BUS depends on UCB1400_CORE help This enables support for the Philips UCB1400 touchscreen interface. The UCB1400 is an AC97 audio codec. The touchscreen interface will be initialized only after the ALSA subsystem has been brought up and the UCB1400 detected. You therefore have to configure ALSA support as well (either built-in or modular, independently of whether this driver is itself built-in or modular) for this driver to work. To compile this driver as a module, choose M here: the module will be called ucb1400_ts. config TOUCHSCREEN_PIXCIR tristate "PIXCIR I2C touchscreens" depends on I2C help Say Y here if you have a pixcir i2c touchscreen controller. If unsure, say N. To compile this driver as a module, choose M here: the module will be called pixcir_i2c_ts. config TOUCHSCREEN_WDT87XX_I2C tristate "Weida HiTech I2C touchscreen" depends on I2C help Say Y here if you have a Weida WDT87XX I2C touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called wdt87xx_i2c. config TOUCHSCREEN_WM831X tristate "Support for WM831x touchscreen controllers" depends on MFD_WM831X help This enables support for the touchscreen controller on the WM831x series of PMICs. To compile this driver as a module, choose M here: the module will be called wm831x-ts. config TOUCHSCREEN_WM97XX tristate "Support for WM97xx AC97 touchscreen controllers" depends on AC97_BUS || AC97_BUS_NEW help Say Y here if you have a Wolfson Microelectronics WM97xx touchscreen connected to your system. Note that this option only enables core driver, you will also need to select support for appropriate chip below. If unsure, say N. To compile this driver as a module, choose M here: the module will be called wm97xx-ts. config TOUCHSCREEN_WM9705 bool "WM9705 Touchscreen interface support" depends on TOUCHSCREEN_WM97XX default y help Say Y here to enable support for the Wolfson Microelectronics WM9705 touchscreen controller. config TOUCHSCREEN_WM9712 bool "WM9712 Touchscreen interface support" depends on TOUCHSCREEN_WM97XX default y help Say Y here to enable support for the Wolfson Microelectronics WM9712 touchscreen controller. config TOUCHSCREEN_WM9713 bool "WM9713 Touchscreen interface support" depends on TOUCHSCREEN_WM97XX default y help Say Y here to enable support for the Wolfson Microelectronics WM9713 touchscreen controller. config TOUCHSCREEN_WM97XX_MAINSTONE tristate "WM97xx Mainstone/Palm accelerated touch" depends on TOUCHSCREEN_WM97XX && ARCH_PXA help Say Y here for support for streaming mode with WM97xx touchscreens on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. If unsure, say N. To compile this driver as a module, choose M here: the module will be called mainstone-wm97xx. config TOUCHSCREEN_WM97XX_ZYLONITE tristate "Zylonite accelerated touch" depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE select TOUCHSCREEN_WM9713 help Say Y here for support for streaming mode with the touchscreen on Zylonite systems. If unsure, say N. To compile this driver as a module, choose M here: the module will be called zylonite-wm97xx. config TOUCHSCREEN_USB_COMPOSITE tristate "USB Touchscreen Driver" depends on USB_ARCH_HAS_HCD select USB help USB Touchscreen driver for: - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) - PanJit TouchSet USB - 3M MicroTouch USB (EX II series) - ITM - some other eTurboTouch - Gunze AHL61 - DMC TSC-10/25 - IRTOUCHSYSTEMS/UNITOP - IdealTEK URTC1000 - GoTop Super_Q2/GogoPen/PenPower tablets - JASTEC USB Touch Controller/DigiTech DTR-02U - Zytronic controllers - Elo TouchSystems 2700 IntelliTouch - EasyTouch USB Touch Controller from Data Modul - e2i (Mimo monitors) Have a look at <http://linux.chapter7.ch/touchkit/> for a usage description and the required user-space stuff. To compile this driver as a module, choose M here: the module will be called usbtouchscreen. config TOUCHSCREEN_MXS_LRADC tristate "Freescale i.MX23/i.MX28 LRADC touchscreen" depends on MFD_MXS_LRADC help Say Y here if you have a touchscreen connected to the low-resolution analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor. To compile this driver as a module, choose M here: the module will be called mxs-lradc-ts. config TOUCHSCREEN_MX25 tristate "Freescale i.MX25 touchscreen input driver" depends on MFD_MX25_TSADC help Enable support for touchscreen connected to your i.MX25. To compile this driver as a module, choose M here: the module will be called fsl-imx25-tcq. config TOUCHSCREEN_MC13783 tristate "Freescale MC13783 touchscreen input driver" depends on MFD_MC13XXX help Say Y here if you have an Freescale MC13783 PMIC on your board and want to use its touchscreen If unsure, say N. To compile this driver as a module, choose M here: the module will be called mc13783_ts. config TOUCHSCREEN_USB_EGALAX default y bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_PANJIT default y bool "PanJit device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_3M default y bool "3M/Microtouch EX II series device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_ITM default y bool "ITM device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_ETURBO default y bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_GUNZE default y bool "Gunze AHL61 device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_DMC_TSC10 default y bool "DMC TSC-10/25 device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_IRTOUCH default y bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_IDEALTEK default y bool "IdealTEK URTC1000 device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_GENERAL_TOUCH default y bool "GeneralTouch Touchscreen device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_GOTOP default y bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_JASTEC default y bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_ELO default y bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_E2I default y bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_ZYTRONIC default y bool "Zytronic controller" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_ETT_TC45USB default y bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_NEXIO default y bool "NEXIO/iNexio device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE config TOUCHSCREEN_USB_EASYTOUCH default y bool "EasyTouch USB Touch controller device support" if EXPERT depends on TOUCHSCREEN_USB_COMPOSITE help Say Y here if you have an EasyTouch USB Touch controller. If unsure, say N. config TOUCHSCREEN_TOUCHIT213 tristate "Sahara TouchIT-213 touchscreen" select SERIO help Say Y here if you have a Sahara TouchIT-213 Tablet PC. If unsure, say N. To compile this driver as a module, choose M here: the module will be called touchit213. config TOUCHSCREEN_TS4800 tristate "TS-4800 touchscreen" depends on HAS_IOMEM && OF depends on SOC_IMX51 || COMPILE_TEST select MFD_SYSCON select INPUT_POLLDEV help Say Y here if you have a touchscreen on a TS-4800 board. On TS-4800, the touchscreen is not handled directly by Linux but by a companion FPGA. If unsure, say N. To compile this driver as a module, choose M here: the module will be called ts4800_ts. config TOUCHSCREEN_TSC_SERIO tristate "TSC-10/25/40 serial touchscreen support" select SERIO help Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called tsc40. config TOUCHSCREEN_TSC200X_CORE tristate config TOUCHSCREEN_TSC2004 tristate "TSC2004 based touchscreens" depends on I2C select REGMAP_I2C select TOUCHSCREEN_TSC200X_CORE help Say Y here if you have a TSC2004 based touchscreen. If unsure, say N. To compile this driver as a module, choose M here: the module will be called tsc2004. config TOUCHSCREEN_TSC2005 tristate "TSC2005 based touchscreens" depends on SPI_MASTER select REGMAP_SPI select TOUCHSCREEN_TSC200X_CORE help Say Y here if you have a TSC2005 based touchscreen. If unsure, say N. To compile this driver as a module, choose M here: the module will be called tsc2005. config TOUCHSCREEN_TSC2007 tristate "TSC2007 based touchscreens" depends on I2C help Say Y here if you have a TSC2007 based touchscreen. If unsure, say N. To compile this driver as a module, choose M here: the module will be called tsc2007. config TOUCHSCREEN_TSC2007_IIO bool "IIO interface for external ADC input and temperature" depends on TOUCHSCREEN_TSC2007 depends on IIO=y || IIO=TOUCHSCREEN_TSC2007 help Saying Y here adds an iio interface to the tsc2007 which provides values for the AUX input (used for e.g. battery or ambient light monitoring), temperature and raw input values. config TOUCHSCREEN_PCAP tristate "Motorola PCAP touchscreen" depends on EZX_PCAP help Say Y here if you have a Motorola EZX telephone and want to enable support for the built-in touchscreen. To compile this driver as a module, choose M here: the module will be called pcap_ts. config TOUCHSCREEN_RM_TS tristate "Raydium I2C Touchscreen" depends on I2C depends on GPIOLIB || COMPILE_TEST help Say Y here if you have Raydium series I2C touchscreen, such as RM32380, connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called raydium_i2c_ts. config TOUCHSCREEN_SILEAD tristate "Silead I2C touchscreen" depends on I2C help Say Y here if you have the Silead touchscreen connected to your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called silead. config TOUCHSCREEN_SIS_I2C tristate "SiS 9200 family I2C touchscreen" depends on I2C select CRC_ITU_T depends on GPIOLIB || COMPILE_TEST help This enables support for SiS 9200 family over I2C based touchscreens. If unsure, say N. To compile this driver as a module, choose M here: the module will be called sis_i2c. config TOUCHSCREEN_ST1232 tristate "Sitronix ST1232 or ST1633 touchscreen controllers" depends on I2C help Say Y here if you want to support the Sitronix ST1232 or ST1633 touchscreen controller. If unsure, say N. To compile this driver as a module, choose M here: the module will be called st1232_ts. config TOUCHSCREEN_STMFTS tristate "STMicroelectronics STMFTS touchscreen" depends on I2C depends on LEDS_CLASS help Say Y here if you want support for STMicroelectronics STMFTS touchscreen. To compile this driver as a module, choose M here: the module will be called stmfts. config TOUCHSCREEN_STMPE tristate "STMicroelectronics STMPE touchscreens" depends on MFD_STMPE depends on (OF || COMPILE_TEST) help Say Y here if you want support for STMicroelectronics STMPE touchscreen controllers. To compile this driver as a module, choose M here: the module will be called stmpe-ts. config TOUCHSCREEN_SUN4I tristate "Allwinner sun4i resistive touchscreen controller support" depends on ARCH_SUNXI || COMPILE_TEST depends on HWMON depends on THERMAL || !THERMAL_OF help This selects support for the resistive touchscreen controller found on Allwinner sunxi SoCs. To compile this driver as a module, choose M here: the module will be called sun4i-ts. config TOUCHSCREEN_SUR40 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen" depends on USB && MEDIA_USB_SUPPORT && HAS_DMA depends on VIDEO_V4L2 select INPUT_POLLDEV select VIDEOBUF2_DMA_SG help Say Y here if you want support for the Samsung SUR40 touchscreen (also known as Microsoft Surface 2.0 or Microsoft PixelSense). To compile this driver as a module, choose M here: the module will be called sur40. config TOUCHSCREEN_SURFACE3_SPI tristate "Ntrig/Microsoft Surface 3 SPI touchscreen" depends on SPI depends on GPIOLIB || COMPILE_TEST help Say Y here if you have the Ntrig/Microsoft SPI touchscreen controller chip as found on the Surface 3 in your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called surface3_spi. config TOUCHSCREEN_SX8654 tristate "Semtech SX8654 touchscreen" depends on I2C help Say Y here if you have a Semtech SX8654 touchscreen controller. If unsure, say N To compile this driver as a module, choose M here: the module will be called sx8654. config TOUCHSCREEN_TPS6507X tristate "TPS6507x based touchscreens" depends on I2C select INPUT_POLLDEV help Say Y here if you have a TPS6507x based touchscreen controller. If unsure, say N. To compile this driver as a module, choose M here: the module will be called tps6507x_ts. config TOUCHSCREEN_ZET6223 tristate "Zeitec ZET6223 touchscreen driver" depends on I2C help Say Y here if you have a touchscreen using Zeitec ZET6223 If unsure, say N. To compile this driver as a module, choose M here: the module will be called zet6223. config TOUCHSCREEN_ZFORCE tristate "Neonode zForce infrared touchscreens" depends on I2C depends on GPIOLIB || COMPILE_TEST help Say Y here if you have a touchscreen using the zforce infraread technology from Neonode. If unsure, say N. To compile this driver as a module, choose M here: the module will be called zforce_ts. config TOUCHSCREEN_COLIBRI_VF50 tristate "Toradex Colibri on board touchscreen driver" depends on IIO && VF610_ADC depends on GPIOLIB || COMPILE_TEST help Say Y here if you have a Colibri VF50 and plan to use the on-board provided 4-wire touchscreen driver. If unsure, say N. To compile this driver as a module, choose M here: the module will be called colibri_vf50_ts. config TOUCHSCREEN_ROHM_BU21023 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens" depends on I2C help Say Y here if you have a touchscreen using ROHM BU21023/24. If unsure, say N. To compile this driver as a module, choose M here: the module will be called bu21023_ts. config TOUCHSCREEN_IQS5XX tristate "Azoteq IQS550/572/525 trackpad/touchscreen controller" depends on I2C help Say Y to enable support for the Azoteq IQS550/572/525 family of trackpad/touchscreen controllers. To compile this driver as a module, choose M here: the module will be called iqs5xx. endif touchscreen/Makefile 0000644 00000012474 14722071600 0010535 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the touchscreen drivers. # # Each configuration option enables a list of files. wm97xx-ts-y := wm97xx-core.o obj-$(CONFIG_TOUCHSCREEN_PROPERTIES) += of_touchscreen.o obj-$(CONFIG_TOUCHSCREEN_88PM860X) += 88pm860x-ts.o obj-$(CONFIG_TOUCHSCREEN_AD7877) += ad7877.o obj-$(CONFIG_TOUCHSCREEN_AD7879) += ad7879.o obj-$(CONFIG_TOUCHSCREEN_AD7879_I2C) += ad7879-i2c.o obj-$(CONFIG_TOUCHSCREEN_AD7879_SPI) += ad7879-spi.o obj-$(CONFIG_TOUCHSCREEN_ADC) += resistive-adc-touch.o obj-$(CONFIG_TOUCHSCREEN_ADS7846) += ads7846.o obj-$(CONFIG_TOUCHSCREEN_AR1021_I2C) += ar1021_i2c.o obj-$(CONFIG_TOUCHSCREEN_ATMEL_MXT) += atmel_mxt_ts.o obj-$(CONFIG_TOUCHSCREEN_AUO_PIXCIR) += auo-pixcir-ts.o obj-$(CONFIG_TOUCHSCREEN_BU21013) += bu21013_ts.o obj-$(CONFIG_TOUCHSCREEN_BU21029) += bu21029_ts.o obj-$(CONFIG_TOUCHSCREEN_CHIPONE_ICN8318) += chipone_icn8318.o obj-$(CONFIG_TOUCHSCREEN_CHIPONE_ICN8505) += chipone_icn8505.o obj-$(CONFIG_TOUCHSCREEN_CY8CTMG110) += cy8ctmg110_ts.o obj-$(CONFIG_TOUCHSCREEN_CYTTSP_CORE) += cyttsp_core.o obj-$(CONFIG_TOUCHSCREEN_CYTTSP_I2C) += cyttsp_i2c.o cyttsp_i2c_common.o obj-$(CONFIG_TOUCHSCREEN_CYTTSP_SPI) += cyttsp_spi.o obj-$(CONFIG_TOUCHSCREEN_CYTTSP4_CORE) += cyttsp4_core.o obj-$(CONFIG_TOUCHSCREEN_CYTTSP4_I2C) += cyttsp4_i2c.o cyttsp_i2c_common.o obj-$(CONFIG_TOUCHSCREEN_CYTTSP4_SPI) += cyttsp4_spi.o obj-$(CONFIG_TOUCHSCREEN_DA9034) += da9034-ts.o obj-$(CONFIG_TOUCHSCREEN_DA9052) += da9052_tsi.o obj-$(CONFIG_TOUCHSCREEN_DYNAPRO) += dynapro.o obj-$(CONFIG_TOUCHSCREEN_EDT_FT5X06) += edt-ft5x06.o obj-$(CONFIG_TOUCHSCREEN_HAMPSHIRE) += hampshire.o obj-$(CONFIG_TOUCHSCREEN_GUNZE) += gunze.o obj-$(CONFIG_TOUCHSCREEN_EETI) += eeti_ts.o obj-$(CONFIG_TOUCHSCREEN_EKTF2127) += ektf2127.o obj-$(CONFIG_TOUCHSCREEN_ELAN) += elants_i2c.o obj-$(CONFIG_TOUCHSCREEN_ELO) += elo.o obj-$(CONFIG_TOUCHSCREEN_EGALAX) += egalax_ts.o obj-$(CONFIG_TOUCHSCREEN_EGALAX_SERIAL) += egalax_ts_serial.o obj-$(CONFIG_TOUCHSCREEN_EXC3000) += exc3000.o obj-$(CONFIG_TOUCHSCREEN_FUJITSU) += fujitsu_ts.o obj-$(CONFIG_TOUCHSCREEN_GOODIX) += goodix.o obj-$(CONFIG_TOUCHSCREEN_HIDEEP) += hideep.o obj-$(CONFIG_TOUCHSCREEN_ILI210X) += ili210x.o obj-$(CONFIG_TOUCHSCREEN_IMX6UL_TSC) += imx6ul_tsc.o obj-$(CONFIG_TOUCHSCREEN_INEXIO) += inexio.o obj-$(CONFIG_TOUCHSCREEN_IPROC) += bcm_iproc_tsc.o obj-$(CONFIG_TOUCHSCREEN_LPC32XX) += lpc32xx_ts.o obj-$(CONFIG_TOUCHSCREEN_MAX11801) += max11801_ts.o obj-$(CONFIG_TOUCHSCREEN_MXS_LRADC) += mxs-lradc-ts.o obj-$(CONFIG_TOUCHSCREEN_MX25) += fsl-imx25-tcq.o obj-$(CONFIG_TOUCHSCREEN_MC13783) += mc13783_ts.o obj-$(CONFIG_TOUCHSCREEN_MCS5000) += mcs5000_ts.o obj-$(CONFIG_TOUCHSCREEN_MELFAS_MIP4) += melfas_mip4.o obj-$(CONFIG_TOUCHSCREEN_MIGOR) += migor_ts.o obj-$(CONFIG_TOUCHSCREEN_MMS114) += mms114.o obj-$(CONFIG_TOUCHSCREEN_MTOUCH) += mtouch.o obj-$(CONFIG_TOUCHSCREEN_MK712) += mk712.o obj-$(CONFIG_TOUCHSCREEN_HP600) += hp680_ts_input.o obj-$(CONFIG_TOUCHSCREEN_HP7XX) += jornada720_ts.o obj-$(CONFIG_TOUCHSCREEN_IPAQ_MICRO) += ipaq-micro-ts.o obj-$(CONFIG_TOUCHSCREEN_HTCPEN) += htcpen.o obj-$(CONFIG_TOUCHSCREEN_USB_COMPOSITE) += usbtouchscreen.o obj-$(CONFIG_TOUCHSCREEN_PCAP) += pcap_ts.o obj-$(CONFIG_TOUCHSCREEN_PENMOUNT) += penmount.o obj-$(CONFIG_TOUCHSCREEN_PIXCIR) += pixcir_i2c_ts.o obj-$(CONFIG_TOUCHSCREEN_RM_TS) += raydium_i2c_ts.o obj-$(CONFIG_TOUCHSCREEN_S3C2410) += s3c2410_ts.o obj-$(CONFIG_TOUCHSCREEN_S6SY761) += s6sy761.o obj-$(CONFIG_TOUCHSCREEN_SILEAD) += silead.o obj-$(CONFIG_TOUCHSCREEN_SIS_I2C) += sis_i2c.o obj-$(CONFIG_TOUCHSCREEN_ST1232) += st1232.o obj-$(CONFIG_TOUCHSCREEN_STMFTS) += stmfts.o obj-$(CONFIG_TOUCHSCREEN_STMPE) += stmpe-ts.o obj-$(CONFIG_TOUCHSCREEN_SUN4I) += sun4i-ts.o obj-$(CONFIG_TOUCHSCREEN_SUR40) += sur40.o obj-$(CONFIG_TOUCHSCREEN_SURFACE3_SPI) += surface3_spi.o obj-$(CONFIG_TOUCHSCREEN_TI_AM335X_TSC) += ti_am335x_tsc.o obj-$(CONFIG_TOUCHSCREEN_TOUCHIT213) += touchit213.o obj-$(CONFIG_TOUCHSCREEN_TOUCHRIGHT) += touchright.o obj-$(CONFIG_TOUCHSCREEN_TOUCHWIN) += touchwin.o obj-$(CONFIG_TOUCHSCREEN_TS4800) += ts4800-ts.o obj-$(CONFIG_TOUCHSCREEN_TSC_SERIO) += tsc40.o obj-$(CONFIG_TOUCHSCREEN_TSC200X_CORE) += tsc200x-core.o obj-$(CONFIG_TOUCHSCREEN_TSC2004) += tsc2004.o obj-$(CONFIG_TOUCHSCREEN_TSC2005) += tsc2005.o tsc2007-y := tsc2007_core.o tsc2007-$(CONFIG_TOUCHSCREEN_TSC2007_IIO) += tsc2007_iio.o obj-$(CONFIG_TOUCHSCREEN_TSC2007) += tsc2007.o obj-$(CONFIG_TOUCHSCREEN_UCB1400) += ucb1400_ts.o obj-$(CONFIG_TOUCHSCREEN_WACOM_W8001) += wacom_w8001.o obj-$(CONFIG_TOUCHSCREEN_WACOM_I2C) += wacom_i2c.o obj-$(CONFIG_TOUCHSCREEN_WDT87XX_I2C) += wdt87xx_i2c.o obj-$(CONFIG_TOUCHSCREEN_WM831X) += wm831x-ts.o obj-$(CONFIG_TOUCHSCREEN_WM97XX) += wm97xx-ts.o wm97xx-ts-$(CONFIG_TOUCHSCREEN_WM9705) += wm9705.o wm97xx-ts-$(CONFIG_TOUCHSCREEN_WM9712) += wm9712.o wm97xx-ts-$(CONFIG_TOUCHSCREEN_WM9713) += wm9713.o obj-$(CONFIG_TOUCHSCREEN_WM97XX_MAINSTONE) += mainstone-wm97xx.o obj-$(CONFIG_TOUCHSCREEN_WM97XX_ZYLONITE) += zylonite-wm97xx.o obj-$(CONFIG_TOUCHSCREEN_SX8654) += sx8654.o obj-$(CONFIG_TOUCHSCREEN_TPS6507X) += tps6507x-ts.o obj-$(CONFIG_TOUCHSCREEN_ZET6223) += zet6223.o obj-$(CONFIG_TOUCHSCREEN_ZFORCE) += zforce_ts.o obj-$(CONFIG_TOUCHSCREEN_COLIBRI_VF50) += colibri-vf50-ts.o obj-$(CONFIG_TOUCHSCREEN_ROHM_BU21023) += rohm_bu21023.o obj-$(CONFIG_TOUCHSCREEN_RASPBERRYPI_FW) += raspberrypi-ts.o obj-$(CONFIG_TOUCHSCREEN_IQS5XX) += iqs5xx.o gameport/Kconfig 0000644 00000003556 14722071600 0007675 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Gameport configuration # config GAMEPORT tristate "Gameport support" ---help--- Gameport support is for the standard 15-pin PC gameport. If you have a joystick, gamepad, gameport card, a soundcard with a gameport or anything else that uses the gameport, say Y or M here and also to at least one of the hardware specific drivers. For Ensoniq AudioPCI (ES1370), AudioPCI 97 (ES1371), ESS Solo1, S3 SonicVibes, Trident 4DWave, SiS7018, and ALi 5451 gameport support is provided by the sound drivers, so you won't need any from the below listed modules. You still need to say Y here. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called gameport. if GAMEPORT config GAMEPORT_NS558 tristate "Classic ISA and PnP gameport support" help Say Y here if you have an ISA or PnP gameport. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called ns558. config GAMEPORT_L4 tristate "PDPI Lightning 4 gamecard support" help Say Y here if you have a PDPI Lightning 4 gamecard. To compile this driver as a module, choose M here: the module will be called lightning. config GAMEPORT_EMU10K1 tristate "SB Live and Audigy gameport support" depends on PCI help Say Y here if you have a SoundBlaster Live! or SoundBlaster Audigy card and want to use its gameport. To compile this driver as a module, choose M here: the module will be called emu10k1-gp. config GAMEPORT_FM801 tristate "ForteMedia FM801 gameport support" depends on PCI help Say Y here if you have ForteMedia FM801 PCI audio controller (Abit AU10, Genius Sound Maker, HP Workstation zx2000, and others), and want to use its gameport. To compile this driver as a module, choose M here: the module will be called fm801-gp. endif gameport/Makefile 0000644 00000000524 14722071600 0010022 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the gameport drivers. # # Each configuration option enables a list of files. obj-$(CONFIG_GAMEPORT) += gameport.o obj-$(CONFIG_GAMEPORT_EMU10K1) += emu10k1-gp.o obj-$(CONFIG_GAMEPORT_FM801) += fm801-gp.o obj-$(CONFIG_GAMEPORT_L4) += lightning.o obj-$(CONFIG_GAMEPORT_NS558) += ns558.o Kconfig 0000644 00000014013 14722071600 0006045 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Input device configuration # menu "Input device support" depends on !UML config INPUT tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT default y help Say Y here if you have any input device (mouse, keyboard, tablet, joystick, steering wheel ...) connected to your system and want it to be available to applications. This includes standard PS/2 keyboard and mouse. Say N here if you have a headless (no monitor, no keyboard) system. More information is available: <file:Documentation/input/input.rst> If unsure, say Y. To compile this driver as a module, choose M here: the module will be called input. if INPUT config INPUT_LEDS tristate "Export input device LEDs in sysfs" depends on LEDS_CLASS default INPUT help Say Y here if you would like to export LEDs on input devices as standard LED class devices in sysfs. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called input-leds. config INPUT_FF_MEMLESS tristate "Support for memoryless force-feedback devices" help Say Y here if you have memoryless force-feedback input device such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual Power 2, or similar. You will also need to enable hardware-specific driver. If unsure, say N. To compile this driver as a module, choose M here: the module will be called ff-memless. config INPUT_POLLDEV tristate "Polled input device skeleton" help Say Y here if you are using a driver for an input device that periodically polls hardware state. This option is only useful for out-of-tree drivers since in-tree drivers select it automatically. If unsure, say N. To compile this driver as a module, choose M here: the module will be called input-polldev. config INPUT_SPARSEKMAP tristate "Sparse keymap support library" help Say Y here if you are using a driver for an input device that uses sparse keymap. This option is only useful for out-of-tree drivers since in-tree drivers select it automatically. If unsure, say N. To compile this driver as a module, choose M here: the module will be called sparse-keymap. config INPUT_MATRIXKMAP tristate "Matrix keymap support library" help Say Y here if you are using a driver for an input device that uses matrix keymap. This option is only useful for out-of-tree drivers since in-tree drivers select it automatically. If unsure, say N. To compile this driver as a module, choose M here: the module will be called matrix-keymap. comment "Userland interfaces" config INPUT_MOUSEDEV tristate "Mouse interface" help Say Y here if you want your mouse to be accessible as char devices 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an emulated IntelliMouse Explorer PS/2 mouse. That way, all user space programs (including SVGAlib, GPM and X) will be able to use your mouse. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called mousedev. config INPUT_MOUSEDEV_PSAUX bool "Provide legacy /dev/psaux device" depends on INPUT_MOUSEDEV help Say Y here if you want your mouse also be accessible as char device 10:1 - /dev/psaux. The data available through /dev/psaux is exactly the same as the data from /dev/input/mice. If unsure, say Y. config INPUT_MOUSEDEV_SCREEN_X int "Horizontal screen resolution" depends on INPUT_MOUSEDEV default "1024" help If you're using a digitizer, or a graphic tablet, and want to use it as a mouse then the mousedev driver needs to know the X window screen resolution you are using to correctly scale the data. If you're not using a digitizer, this value is ignored. config INPUT_MOUSEDEV_SCREEN_Y int "Vertical screen resolution" depends on INPUT_MOUSEDEV default "768" help If you're using a digitizer, or a graphic tablet, and want to use it as a mouse then the mousedev driver needs to know the X window screen resolution you are using to correctly scale the data. If you're not using a digitizer, this value is ignored. config INPUT_JOYDEV tristate "Joystick interface" help Say Y here if you want your joystick or gamepad to be accessible as char device 13:0+ - /dev/input/jsX device. If unsure, say Y. More information is available: <file:Documentation/input/joydev/joystick.rst> To compile this driver as a module, choose M here: the module will be called joydev. config INPUT_EVDEV tristate "Event interface" help Say Y here if you want your input device events be accessible under char device 13:64+ - /dev/input/eventX in a generic way. To compile this driver as a module, choose M here: the module will be called evdev. config INPUT_EVBUG tristate "Event debugging" help Say Y here if you have a problem with the input subsystem and want all events (keypresses, mouse movements), to be output to the system log. While this is useful for debugging, it's also a security threat - your keypresses include your passwords, of course. If unsure, say N. To compile this driver as a module, choose M here: the module will be called evbug. config INPUT_APMPOWER tristate "Input Power Event -> APM Bridge" if EXPERT depends on INPUT && APM_EMULATION help Say Y here if you want suspend key events to trigger a user requested suspend through APM. This is useful on embedded systems where such behaviour is desired without userspace interaction. If unsure, say N. To compile this driver as a module, choose M here: the module will be called apm-power. comment "Input Device Drivers" source "drivers/input/keyboard/Kconfig" source "drivers/input/mouse/Kconfig" source "drivers/input/joystick/Kconfig" source "drivers/input/tablet/Kconfig" source "drivers/input/touchscreen/Kconfig" source "drivers/input/misc/Kconfig" source "drivers/input/rmi4/Kconfig" endif menu "Hardware I/O ports" source "drivers/input/serio/Kconfig" source "drivers/input/gameport/Kconfig" endmenu endmenu misc/Kconfig 0000644 00000064116 14722071600 0007011 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Input misc drivers configuration # menuconfig INPUT_MISC bool "Miscellaneous devices" help Say Y here, and a list of miscellaneous input drivers will be displayed. Everything that didn't fit into the other categories is here. This option doesn't affect the kernel. If unsure, say Y. if INPUT_MISC config INPUT_88PM860X_ONKEY tristate "88PM860x ONKEY support" depends on MFD_88PM860X help Support the ONKEY of Marvell 88PM860x PMICs as an input device reporting power button status. To compile this driver as a module, choose M here: the module will be called 88pm860x_onkey. config INPUT_88PM80X_ONKEY tristate "88PM80x ONKEY support" depends on MFD_88PM800 help Support the ONKEY of Marvell 88PM80x PMICs as an input device reporting power button status. To compile this driver as a module, choose M here: the module will be called 88pm80x_onkey. config INPUT_AB8500_PONKEY tristate "AB8500 Pon (PowerOn) Key" depends on AB8500_CORE help Say Y here to use the PowerOn Key for ST-Ericsson's AB8500 Mix-Sig PMIC. To compile this driver as a module, choose M here: the module will be called ab8500-ponkey. config INPUT_AD714X tristate "Analog Devices AD714x Capacitance Touch Sensor" help Say Y here if you want to support an AD7142/3/7/8/7A touch sensor. You should select a bus connection too. To compile this driver as a module, choose M here: the module will be called ad714x. config INPUT_AD714X_I2C tristate "support I2C bus connection" depends on INPUT_AD714X && I2C default y help Say Y here if you have AD7142/AD7147 hooked to an I2C bus. To compile this driver as a module, choose M here: the module will be called ad714x-i2c. config INPUT_AD714X_SPI tristate "support SPI bus connection" depends on INPUT_AD714X && SPI default y help Say Y here if you have AD7142/AD7147 hooked to a SPI bus. To compile this driver as a module, choose M here: the module will be called ad714x-spi. config INPUT_ARIZONA_HAPTICS tristate "Arizona haptics support" depends on MFD_ARIZONA && SND_SOC select INPUT_FF_MEMLESS help Say Y to enable support for the haptics module in Arizona CODECs. To compile this driver as a module, choose M here: the module will be called arizona-haptics. config INPUT_ATMEL_CAPTOUCH tristate "Atmel Capacitive Touch Button Driver" depends on OF || COMPILE_TEST depends on I2C help Say Y here if an Atmel Capacitive Touch Button device which implements "captouch" protocol is connected to I2C bus. Typically this device consists of Atmel Touch sensor controlled by AtMegaXX MCU running firmware based on Qtouch library. One should find "atmel,captouch" node in the board specific DTS. To compile this driver as a module, choose M here: the module will be called atmel_captouch. config INPUT_BMA150 tristate "BMA150/SMB380 acceleration sensor support" depends on I2C select INPUT_POLLDEV help Say Y here if you have Bosch Sensortec's BMA150 or SMB380 acceleration sensor hooked to an I2C bus. To compile this driver as a module, choose M here: the module will be called bma150. config INPUT_E3X0_BUTTON tristate "NI Ettus Research USRP E3xx Button support." default n help Say Y here to enable support for the NI Ettus Research USRP E3xx Button. To compile this driver as a module, choose M here: the module will be called e3x0_button. config INPUT_MSM_VIBRATOR tristate "Qualcomm MSM vibrator driver" select INPUT_FF_MEMLESS help Support for the vibrator that is found on various Qualcomm MSM SOCs. To compile this driver as a module, choose M here: the module will be called msm_vibrator. config INPUT_PCSPKR tristate "PC Speaker support" depends on PCSPKR_PLATFORM help Say Y here if you want the standard PC Speaker to be used for bells and whistles. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called pcspkr. config INPUT_PM8941_PWRKEY tristate "Qualcomm PM8941 power key support" depends on MFD_SPMI_PMIC help Say Y here if you want support for the power key usually found on boards using a Qualcomm PM8941 compatible PMIC. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called pm8941-pwrkey. config INPUT_PM8XXX_VIBRATOR tristate "Qualcomm PM8XXX vibrator support" depends on MFD_PM8XXX || MFD_SPMI_PMIC select INPUT_FF_MEMLESS help This option enables device driver support for the vibrator on Qualcomm PM8xxx chip. This driver supports ff-memless interface from input framework. To compile this driver as module, choose M here: the module will be called pm8xxx-vibrator. config INPUT_PMIC8XXX_PWRKEY tristate "PMIC8XXX power key support" depends on MFD_PM8XXX help Say Y here if you want support for the PMIC8XXX power key. If unsure, say N. To compile this driver as a module, choose M here: the module will be called pmic8xxx-pwrkey. config INPUT_SPARCSPKR tristate "SPARC Speaker support" depends on PCI && SPARC64 help Say Y here if you want the standard Speaker on Sparc PCI systems to be used for bells and whistles. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called sparcspkr. config INPUT_M68K_BEEP tristate "M68k Beeper support" depends on M68K config INPUT_MAX77650_ONKEY tristate "Maxim MAX77650 ONKEY support" depends on MFD_MAX77650 help Support the ONKEY of the MAX77650 PMIC as an input device. To compile this driver as a module, choose M here: the module will be called max77650-onkey. config INPUT_MAX77693_HAPTIC tristate "MAXIM MAX77693/MAX77843 haptic controller support" depends on (MFD_MAX77693 || MFD_MAX77843) && PWM select INPUT_FF_MEMLESS help This option enables support for the haptic controller on MAXIM MAX77693 and MAX77843 chips. To compile this driver as module, choose M here: the module will be called max77693-haptic. config INPUT_MAX8925_ONKEY tristate "MAX8925 ONKEY support" depends on MFD_MAX8925 help Support the ONKEY of MAX8925 PMICs as an input device reporting power button status. To compile this driver as a module, choose M here: the module will be called max8925_onkey. config INPUT_MAX8997_HAPTIC tristate "MAXIM MAX8997 haptic controller support" depends on PWM && MFD_MAX8997 select INPUT_FF_MEMLESS help This option enables device driver support for the haptic controller on MAXIM MAX8997 chip. This driver supports ff-memless interface from input framework. To compile this driver as module, choose M here: the module will be called max8997-haptic. config INPUT_MC13783_PWRBUTTON tristate "MC13783 ON buttons" depends on MFD_MC13XXX help Support the ON buttons of MC13783 PMIC as an input device reporting power button status. To compile this driver as a module, choose M here: the module will be called mc13783-pwrbutton. config INPUT_MMA8450 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" depends on I2C select INPUT_POLLDEV help Say Y here if you want to support Freescale's MMA8450 Accelerometer through I2C interface. To compile this driver as a module, choose M here: the module will be called mma8450. config INPUT_APANEL tristate "Fujitsu Lifebook Application Panel buttons" depends on X86 && I2C && LEDS_CLASS select INPUT_POLLDEV select CHECK_SIGNATURE help Say Y here for support of the Application Panel buttons, used on Fujitsu Lifebook. These are attached to the mainboard through an SMBus interface managed by the I2C Intel ICH (i801) driver, which you should also build for this kernel. To compile this driver as a module, choose M here: the module will be called apanel. config INPUT_GP2A tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver" depends on I2C depends on GPIOLIB || COMPILE_TEST help Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip hooked to an I2C bus. To compile this driver as a module, choose M here: the module will be called gp2ap002a00f. config INPUT_GPIO_BEEPER tristate "Generic GPIO Beeper support" depends on GPIOLIB || COMPILE_TEST help Say Y here if you have a beeper connected to a GPIO pin. To compile this driver as a module, choose M here: the module will be called gpio-beeper. config INPUT_GPIO_DECODER tristate "Polled GPIO Decoder Input driver" depends on GPIOLIB || COMPILE_TEST select INPUT_POLLDEV help Say Y here if you want driver to read status of multiple GPIO lines and report the encoded value as an absolute integer to input subsystem. To compile this driver as a module, choose M here: the module will be called gpio_decoder. config INPUT_GPIO_VIBRA tristate "GPIO vibrator support" depends on GPIOLIB || COMPILE_TEST select INPUT_FF_MEMLESS help Say Y here to get support for GPIO based vibrator devices. If unsure, say N. To compile this driver as a module, choose M here: the module will be called gpio-vibra. config INPUT_IXP4XX_BEEPER tristate "IXP4XX Beeper support" depends on ARCH_IXP4XX help If you say yes here, you can connect a beeper to the ixp4xx gpio pins. This is used by the LinkSys NSLU2. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called ixp4xx-beeper. config INPUT_COBALT_BTNS tristate "Cobalt button interface" depends on MIPS_COBALT select INPUT_POLLDEV help Say Y here if you want to support MIPS Cobalt button interface. To compile this driver as a module, choose M here: the module will be called cobalt_btns. config INPUT_CPCAP_PWRBUTTON tristate "CPCAP OnKey" depends on MFD_CPCAP help Say Y here if you want to enable power key reporting via the Motorola CPCAP chip. To compile this driver as a module, choose M here. The module will be called cpcap-pwrbutton. config INPUT_WISTRON_BTNS tristate "x86 Wistron laptop button interface" depends on X86_32 select INPUT_POLLDEV select INPUT_SPARSEKMAP select NEW_LEDS select LEDS_CLASS select CHECK_SIGNATURE help Say Y here for support of Wistron laptop button interfaces, used on laptops of various brands, including Acer and Fujitsu-Siemens. If available, mail and wifi LEDs will be controllable via /sys/class/leds. To compile this driver as a module, choose M here: the module will be called wistron_btns. config INPUT_ATLAS_BTNS tristate "x86 Atlas button interface" depends on X86 && ACPI help Say Y here for support of Atlas wallmount touchscreen buttons. The events will show up as scancodes F1 through F9 via evdev. To compile this driver as a module, choose M here: the module will be called atlas_btns. config INPUT_ATI_REMOTE2 tristate "ATI / Philips USB RF remote control" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use an ATI or Philips USB RF remote control. These are RF remotes with USB receivers. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards and is also available as a separate product. This driver provides mouse pointer, left and right mouse buttons, and maps all the other remote buttons to keypress events. To compile this driver as a module, choose M here: the module will be called ati_remote2. config INPUT_KEYSPAN_REMOTE tristate "Keyspan DMR USB remote control" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use a Keyspan DMR USB remote control. Currently only the UIA-11 type of receiver has been tested. The tag on the receiver that connects to the USB port should have a P/N that will tell you what type of DMR you have. The UIA-10 type is not supported at this time. This driver maps all buttons to keypress events. To compile this driver as a module, choose M here: the module will be called keyspan_remote. config INPUT_KXTJ9 tristate "Kionix KXTJ9 tri-axis digital accelerometer" depends on I2C help Say Y here to enable support for the Kionix KXTJ9 digital tri-axis accelerometer. To compile this driver as a module, choose M here: the module will be called kxtj9. config INPUT_KXTJ9_POLLED_MODE bool "Enable polling mode support" depends on INPUT_KXTJ9 select INPUT_POLLDEV help Say Y here if you need accelerometer to work in polling mode. config INPUT_POWERMATE tristate "Griffin PowerMate and Contour Jog support" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use Griffin PowerMate or Contour Jog devices. These are aluminum dials which can measure clockwise and anticlockwise rotation. The dial also acts as a pushbutton. The base contains an LED which can be instructed to pulse or to switch to a particular intensity. You can download userspace tools from <http://sowerbutts.com/powermate/>. To compile this driver as a module, choose M here: the module will be called powermate. config INPUT_YEALINK tristate "Yealink usb-p1k voip phone" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to enable keyboard and LCD functions of the Yealink usb-p1k usb phones. The audio part is enabled by the generic usb sound driver, so you might want to enable that as well. For information about how to use these additional functions, see <file:Documentation/input/devices/yealink.rst>. To compile this driver as a module, choose M here: the module will be called yealink. config INPUT_CM109 tristate "C-Media CM109 USB I/O Controller" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to enable keyboard and buzzer functions of the C-Media CM109 usb phones. The audio part is enabled by the generic usb sound driver, so you might want to enable that as well. To compile this driver as a module, choose M here: the module will be called cm109. config INPUT_REGULATOR_HAPTIC tristate "Regulator haptics support" depends on REGULATOR select INPUT_FF_MEMLESS help This option enables device driver support for the haptic controlled by a regulator. This driver supports ff-memless interface from input framework. To compile this driver as a module, choose M here: the module will be called regulator-haptic. config INPUT_RETU_PWRBUTTON tristate "Retu Power button Driver" depends on MFD_RETU help Say Y here if you want to enable power key reporting via the Retu chips found in Nokia Internet Tablets (770, N800, N810). To compile this driver as a module, choose M here. The module will be called retu-pwrbutton. config INPUT_TPS65218_PWRBUTTON tristate "TPS65218 Power button driver" depends on (MFD_TPS65217 || MFD_TPS65218) help Say Y here if you want to enable power button reporting for TPS65217 and TPS65218 Power Management IC devices. To compile this driver as a module, choose M here. The module will be called tps65218-pwrbutton. config INPUT_AXP20X_PEK tristate "X-Powers AXP20X power button driver" depends on MFD_AXP20X help Say Y here if you want to enable power key reporting via the AXP20X PMIC. To compile this driver as a module, choose M here. The module will be called axp20x-pek. config INPUT_TWL4030_PWRBUTTON tristate "TWL4030 Power button Driver" depends on TWL4030_CORE help Say Y here if you want to enable power key reporting via the TWL4030 family of chips. To compile this driver as a module, choose M here. The module will be called twl4030_pwrbutton. config INPUT_TWL4030_VIBRA tristate "Support for TWL4030 Vibrator" depends on TWL4030_CORE select MFD_TWL4030_AUDIO select INPUT_FF_MEMLESS help This option enables support for TWL4030 Vibrator Driver. To compile this driver as a module, choose M here. The module will be called twl4030_vibra. config INPUT_TWL6040_VIBRA tristate "Support for TWL6040 Vibrator" depends on TWL6040_CORE select INPUT_FF_MEMLESS help This option enables support for TWL6040 Vibrator Driver. To compile this driver as a module, choose M here. The module will be called twl6040_vibra. config INPUT_UINPUT tristate "User level driver support" help Say Y here if you want to support user level drivers for input subsystem accessible under char device 10:223 - /dev/input/uinput. To compile this driver as a module, choose M here: the module will be called uinput. config INPUT_SGI_BTNS tristate "SGI Indy/O2 volume button interface" depends on SGI_IP22 || SGI_IP32 select INPUT_POLLDEV help Say Y here if you want to support SGI Indy/O2 volume button interface. To compile this driver as a module, choose M here: the module will be called sgi_btns. config HP_SDC_RTC tristate "HP SDC Real Time Clock" depends on (GSC || HP300) && SERIO select HP_SDC help Say Y here if you want to support the built-in real time clock of the HP SDC controller. config INPUT_PALMAS_PWRBUTTON tristate "Palmas Power button Driver" depends on MFD_PALMAS help Say Y here if you want to enable power key reporting via the Palmas family of PMICs. To compile this driver as a module, choose M here. The module will be called palmas_pwrbutton. config INPUT_PCF50633_PMU tristate "PCF50633 PMU events" depends on MFD_PCF50633 help Say Y to include support for delivering PMU events via input layer on NXP PCF50633. config INPUT_PCF8574 tristate "PCF8574 Keypad input device" depends on I2C help Say Y here if you want to support a keypad connected via I2C with a PCF8574. To compile this driver as a module, choose M here: the module will be called pcf8574_keypad. config INPUT_PWM_BEEPER tristate "PWM beeper support" depends on PWM help Say Y here to get support for PWM based beeper devices. If unsure, say N. To compile this driver as a module, choose M here: the module will be called pwm-beeper. config INPUT_PWM_VIBRA tristate "PWM vibrator support" depends on PWM select INPUT_FF_MEMLESS help Say Y here to get support for PWM based vibrator devices. If unsure, say N. To compile this driver as a module, choose M here: the module will be called pwm-vibra. config INPUT_RK805_PWRKEY tristate "Rockchip RK805 PMIC power key support" depends on MFD_RK808 help Select this option to enable power key driver for RK805. If unsure, say N. To compile this driver as a module, choose M here: the module will be called rk805_pwrkey. config INPUT_GPIO_ROTARY_ENCODER tristate "Rotary encoders connected to GPIO pins" depends on GPIOLIB || COMPILE_TEST help Say Y here to add support for rotary encoders connected to GPIO lines. Check file:Documentation/input/devices/rotary-encoder.rst for more information. To compile this driver as a module, choose M here: the module will be called rotary_encoder. config INPUT_RB532_BUTTON tristate "Mikrotik Routerboard 532 button interface" depends on MIKROTIK_RB532 depends on GPIOLIB select INPUT_POLLDEV help Say Y here if you want support for the S1 button built into Mikrotik's Routerboard 532. To compile this driver as a module, choose M here: the module will be called rb532_button. config INPUT_DA9052_ONKEY tristate "Dialog DA9052/DA9053 Onkey" depends on PMIC_DA9052 help Support the ONKEY of Dialog DA9052 PMICs as an input device reporting power button status. To compile this driver as a module, choose M here: the module will be called da9052_onkey. config INPUT_DA9055_ONKEY tristate "Dialog Semiconductor DA9055 ONKEY" depends on MFD_DA9055 help Support the ONKEY of DA9055 PMICs as an input device reporting power button status. To compile this driver as a module, choose M here: the module will be called da9055_onkey. config INPUT_DA9063_ONKEY tristate "Dialog DA9063/62/61 OnKey" depends on MFD_DA9063 || MFD_DA9062 help Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power Management ICs as an input device capable of reporting the power button status. To compile this driver as a module, choose M here: the module will be called da9063_onkey. config INPUT_DM355EVM tristate "TI DaVinci DM355 EVM Keypad and IR Remote" depends on MFD_DM355EVM_MSP select INPUT_SPARSEKMAP help Supports the pushbuttons and IR remote used with the DM355 EVM board. To compile this driver as a module, choose M here: the module will be called dm355evm_keys. config INPUT_WM831X_ON tristate "WM831X ON pin" depends on MFD_WM831X help Support the ON pin of WM831X PMICs as an input device reporting power button status. To compile this driver as a module, choose M here: the module will be called wm831x_on. config INPUT_PCAP tristate "Motorola EZX PCAP misc input events" depends on EZX_PCAP help Say Y here if you want to use Power key and Headphone button on Motorola EZX phones. To compile this driver as a module, choose M here: the module will be called pcap_keys. config INPUT_ADXL34X tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" default n help Say Y here if you have a Accelerometer interface using the ADXL345/6 controller, and your board-specific initialization code includes that in its table of devices. This driver can use either I2C or SPI communication to the ADXL345/6 controller. Select the appropriate method for your system. If unsure, say N (but it's safe to say "Y"). To compile this driver as a module, choose M here: the module will be called adxl34x. config INPUT_ADXL34X_I2C tristate "support I2C bus connection" depends on INPUT_ADXL34X && I2C default y help Say Y here if you have ADXL345/6 hooked to an I2C bus. To compile this driver as a module, choose M here: the module will be called adxl34x-i2c. config INPUT_ADXL34X_SPI tristate "support SPI bus connection" depends on INPUT_ADXL34X && SPI default y help Say Y here if you have ADXL345/6 hooked to a SPI bus. To compile this driver as a module, choose M here: the module will be called adxl34x-spi. config INPUT_IMS_PCU tristate "IMS Passenger Control Unit driver" depends on USB depends on LEDS_CLASS help Say Y here if you have system with IMS Rave Passenger Control Unit. To compile this driver as a module, choose M here: the module will be called ims_pcu. config INPUT_CMA3000 tristate "VTI CMA3000 Tri-axis accelerometer" help Say Y here if you want to use VTI CMA3000_D0x Accelerometer driver This driver currently only supports I2C interface to the controller. Also select the I2C method. If unsure, say N To compile this driver as a module, choose M here: the module will be called cma3000_d0x. config INPUT_CMA3000_I2C tristate "Support I2C bus connection" depends on INPUT_CMA3000 && I2C help Say Y here if you want to use VTI CMA3000_D0x Accelerometer through I2C interface. To compile this driver as a module, choose M here: the module will be called cma3000_d0x_i2c. config INPUT_XEN_KBDDEV_FRONTEND tristate "Xen virtual keyboard and mouse support" depends on XEN default y select XEN_XENBUS_FRONTEND help This driver implements the front-end of the Xen virtual keyboard and mouse device driver. It communicates with a back-end in another domain. To compile this driver as a module, choose M here: the module will be called xen-kbdfront. config INPUT_SIRFSOC_ONKEY tristate "CSR SiRFSoC power on/off/suspend key support" depends on ARCH_SIRF && OF default y help Say Y here if you want to support for the SiRFSoC power on/off/suspend key in Linux, after you press the onkey, system will suspend. If unsure, say N. config INPUT_IDEAPAD_SLIDEBAR tristate "IdeaPad Laptop Slidebar" depends on INPUT depends on SERIO_I8042 help Say Y here if you have an IdeaPad laptop with a slidebar. To compile this driver as a module, choose M here: the module will be called ideapad_slidebar. config INPUT_SOC_BUTTON_ARRAY tristate "Windows-compatible SoC Button Array" depends on KEYBOARD_GPIO && ACPI help Say Y here if you have a SoC-based tablet that originally runs Windows 8 or a Microsoft Surface Book 2, Pro 5, Laptop 1 or later. To compile this driver as a module, choose M here: the module will be called soc_button_array. config INPUT_DRV260X_HAPTICS tristate "TI DRV260X haptics support" depends on INPUT && I2C depends on GPIOLIB || COMPILE_TEST select INPUT_FF_MEMLESS select REGMAP_I2C help Say Y to enable support for the TI DRV260X haptics driver. To compile this driver as a module, choose M here: the module will be called drv260x-haptics. config INPUT_DRV2665_HAPTICS tristate "TI DRV2665 haptics support" depends on INPUT && I2C select INPUT_FF_MEMLESS select REGMAP_I2C help Say Y to enable support for the TI DRV2665 haptics driver. To compile this driver as a module, choose M here: the module will be called drv2665-haptics. config INPUT_DRV2667_HAPTICS tristate "TI DRV2667 haptics support" depends on INPUT && I2C select INPUT_FF_MEMLESS select REGMAP_I2C help Say Y to enable support for the TI DRV2667 haptics driver. To compile this driver as a module, choose M here: the module will be called drv2667-haptics. config INPUT_HISI_POWERKEY tristate "Hisilicon PMIC ONKEY support" depends on ARCH_HISI || COMPILE_TEST help Say Y to enable support for PMIC ONKEY. To compile this driver as a module, choose M here: the module will be called hisi_powerkey. config INPUT_RAVE_SP_PWRBUTTON tristate "RAVE SP Power button Driver" depends on RAVE_SP_CORE help Say Y here if you want to enable power key reporting from RAVE SP To compile this driver as a module, choose M here: the module will be called rave-sp-pwrbutton. config INPUT_SC27XX_VIBRA tristate "Spreadtrum sc27xx vibrator support" depends on MFD_SC27XX_PMIC || COMPILE_TEST select INPUT_FF_MEMLESS help This option enables support for Spreadtrum sc27xx vibrator driver. To compile this driver as a module, choose M here. The module will be called sc27xx_vibra. config INPUT_STPMIC1_ONKEY tristate "STPMIC1 PMIC Onkey support" depends on MFD_STPMIC1 help Say Y to enable support of onkey embedded into STPMIC1 PMIC. onkey can be used to wakeup from low power modes and force a shut-down on long press. To compile this driver as a module, choose M here: the module will be called stpmic1_onkey. endif misc/Makefile 0000644 00000010112 14722071600 0007131 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the input misc drivers. # # Each configuration option enables a list of files. obj-$(CONFIG_INPUT_88PM860X_ONKEY) += 88pm860x_onkey.o obj-$(CONFIG_INPUT_88PM80X_ONKEY) += 88pm80x_onkey.o obj-$(CONFIG_INPUT_AB8500_PONKEY) += ab8500-ponkey.o obj-$(CONFIG_INPUT_AD714X) += ad714x.o obj-$(CONFIG_INPUT_AD714X_I2C) += ad714x-i2c.o obj-$(CONFIG_INPUT_AD714X_SPI) += ad714x-spi.o obj-$(CONFIG_INPUT_ADXL34X) += adxl34x.o obj-$(CONFIG_INPUT_ADXL34X_I2C) += adxl34x-i2c.o obj-$(CONFIG_INPUT_ADXL34X_SPI) += adxl34x-spi.o obj-$(CONFIG_INPUT_APANEL) += apanel.o obj-$(CONFIG_INPUT_ARIZONA_HAPTICS) += arizona-haptics.o obj-$(CONFIG_INPUT_ATI_REMOTE2) += ati_remote2.o obj-$(CONFIG_INPUT_ATLAS_BTNS) += atlas_btns.o obj-$(CONFIG_INPUT_ATMEL_CAPTOUCH) += atmel_captouch.o obj-$(CONFIG_INPUT_BMA150) += bma150.o obj-$(CONFIG_INPUT_CM109) += cm109.o obj-$(CONFIG_INPUT_CMA3000) += cma3000_d0x.o obj-$(CONFIG_INPUT_CMA3000_I2C) += cma3000_d0x_i2c.o obj-$(CONFIG_INPUT_COBALT_BTNS) += cobalt_btns.o obj-$(CONFIG_INPUT_CPCAP_PWRBUTTON) += cpcap-pwrbutton.o obj-$(CONFIG_INPUT_DA9052_ONKEY) += da9052_onkey.o obj-$(CONFIG_INPUT_DA9055_ONKEY) += da9055_onkey.o obj-$(CONFIG_INPUT_DA9063_ONKEY) += da9063_onkey.o obj-$(CONFIG_INPUT_DM355EVM) += dm355evm_keys.o obj-$(CONFIG_INPUT_E3X0_BUTTON) += e3x0-button.o obj-$(CONFIG_INPUT_DRV260X_HAPTICS) += drv260x.o obj-$(CONFIG_INPUT_DRV2665_HAPTICS) += drv2665.o obj-$(CONFIG_INPUT_DRV2667_HAPTICS) += drv2667.o obj-$(CONFIG_INPUT_GP2A) += gp2ap002a00f.o obj-$(CONFIG_INPUT_GPIO_BEEPER) += gpio-beeper.o obj-$(CONFIG_INPUT_GPIO_DECODER) += gpio_decoder.o obj-$(CONFIG_INPUT_GPIO_VIBRA) += gpio-vibra.o obj-$(CONFIG_INPUT_HISI_POWERKEY) += hisi_powerkey.o obj-$(CONFIG_HP_SDC_RTC) += hp_sdc_rtc.o obj-$(CONFIG_INPUT_IMS_PCU) += ims-pcu.o obj-$(CONFIG_INPUT_IXP4XX_BEEPER) += ixp4xx-beeper.o obj-$(CONFIG_INPUT_KEYSPAN_REMOTE) += keyspan_remote.o obj-$(CONFIG_INPUT_KXTJ9) += kxtj9.o obj-$(CONFIG_INPUT_M68K_BEEP) += m68kspkr.o obj-$(CONFIG_INPUT_MAX77650_ONKEY) += max77650-onkey.o obj-$(CONFIG_INPUT_MAX77693_HAPTIC) += max77693-haptic.o obj-$(CONFIG_INPUT_MAX8925_ONKEY) += max8925_onkey.o obj-$(CONFIG_INPUT_MAX8997_HAPTIC) += max8997_haptic.o obj-$(CONFIG_INPUT_MC13783_PWRBUTTON) += mc13783-pwrbutton.o obj-$(CONFIG_INPUT_MMA8450) += mma8450.o obj-$(CONFIG_INPUT_MSM_VIBRATOR) += msm-vibrator.o obj-$(CONFIG_INPUT_PALMAS_PWRBUTTON) += palmas-pwrbutton.o obj-$(CONFIG_INPUT_PCAP) += pcap_keys.o obj-$(CONFIG_INPUT_PCF50633_PMU) += pcf50633-input.o obj-$(CONFIG_INPUT_PCF8574) += pcf8574_keypad.o obj-$(CONFIG_INPUT_PCSPKR) += pcspkr.o obj-$(CONFIG_INPUT_PM8941_PWRKEY) += pm8941-pwrkey.o obj-$(CONFIG_INPUT_PM8XXX_VIBRATOR) += pm8xxx-vibrator.o obj-$(CONFIG_INPUT_PMIC8XXX_PWRKEY) += pmic8xxx-pwrkey.o obj-$(CONFIG_INPUT_POWERMATE) += powermate.o obj-$(CONFIG_INPUT_PWM_BEEPER) += pwm-beeper.o obj-$(CONFIG_INPUT_PWM_VIBRA) += pwm-vibra.o obj-$(CONFIG_INPUT_RAVE_SP_PWRBUTTON) += rave-sp-pwrbutton.o obj-$(CONFIG_INPUT_RB532_BUTTON) += rb532_button.o obj-$(CONFIG_INPUT_REGULATOR_HAPTIC) += regulator-haptic.o obj-$(CONFIG_INPUT_RETU_PWRBUTTON) += retu-pwrbutton.o obj-$(CONFIG_INPUT_AXP20X_PEK) += axp20x-pek.o obj-$(CONFIG_INPUT_GPIO_ROTARY_ENCODER) += rotary_encoder.o obj-$(CONFIG_INPUT_RK805_PWRKEY) += rk805-pwrkey.o obj-$(CONFIG_INPUT_SC27XX_VIBRA) += sc27xx-vibra.o obj-$(CONFIG_INPUT_SGI_BTNS) += sgi_btns.o obj-$(CONFIG_INPUT_SIRFSOC_ONKEY) += sirfsoc-onkey.o obj-$(CONFIG_INPUT_SOC_BUTTON_ARRAY) += soc_button_array.o obj-$(CONFIG_INPUT_SPARCSPKR) += sparcspkr.o obj-$(CONFIG_INPUT_STPMIC1_ONKEY) += stpmic1_onkey.o obj-$(CONFIG_INPUT_TPS65218_PWRBUTTON) += tps65218-pwrbutton.o obj-$(CONFIG_INPUT_TWL4030_PWRBUTTON) += twl4030-pwrbutton.o obj-$(CONFIG_INPUT_TWL4030_VIBRA) += twl4030-vibra.o obj-$(CONFIG_INPUT_TWL6040_VIBRA) += twl6040-vibra.o obj-$(CONFIG_INPUT_UINPUT) += uinput.o obj-$(CONFIG_INPUT_WISTRON_BTNS) += wistron_btns.o obj-$(CONFIG_INPUT_WM831X_ON) += wm831x-on.o obj-$(CONFIG_INPUT_XEN_KBDDEV_FRONTEND) += xen-kbdfront.o obj-$(CONFIG_INPUT_YEALINK) += yealink.o obj-$(CONFIG_INPUT_IDEAPAD_SLIDEBAR) += ideapad_slidebar.o joystick/iforce/Kconfig 0000644 00000001721 14722071600 0011155 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # I-Force driver configuration # config JOYSTICK_IFORCE tristate "I-Force devices" depends on INPUT && INPUT_JOYSTICK help Say Y here if you have an I-Force joystick or steering wheel You also must choose at least one of the two options below. To compile this driver as a module, choose M here: the module will be called iforce. config JOYSTICK_IFORCE_USB tristate "I-Force USB joysticks and wheels" depends on JOYSTICK_IFORCE && USB help Say Y here if you have an I-Force joystick or steering wheel connected to your USB port. config JOYSTICK_IFORCE_232 tristate "I-Force Serial joysticks and wheels" depends on JOYSTICK_IFORCE && SERIO help Say Y here if you have an I-Force joystick or steering wheel connected to your serial (COM) port. You will need an additional utility called inputattach, see <file:Documentation/input/joydev/joystick.rst> and <file:Documentation/input/ff.rst>. joystick/iforce/Makefile 0000644 00000000506 14722071600 0011312 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the I-Force driver # # By Johann Deneux <johann.deneux@gmail.com> # obj-$(CONFIG_JOYSTICK_IFORCE) += iforce.o iforce-y := iforce-ff.o iforce-main.o iforce-packets.o obj-$(CONFIG_JOYSTICK_IFORCE_232) += iforce-serio.o obj-$(CONFIG_JOYSTICK_IFORCE_USB) += iforce-usb.o joystick/Kconfig 0000644 00000027226 14722071600 0007716 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Joystick driver configuration # menuconfig INPUT_JOYSTICK bool "Joysticks/Gamepads" help If you have a joystick, 6dof controller, gamepad, steering wheel, weapon control system or something like that you can say Y here and the list of supported devices will be displayed. This option doesn't affect the kernel. Please read the file <file:Documentation/input/joydev/joystick.rst> which contains more information. if INPUT_JOYSTICK config JOYSTICK_ANALOG tristate "Classic PC analog joysticks and gamepads" select GAMEPORT ---help--- Say Y here if you have a joystick that connects to the PC gameport. In addition to the usual PC analog joystick, this driver supports many extensions, including joysticks with throttle control, with rudders, additional hats and buttons compatible with CH Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg joysticks. Please read the file <file:Documentation/input/joydev/joystick.rst> which contains more information. To compile this driver as a module, choose M here: the module will be called analog. config JOYSTICK_A3D tristate "Assassin 3D and MadCatz Panther devices" select GAMEPORT help Say Y here if you have an FPGaming or MadCatz controller using the A3D protocol over the PC gameport. To compile this driver as a module, choose M here: the module will be called a3d. config JOYSTICK_ADI tristate "Logitech ADI digital joysticks and gamepads" select GAMEPORT help Say Y here if you have a Logitech controller using the ADI protocol over the PC gameport. To compile this driver as a module, choose M here: the module will be called adi. config JOYSTICK_COBRA tristate "Creative Labs Blaster Cobra gamepad" select GAMEPORT help Say Y here if you have a Creative Labs Blaster Cobra gamepad. To compile this driver as a module, choose M here: the module will be called cobra. config JOYSTICK_GF2K tristate "Genius Flight2000 Digital joysticks and gamepads" select GAMEPORT help Say Y here if you have a Genius Flight2000 or MaxFighter digitally communicating joystick or gamepad. To compile this driver as a module, choose M here: the module will be called gf2k. config JOYSTICK_GRIP tristate "Gravis GrIP joysticks and gamepads" select GAMEPORT help Say Y here if you have a Gravis controller using the GrIP protocol over the PC gameport. To compile this driver as a module, choose M here: the module will be called grip. config JOYSTICK_GRIP_MP tristate "Gravis GrIP MultiPort" select GAMEPORT help Say Y here if you have the original Gravis GrIP MultiPort, a hub that connects to the gameport and you connect gamepads to it. To compile this driver as a module, choose M here: the module will be called grip_mp. config JOYSTICK_GUILLEMOT tristate "Guillemot joysticks and gamepads" select GAMEPORT help Say Y here if you have a Guillemot joystick using a digital protocol over the PC gameport. To compile this driver as a module, choose M here: the module will be called guillemot. config JOYSTICK_INTERACT tristate "InterAct digital joysticks and gamepads" select GAMEPORT help Say Y here if you have an InterAct gameport or joystick communicating digitally over the gameport. To compile this driver as a module, choose M here: the module will be called interact. config JOYSTICK_SIDEWINDER tristate "Microsoft SideWinder digital joysticks and gamepads" select GAMEPORT help Say Y here if you have a Microsoft controller using the Digital Overdrive protocol over PC gameport. To compile this driver as a module, choose M here: the module will be called sidewinder. config JOYSTICK_TMDC tristate "ThrustMaster DirectConnect joysticks and gamepads" select GAMEPORT help Say Y here if you have a ThrustMaster controller using the DirectConnect (BSP) protocol over the PC gameport. To compile this driver as a module, choose M here: the module will be called tmdc. source "drivers/input/joystick/iforce/Kconfig" config JOYSTICK_WARRIOR tristate "Logitech WingMan Warrior joystick" select SERIO help Say Y here if you have a Logitech WingMan Warrior joystick connected to your computer's serial port. To compile this driver as a module, choose M here: the module will be called warrior. config JOYSTICK_MAGELLAN tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers" select SERIO help Say Y here if you have a Magellan or Space Mouse 6DOF controller connected to your computer's serial port. To compile this driver as a module, choose M here: the module will be called magellan. config JOYSTICK_SPACEORB tristate "SpaceTec SpaceOrb/Avenger 6dof controllers" select SERIO help Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF controller connected to your computer's serial port. To compile this driver as a module, choose M here: the module will be called spaceorb. config JOYSTICK_SPACEBALL tristate "SpaceTec SpaceBall 6dof controllers" select SERIO help Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX controller connected to your computer's serial port. For the SpaceBall 4000 USB model, use the USB HID driver. To compile this driver as a module, choose M here: the module will be called spaceball. config JOYSTICK_STINGER tristate "Gravis Stinger gamepad" select SERIO help Say Y here if you have a Gravis Stinger connected to one of your serial ports. To compile this driver as a module, choose M here: the module will be called stinger. config JOYSTICK_TWIDJOY tristate "Twiddler as a joystick" select SERIO help Say Y here if you have a Handykey Twiddler connected to your computer's serial port and want to use it as a joystick. To compile this driver as a module, choose M here: the module will be called twidjoy. config JOYSTICK_ZHENHUA tristate "5-byte Zhenhua RC transmitter" select SERIO select BITREVERSE help Say Y here if you have a Zhen Hua PPM-4CH transmitter which is supplied with a ready to fly micro electric indoor helicopters such as EasyCopter, Lama, MiniCopter, DragonFly or Jabo and want to use it via serial cable as a joystick. To compile this driver as a module, choose M here: the module will be called zhenhua. config JOYSTICK_DB9 tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads" depends on PARPORT help Say Y here if you have a Sega Master System gamepad, Sega Genesis gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga, Commodore, Amstrad CPC joystick connected to your parallel port. For more information on how to use the driver please read <file:Documentation/input/devices/joystick-parport.rst>. To compile this driver as a module, choose M here: the module will be called db9. config JOYSTICK_GAMECON tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads" depends on PARPORT select INPUT_FF_MEMLESS ---help--- Say Y here if you have a Nintendo Entertainment System gamepad, Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad, Sony PlayStation gamepad or a Multisystem -- Atari, Amiga, Commodore, Amstrad CPC joystick connected to your parallel port. For more information on how to use the driver please read <file:Documentation/input/devices/joystick-parport.rst>. To compile this driver as a module, choose M here: the module will be called gamecon. config JOYSTICK_TURBOGRAFX tristate "Multisystem joysticks via TurboGraFX device" depends on PARPORT help Say Y here if you have the TurboGraFX interface by Steffen Schwenke, and want to use it with Multisystem -- Atari, Amiga, Commodore, Amstrad CPC joystick. For more information on how to use the driver please read <file:Documentation/input/devices/joystick-parport.rst>. To compile this driver as a module, choose M here: the module will be called turbografx. config JOYSTICK_AMIGA tristate "Amiga joysticks" depends on AMIGA help Say Y here if you have an Amiga with a digital joystick connected to it. To compile this driver as a module, choose M here: the module will be called amijoy. config JOYSTICK_AS5011 tristate "Austria Microsystem AS5011 joystick" depends on I2C help Say Y here if you have an AS5011 digital joystick connected to your system. To compile this driver as a module, choose M here: the module will be called as5011. config JOYSTICK_JOYDUMP tristate "Gameport data dumper" select GAMEPORT help Say Y here if you want to dump data from your joystick into the system log for debugging purposes. Say N if you are making a production configuration or aren't sure. To compile this driver as a module, choose M here: the module will be called joydump. config JOYSTICK_XPAD tristate "X-Box gamepad support" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use the X-Box pad with your computer. Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV) and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. For information about how to connect the X-Box pad to USB, see <file:Documentation/input/devices/xpad.rst>. To compile this driver as a module, choose M here: the module will be called xpad. config JOYSTICK_XPAD_FF bool "X-Box gamepad rumble support" depends on JOYSTICK_XPAD && INPUT select INPUT_FF_MEMLESS ---help--- Say Y here if you want to take advantage of xbox 360 rumble features. config JOYSTICK_XPAD_LEDS bool "LED Support for Xbox360 controller 'BigX' LED" depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD) ---help--- This option enables support for the LED which surrounds the Big X on XBox 360 controller. config JOYSTICK_WALKERA0701 tristate "Walkera WK-0701 RC transmitter" depends on HIGH_RES_TIMERS && PARPORT help Say Y or M here if you have a Walkera WK-0701 transmitter which is supplied with a ready to fly Walkera helicopters such as HM36, HM37, HM60 and want to use it via parport as a joystick. More information is available: <file:Documentation/input/devices/walkera0701.rst> To compile this driver as a module, choose M here: the module will be called walkera0701. config JOYSTICK_MAPLE tristate "Dreamcast control pad" depends on MAPLE help Say Y here if you have a SEGA Dreamcast and want to use your controller as a joystick. Most Dreamcast users will say Y. To compile this as a module choose M here: the module will be called maplecontrol. config JOYSTICK_PSXPAD_SPI tristate "PlayStation 1/2 joypads via SPI interface" depends on SPI select INPUT_POLLDEV help Say Y here if you wish to connect PlayStation 1/2 joypads via SPI interface. To compile this driver as a module, choose M here: the module will be called psxpad-spi. config JOYSTICK_PSXPAD_SPI_FF bool "PlayStation 1/2 joypads force feedback (rumble) support" depends on JOYSTICK_PSXPAD_SPI select INPUT_FF_MEMLESS help Say Y here if you want to take advantage of PlayStation 1/2 joypads rumble features. To drive rumble motor a dedicated power supply is required. config JOYSTICK_PXRC tristate "PhoenixRC Flight Controller Adapter" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use the PhoenixRC Flight Controller Adapter. To compile this driver as a module, choose M here: the module will be called pxrc. config JOYSTICK_FSIA6B tristate "FlySky FS-iA6B RC Receiver" select SERIO help Say Y here if you use a FlySky FS-i6 RC remote control along with the FS-iA6B RC receiver as a joystick input device. To compile this driver as a module, choose M here: the module will be called fsia6b. endif joystick/Makefile 0000644 00000002730 14722071601 0010045 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the input core drivers. # # Each configuration option enables a list of files. obj-$(CONFIG_JOYSTICK_A3D) += a3d.o obj-$(CONFIG_JOYSTICK_ADI) += adi.o obj-$(CONFIG_JOYSTICK_AMIGA) += amijoy.o obj-$(CONFIG_JOYSTICK_AS5011) += as5011.o obj-$(CONFIG_JOYSTICK_ANALOG) += analog.o obj-$(CONFIG_JOYSTICK_COBRA) += cobra.o obj-$(CONFIG_JOYSTICK_DB9) += db9.o obj-$(CONFIG_JOYSTICK_FSIA6B) += fsia6b.o obj-$(CONFIG_JOYSTICK_GAMECON) += gamecon.o obj-$(CONFIG_JOYSTICK_GF2K) += gf2k.o obj-$(CONFIG_JOYSTICK_GRIP) += grip.o obj-$(CONFIG_JOYSTICK_GRIP_MP) += grip_mp.o obj-$(CONFIG_JOYSTICK_GUILLEMOT) += guillemot.o obj-$(CONFIG_JOYSTICK_IFORCE) += iforce/ obj-$(CONFIG_JOYSTICK_INTERACT) += interact.o obj-$(CONFIG_JOYSTICK_JOYDUMP) += joydump.o obj-$(CONFIG_JOYSTICK_MAGELLAN) += magellan.o obj-$(CONFIG_JOYSTICK_MAPLE) += maplecontrol.o obj-$(CONFIG_JOYSTICK_PSXPAD_SPI) += psxpad-spi.o obj-$(CONFIG_JOYSTICK_PXRC) += pxrc.o obj-$(CONFIG_JOYSTICK_SIDEWINDER) += sidewinder.o obj-$(CONFIG_JOYSTICK_SPACEBALL) += spaceball.o obj-$(CONFIG_JOYSTICK_SPACEORB) += spaceorb.o obj-$(CONFIG_JOYSTICK_STINGER) += stinger.o obj-$(CONFIG_JOYSTICK_TMDC) += tmdc.o obj-$(CONFIG_JOYSTICK_TURBOGRAFX) += turbografx.o obj-$(CONFIG_JOYSTICK_TWIDJOY) += twidjoy.o obj-$(CONFIG_JOYSTICK_WARRIOR) += warrior.o obj-$(CONFIG_JOYSTICK_WALKERA0701) += walkera0701.o obj-$(CONFIG_JOYSTICK_XPAD) += xpad.o obj-$(CONFIG_JOYSTICK_ZHENHUA) += zhenhua.o rmi4/Kconfig 0000644 00000005715 14722071601 0006732 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # RMI4 configuration # config RMI4_CORE tristate "Synaptics RMI4 bus support" select IRQ_DOMAIN help Say Y here if you want to support the Synaptics RMI4 bus. This is required for all RMI4 device support. If unsure, say Y. if RMI4_CORE config RMI4_I2C tristate "RMI4 I2C Support" depends on I2C help Say Y here if you want to support RMI4 devices connected to an I2C bus. If unsure, say Y. config RMI4_SPI tristate "RMI4 SPI Support" depends on SPI help Say Y here if you want to support RMI4 devices connected to a SPI bus. If unsure, say N. config RMI4_SMB tristate "RMI4 SMB Support" depends on I2C help Say Y here if you want to support RMI4 devices connected to an SMB bus. If unsure, say N. To compile this driver as a module, choose M here: the module will be called rmi_smbus. config RMI4_F03 bool "RMI4 Function 03 (PS2 Guest)" depends on RMI4_CORE help Say Y here if you want to add support for RMI4 function 03. Function 03 provides PS2 guest support for RMI4 devices. This includes support for TrackPoints on TouchPads. config RMI4_F03_SERIO tristate depends on RMI4_CORE depends on RMI4_F03 default RMI4_CORE select SERIO config RMI4_2D_SENSOR bool config RMI4_F11 bool "RMI4 Function 11 (2D pointing)" select RMI4_2D_SENSOR help Say Y here if you want to add support for RMI4 function 11. Function 11 provides 2D multifinger pointing for touchscreens and touchpads. For sensors that support relative pointing, F11 also provides mouse input. config RMI4_F12 bool "RMI4 Function 12 (2D pointing)" select RMI4_2D_SENSOR help Say Y here if you want to add support for RMI4 function 12. Function 12 provides 2D multifinger pointing for touchscreens and touchpads. For sensors that support relative pointing, F12 also provides mouse input. config RMI4_F30 bool "RMI4 Function 30 (GPIO LED)" help Say Y here if you want to add support for RMI4 function 30. Function 30 provides GPIO and LED support for RMI4 devices. This includes support for buttons on TouchPads and ClickPads. config RMI4_F34 bool "RMI4 Function 34 (Device reflash)" select FW_LOADER help Say Y here if you want to add support for RMI4 function 34. Function 34 provides support for upgrading the firmware on the RMI4 device via the firmware loader interface. This is triggered using a sysfs attribute. config RMI4_F54 bool "RMI4 Function 54 (Analog diagnostics)" depends on VIDEO_V4L2=y || (RMI4_CORE=m && VIDEO_V4L2=m) select VIDEOBUF2_VMALLOC select RMI4_F55 help Say Y here if you want to add support for RMI4 function 54 Function 54 provides access to various diagnostic features in certain RMI4 touch sensors. config RMI4_F55 bool "RMI4 Function 55 (Sensor tuning)" help Say Y here if you want to add support for RMI4 function 55 Function 55 provides access to the RMI4 touch sensor tuning mechanism. endif # RMI_CORE rmi4/Makefile 0000644 00000001151 14722071601 0007055 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_RMI4_CORE) += rmi_core.o rmi_core-y := rmi_bus.o rmi_driver.o rmi_f01.o rmi_core-$(CONFIG_RMI4_2D_SENSOR) += rmi_2d_sensor.o # Function drivers rmi_core-$(CONFIG_RMI4_F03) += rmi_f03.o rmi_core-$(CONFIG_RMI4_F11) += rmi_f11.o rmi_core-$(CONFIG_RMI4_F12) += rmi_f12.o rmi_core-$(CONFIG_RMI4_F30) += rmi_f30.o rmi_core-$(CONFIG_RMI4_F34) += rmi_f34.o rmi_f34v7.o rmi_core-$(CONFIG_RMI4_F54) += rmi_f54.o rmi_core-$(CONFIG_RMI4_F55) += rmi_f55.o # Transports obj-$(CONFIG_RMI4_I2C) += rmi_i2c.o obj-$(CONFIG_RMI4_SPI) += rmi_spi.o obj-$(CONFIG_RMI4_SMB) += rmi_smbus.o serio/Kconfig 0000644 00000022243 14722071601 0007173 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Input core configuration # config SERIO tristate "Serial I/O support" default y help Say Yes here if you have any input device that uses serial I/O to communicate with the system. This includes the * standard AT keyboard and PS/2 mouse * as well as serial mice, Sun keyboards, some joysticks and 6dof devices and more. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called serio. config ARCH_MIGHT_HAVE_PC_SERIO bool help Select this config option from the architecture Kconfig if the architecture might use a PC serio device (i8042) to communicate with keyboard, mouse, etc. if SERIO config SERIO_I8042 tristate "i8042 PC Keyboard controller" default y depends on ARCH_MIGHT_HAVE_PC_SERIO help i8042 is the chip over which the standard AT keyboard and PS/2 mouse are connected to the computer. If you use these devices, you'll need to say Y here. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called i8042. config SERIO_SERPORT tristate "Serial port line discipline" default y depends on TTY help Say Y here if you plan to use an input device (mouse, joystick, tablet, 6dof) that communicates over the RS232 serial (COM) port. More information is available: <file:Documentation/input/input.rst> If unsure, say Y. To compile this driver as a module, choose M here: the module will be called serport. config SERIO_CT82C710 tristate "ct82c710 Aux port controller" depends on X86 help Say Y here if you have a Texas Instruments TravelMate notebook equipped with the ct82c710 chip and want to use a mouse connected to the "QuickPort". If unsure, say N. To compile this driver as a module, choose M here: the module will be called ct82c710. config SERIO_Q40KBD tristate "Q40 keyboard controller" depends on Q40 config SERIO_PARKBD tristate "Parallel port keyboard adapter" depends on PARPORT help Say Y here if you built a simple parallel port adapter to attach an additional AT keyboard, XT keyboard or PS/2 mouse. More information is available: <file:Documentation/input/input.rst> If unsure, say N. To compile this driver as a module, choose M here: the module will be called parkbd. config SERIO_RPCKBD tristate "Acorn RiscPC keyboard controller" depends on ARCH_ACORN default y help Say Y here if you have the Acorn RiscPC and want to use an AT keyboard connected to its keyboard controller. To compile this driver as a module, choose M here: the module will be called rpckbd. config SERIO_AMBAKMI tristate "AMBA KMI keyboard controller" depends on ARM_AMBA config SERIO_SA1111 tristate "Intel SA1111 keyboard controller" depends on SA1111 config SERIO_GSCPS2 tristate "HP GSC PS/2 keyboard and PS/2 mouse controller" depends on GSC default y help This driver provides support for the PS/2 ports on PA-RISC machines over which HP PS/2 keyboards and PS/2 mice may be connected. If you use these devices, you'll need to say Y here. It's safe to enable this driver, so if unsure, say Y. To compile this driver as a module, choose M here: the module will be called gscps2. config HP_SDC tristate "HP System Device Controller i8042 Support" depends on (GSC || HP300) && SERIO default y help This option enables support for the "System Device Controller", an i8042 carrying microcode to manage a few miscellaneous devices on some Hewlett Packard systems. The SDC itself contains a 10ms resolution timer/clock capable of delivering interrupts on a periodic and one-shot basis. The SDC may also be connected to a battery-backed real-time clock, a basic audio waveform generator, and an HP-HIL Master Link Controller serving up to seven input devices. By itself this option is rather useless, but enabling it will enable selection of drivers for the abovementioned devices. It is, however, incompatible with the old, reliable HIL keyboard driver, and the new HIL driver is experimental, so if you plan to use a HIL keyboard as your primary keyboard, you may wish to keep using that driver until the new HIL drivers have had more testing. config HIL_MLC tristate "HIL MLC Support (needed for HIL input devices)" depends on HP_SDC config SERIO_PCIPS2 tristate "PCI PS/2 keyboard and PS/2 mouse controller" depends on PCI help Say Y here if you have a Mobility Docking station with PS/2 keyboard and mice ports. To compile this driver as a module, choose M here: the module will be called pcips2. config SERIO_MACEPS2 tristate "SGI O2 MACE PS/2 controller" depends on SGI_IP32 help Say Y here if you have SGI O2 workstation and want to use its PS/2 ports. To compile this driver as a module, choose M here: the module will be called maceps2. config SERIO_LIBPS2 tristate "PS/2 driver library" depends on SERIO_I8042 || SERIO_I8042=n help Say Y here if you are using a driver for device connected to a PS/2 port, such as PS/2 mouse or standard AT keyboard. To compile this driver as a module, choose M here: the module will be called libps2. config SERIO_RAW tristate "Raw access to serio ports" help Say Y here if you want to have raw access to serio ports, such as AUX ports on i8042 keyboard controller. Each serio port that is bound to this driver will be accessible via a char device with major 10 and dynamically allocated minor. The driver will try allocating minor 1 (that historically corresponds to /dev/psaux) first. To bind this driver to a serio port use sysfs interface: echo -n "serio_raw" > /sys/bus/serio/devices/serioX/drvctl To compile this driver as a module, choose M here: the module will be called serio_raw. config SERIO_XILINX_XPS_PS2 tristate "Xilinx XPS PS/2 Controller Support" depends on PPC || MICROBLAZE help This driver supports XPS PS/2 IP from the Xilinx EDK on PowerPC platform. To compile this driver as a module, choose M here: the module will be called xilinx_ps2. config SERIO_ALTERA_PS2 tristate "Altera UP PS/2 controller" depends on HAS_IOMEM help Say Y here if you have Altera University Program PS/2 ports. To compile this driver as a module, choose M here: the module will be called altera_ps2. config SERIO_AMS_DELTA tristate "Amstrad Delta (E3) mailboard support" depends on MACH_AMS_DELTA default y ---help--- Say Y here if you have an E3 and want to use its mailboard, or any standard AT keyboard connected to the mailboard port. When used for the E3 mailboard, a non-standard key table must be loaded from userspace, possibly using udev extras provided keymap helper utility. To compile this driver as a module, choose M here; the module will be called ams_delta_serio. config SERIO_PS2MULT tristate "TQC PS/2 multiplexer" help Say Y here if you have the PS/2 line multiplexer like the one present on TQC boards. To compile this driver as a module, choose M here: the module will be called ps2mult. config SERIO_ARC_PS2 tristate "ARC PS/2 support" depends on HAS_IOMEM help Say Y here if you have an ARC FPGA platform with a PS/2 controller in it. To compile this driver as a module, choose M here; the module will be called arc_ps2. config SERIO_APBPS2 tristate "GRLIB APBPS2 PS/2 keyboard/mouse controller" depends on OF help Say Y here if you want support for GRLIB APBPS2 peripherals used to connect to PS/2 keyboard and/or mouse. To compile this driver as a module, choose M here: the module will be called apbps2. config SERIO_OLPC_APSP tristate "OLPC AP-SP input support" depends on ARCH_MMP || COMPILE_TEST help Say Y here if you want support for the keyboard and touchpad included in the OLPC XO-1.75 and XO-4 laptops. To compile this driver as a module, choose M here: the module will be called olpc_apsp. config HYPERV_KEYBOARD tristate "Microsoft Synthetic Keyboard driver" depends on HYPERV default HYPERV help Select this option to enable the Hyper-V Keyboard driver. To compile this driver as a module, choose M here: the module will be called hyperv_keyboard. config SERIO_SUN4I_PS2 tristate "Allwinner A10 PS/2 controller support" depends on ARCH_SUNXI || COMPILE_TEST help This selects support for the PS/2 Host Controller on Allwinner A10. To compile this driver as a module, choose M here: the module will be called sun4i-ps2. config SERIO_GPIO_PS2 tristate "GPIO PS/2 bit banging driver" depends on GPIOLIB help Say Y here if you want PS/2 bit banging support via GPIO. To compile this driver as a module, choose M here: the module will be called ps2-gpio. If you are unsure, say N. config USERIO tristate "User space serio port driver support" help Say Y here if you want to support user level drivers for serio subsystem accessible under char device 10:240 - /dev/userio. Using this facility userspace programs can implement serio ports that will be used by the standard in-kernel serio consumer drivers, such as psmouse and atkbd. To compile this driver as a module, choose M here: the module will be called userio. If you are unsure, say N. endif serio/Makefile 0000644 00000002347 14722071601 0007333 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the input core drivers. # # Each configuration option enables a list of files. obj-$(CONFIG_SERIO) += serio.o obj-$(CONFIG_SERIO_I8042) += i8042.o obj-$(CONFIG_SERIO_PARKBD) += parkbd.o obj-$(CONFIG_SERIO_SERPORT) += serport.o obj-$(CONFIG_SERIO_CT82C710) += ct82c710.o obj-$(CONFIG_SERIO_RPCKBD) += rpckbd.o obj-$(CONFIG_SERIO_SA1111) += sa1111ps2.o obj-$(CONFIG_SERIO_AMBAKMI) += ambakmi.o obj-$(CONFIG_SERIO_Q40KBD) += q40kbd.o obj-$(CONFIG_SERIO_GSCPS2) += gscps2.o obj-$(CONFIG_HP_SDC) += hp_sdc.o obj-$(CONFIG_HIL_MLC) += hp_sdc_mlc.o hil_mlc.o obj-$(CONFIG_SERIO_PCIPS2) += pcips2.o obj-$(CONFIG_SERIO_PS2MULT) += ps2mult.o obj-$(CONFIG_SERIO_MACEPS2) += maceps2.o obj-$(CONFIG_SERIO_LIBPS2) += libps2.o obj-$(CONFIG_SERIO_RAW) += serio_raw.o obj-$(CONFIG_SERIO_AMS_DELTA) += ams_delta_serio.o obj-$(CONFIG_SERIO_XILINX_XPS_PS2) += xilinx_ps2.o obj-$(CONFIG_SERIO_ALTERA_PS2) += altera_ps2.o obj-$(CONFIG_SERIO_ARC_PS2) += arc_ps2.o obj-$(CONFIG_SERIO_APBPS2) += apbps2.o obj-$(CONFIG_SERIO_OLPC_APSP) += olpc_apsp.o obj-$(CONFIG_HYPERV_KEYBOARD) += hyperv-keyboard.o obj-$(CONFIG_SERIO_SUN4I_PS2) += sun4i-ps2.o obj-$(CONFIG_SERIO_GPIO_PS2) += ps2-gpio.o obj-$(CONFIG_USERIO) += userio.o tablet/Kconfig 0000644 00000006151 14722071601 0007325 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Tablet driver configuration # menuconfig INPUT_TABLET bool "Tablets" help Say Y here, and a list of supported tablets will be displayed. This option doesn't affect the kernel. If unsure, say Y. if INPUT_TABLET config TABLET_USB_ACECAD tristate "Acecad Flair tablet support (USB)" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use the USB version of the Acecad Flair tablet. Make sure to say Y to "Mouse support" (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. To compile this driver as a module, choose M here: the module will be called acecad. config TABLET_USB_AIPTEK tristate "Aiptek 6000U/8000U and Genius G_PEN tablet support (USB)" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use the USB version of the Aiptek 6000U, Aiptek 8000U or Genius G-PEN 560 tablet. Make sure to say Y to "Mouse support" (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. To compile this driver as a module, choose M here: the module will be called aiptek. config TABLET_USB_GTCO tristate "GTCO CalComp/InterWrite USB Support" depends on USB && INPUT help Say Y here if you want to use the USB version of the GTCO CalComp/InterWrite Tablet. Make sure to say Y to "Mouse support" (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. To compile this driver as a module, choose M here: the module will be called gtco. config TABLET_USB_HANWANG tristate "Hanwang Art Master III tablet support (USB)" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use the USB version of the Hanwang Art Master III tablet. To compile this driver as a module, choose M here: the module will be called hanwang. config TABLET_USB_KBTAB tristate "KB Gear JamStudio tablet support (USB)" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use the USB version of the KB Gear JamStudio tablet. Make sure to say Y to "Mouse support" (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. To compile this driver as a module, choose M here: the module will be called kbtab. config TABLET_USB_PEGASUS tristate "Pegasus Mobile Notetaker Pen input tablet support" depends on USB_ARCH_HAS_HCD select USB help Say Y here if you want to use the Pegasus Mobile Notetaker, also known as: Genie e-note The Notetaker, Staedtler Digital ballpoint pen 990 01, IRISnotes Express or NEWLink Digital Note Taker. To compile this driver as a module, choose M here: the module will be called pegasus_notetaker. config TABLET_SERIAL_WACOM4 tristate "Wacom protocol 4 serial tablet support" select SERIO help Say Y here if you want to use Wacom protocol 4 serial tablets. E.g. serial versions of the Cintiq, Graphire or Penpartner. To compile this driver as a module, choose M here: the module will be called wacom_serial4. endif tablet/Makefile 0000644 00000000621 14722071601 0007456 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the tablet drivers # obj-$(CONFIG_TABLET_USB_ACECAD) += acecad.o obj-$(CONFIG_TABLET_USB_AIPTEK) += aiptek.o obj-$(CONFIG_TABLET_USB_GTCO) += gtco.o obj-$(CONFIG_TABLET_USB_HANWANG) += hanwang.o obj-$(CONFIG_TABLET_USB_KBTAB) += kbtab.o obj-$(CONFIG_TABLET_USB_PEGASUS) += pegasus_notetaker.o obj-$(CONFIG_TABLET_SERIAL_WACOM4) += wacom_serial4.o Makefile 0000644 00000001677 14722071601 0006217 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the input core drivers. # # Each configuration option enables a list of files. obj-$(CONFIG_INPUT) += input-core.o input-core-y := input.o input-compat.o input-mt.o input-poller.o ff-core.o obj-$(CONFIG_INPUT_FF_MEMLESS) += ff-memless.o obj-$(CONFIG_INPUT_POLLDEV) += input-polldev.o obj-$(CONFIG_INPUT_SPARSEKMAP) += sparse-keymap.o obj-$(CONFIG_INPUT_MATRIXKMAP) += matrix-keymap.o obj-$(CONFIG_INPUT_LEDS) += input-leds.o obj-$(CONFIG_INPUT_MOUSEDEV) += mousedev.o obj-$(CONFIG_INPUT_JOYDEV) += joydev.o obj-$(CONFIG_INPUT_EVDEV) += evdev.o obj-$(CONFIG_INPUT_EVBUG) += evbug.o obj-$(CONFIG_INPUT_KEYBOARD) += keyboard/ obj-$(CONFIG_INPUT_MOUSE) += mouse/ obj-$(CONFIG_INPUT_JOYSTICK) += joystick/ obj-$(CONFIG_INPUT_TABLET) += tablet/ obj-$(CONFIG_INPUT_TOUCHSCREEN) += touchscreen/ obj-$(CONFIG_INPUT_MISC) += misc/ obj-$(CONFIG_INPUT_APMPOWER) += apm-power.o obj-$(CONFIG_RMI4_CORE) += rmi4/ keyboard/Kconfig 0000644 00000055230 14722071601 0007654 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Input core configuration # menuconfig INPUT_KEYBOARD bool "Keyboards" default y help Say Y here, and a list of supported keyboards will be displayed. This option doesn't affect the kernel. If unsure, say Y. if INPUT_KEYBOARD config KEYBOARD_ADC tristate "ADC Ladder Buttons" depends on IIO select INPUT_POLLDEV help This driver implements support for buttons connected to an ADC using a resistor ladder. Say Y here if your device has such buttons connected to an ADC. Your board-specific setup logic must also provide a configuration data for mapping voltages to buttons. To compile this driver as a module, choose M here: the module will be called adc_keys. config KEYBOARD_ADP5520 tristate "Keypad Support for ADP5520 PMIC" depends on PMIC_ADP5520 help This option enables support for the keypad scan matrix on Analog Devices ADP5520 PMICs. To compile this driver as a module, choose M here: the module will be called adp5520-keys. config KEYBOARD_ADP5588 tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander" depends on I2C help Say Y here if you want to use a ADP5588/87 attached to your system I2C bus. To compile this driver as a module, choose M here: the module will be called adp5588-keys. config KEYBOARD_ADP5589 tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander" depends on I2C help Say Y here if you want to use a ADP5585/ADP5589 attached to your system I2C bus. To compile this driver as a module, choose M here: the module will be called adp5589-keys. config KEYBOARD_AMIGA tristate "Amiga keyboard" depends on AMIGA help Say Y here if you are running Linux on any AMIGA and have a keyboard attached. To compile this driver as a module, choose M here: the module will be called amikbd. config KEYBOARD_APPLESPI tristate "Apple SPI keyboard and trackpad" depends on ACPI && EFI depends on SPI depends on X86 || COMPILE_TEST depends on LEDS_CLASS select CRC16 help Say Y here if you are running Linux on any Apple MacBook8,1 or later, or any MacBookPro13,* or MacBookPro14,*. You will also need to enable appropriate SPI master controllers: spi_pxa2xx_platform and spi_pxa2xx_pci for MacBook8,1, and spi_pxa2xx_platform and intel_lpss_pci for the rest. To compile this driver as a module, choose M here: the module will be called applespi. config KEYBOARD_ATARI tristate "Atari keyboard" depends on ATARI select ATARI_KBD_CORE help Say Y here if you are running Linux on any Atari and have a keyboard attached. To compile this driver as a module, choose M here: the module will be called atakbd. config KEYBOARD_ATKBD tristate "AT keyboard" default y select SERIO select SERIO_LIBPS2 select SERIO_I8042 if ARCH_MIGHT_HAVE_PC_SERIO select SERIO_GSCPS2 if GSC help Say Y here if you want to use a standard AT or PS/2 keyboard. Usually you'll need this, unless you have a different type keyboard (USB, ADB or other). This also works for AT and PS/2 keyboards connected over a PS/2 to serial converter. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called atkbd. config KEYBOARD_ATKBD_HP_KEYCODES bool "Use HP keyboard scancodes" depends on PARISC && KEYBOARD_ATKBD default y help Say Y here if you have a PA-RISC machine and want to use an AT or PS/2 keyboard, and your keyboard uses keycodes that are specific to PA-RISC keyboards. Say N if you use a standard keyboard. config KEYBOARD_ATKBD_RDI_KEYCODES bool "Use PrecisionBook keyboard scancodes" depends on KEYBOARD_ATKBD_HP_KEYCODES default n help If you have an RDI PrecisionBook, say Y here if you want to use its built-in keyboard (as opposed to an external keyboard). The PrecisionBook has five keys that conflict with those used by most AT and PS/2 keyboards. These are as follows: PrecisionBook Standard AT or PS/2 F1 F12 Left Ctrl Left Alt Caps Lock Left Ctrl Right Ctrl Caps Lock Left 102nd key (the key to the right of Left Shift) If you say N here, and use the PrecisionBook keyboard, then each key in the left-hand column will be interpreted as the corresponding key in the right-hand column. If you say Y here, and use an external keyboard, then each key in the right-hand column will be interpreted as the key shown in the left-hand column. config KEYBOARD_QT1050 tristate "Microchip AT42QT1050 Touch Sensor Chip" depends on I2C select REGMAP_I2C help Say Y here if you want to use Microchip AT42QT1050 QTouch Sensor chip as input device. To compile this driver as a module, choose M here: the module will be called qt1050 config KEYBOARD_QT1070 tristate "Atmel AT42QT1070 Touch Sensor Chip" depends on I2C help Say Y here if you want to use Atmel AT42QT1070 QTouch Sensor chip as input device. To compile this driver as a module, choose M here: the module will be called qt1070 config KEYBOARD_QT2160 tristate "Atmel AT42QT2160 Touch Sensor Chip" depends on I2C help If you say yes here you get support for Atmel AT42QT2160 Touch Sensor chip as a keyboard input. This driver can also be built as a module. If so, the module will be called qt2160. config KEYBOARD_CLPS711X tristate "CLPS711X Keypad support" depends on OF_GPIO && (ARCH_CLPS711X || COMPILE_TEST) select INPUT_MATRIXKMAP select INPUT_POLLDEV help Say Y here to enable the matrix keypad on the Cirrus Logic CLPS711X CPUs. To compile this driver as a module, choose M here: the module will be called clps711x-keypad. config KEYBOARD_DLINK_DIR685 tristate "D-Link DIR-685 touchkeys support" depends on I2C default ARCH_GEMINI help If you say yes here you get support for the D-Link DIR-685 touchkeys. To compile this driver as a module, choose M here: the module will be called dlink-dir685-touchkeys. config KEYBOARD_LKKBD tristate "DECstation/VAXstation LK201/LK401 keyboard" select SERIO help Say Y here if you want to use a LK201 or LK401 style serial keyboard. This keyboard is also useable on PCs if you attach it with the inputattach program. The connector pinout is described within lkkbd.c. To compile this driver as a module, choose M here: the module will be called lkkbd. config KEYBOARD_EP93XX tristate "EP93xx Matrix Keypad support" depends on ARCH_EP93XX || COMPILE_TEST select INPUT_MATRIXKMAP help Say Y here to enable the matrix keypad on the Cirrus EP93XX. To compile this driver as a module, choose M here: the module will be called ep93xx_keypad. config KEYBOARD_GPIO tristate "GPIO Buttons" depends on GPIOLIB || COMPILE_TEST help This driver implements support for buttons connected to GPIO pins of various CPUs (and some other chips). Say Y here if your device has buttons connected directly to such GPIO pins. Your board-specific setup logic must also provide a platform device, with configuration data saying which GPIOs are used. To compile this driver as a module, choose M here: the module will be called gpio_keys. config KEYBOARD_GPIO_POLLED tristate "Polled GPIO buttons" depends on GPIOLIB select INPUT_POLLDEV help This driver implements support for buttons connected to GPIO pins that are not capable of generating interrupts. Say Y here if your device has buttons connected directly to such GPIO pins. Your board-specific setup logic must also provide a platform device, with configuration data saying which GPIOs are used. To compile this driver as a module, choose M here: the module will be called gpio_keys_polled. config KEYBOARD_TCA6416 tristate "TCA6416/TCA6408A Keypad Support" depends on I2C help This driver implements basic keypad functionality for keys connected through TCA6416/TCA6408A IO expanders. Say Y here if your device has keys connected to TCA6416/TCA6408A IO expander. Your board-specific setup logic must also provide pin-mask details(of which TCA6416 pins are used for keypad). If enabled the entire TCA6416 device will be managed through this driver. To compile this driver as a module, choose M here: the module will be called tca6416_keypad. config KEYBOARD_TCA8418 tristate "TCA8418 Keypad Support" depends on I2C select INPUT_MATRIXKMAP help This driver implements basic keypad functionality for keys connected through TCA8418 keypad decoder. Say Y here if your device has keys connected to TCA8418 keypad decoder. If enabled the complete TCA8418 device will be managed through this driver. To compile this driver as a module, choose M here: the module will be called tca8418_keypad. config KEYBOARD_MATRIX tristate "GPIO driven matrix keypad support" depends on GPIOLIB || COMPILE_TEST select INPUT_MATRIXKMAP help Enable support for GPIO driven matrix keypad. To compile this driver as a module, choose M here: the module will be called matrix_keypad. config KEYBOARD_HIL_OLD tristate "HP HIL keyboard support (simple driver)" depends on GSC || HP300 default y help The "Human Interface Loop" is a older, 8-channel USB-like controller used in several Hewlett Packard models. This driver was adapted from the one written for m68k/hp300, and implements support for a keyboard attached to the HIL port, but not for any other types of HIL input devices like mice or tablets. However, it has been thoroughly tested and is stable. If you want full HIL support including support for multiple keyboards, mice, and tablets, you have to enable the "HP System Device Controller i8042 Support" in the input/serio submenu. config KEYBOARD_HIL tristate "HP HIL keyboard/pointer support" depends on GSC || HP300 default y select HP_SDC select HIL_MLC select SERIO help The "Human Interface Loop" is a older, 8-channel USB-like controller used in several Hewlett Packard models. This driver implements support for HIL-keyboards and pointing devices (mice, tablets, touchscreens) attached to your machine, so normally you should say Y here. config KEYBOARD_HP6XX tristate "HP Jornada 6xx keyboard" depends on SH_HP6XX select INPUT_POLLDEV help Say Y here if you have a HP Jornada 620/660/680/690 and want to support the built-in keyboard. To compile this driver as a module, choose M here: the module will be called jornada680_kbd. config KEYBOARD_HP7XX tristate "HP Jornada 7xx keyboard" depends on SA1100_JORNADA720_SSP && SA1100_SSP help Say Y here if you have a HP Jornada 710/720/728 and want to support the built-in keyboard. To compile this driver as a module, choose M here: the module will be called jornada720_kbd. config KEYBOARD_LM8323 tristate "LM8323 keypad chip" depends on I2C depends on LEDS_CLASS help If you say yes here you get support for the National Semiconductor LM8323 keypad controller. To compile this driver as a module, choose M here: the module will be called lm8323. config KEYBOARD_LM8333 tristate "LM8333 keypad chip" depends on I2C select INPUT_MATRIXKMAP help If you say yes here you get support for the National Semiconductor LM8333 keypad controller. To compile this driver as a module, choose M here: the module will be called lm8333. config KEYBOARD_LOCOMO tristate "LoCoMo Keyboard Support" depends on SHARP_LOCOMO help Say Y here if you are running Linux on a Sharp Zaurus Collie or Poodle based PDA To compile this driver as a module, choose M here: the module will be called locomokbd. config KEYBOARD_LPC32XX tristate "LPC32XX matrix key scanner support" depends on ARCH_LPC32XX && OF select INPUT_MATRIXKMAP help Say Y here if you want to use NXP LPC32XX SoC key scanner interface, connected to a key matrix. To compile this driver as a module, choose M here: the module will be called lpc32xx-keys. config KEYBOARD_MAPLE tristate "Maple bus keyboard" depends on SH_DREAMCAST && MAPLE help Say Y here if you have a Dreamcast console running Linux and have a keyboard attached to its Maple bus. To compile this driver as a module, choose M here: the module will be called maple_keyb. config KEYBOARD_MAX7359 tristate "Maxim MAX7359 Key Switch Controller" select INPUT_MATRIXKMAP depends on I2C help If you say yes here you get support for the Maxim MAX7359 Key Switch Controller chip. This providers microprocessors with management of up to 64 key switches To compile this driver as a module, choose M here: the module will be called max7359_keypad. config KEYBOARD_MCS tristate "MELFAS MCS Touchkey" depends on I2C help Say Y here if you have the MELFAS MCS5000/5080 touchkey controller chip in your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called mcs_touchkey. config KEYBOARD_MPR121 tristate "Freescale MPR121 Touchkey" depends on I2C help Say Y here if you have Freescale MPR121 touchkey controller chip in your system. If unsure, say N. To compile this driver as a module, choose M here: the module will be called mpr121_touchkey. config KEYBOARD_SNVS_PWRKEY tristate "IMX SNVS Power Key Driver" depends on ARCH_MXC || COMPILE_TEST depends on OF help This is the snvs powerkey driver for the Freescale i.MX application processors that are newer than i.MX6 SX. To compile this driver as a module, choose M here; the module will be called snvs_pwrkey. config KEYBOARD_IMX tristate "IMX keypad support" depends on ARCH_MXC select INPUT_MATRIXKMAP help Enable support for IMX keypad port. To compile this driver as a module, choose M here: the module will be called imx_keypad. config KEYBOARD_NEWTON tristate "Newton keyboard" select SERIO help Say Y here if you have a Newton keyboard on a serial port. To compile this driver as a module, choose M here: the module will be called newtonkbd. config KEYBOARD_NOMADIK tristate "ST-Ericsson Nomadik SKE keyboard" depends on (ARCH_NOMADIK || ARCH_U8500) select INPUT_MATRIXKMAP help Say Y here if you want to use a keypad provided on the SKE controller used on the Ux500 and Nomadik platforms To compile this driver as a module, choose M here: the module will be called nmk-ske-keypad. config KEYBOARD_NSPIRE tristate "TI-NSPIRE built-in keyboard" depends on ARCH_NSPIRE && OF select INPUT_MATRIXKMAP help Say Y here if you want to use the built-in keypad on TI-NSPIRE. To compile this driver as a module, choose M here: the module will be called nspire-keypad. config KEYBOARD_TEGRA tristate "NVIDIA Tegra internal matrix keyboard controller support" depends on ARCH_TEGRA && OF select INPUT_MATRIXKMAP help Say Y here if you want to use a matrix keyboard connected directly to the internal keyboard controller on Tegra SoCs. To compile this driver as a module, choose M here: the module will be called tegra-kbc. config KEYBOARD_OPENCORES tristate "OpenCores Keyboard Controller" depends on HAS_IOMEM help Say Y here if you want to use the OpenCores Keyboard Controller http://www.opencores.org/project,keyboardcontroller To compile this driver as a module, choose M here; the module will be called opencores-kbd. config KEYBOARD_PXA27x tristate "PXA27x/PXA3xx keypad support" depends on PXA27x || PXA3xx || ARCH_MMP select INPUT_MATRIXKMAP help Enable support for PXA27x/PXA3xx keypad controller. To compile this driver as a module, choose M here: the module will be called pxa27x_keypad. config KEYBOARD_PXA930_ROTARY tristate "PXA930/PXA935 Enhanced Rotary Controller Support" depends on CPU_PXA930 || CPU_PXA935 help Enable support for PXA930/PXA935 Enhanced Rotary Controller. To compile this driver as a module, choose M here: the module will be called pxa930_rotary. config KEYBOARD_PMIC8XXX tristate "Qualcomm PMIC8XXX keypad support" depends on MFD_PM8XXX select INPUT_MATRIXKMAP help Say Y here if you want to enable the driver for the PMIC8XXX keypad provided as a reference design from Qualcomm. This is intended to support upto 18x8 matrix based keypad design. To compile this driver as a module, choose M here: the module will be called pmic8xxx-keypad. config KEYBOARD_SAMSUNG tristate "Samsung keypad support" depends on HAVE_CLK select INPUT_MATRIXKMAP help Say Y here if you want to use the keypad on your Samsung mobile device. To compile this driver as a module, choose M here: the module will be called samsung-keypad. config KEYBOARD_GOLDFISH_EVENTS depends on GOLDFISH || COMPILE_TEST tristate "Generic Input Event device for Goldfish" help Say Y here to get an input event device for the Goldfish virtual device emulator. To compile this driver as a module, choose M here: the module will be called goldfish-events. config KEYBOARD_STOWAWAY tristate "Stowaway keyboard" select SERIO help Say Y here if you have a Stowaway keyboard on a serial port. Stowaway compatible keyboards like Dicota Input-PDA keyboard are also supported by this driver. To compile this driver as a module, choose M here: the module will be called stowaway. config KEYBOARD_ST_KEYSCAN tristate "STMicroelectronics keyscan support" depends on ARCH_STI || COMPILE_TEST select INPUT_MATRIXKMAP help Say Y here if you want to use a keypad attached to the keyscan block on some STMicroelectronics SoC devices. To compile this driver as a module, choose M here: the module will be called st-keyscan. config KEYBOARD_SUNKBD tristate "Sun Type 4 and Type 5 keyboard" select SERIO help Say Y here if you want to use a Sun Type 4 or Type 5 keyboard, connected either to the Sun keyboard connector or to an serial (RS-232) port via a simple adapter. To compile this driver as a module, choose M here: the module will be called sunkbd. config KEYBOARD_SH_KEYSC tristate "SuperH KEYSC keypad support" depends on ARCH_SHMOBILE || COMPILE_TEST help Say Y here if you want to use a keypad attached to the KEYSC block on SuperH processors such as sh7722 and sh7343. To compile this driver as a module, choose M here: the module will be called sh_keysc. config KEYBOARD_STMPE tristate "STMPE keypad support" depends on MFD_STMPE depends on OF select INPUT_MATRIXKMAP help Say Y here if you want to use the keypad controller on STMPE I/O expanders. To compile this driver as a module, choose M here: the module will be called stmpe-keypad. config KEYBOARD_SUN4I_LRADC tristate "Allwinner sun4i low res adc attached tablet keys support" depends on ARCH_SUNXI help This selects support for the Allwinner low res adc attached tablet keys found on Allwinner sunxi SoCs. To compile this driver as a module, choose M here: the module will be called sun4i-lradc-keys. config KEYBOARD_DAVINCI tristate "TI DaVinci Key Scan" depends on ARCH_DAVINCI_DM365 help Say Y to enable keypad module support for the TI DaVinci platforms (DM365). To compile this driver as a module, choose M here: the module will be called davinci_keyscan. config KEYBOARD_IPAQ_MICRO tristate "Buttons on Micro SoC (iPaq h3100,h3600,h3700)" depends on MFD_IPAQ_MICRO help Say Y to enable support for the buttons attached to Micro peripheral controller on iPAQ h3100/h3600/h3700 To compile this driver as a module, choose M here: the module will be called ipaq-micro-keys. config KEYBOARD_OMAP tristate "TI OMAP keypad support" depends on ARCH_OMAP1 select INPUT_MATRIXKMAP help Say Y here if you want to use the OMAP keypad. To compile this driver as a module, choose M here: the module will be called omap-keypad. config KEYBOARD_OMAP4 tristate "TI OMAP4+ keypad support" depends on OF || ARCH_OMAP2PLUS select INPUT_MATRIXKMAP help Say Y here if you want to use the OMAP4+ keypad. To compile this driver as a module, choose M here: the module will be called omap4-keypad. config KEYBOARD_SPEAR tristate "ST SPEAR keyboard support" depends on PLAT_SPEAR select INPUT_MATRIXKMAP help Say Y here if you want to use the SPEAR keyboard. To compile this driver as a module, choose M here: the module will be called spear-keboard. config KEYBOARD_TC3589X tristate "TC3589X Keypad support" depends on MFD_TC3589X select INPUT_MATRIXKMAP help Say Y here if you want to use the keypad controller on TC35892/3 I/O expander. To compile this driver as a module, choose M here: the module will be called tc3589x-keypad. config KEYBOARD_TM2_TOUCHKEY tristate "TM2 touchkey support" depends on I2C depends on LEDS_CLASS help Say Y here to enable device driver for tm2-touchkey with LED control for the Exynos5433 TM2 board. To compile this driver as a module, choose M here. module will be called tm2-touchkey. config KEYBOARD_TWL4030 tristate "TI TWL4030/TWL5030/TPS659x0 keypad support" depends on TWL4030_CORE select INPUT_MATRIXKMAP help Say Y here if your board use the keypad controller on TWL4030 family chips. It's safe to say enable this even on boards that don't use the keypad controller. To compile this driver as a module, choose M here: the module will be called twl4030_keypad. config KEYBOARD_XTKBD tristate "XT keyboard" select SERIO help Say Y here if you want to use the old IBM PC/XT keyboard (or compatible) on your system. This is only possible with a parallel port keyboard adapter, you cannot connect it to the keyboard port on a PC that runs Linux. To compile this driver as a module, choose M here: the module will be called xtkbd. config KEYBOARD_CROS_EC tristate "ChromeOS EC keyboard" select INPUT_MATRIXKMAP depends on CROS_EC help Say Y here to enable the matrix keyboard used by ChromeOS devices and implemented on the ChromeOS EC. You must enable one bus option (CROS_EC_I2C or CROS_EC_SPI) to use this. To compile this driver as a module, choose M here: the module will be called cros_ec_keyb. config KEYBOARD_CAP11XX tristate "Microchip CAP11XX based touch sensors" depends on OF && I2C select REGMAP_I2C help Say Y here to enable the CAP11XX touch sensor driver. To compile this driver as a module, choose M here: the module will be called cap11xx. config KEYBOARD_BCM tristate "Broadcom keypad driver" depends on OF && HAVE_CLK select INPUT_MATRIXKMAP default ARCH_BCM_CYGNUS help Say Y here if you want to use Broadcom keypad. To compile this driver as a module, choose M here: the module will be called bcm-keypad. config KEYBOARD_MTK_PMIC tristate "MediaTek PMIC keys support" depends on MFD_MT6397 help Say Y here if you want to use the pmic keys (powerkey/homekey). To compile this driver as a module, choose M here: the module will be called pmic-keys. endif keyboard/Makefile 0000644 00000006226 14722071601 0010012 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the input core drivers. # # Each configuration option enables a list of files. obj-$(CONFIG_KEYBOARD_ADC) += adc-keys.o obj-$(CONFIG_KEYBOARD_ADP5520) += adp5520-keys.o obj-$(CONFIG_KEYBOARD_ADP5588) += adp5588-keys.o obj-$(CONFIG_KEYBOARD_ADP5589) += adp5589-keys.o obj-$(CONFIG_KEYBOARD_AMIGA) += amikbd.o obj-$(CONFIG_KEYBOARD_APPLESPI) += applespi.o obj-$(CONFIG_KEYBOARD_ATARI) += atakbd.o obj-$(CONFIG_KEYBOARD_ATKBD) += atkbd.o obj-$(CONFIG_KEYBOARD_BCM) += bcm-keypad.o obj-$(CONFIG_KEYBOARD_CAP11XX) += cap11xx.o obj-$(CONFIG_KEYBOARD_CLPS711X) += clps711x-keypad.o obj-$(CONFIG_KEYBOARD_CROS_EC) += cros_ec_keyb.o obj-$(CONFIG_KEYBOARD_DAVINCI) += davinci_keyscan.o obj-$(CONFIG_KEYBOARD_DLINK_DIR685) += dlink-dir685-touchkeys.o obj-$(CONFIG_KEYBOARD_EP93XX) += ep93xx_keypad.o obj-$(CONFIG_KEYBOARD_GOLDFISH_EVENTS) += goldfish_events.o obj-$(CONFIG_KEYBOARD_GPIO) += gpio_keys.o obj-$(CONFIG_KEYBOARD_GPIO_POLLED) += gpio_keys_polled.o obj-$(CONFIG_KEYBOARD_TCA6416) += tca6416-keypad.o obj-$(CONFIG_KEYBOARD_TCA8418) += tca8418_keypad.o obj-$(CONFIG_KEYBOARD_HIL) += hil_kbd.o obj-$(CONFIG_KEYBOARD_HIL_OLD) += hilkbd.o obj-$(CONFIG_KEYBOARD_IPAQ_MICRO) += ipaq-micro-keys.o obj-$(CONFIG_KEYBOARD_IMX) += imx_keypad.o obj-$(CONFIG_KEYBOARD_HP6XX) += jornada680_kbd.o obj-$(CONFIG_KEYBOARD_HP7XX) += jornada720_kbd.o obj-$(CONFIG_KEYBOARD_LKKBD) += lkkbd.o obj-$(CONFIG_KEYBOARD_LM8323) += lm8323.o obj-$(CONFIG_KEYBOARD_LM8333) += lm8333.o obj-$(CONFIG_KEYBOARD_LOCOMO) += locomokbd.o obj-$(CONFIG_KEYBOARD_LPC32XX) += lpc32xx-keys.o obj-$(CONFIG_KEYBOARD_MAPLE) += maple_keyb.o obj-$(CONFIG_KEYBOARD_MATRIX) += matrix_keypad.o obj-$(CONFIG_KEYBOARD_MAX7359) += max7359_keypad.o obj-$(CONFIG_KEYBOARD_MCS) += mcs_touchkey.o obj-$(CONFIG_KEYBOARD_MPR121) += mpr121_touchkey.o obj-$(CONFIG_KEYBOARD_MTK_PMIC) += mtk-pmic-keys.o obj-$(CONFIG_KEYBOARD_NEWTON) += newtonkbd.o obj-$(CONFIG_KEYBOARD_NOMADIK) += nomadik-ske-keypad.o obj-$(CONFIG_KEYBOARD_NSPIRE) += nspire-keypad.o obj-$(CONFIG_KEYBOARD_OMAP) += omap-keypad.o obj-$(CONFIG_KEYBOARD_OMAP4) += omap4-keypad.o obj-$(CONFIG_KEYBOARD_OPENCORES) += opencores-kbd.o obj-$(CONFIG_KEYBOARD_PMIC8XXX) += pmic8xxx-keypad.o obj-$(CONFIG_KEYBOARD_PXA27x) += pxa27x_keypad.o obj-$(CONFIG_KEYBOARD_PXA930_ROTARY) += pxa930_rotary.o obj-$(CONFIG_KEYBOARD_QT1050) += qt1050.o obj-$(CONFIG_KEYBOARD_QT1070) += qt1070.o obj-$(CONFIG_KEYBOARD_QT2160) += qt2160.o obj-$(CONFIG_KEYBOARD_SAMSUNG) += samsung-keypad.o obj-$(CONFIG_KEYBOARD_SH_KEYSC) += sh_keysc.o obj-$(CONFIG_KEYBOARD_SNVS_PWRKEY) += snvs_pwrkey.o obj-$(CONFIG_KEYBOARD_SPEAR) += spear-keyboard.o obj-$(CONFIG_KEYBOARD_STMPE) += stmpe-keypad.o obj-$(CONFIG_KEYBOARD_STOWAWAY) += stowaway.o obj-$(CONFIG_KEYBOARD_ST_KEYSCAN) += st-keyscan.o obj-$(CONFIG_KEYBOARD_SUN4I_LRADC) += sun4i-lradc-keys.o obj-$(CONFIG_KEYBOARD_SUNKBD) += sunkbd.o obj-$(CONFIG_KEYBOARD_TC3589X) += tc3589x-keypad.o obj-$(CONFIG_KEYBOARD_TEGRA) += tegra-kbc.o obj-$(CONFIG_KEYBOARD_TM2_TOUCHKEY) += tm2-touchkey.o obj-$(CONFIG_KEYBOARD_TWL4030) += twl4030_keypad.o obj-$(CONFIG_KEYBOARD_XTKBD) += xtkbd.o
| ver. 1.4 |
Github
|
.
| PHP 7.4.3-4ubuntu2.24 | Генерация страницы: 0.02 |
proxy
|
phpinfo
|
Настройка