if INPUT_TOUCHSCREEN
-config CT36X_TS
- tristate "CT36X touchscreens support"
-
-config TOUCHSCREEN_GSLX680
- tristate "gslX680 touchscreen panel support "
- depends on I2C2_RK29 || I2C2_RK30
-config TOUCHSCREEN_GSLX680_RK3168
- tristate "gslX680 rk3168 touchscreen panel support "
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_XPT2046_SPI
- tristate "XPT2046 based touchscreens:SPI Interface"
- depends on SPIM_RK29
-
- config TOUCHSCREEN_XPT2046_NORMAL_SPI
- tristate "normal mode"
- depends on TOUCHSCREEN_XPT2046_SPI
-
- config TOUCHSCREEN_480X800
- tristate "480X800 resolution"
- depends on TOUCHSCREEN_XPT2046_NORMAL_SPI
-
- config TOUCHSCREEN_800X480
- tristate "800X480 resolution"
- depends on TOUCHSCREEN_XPT2046_NORMAL_SPI
-
- config TOUCHSCREEN_320X480
- tristate "320X480 resolution"
- depends on TOUCHSCREEN_XPT2046_NORMAL_SPI
-
- config TOUCHSCREEN_XPT2046_TSLIB_SPI
- tristate "tslib mode"
- depends on TOUCHSCREEN_XPT2046_SPI
-
- config TOUCHSCREEN_480X800
- tristate "480X800 resolution"
- depends on TOUCHSCREEN_XPT2046_TSLIB_SPI
-
- config TOUCHSCREEN_800X480
- tristate "800X480 resolution"
- depends on TOUCHSCREEN_XPT2046_TSLIB_SPI
-
- config TOUCHSCREEN_320X480
- tristate "320X480 resolution"
- depends on TOUCHSCREEN_XPT2046_TSLIB_SPI
+config TOUCHSCREEN_ZET62XX
+ tristate "zet62xx touchscreen driver"
+ help
+ zet62xx touchscreen driver
- config TOUCHSCREEN_XPT2046_CBN_SPI
- tristate "calibration mode"
- depends on TOUCHSCREEN_XPT2046_SPI
- config TOUCHSCREEN_480X800
- tristate "480X800 resolution"
- depends on TOUCHSCREEN_XPT2046_CBN_SPI
+config TOUCHSCREEN_GSLX680
+ tristate "gslX680 touchscreen driver"
+ help
+ gslX680 touchscreen driver
- config TOUCHSCREEN_800X480
- tristate "800X480 resolution"
- depends on TOUCHSCREEN_XPT2046_CBN_SPI
+config TOUCHSCREEN_GT8XX
+ tristate "Goodix touch screen gt801X2 support for rockchip based platform"
+ help
+ Say Y here if you have a touchscreen interface using the
+ two goodix gt801 , and your board-specific initialization
+ code includes that in its table of IIC devices.
+ If unsure, say N.
- config TOUCHSCREEN_320X480
- tristate "320X480 resolution"
- depends on TOUCHSCREEN_XPT2046_CBN_SPI
+config TOUCHSCREEN_GT9XX
+ tristate "Goodix touch screen gt9xx support for rockchip based platform"
+ help
+ Say Y here if you have a touchscreen interface using the
+ two goodix gt9xx, and your board-specific initialization
+ code includes that in its table of IIC devices.
+ If unsure, say N.
+config TOUCHSCREEN_CT36X_TS
+ tristate "CT36X touchscreens support"
+
+config TOUCHSCREEN_VTL_CT36X
+ tristate "VTL touchscreens support"
+
config TOUCHSCREEN_88PM860X
tristate "Marvell 88PM860x touchscreen"
depends on MFD_88PM860X
To compile this driver as a module, choose M here: the
module will be called ad7877.
-config TOUCHSCREEN_ILI2102_IIC
- tristate "ili2102 based touchscreens: IIC Interface"
- help
- Say Y here if you have a touchscreen interface using the
- hx8520 controller, and your board-specific initialization
- code includes that in its table of IIC devices.
-
- If unsure, say N (but it's safe to say "Y").
-config TOUCHSCREEN_GT8XX
- tristate "Goodix touch screen gt801X2 support for rockchip based platform"
- help
- Say Y here if you have a touchscreen interface using the
- two goodix gt801 , and your board-specific initialization
- code includes that in its table of IIC devices.
- If unsure, say N.
- config TOUCH_MAX_X
- int "touch max x resolution"
- depends on TOUCHSCREEN_GT8XX
- default 1280
- help
- goodix touch max X resolution
-
- config TOUCH_MAX_Y
- int "touch max y resolution"
- depends on TOUCHSCREEN_GT8XX
- default 800
- help
- goodix touch max y resolution
-
-config TOUCHSCREEN_CT36X
- default n
- tristate "CT36X based touchscreens"
-
-config RK28_I2C_TS_NTP070
- tristate "NTP070 based touchscreens: NTP070 Interface"
- depends on I2C_RK2818
-
-config TOUCHSCREEN_IT7250
- tristate "IT7250 based touchscreens: IT7250 Interface"
- help
- Say Y here if you have a touchscreen interface using the
- xpt2046 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").
-
config TOUCHSCREEN_AD7879
tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
help
To compile this driver as a module, choose M here: the
module will be called atmel_mxt_ts.
-config TOUCHSCREEN_BITSY
- tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
- depends on SA1100_BITSY
- select SERIO
+config TOUCHSCREEN_AUO_PIXCIR
+ tristate "AUO in-cell touchscreen using Pixcir ICs"
+ depends on I2C
+ depends on GPIOLIB
help
- Say Y here if you have the h3600 (Bitsy) touchscreen.
+ 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 h3600_ts_input.
+ module will be called auo-pixcir-ts.
config TOUCHSCREEN_BU21013
tristate "BU21013 based touch panel controllers"
tristate "cy8ctmg110 touchscreen"
depends on I2C
depends on GPIOLIB
-
help
Say Y here if you have a cy8ctmg110 capacitive touchscreen on
an AAVA device.
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_DA9034
tristate "Touchscreen support for Dialog Semiconductor DA9034"
depends on PMIC_DA903X
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
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_FUJITSU
tristate "Fujitsu serial touchscreen"
select SERIO
To compile this driver as a module, choose M here: the
module will be called fujitsu-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_S3C2410
tristate "Samsung S3C2410/generic touchscreen input driver"
- depends on ARCH_S3C2410 || SAMSUNG_DEV_TS
+ depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
select S3C_ADC
help
Say Y here if you have the s3c2410 touchscreen.
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
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 && GENERIC_HARDIRQS
+ 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_MTOUCH
tristate "MicroTouch serial touchscreens"
select SERIO
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_MIGOR
tristate "Renesas MIGO-R touchscreen"
depends on SH_MIGOR && I2C
To compile this driver as a module, choose M here: the
module will be called tnetv107x-ts.
-config TOUCHSCREEN_SYNAPTICS_I2C_RMI
- tristate "Synaptics i2c touchscreen"
- depends on I2C
- help
- This enables support for Synaptics RMI over I2C based touchscreens.
-
config TOUCHSCREEN_TOUCHRIGHT
tristate "Touchright serial touchscreen"
select SERIO
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_ATMEL_TSADCC
tristate "Atmel Touchscreen Interface"
- depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
+ depends on ARCH_AT91
help
Say Y here if you have a 4-wire touchscreen connected to the
- ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
+ ADC Controller on your Atmel SoC.
If unsure, say N.
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_WM831X
tristate "Support for WM831x touchscreen controllers"
depends on MFD_WM831X
- 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.
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)"
+ bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
depends on TOUCHSCREEN_USB_COMPOSITE
config TOUCHSCREEN_USB_ZYTRONIC
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 EMBEDDED
+ 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
To compile this driver as a module, choose M here: the
module will be called touchit213.
+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_TSC2005
tristate "TSC2005 based touchscreens"
depends on SPI_MASTER && GENERIC_HARDIRQS
To compile this driver as a module, choose M here: the
module will be called tps6507x_ts.
-config HANNSTAR_P1003
- tristate "Hannstar P1003 touchscreen"
- depends on I2C2_RK29
- help
- RK29 hannstar touch
-
- config HANNSTAR_MAX_X
- int "hannstar touch x max"
- depends on HANNSTAR_P1003
- default 1087
- help
- RK29 hannstar touch max X size
-
- config HANNSTAR_MAX_Y
- int "hannstar touch Y max"
- depends on HANNSTAR_P1003
- default 800
- help
- RK29 hannstar touch max Y size
-
- config HANNSTAR_DEBUG
- bool "hannstar debug"
- depends on HANNSTAR_P1003
- default n
- help
- RK29 hannstar touch debug
-
-config ATMEL_MXT224
- tristate "Atmel mXT224 touchscreen"
- depends on I2C2_RK29
- help
- RK29 Atmel_mXT224 touch
-
- config MXT224_MAX_X
- int "atmel_mxt224 touch X max"
- depends on ATMEL_MXT224
- default 4095
- help
- RK29 atmel_mxt224 touch max X size
-
- config MXT224_MAX_Y
- int "atmel_mxt224 touch Y max"
- depends on ATMEL_MXT224
- default 4095
- help
- RK29 atmel_mxt224 touch max Y size
-
-config SINTEK_3FA16
- tristate "Sintek 3FA16 touchscreen"
- depends on I2C2_RK29
- help
- RK29 Sintek touch
-
- config HANNSTAR_MAX_X
- int "Sintek touch x max"
- depends on SINTEK_3FA16
- default 1024
- help
- RK29 hannstar touch max X size
-
- config HANNSTAR_MAX_Y
- int "Sintek touch Y max"
- depends on SINTEK_3FA16
- default 600
- help
- RK29 hannstar touch max Y size
-
- config HANNSTAR_DEBUG
- bool "Sintek debug"
- depends on SINTEK_3FA16
- default n
- help
- RK29 hannstar touch debug
-
-config EETI_EGALAX
- tristate "EETI_EGALAX 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_egalax_ts.
-
- config EETI_EGALAX_MAX_X
- int "EETI_EGALAX_MAX_X"
- depends on EETI_EGALAX
- default 2047
- help
- RK29 EETI_EGALAX touch max X size
-
- config EETI_EGALAX_MAX_Y
- int "EETI_EGALAX_MAX_Y"
- depends on EETI_EGALAX
- default 2047
- help
- RK29 EETI_EGALAX touch max Y size
-
- config EETI_EGALAX_DEBUG
- bool "EETI_EGALAX debug"
- depends on EETI_EGALAX
- default n
- help
- RK29 EETI_EGALAX touch debug
-
-config TOUCHSCREEN_IT7260
- tristate "IT7260 based touchscreens: IT7260 Interface"
- depends on I2C2_RK29
- help
- Say Y here if you have a touchscreen interface using the
- it7260 controller, and your board-specific initialization
- code includes that in its table of I2C devices.
-
- If unsure, say N (but it's safe to say "Y").
-
-config TOUCHSCREEN_IT7260_I2C
- tristate "IT7260 based touchscreens: IT7260 I2C Interface"
- depends on I2C_RK29
- help
- Say Y here if you have a touchscreen interface using the
- IT7260 controller, and your board-specific initialization
- code includes that in its table of I2C devices.
-
- If unsure, say N (but it's safe to say "Y").
-
-config TOUCHSCREEN_NAS
- tristate "NAS based touchscreens: NAS Interface"
- depends on I2C2_RK29
- help
- Say Y here if you have a touchscreen interface using the
- nas controller, and your board-specific initialization
- code includes that in its table of I2C devices.
-
- If unsure, say N (but it's safe to say "Y").
-
-config LAIBAO_TS
- tristate "LAIBAO touchscreen"
- depends on I2C2_RK29
- help
- RK29 LAIBAO touchscreen
-
-config TOUCHSCREEN_GT801_IIC
- tristate "GT801_IIC based touchscreens"
- depends on I2C2_RK29
-
-config TOUCHSCREEN_GT811_IIC
- tristate "GT811_IIC based touchscreens"
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_86V_GT811_IIC
- tristate "RK3168_86V GT811_IIC based touchscreens"
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_GT82X_IIC
- tristate "GT82x_IIC based touchscreens"
- depends on I2C2_RK30
-
-config TOUCHSCREEN_GT82X_IIC_760
- tristate "GT82x_IIC based touchscreens for 760"
- depends on I2C2_RK30
-config TOUCHSCREEN_GT818_IIC
- tristate "GT818_IIC based touchscreens"
- depends on I2C2_RK29
-
-config TOUCHSCREEN_PIXCIR
- tristate "PIXCIR_IIC based touchscreens"
- depends on I2C2_RK29
-
-config TOUCHSCREEN_SYNAPTICS_RMI4_I2C_RK
- tristate "Synaptics i2c rmi4 touchscreen"
- depends on I2C_RK30
- help
- This enables support for Synaptics RMI over I2C based touchscreens.
- config TOUCHSCREEN_SYNAPTICS_S3202
- tristate "SYNAPTICS S3202 touchscreen"
- depends on TOUCHSCREEN_SYNAPTICS_RMI4_I2C_RK
- source "drivers/input/touchscreen/rmi4/Kconfig"
-config D70_L3188A
- tristate "D70-L3188A based touchscreens"
- depends on I2C2_RK29
-
-config TOUCHSCREEN_GT819
- tristate "GT819 based touchscreens"
- depends on I2C2_RK29
-
-
-config TOUCHSCREEN_GT8110
- tristate "GT8110 based touchscreens"
- depends on I2C2_RK29 || I2C_RK30
-config TP_760_TS
- tristate "tp for 760"
- depends on I2C2_RK29 || I2C_RK30
-config TOUCHSCREEN_CT360_IIC
- tristate "CT360 based touchscreens"
- depends on I2C_RK29 || I2C_RK30
-
-config TOUCHSCREEN_FT5306
- tristate "FT5306 based touchscreens: FT5306 Interface"
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_I30
- tristate "i30 based touchscreens: i30(ft5306) Interface"
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_BYD693X
- tristate "touchscreen BYD693X I2C Interface"
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_SITRONIX_A720
- tristate "SITRONIX based touchscreens: SITRONIX Interface for a720"
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_FT5306_WPX2
- tristate "FT5306 based touchscreens: FT5306 Interface,only used for umeox wpx2 board"
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_FT5306_AV
- tristate "FT5306 based touchscreens: FT5306 Interface base on AV-Display factory 1204*600"
- depends on I2C2_RK29 || I2C2_RK30
-
-config TOUCHSCREEN_FT5406
- tristate "FT5406 based touchscreens: FT5406 Interface"
- depends on I2C2_RK29
- help
- say Y here if you have a touchscreen interface using the FT5406
- controller,and your board-specific initialization code includes that
- in its table of I2C devices.
-
- If unsure, say N(but it's safe to say "Y").
-
-config TOUCHSCREEN_FT5X0X
- tristate "ft5x0x touchscreen panel support "
- depends on I2C2_RK29 || I2C2_RK30
-config TOUCHSCREEN_FT5506
- tristate "FT5506 based touchscreens: FT5506 Interface"
- depends on I2C2_RK29 || I2C2_RK30
- help
- say Y here if you have a touchscreen interface using the FT5506
- controller,and your board-specific initialization code includes that
- in its table of I2C devices.
-
- If unsure, say N(but it's safe to say "Y").
-# VTL TouchScreen Driver Config
-source "drivers/input/touchscreen/ct36x_ts/Kconfig"
-
-config ATMEL_MXT1386
- tristate "ATMEL_MXT1386 touchscreen panel support"
- depends on I2C
- help
- Say Y here to enable support for I2C connected ATMEL_MXT1386 touch panels.
-
- To compile this driver as a module, choose M here: the
- module will be called atmel_mxt1386_ts.
-
- config ATMEL_MXT1386_MAX_X
- int "ATMEL_MXT1386_MAX_X"
- depends on ATMEL_MXT1386
- default 4095
- help
- RK29 ATMEL_MXT1386 touch max X size
-
- config ATMEL_MXT1386_MAX_Y
- int "ATMEL_MXT1386_MAX_Y"
- depends on ATMEL_MXT1386
- default 4095
- help
- RK29 ATMEL_MXT1386 touch max Y size
-
- config ATMEL_MXT1386_DEBUG
- bool "ATMEL_MXT1386 debug"
- depends on ATMEL_MXT1386
- default n
- help
- RK29 ATMEL_MXT1386 touch debug
endif
projects / firefly-linux-kernel-4.4.55.git / blobdiff