# SPDX-License-Identifier: GPL-2.0-only
#
# Touchscreen driver configuration
#
menuconfig [31mCONFIG_INPUT_TOUCHSCREEN[0m
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 [31mCONFIG_INPUT_TOUCHSCREEN[0m
config [31mCONFIG_TOUCHSCREEN_PROPERTIES[0m
def_tristate [31mCONFIG_INPUT[0m
depends on [31mCONFIG_INPUT[0m
config [31mCONFIG_TOUCHSCREEN_88PM860X[0m
tristate "Marvell 88PM860x touchscreen"
depends on [31mCONFIG_MFD_88PM860X[0m
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 [31mCONFIG_M[0m here: the
module will be called 88pm860x-ts.
config [31mCONFIG_TOUCHSCREEN_ADS7846[0m
tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens"
depends on [31mCONFIG_SPI_MASTER[0m
depends on [31mCONFIG_HWMON[0m = n || [31mCONFIG_HWMON[0m
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 [31mCONFIG_SPI[0m devices.
If [31mCONFIG_HWMON[0m 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 [31mCONFIG_M[0m here: the
module will be called ads7846.
config [31mCONFIG_TOUCHSCREEN_AD7877[0m
tristate "AD7877 based touchscreens"
depends on [31mCONFIG_SPI_MASTER[0m
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 [31mCONFIG_SPI[0m devices.
If unsure, say N (but it's safe to say "Y").
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ad7877.
config [31mCONFIG_TOUCHSCREEN_AD7879[0m
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 [31mCONFIG_M[0m here: the
module will be called ad7879.
config [31mCONFIG_TOUCHSCREEN_AD7879_I2C[0m
tristate "support I2C bus connection"
depends on [31mCONFIG_TOUCHSCREEN_AD7879[0m && [31mCONFIG_I2C[0m
select [31mCONFIG_REGMAP_I2C[0m
help
Say Y here if you have AD7879-1/AD7889-1 hooked to an [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ad7879-i2c.
config [31mCONFIG_TOUCHSCREEN_AD7879_SPI[0m
tristate "support SPI bus connection"
depends on [31mCONFIG_TOUCHSCREEN_AD7879[0m && [31mCONFIG_SPI_MASTER[0m
select [31mCONFIG_REGMAP_SPI[0m
help
Say Y here if you have AD7879-1/AD7889-1 hooked to a [31mCONFIG_SPI[0m bus.
If unsure, say N (but it's safe to say "Y").
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ad7879-spi.
config [31mCONFIG_TOUCHSCREEN_ADC[0m
tristate "Generic ADC based resistive touchscreen"
depends on [31mCONFIG_IIO[0m
select [31mCONFIG_IIO_BUFFER_CB[0m
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 [31mCONFIG_M[0m here: the
module will be called resistive-adc-touch.ko.
config [31mCONFIG_TOUCHSCREEN_AR1021_I2C[0m
tristate "Microchip AR1020/1021 i2c touchscreen"
depends on [31mCONFIG_I2C[0m && [31mCONFIG_OF[0m
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 [31mCONFIG_M[0m here: the
module will be called ar1021_i2c.
config [31mCONFIG_TOUCHSCREEN_ATMEL_MXT[0m
tristate "Atmel mXT I2C Touchscreen"
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_FW_LOADER[0m
help
Say Y here if you have Atmel mXT series [31mCONFIG_I2C[0m touchscreen,
such as AT42QT602240/ATMXT224, connected to your system.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called atmel_mxt_ts.
config [31mCONFIG_TOUCHSCREEN_ATMEL_MXT_T37[0m
bool "Support T37 Diagnostic Data"
depends on [31mCONFIG_TOUCHSCREEN_ATMEL_MXT[0m
depends on [31mCONFIG_VIDEO_V4L2[0m=y || ([31mCONFIG_TOUCHSCREEN_ATMEL_MXT[0m=m && [31mCONFIG_VIDEO_V4L2[0m=m)
select [31mCONFIG_VIDEOBUF2_VMALLOC[0m
help
Say Y here if you want support to output data from the T37
Diagnostic Data object using a V4L device.
config [31mCONFIG_TOUCHSCREEN_AUO_PIXCIR[0m
tristate "AUO in-cell touchscreen using Pixcir ICs"
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
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 [31mCONFIG_M[0m here: the
module will be called auo-pixcir-ts.
config [31mCONFIG_TOUCHSCREEN_BU21013[0m
tristate "BU21013 based touch panel controllers"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called bu21013_ts.
config [31mCONFIG_TOUCHSCREEN_BU21029[0m
tristate "Rohm BU21029 based touch panel controllers"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called bu21029_ts.
config [31mCONFIG_TOUCHSCREEN_CHIPONE_ICN8318[0m
tristate "chipone icn8318 touchscreen controller"
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_OF[0m
help
Say Y here if you have a ChipOne icn8318 based [31mCONFIG_I2C[0m touchscreen.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called chipone_icn8318.
config [31mCONFIG_TOUCHSCREEN_CHIPONE_ICN8505[0m
tristate "chipone icn8505 touchscreen controller"
depends on [31mCONFIG_I2C[0m && [31mCONFIG_ACPI[0m
help
Say Y here if you have a ChipOne icn8505 based [31mCONFIG_I2C[0m touchscreen.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called chipone_icn8505.
config [31mCONFIG_TOUCHSCREEN_CY8CTMG110[0m
tristate "cy8ctmg110 touchscreen"
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
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 [31mCONFIG_M[0m here: the
module will be called cy8ctmg110_ts.
config [31mCONFIG_TOUCHSCREEN_CYTTSP_CORE[0m
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 [31mCONFIG_M[0m here: the
module will be called cyttsp_core.
config [31mCONFIG_TOUCHSCREEN_CYTTSP_I2C[0m
tristate "support I2C bus connection"
depends on [31mCONFIG_TOUCHSCREEN_CYTTSP_CORE[0m && [31mCONFIG_I2C[0m
help
Say Y here if the touchscreen is connected via [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cyttsp_i2c.
config [31mCONFIG_TOUCHSCREEN_CYTTSP_SPI[0m
tristate "support SPI bus connection"
depends on [31mCONFIG_TOUCHSCREEN_CYTTSP_CORE[0m && [31mCONFIG_SPI_MASTER[0m
help
Say Y here if the touchscreen is connected via [31mCONFIG_SPI[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cyttsp_spi.
config [31mCONFIG_TOUCHSCREEN_CYTTSP4_CORE[0m
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 [31mCONFIG_M[0m here.
config [31mCONFIG_TOUCHSCREEN_CYTTSP4_I2C[0m
tristate "support I2C bus connection"
depends on [31mCONFIG_TOUCHSCREEN_CYTTSP4_CORE[0m && [31mCONFIG_I2C[0m
help
Say Y here if the touchscreen is connected via [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cyttsp4_i2c.
config [31mCONFIG_TOUCHSCREEN_CYTTSP4_SPI[0m
tristate "support SPI bus connection"
depends on [31mCONFIG_TOUCHSCREEN_CYTTSP4_CORE[0m && [31mCONFIG_SPI_MASTER[0m
help
Say Y here if the touchscreen is connected via [31mCONFIG_SPI[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cyttsp4_spi.
config [31mCONFIG_TOUCHSCREEN_DA9034[0m
tristate "Touchscreen support for Dialog Semiconductor DA9034"
depends on [31mCONFIG_PMIC_DA903X[0m
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 [31mCONFIG_M[0m here: the
module will be called da9034-ts.
config [31mCONFIG_TOUCHSCREEN_DA9052[0m
tristate "Dialog DA9052/DA9053 TSI"
depends on [31mCONFIG_PMIC_DA9052[0m
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 [31mCONFIG_M[0m here: the
module will be called da9052_tsi.
config [31mCONFIG_TOUCHSCREEN_DYNAPRO[0m
tristate "Dynapro serial touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called dynapro.
config [31mCONFIG_TOUCHSCREEN_HAMPSHIRE[0m
tristate "Hampshire serial touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called hampshire.
config [31mCONFIG_TOUCHSCREEN_EETI[0m
tristate "EETI touchscreen panel support"
depends on [31mCONFIG_I2C[0m
help
Say Y here to enable support for [31mCONFIG_I2C[0m connected EETI touch panels.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called eeti_ts.
config [31mCONFIG_TOUCHSCREEN_EGALAX[0m
tristate "EETI eGalax multi-touch panel support"
depends on [31mCONFIG_I2C[0m && [31mCONFIG_OF[0m
help
Say Y here to enable support for [31mCONFIG_I2C[0m connected EETI
eGalax multi-touch panels.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called egalax_ts.
config [31mCONFIG_TOUCHSCREEN_EGALAX_SERIAL[0m
tristate "EETI eGalax serial touchscreen"
select [31mCONFIG_SERIO[0m
help
Say Y here to enable support for serial connected EETI
eGalax touch panels.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called egalax_ts_serial.
config [31mCONFIG_TOUCHSCREEN_EXC3000[0m
tristate "EETI EXC3000 multi-touch panel support"
depends on [31mCONFIG_I2C[0m
help
Say Y here to enable support for [31mCONFIG_I2C[0m connected EETI
EXC3000 multi-touch panels.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called exc3000.
config [31mCONFIG_TOUCHSCREEN_FUJITSU[0m
tristate "Fujitsu serial touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called fujitsu-ts.
config [31mCONFIG_TOUCHSCREEN_GOODIX[0m
tristate "Goodix I2C touchscreen"
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
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 [31mCONFIG_ARM[0m tablets, like Wexler TAB7200 and MSI Primo73.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called goodix.
config [31mCONFIG_TOUCHSCREEN_HIDEEP[0m
tristate "HiDeep Touch IC"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have a touchscreen using HiDeep.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here : the
module will be called hideep_ts.
config [31mCONFIG_TOUCHSCREEN_ILI210X[0m
tristate "Ilitek ILI210X based touchscreen"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called ili210x.
config [31mCONFIG_TOUCHSCREEN_IPROC[0m
tristate "IPROC touch panel driver support"
depends on [31mCONFIG_ARCH_BCM_IPROC[0m || [31mCONFIG_COMPILE_TEST[0m
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 [31mCONFIG_M[0m here: the
module will be called bcm_iproc_tsc.
config [31mCONFIG_TOUCHSCREEN_S3C2410[0m
tristate "Samsung S3C2410/generic touchscreen input driver"
depends on [31mCONFIG_ARCH_S3C24XX[0m || [31mCONFIG_SAMSUNG_DEV_TS[0m
depends on [31mCONFIG_S3C_ADC[0m
help
Say Y here if you have the s3c2410 touchscreen.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called s3c2410_ts.
config [31mCONFIG_TOUCHSCREEN_S6SY761[0m
tristate "Samsung S6SY761 Touchscreen driver"
depends on [31mCONFIG_I2C[0m
help
Say Y if you have the Samsung S6SY761 driver
If unsure, say N
To compile this driver as module, choose [31mCONFIG_M[0m here: the
module will be called s6sy761.
config [31mCONFIG_TOUCHSCREEN_GUNZE[0m
tristate "Gunze AHL-51S touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called gunze.
config [31mCONFIG_TOUCHSCREEN_EKTF2127[0m
tristate "Elan eKTF2127 I2C touchscreen"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called ektf2127.
config [31mCONFIG_TOUCHSCREEN_ELAN[0m
tristate "Elan eKTH I2C touchscreen"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have an Elan eKTH [31mCONFIG_I2C[0m touchscreen
connected to your system.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called elants_i2c.
config [31mCONFIG_TOUCHSCREEN_ELO[0m
tristate "Elo serial touchscreens"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called elo.
config [31mCONFIG_TOUCHSCREEN_WACOM_W8001[0m
tristate "Wacom W8001 penabled serial touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called wacom_w8001.
config [31mCONFIG_TOUCHSCREEN_WACOM_I2C[0m
tristate "Wacom Tablet support (I2C)"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you want to use the [31mCONFIG_I2C[0m version of the Wacom
Pen Tablet.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called wacom_i2c.
config [31mCONFIG_TOUCHSCREEN_LPC32XX[0m
tristate "LPC32XX touchscreen controller"
depends on [31mCONFIG_ARCH_LPC32XX[0m
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 [31mCONFIG_M[0m here: the
module will be called lpc32xx_ts.
config [31mCONFIG_TOUCHSCREEN_MAX11801[0m
tristate "MAX11801 based touchscreens"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have a MAX11801 based touchscreen
controller.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called max11801_ts.
config [31mCONFIG_TOUCHSCREEN_MCS5000[0m
tristate "MELFAS MCS-5000 touchscreen"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called mcs5000_ts.
config [31mCONFIG_TOUCHSCREEN_MMS114[0m
tristate "MELFAS MMS114 touchscreen"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called mms114.
config [31mCONFIG_TOUCHSCREEN_MELFAS_MIP4[0m
tristate "MELFAS MIP4 Touchscreen"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have a MELFAS MIP4 Touchscreen device.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here:
the module will be called melfas_mip4.
config [31mCONFIG_TOUCHSCREEN_MTOUCH[0m
tristate "MicroTouch serial touchscreens"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called mtouch.
config [31mCONFIG_TOUCHSCREEN_IMX6UL_TSC[0m
tristate "Freescale i.MX6UL touchscreen controller"
depends on ([31mCONFIG_OF[0m && [31mCONFIG_GPIOLIB[0m) || [31mCONFIG_COMPILE_TEST[0m
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 [31mCONFIG_M[0m here: the
module will be called imx6ul_tsc.
config [31mCONFIG_TOUCHSCREEN_INEXIO[0m
tristate "iNexio serial touchscreens"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called inexio.
config [31mCONFIG_TOUCHSCREEN_MK712[0m
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 [31mCONFIG_M[0m here: the
module will be called mk712.
config [31mCONFIG_TOUCHSCREEN_HP600[0m
tristate "HP Jornada 6xx touchscreen"
depends on [31mCONFIG_SH_HP6XX[0m && [31mCONFIG_SH_ADC[0m
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 [31mCONFIG_M[0m here: the
module will be called hp680_ts_input.
config [31mCONFIG_TOUCHSCREEN_HP7XX[0m
tristate "HP Jornada 7xx touchscreen"
depends on [31mCONFIG_SA1100_JORNADA720_SSP[0m
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 [31mCONFIG_M[0m here: the
module will be called jornada720_ts.
config [31mCONFIG_TOUCHSCREEN_IPAQ_MICRO[0m
tristate "HP iPAQ Atmel Micro ASIC touchscreen"
depends on [31mCONFIG_MFD_IPAQ_MICRO[0m
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 [31mCONFIG_M[0m here: the
module will be called ipaq-micro-ts.
config [31mCONFIG_TOUCHSCREEN_HTCPEN[0m
tristate "HTC Shift X9500 touchscreen"
depends on [31mCONFIG_ISA[0m
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 [31mCONFIG_M[0m here: the
module will be called htcpen.
config [31mCONFIG_TOUCHSCREEN_PENMOUNT[0m
tristate "Penmount serial touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called penmount.
config [31mCONFIG_TOUCHSCREEN_EDT_FT5X06[0m
tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called edt-ft5x06.
config [31mCONFIG_TOUCHSCREEN_RASPBERRYPI_FW[0m
tristate "Raspberry Pi's firmware base touch screen support"
depends on [31mCONFIG_RASPBERRYPI_FIRMWARE[0m || ([31mCONFIG_RASPBERRYPI_FIRMWARE[0m=n && [31mCONFIG_COMPILE_TEST[0m)
select [31mCONFIG_INPUT_POLLDEV[0m
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 [31mCONFIG_M[0m here: the
module will be called raspberrypi-ts.
config [31mCONFIG_TOUCHSCREEN_MIGOR[0m
tristate "Renesas MIGO-R touchscreen"
depends on ([31mCONFIG_SH_MIGOR[0m || [31mCONFIG_COMPILE_TEST[0m) && [31mCONFIG_I2C[0m
help
Say Y here to enable MIGO-R touchscreen support.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called migor_ts.
config [31mCONFIG_TOUCHSCREEN_TOUCHRIGHT[0m
tristate "Touchright serial touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called touchright.
config [31mCONFIG_TOUCHSCREEN_TOUCHWIN[0m
tristate "Touchwin serial touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called touchwin.
config [31mCONFIG_TOUCHSCREEN_TI_AM335X_TSC[0m
tristate "TI Touchscreen Interface"
depends on [31mCONFIG_MFD_TI_AM335X_TSCADC[0m
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 [31mCONFIG_M[0m here: the
module will be called ti_am335x_tsc.
config [31mCONFIG_TOUCHSCREEN_UCB1400[0m
tristate "Philips UCB1400 touchscreen"
depends on [31mCONFIG_AC97_BUS[0m
depends on [31mCONFIG_UCB1400_CORE[0m
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 [31mCONFIG_M[0m here: the
module will be called ucb1400_ts.
config [31mCONFIG_TOUCHSCREEN_PIXCIR[0m
tristate "PIXCIR I2C touchscreens"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have a pixcir i2c touchscreen
controller.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pixcir_i2c_ts.
config [31mCONFIG_TOUCHSCREEN_WDT87XX_I2C[0m
tristate "Weida HiTech I2C touchscreen"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have a Weida WDT87XX [31mCONFIG_I2C[0m touchscreen
connected to your system.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called wdt87xx_i2c.
config [31mCONFIG_TOUCHSCREEN_WM831X[0m
tristate "Support for WM831x touchscreen controllers"
depends on [31mCONFIG_MFD_WM831X[0m
help
This enables support for the touchscreen controller on the WM831x
series of PMICs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called wm831x-ts.
config [31mCONFIG_TOUCHSCREEN_WM97XX[0m
tristate "Support for WM97xx AC97 touchscreen controllers"
depends on [31mCONFIG_AC97_BUS[0m || [31mCONFIG_AC97_BUS_NEW[0m
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 [31mCONFIG_M[0m here: the
module will be called wm97xx-ts.
config [31mCONFIG_TOUCHSCREEN_WM9705[0m
bool "WM9705 Touchscreen interface support"
depends on [31mCONFIG_TOUCHSCREEN_WM97XX[0m
default y
help
Say Y here to enable support for the Wolfson Microelectronics
WM9705 touchscreen controller.
config [31mCONFIG_TOUCHSCREEN_WM9712[0m
bool "WM9712 Touchscreen interface support"
depends on [31mCONFIG_TOUCHSCREEN_WM97XX[0m
default y
help
Say Y here to enable support for the Wolfson Microelectronics
WM9712 touchscreen controller.
config [31mCONFIG_TOUCHSCREEN_WM9713[0m
bool "WM9713 Touchscreen interface support"
depends on [31mCONFIG_TOUCHSCREEN_WM97XX[0m
default y
help
Say Y here to enable support for the Wolfson Microelectronics
WM9713 touchscreen controller.
config [31mCONFIG_TOUCHSCREEN_WM97XX_MAINSTONE[0m
tristate "WM97xx Mainstone/Palm accelerated touch"
depends on [31mCONFIG_TOUCHSCREEN_WM97XX[0m && [31mCONFIG_ARCH_PXA[0m
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 [31mCONFIG_M[0m here: the
module will be called mainstone-wm97xx.
config [31mCONFIG_TOUCHSCREEN_WM97XX_ZYLONITE[0m
tristate "Zylonite accelerated touch"
depends on [31mCONFIG_TOUCHSCREEN_WM97XX[0m && [31mCONFIG_MACH_ZYLONITE[0m
select [31mCONFIG_TOUCHSCREEN_WM9713[0m
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 [31mCONFIG_M[0m here: the
module will be called zylonite-wm97xx.
config [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
tristate "USB Touchscreen Driver"
depends on [31mCONFIG_USB_ARCH_HAS_HCD[0m
select [31mCONFIG_USB[0m
help
[31mCONFIG_USB[0m Touchscreen driver for:
- eGalax Touchkit [31mCONFIG_USB[0m (also includes eTurboTouch CT-410/510/700)
- PanJit TouchSet [31mCONFIG_USB[0m
- 3M MicroTouch [31mCONFIG_USB[0m (EX II series)
- ITM
- some other eTurboTouch
- Gunze AHL61
- DMC TSC-10/25
- IRTOUCHSYSTEMS/UNITOP
- IdealTEK URTC1000
- GoTop Super_Q2/GogoPen/PenPower tablets
- JASTEC [31mCONFIG_USB[0m Touch Controller/DigiTech DTR-02U
- Zytronic controllers
- Elo TouchSystems 2700 IntelliTouch
- EasyTouch [31mCONFIG_USB[0m 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 [31mCONFIG_M[0m here: the
module will be called usbtouchscreen.
config [31mCONFIG_TOUCHSCREEN_MXS_LRADC[0m
tristate "Freescale i.MX23/i.MX28 LRADC touchscreen"
depends on [31mCONFIG_MFD_MXS_LRADC[0m
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 [31mCONFIG_M[0m here: the module will be
called mxs-lradc-ts.
config [31mCONFIG_TOUCHSCREEN_MX25[0m
tristate "Freescale i.MX25 touchscreen input driver"
depends on [31mCONFIG_MFD_MX25_TSADC[0m
help
Enable support for touchscreen connected to your i.MX25.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called fsl-imx25-tcq.
config [31mCONFIG_TOUCHSCREEN_MC13783[0m
tristate "Freescale MC13783 touchscreen input driver"
depends on [31mCONFIG_MFD_MC13XXX[0m
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 [31mCONFIG_M[0m here: the
module will be called mc13783_ts.
config [31mCONFIG_TOUCHSCREEN_USB_EGALAX[0m
default y
bool "eGalax, eTurboTouch CT-410/510/700 device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_PANJIT[0m
default y
bool "PanJit device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_3M[0m
default y
bool "3M/Microtouch EX II series device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_ITM[0m
default y
bool "ITM device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_ETURBO[0m
default y
bool "eTurboTouch (non-eGalax compatible) device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_GUNZE[0m
default y
bool "Gunze AHL61 device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_DMC_TSC10[0m
default y
bool "DMC TSC-10/25 device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_IRTOUCH[0m
default y
bool "IRTOUCHSYSTEMS/UNITOP device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_IDEALTEK[0m
default y
bool "IdealTEK URTC1000 device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH[0m
default y
bool "GeneralTouch Touchscreen device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_GOTOP[0m
default y
bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_JASTEC[0m
default y
bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_ELO[0m
default y
bool "Elo TouchSystems 2700 IntelliTouch controller device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_E2I[0m
default y
bool "e2i Touchscreen controller (e.g. from Mimo 740)" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_ZYTRONIC[0m
default y
bool "Zytronic controller" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_ETT_TC45USB[0m
default y
bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_NEXIO[0m
default y
bool "NEXIO/iNexio device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
config [31mCONFIG_TOUCHSCREEN_USB_EASYTOUCH[0m
default y
bool "EasyTouch USB Touch controller device support" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_TOUCHSCREEN_USB_COMPOSITE[0m
help
Say Y here if you have an EasyTouch [31mCONFIG_USB[0m Touch controller.
If unsure, say N.
config [31mCONFIG_TOUCHSCREEN_TOUCHIT213[0m
tristate "Sahara TouchIT-213 touchscreen"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called touchit213.
config [31mCONFIG_TOUCHSCREEN_TS4800[0m
tristate "TS-4800 touchscreen"
depends on [31mCONFIG_HAS_IOMEM[0m && [31mCONFIG_OF[0m
depends on [31mCONFIG_SOC_IMX51[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_MFD_SYSCON[0m
select [31mCONFIG_INPUT_POLLDEV[0m
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 [31mCONFIG_FPGA[0m.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ts4800_ts.
config [31mCONFIG_TOUCHSCREEN_TSC_SERIO[0m
tristate "TSC-10/25/40 serial touchscreen support"
select [31mCONFIG_SERIO[0m
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 [31mCONFIG_M[0m here: the
module will be called tsc40.
config [31mCONFIG_TOUCHSCREEN_TSC200X_CORE[0m
tristate
config [31mCONFIG_TOUCHSCREEN_TSC2004[0m
tristate "TSC2004 based touchscreens"
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_REGMAP_I2C[0m
select [31mCONFIG_TOUCHSCREEN_TSC200X_CORE[0m
help
Say Y here if you have a TSC2004 based touchscreen.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called tsc2004.
config [31mCONFIG_TOUCHSCREEN_TSC2005[0m
tristate "TSC2005 based touchscreens"
depends on [31mCONFIG_SPI_MASTER[0m
select [31mCONFIG_REGMAP_SPI[0m
select [31mCONFIG_TOUCHSCREEN_TSC200X_CORE[0m
help
Say Y here if you have a TSC2005 based touchscreen.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called tsc2005.
config [31mCONFIG_TOUCHSCREEN_TSC2007[0m
tristate "TSC2007 based touchscreens"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have a TSC2007 based touchscreen.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called tsc2007.
config [31mCONFIG_TOUCHSCREEN_TSC2007_IIO[0m
bool "IIO interface for external ADC input and temperature"
depends on [31mCONFIG_TOUCHSCREEN_TSC2007[0m
depends on [31mCONFIG_IIO[0m=y || [31mCONFIG_IIO[0m=[31mCONFIG_TOUCHSCREEN_TSC2007[0m
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 [31mCONFIG_TOUCHSCREEN_PCAP[0m
tristate "Motorola PCAP touchscreen"
depends on [31mCONFIG_EZX_PCAP[0m
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 [31mCONFIG_M[0m here: the
module will be called pcap_ts.
config [31mCONFIG_TOUCHSCREEN_RM_TS[0m
tristate "Raydium I2C Touchscreen"
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y here if you have Raydium series [31mCONFIG_I2C[0m touchscreen,
such as RM32380, connected to your system.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called raydium_i2c_ts.
config [31mCONFIG_TOUCHSCREEN_SILEAD[0m
tristate "Silead I2C touchscreen"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called silead.
config [31mCONFIG_TOUCHSCREEN_SIS_I2C[0m
tristate "SiS 9200 family I2C touchscreen"
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_CRC_ITU_T[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
This enables support for SiS 9200 family over [31mCONFIG_I2C[0m based touchscreens.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sis_i2c.
config [31mCONFIG_TOUCHSCREEN_ST1232[0m
tristate "Sitronix ST1232 or ST1633 touchscreen controllers"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called st1232_ts.
config [31mCONFIG_TOUCHSCREEN_STMFTS[0m
tristate "STMicroelectronics STMFTS touchscreen"
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_LEDS_CLASS[0m
help
Say Y here if you want support for STMicroelectronics
STMFTS touchscreen.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called stmfts.
config [31mCONFIG_TOUCHSCREEN_STMPE[0m
tristate "STMicroelectronics STMPE touchscreens"
depends on [31mCONFIG_MFD_STMPE[0m
depends on ([31mCONFIG_OF[0m || [31mCONFIG_COMPILE_TEST[0m)
help
Say Y here if you want support for STMicroelectronics
STMPE touchscreen controllers.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called stmpe-ts.
config [31mCONFIG_TOUCHSCREEN_SUN4I[0m
tristate "Allwinner sun4i resistive touchscreen controller support"
depends on [31mCONFIG_ARCH_SUNXI[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HWMON[0m
depends on [31mCONFIG_THERMAL[0m || ![31mCONFIG_THERMAL_OF[0m
help
This selects support for the resistive touchscreen controller
found on Allwinner sunxi SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sun4i-ts.
config [31mCONFIG_TOUCHSCREEN_SUR40[0m
tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
depends on [31mCONFIG_USB[0m && [31mCONFIG_MEDIA_USB_SUPPORT[0m && [31mCONFIG_HAS_DMA[0m
depends on [31mCONFIG_VIDEO_V4L2[0m
select [31mCONFIG_INPUT_POLLDEV[0m
select [31mCONFIG_VIDEOBUF2_DMA_SG[0m
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 [31mCONFIG_M[0m here: the
module will be called sur40.
config [31mCONFIG_TOUCHSCREEN_SURFACE3_SPI[0m
tristate "Ntrig/Microsoft Surface 3 SPI touchscreen"
depends on [31mCONFIG_SPI[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y here if you have the Ntrig/Microsoft [31mCONFIG_SPI[0m touchscreen
controller chip as found on the Surface 3 in your system.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called surface3_spi.
config [31mCONFIG_TOUCHSCREEN_SX8654[0m
tristate "Semtech SX8654 touchscreen"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have a Semtech SX8654 touchscreen controller.
If unsure, say N
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sx8654.
config [31mCONFIG_TOUCHSCREEN_TPS6507X[0m
tristate "TPS6507x based touchscreens"
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
Say Y here if you have a TPS6507x based touchscreen
controller.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called tps6507x_ts.
config [31mCONFIG_TOUCHSCREEN_ZET6223[0m
tristate "Zeitec ZET6223 touchscreen driver"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you have a touchscreen using Zeitec ZET6223
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called zet6223.
config [31mCONFIG_TOUCHSCREEN_ZFORCE[0m
tristate "Neonode zForce infrared touchscreens"
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
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 [31mCONFIG_M[0m here: the
module will be called zforce_ts.
config [31mCONFIG_TOUCHSCREEN_COLIBRI_VF50[0m
tristate "Toradex Colibri on board touchscreen driver"
depends on [31mCONFIG_IIO[0m && [31mCONFIG_VF610_ADC[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
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 [31mCONFIG_M[0m here: the
module will be called colibri_vf50_ts.
config [31mCONFIG_TOUCHSCREEN_ROHM_BU21023[0m
tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called bu21023_ts.
config [31mCONFIG_TOUCHSCREEN_IQS5XX[0m
tristate "Azoteq IQS550/572/525 trackpad/touchscreen controller"
depends on [31mCONFIG_I2C[0m
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 [31mCONFIG_M[0m here: the
module will be called iqs5xx.
endif