2 # Touchscreen driver configuration
4 menuconfig INPUT_TOUCHSCREEN
7 Say Y here, and a list of supported touchscreens will be displayed.
8 This option doesn't affect the kernel.
14 config TOUCHSCREEN_PROPERTIES
18 config TOUCHSCREEN_88PM860X
19 tristate "Marvell 88PM860x touchscreen"
20 depends on MFD_88PM860X
22 Say Y here if you have a 88PM860x PMIC and want to enable
23 support for the built-in touchscreen.
27 To compile this driver as a module, choose M here: the
28 module will be called 88pm860x-ts.
30 config TOUCHSCREEN_ADS7846
31 tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens"
33 depends on HWMON = n || HWMON
35 Say Y here if you have a touchscreen interface using the
36 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
37 and your board-specific setup code includes that in its
40 If HWMON is selected, and the driver is told the reference voltage
41 on your board, you will also get hwmon interfaces for the voltage
42 (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
44 If unsure, say N (but it's safe to say "Y").
46 To compile this driver as a module, choose M here: the
47 module will be called ads7846.
49 config TOUCHSCREEN_AD7877
50 tristate "AD7877 based touchscreens"
53 Say Y here if you have a touchscreen interface using the
54 AD7877 controller, and your board-specific initialization
55 code includes that in its table of SPI devices.
57 If unsure, say N (but it's safe to say "Y").
59 To compile this driver as a module, choose M here: the
60 module will be called ad7877.
62 config TOUCHSCREEN_AD7879
63 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
65 Say Y here if you want to support a touchscreen interface using
66 the AD7879-1/AD7889-1 controller.
68 You should select a bus connection too.
70 To compile this driver as a module, choose M here: the
71 module will be called ad7879.
73 config TOUCHSCREEN_AD7879_I2C
74 tristate "support I2C bus connection"
75 depends on TOUCHSCREEN_AD7879 && I2C
77 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
79 To compile this driver as a module, choose M here: the
80 module will be called ad7879-i2c.
82 config TOUCHSCREEN_AD7879_SPI
83 tristate "support SPI bus connection"
84 depends on TOUCHSCREEN_AD7879 && SPI_MASTER
86 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
88 If unsure, say N (but it's safe to say "Y").
90 To compile this driver as a module, choose M here: the
91 module will be called ad7879-spi.
93 config TOUCHSCREEN_AR1021_I2C
94 tristate "Microchip AR1021 i2c touchscreen"
97 Say Y here if you have the Microchip AR1021 touchscreen controller
102 To compile this driver as a module, choose M here: the
103 module will be called ar1021_i2c.
105 config TOUCHSCREEN_ATMEL_MXT
106 tristate "Atmel mXT I2C Touchscreen"
110 Say Y here if you have Atmel mXT series I2C touchscreen,
111 such as AT42QT602240/ATMXT224, connected to your system.
115 To compile this driver as a module, choose M here: the
116 module will be called atmel_mxt_ts.
118 config TOUCHSCREEN_AUO_PIXCIR
119 tristate "AUO in-cell touchscreen using Pixcir ICs"
121 depends on GPIOLIB || COMPILE_TEST
123 Say Y here if you have a AUO display with in-cell touchscreen
128 To compile this driver as a module, choose M here: the
129 module will be called auo-pixcir-ts.
131 config TOUCHSCREEN_BU21013
132 tristate "BU21013 based touch panel controllers"
135 Say Y here if you have a bu21013 touchscreen connected to
140 To compile this driver as a module, choose M here: the
141 module will be called bu21013_ts.
143 config TOUCHSCREEN_CHIPONE_ICN8318
144 tristate "chipone icn8318 touchscreen controller"
145 depends on GPIOLIB || COMPILE_TEST
149 Say Y here if you have a ChipOne icn8318 based I2C touchscreen.
153 To compile this driver as a module, choose M here: the
154 module will be called chipone_icn8318.
156 config TOUCHSCREEN_CY8CTMG110
157 tristate "cy8ctmg110 touchscreen"
159 depends on GPIOLIB || COMPILE_TEST
161 Say Y here if you have a cy8ctmg110 capacitive touchscreen on
166 To compile this driver as a module, choose M here: the
167 module will be called cy8ctmg110_ts.
169 config TOUCHSCREEN_CYTTSP_CORE
170 tristate "Cypress TTSP touchscreen"
172 Say Y here if you have a touchscreen using controller from
173 the Cypress TrueTouch(tm) Standard Product family connected
174 to your system. You will also need to select appropriate
175 bus connection below.
179 To compile this driver as a module, choose M here: the
180 module will be called cyttsp_core.
182 config TOUCHSCREEN_CYTTSP_I2C
183 tristate "support I2C bus connection"
184 depends on TOUCHSCREEN_CYTTSP_CORE && I2C
186 Say Y here if the touchscreen is connected via I2C bus.
188 To compile this driver as a module, choose M here: the
189 module will be called cyttsp_i2c.
191 config TOUCHSCREEN_CYTTSP_SPI
192 tristate "support SPI bus connection"
193 depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
195 Say Y here if the touchscreen is connected via SPI bus.
197 To compile this driver as a module, choose M here: the
198 module will be called cyttsp_spi.
200 config TOUCHSCREEN_CYTTSP4_CORE
201 tristate "Cypress TrueTouch Gen4 Touchscreen Driver"
203 Core driver for Cypress TrueTouch(tm) Standard Product
204 Generation4 touchscreen controllers.
206 Say Y here if you have a Cypress Gen4 touchscreen.
210 To compile this driver as a module, choose M here.
212 config TOUCHSCREEN_CYTTSP4_I2C
213 tristate "support I2C bus connection"
214 depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
216 Say Y here if the touchscreen is connected via I2C bus.
218 To compile this driver as a module, choose M here: the
219 module will be called cyttsp4_i2c.
221 config TOUCHSCREEN_CYTTSP4_SPI
222 tristate "support SPI bus connection"
223 depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
225 Say Y here if the touchscreen is connected via SPI bus.
227 To compile this driver as a module, choose M here: the
228 module will be called cyttsp4_spi.
230 config TOUCHSCREEN_DA9034
231 tristate "Touchscreen support for Dialog Semiconductor DA9034"
232 depends on PMIC_DA903X
235 Say Y here to enable the support for the touchscreen found
236 on Dialog Semiconductor DA9034 PMIC.
240 To compile this driver as a module, choose M here: the
241 module will be called da9034-ts.
243 config TOUCHSCREEN_DA9052
244 tristate "Dialog DA9052/DA9053 TSI"
245 depends on PMIC_DA9052
247 Say Y here to support the touchscreen found on Dialog Semiconductor
248 DA9052-BC and DA9053-AA/Bx PMICs.
252 To compile this driver as a module, choose M here: the
253 module will be called da9052_tsi.
255 config TOUCHSCREEN_DYNAPRO
256 tristate "Dynapro serial touchscreen"
259 Say Y here if you have a Dynapro serial touchscreen connected to
264 To compile this driver as a module, choose M here: the
265 module will be called dynapro.
267 config TOUCHSCREEN_HAMPSHIRE
268 tristate "Hampshire serial touchscreen"
271 Say Y here if you have a Hampshire serial touchscreen connected to
276 To compile this driver as a module, choose M here: the
277 module will be called hampshire.
279 config TOUCHSCREEN_EETI
280 tristate "EETI touchscreen panel support"
283 Say Y here to enable support for I2C connected EETI touch panels.
285 To compile this driver as a module, choose M here: the
286 module will be called eeti_ts.
288 config TOUCHSCREEN_EGALAX
289 tristate "EETI eGalax multi-touch panel support"
292 Say Y here to enable support for I2C connected EETI
293 eGalax multi-touch panels.
295 To compile this driver as a module, choose M here: the
296 module will be called egalax_ts.
298 config TOUCHSCREEN_EGALAX_SERIAL
299 tristate "EETI eGalax serial touchscreen"
302 Say Y here to enable support for serial connected EETI
305 To compile this driver as a module, choose M here: the
306 module will be called egalax_ts_serial.
308 config TOUCHSCREEN_FT6236
309 tristate "FT6236 I2C touchscreen"
311 depends on GPIOLIB || COMPILE_TEST
313 Say Y here to enable support for the I2C connected FT6x06 and
314 FT6x36 family of capacitive touchscreen drivers.
318 To compile this driver as a module, choose M here: the
319 module will be called ft6236.
321 config TOUCHSCREEN_FUJITSU
322 tristate "Fujitsu serial touchscreen"
325 Say Y here if you have the Fujitsu touchscreen (such as one
326 installed in Lifebook P series laptop) connected to your
331 To compile this driver as a module, choose M here: the
332 module will be called fujitsu-ts.
334 config TOUCHSCREEN_GOODIX
335 tristate "Goodix I2C touchscreen"
337 depends on GPIOLIB || COMPILE_TEST
339 Say Y here if you have the Goodix touchscreen (such as one
340 installed in Onda v975w tablets) connected to your
341 system. It also supports 5-finger chip models, which can be
342 found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
346 To compile this driver as a module, choose M here: the
347 module will be called goodix.
349 config TOUCHSCREEN_ILI210X
350 tristate "Ilitek ILI210X based touchscreen"
353 Say Y here if you have a ILI210X based touchscreen
354 controller. This driver supports models ILI2102,
355 ILI2102s, ILI2103, ILI2103s and ILI2105.
356 Such kind of chipsets can be found in Amazon Kindle Fire
361 To compile this driver as a module, choose M here: the
362 module will be called ili210x.
364 config TOUCHSCREEN_IPROC
365 tristate "IPROC touch panel driver support"
366 depends on ARCH_BCM_IPROC || COMPILE_TEST
368 Say Y here if you want to add support for the IPROC touch
369 controller to your system.
373 To compile this driver as a module, choose M here: the
374 module will be called bcm_iproc_tsc.
376 config TOUCHSCREEN_S3C2410
377 tristate "Samsung S3C2410/generic touchscreen input driver"
378 depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
381 Say Y here if you have the s3c2410 touchscreen.
385 To compile this driver as a module, choose M here: the
386 module will be called s3c2410_ts.
388 config TOUCHSCREEN_GUNZE
389 tristate "Gunze AHL-51S touchscreen"
392 Say Y here if you have the Gunze AHL-51 touchscreen connected to
397 To compile this driver as a module, choose M here: the
398 module will be called gunze.
400 config TOUCHSCREEN_ELAN
401 tristate "Elan eKTH I2C touchscreen"
404 Say Y here if you have an Elan eKTH I2C touchscreen
405 connected to your system.
409 To compile this driver as a module, choose M here: the
410 module will be called elants_i2c.
412 config TOUCHSCREEN_ELO
413 tristate "Elo serial touchscreens"
416 Say Y here if you have an Elo serial touchscreen connected to
421 To compile this driver as a module, choose M here: the
422 module will be called elo.
424 config TOUCHSCREEN_WACOM_W8001
425 tristate "Wacom W8001 penabled serial touchscreen"
428 Say Y here if you have an Wacom W8001 penabled serial touchscreen
429 connected to your system.
433 To compile this driver as a module, choose M here: the
434 module will be called wacom_w8001.
436 config TOUCHSCREEN_WACOM_I2C
437 tristate "Wacom Tablet support (I2C)"
440 Say Y here if you want to use the I2C version of the Wacom
445 To compile this driver as a module, choose M here: the module
446 will be called wacom_i2c.
448 config TOUCHSCREEN_LPC32XX
449 tristate "LPC32XX touchscreen controller"
450 depends on ARCH_LPC32XX
452 Say Y here if you have a LPC32XX device and want
453 to support the built-in touchscreen.
455 To compile this driver as a module, choose M here: the
456 module will be called lpc32xx_ts.
458 config TOUCHSCREEN_MAX11801
459 tristate "MAX11801 based touchscreens"
462 Say Y here if you have a MAX11801 based touchscreen
467 To compile this driver as a module, choose M here: the
468 module will be called max11801_ts.
470 config TOUCHSCREEN_MCS5000
471 tristate "MELFAS MCS-5000 touchscreen"
474 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
479 To compile this driver as a module, choose M here: the
480 module will be called mcs5000_ts.
482 config TOUCHSCREEN_MMS114
483 tristate "MELFAS MMS114 touchscreen"
486 Say Y here if you have the MELFAS MMS114 touchscreen controller
491 To compile this driver as a module, choose M here: the
492 module will be called mms114.
494 config TOUCHSCREEN_MTOUCH
495 tristate "MicroTouch serial touchscreens"
498 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
503 To compile this driver as a module, choose M here: the
504 module will be called mtouch.
506 config TOUCHSCREEN_IMX6UL_TSC
507 tristate "Freescale i.MX6UL touchscreen controller"
508 depends on (OF && GPIOLIB) || COMPILE_TEST
510 Say Y here if you have a Freescale i.MX6UL, and want to
511 use the internal touchscreen controller.
515 To compile this driver as a module, choose M here: the
516 module will be called imx6ul_tsc.
518 config TOUCHSCREEN_INEXIO
519 tristate "iNexio serial touchscreens"
522 Say Y here if you have an iNexio serial touchscreen connected to
527 To compile this driver as a module, choose M here: the
528 module will be called inexio.
530 config TOUCHSCREEN_INTEL_MID
531 tristate "Intel MID platform resistive touchscreen"
532 depends on INTEL_SCU_IPC
534 Say Y here if you have a Intel MID based touchscreen in
539 To compile this driver as a module, choose M here: the
540 module will be called intel_mid_touch.
542 config TOUCHSCREEN_MK712
543 tristate "ICS MicroClock MK712 touchscreen"
545 Say Y here if you have the ICS MicroClock MK712 touchscreen
546 controller chip in your system.
550 To compile this driver as a module, choose M here: the
551 module will be called mk712.
553 config TOUCHSCREEN_HP600
554 tristate "HP Jornada 6xx touchscreen"
555 depends on SH_HP6XX && SH_ADC
557 Say Y here if you have a HP Jornada 620/660/680/690 and want to
558 support the built-in touchscreen.
560 To compile this driver as a module, choose M here: the
561 module will be called hp680_ts_input.
563 config TOUCHSCREEN_HP7XX
564 tristate "HP Jornada 7xx touchscreen"
565 depends on SA1100_JORNADA720_SSP
567 Say Y here if you have a HP Jornada 710/720/728 and want
568 to support the built-in touchscreen.
570 To compile this driver as a module, choose M here: the
571 module will be called jornada720_ts.
573 config TOUCHSCREEN_IPAQ_MICRO
574 tristate "HP iPAQ Atmel Micro ASIC touchscreen"
575 depends on MFD_IPAQ_MICRO
577 Say Y here to enable support for the touchscreen attached to
578 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
582 To compile this driver as a module, choose M here: the
583 module will be called ipaq-micro-ts.
585 config TOUCHSCREEN_HTCPEN
586 tristate "HTC Shift X9500 touchscreen"
589 Say Y here if you have an HTC Shift UMPC also known as HTC X9500
590 Clio / Shangrila and want to support the built-in touchscreen.
594 To compile this driver as a module, choose M here: the
595 module will be called htcpen.
597 config TOUCHSCREEN_PENMOUNT
598 tristate "Penmount serial touchscreen"
601 Say Y here if you have a Penmount serial touchscreen connected to
606 To compile this driver as a module, choose M here: the
607 module will be called penmount.
609 config TOUCHSCREEN_EDT_FT5X06
610 tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
613 Say Y here if you have an EDT "Polytouch" touchscreen based
614 on the FocalTech FT5x06 family of controllers connected to
619 To compile this driver as a module, choose M here: the
620 module will be called edt-ft5x06.
622 config TOUCHSCREEN_MIGOR
623 tristate "Renesas MIGO-R touchscreen"
624 depends on SH_MIGOR && I2C
626 Say Y here to enable MIGO-R touchscreen support.
630 To compile this driver as a module, choose M here: the
631 module will be called migor_ts.
633 config TOUCHSCREEN_TOUCHRIGHT
634 tristate "Touchright serial touchscreen"
637 Say Y here if you have a Touchright serial touchscreen connected to
642 To compile this driver as a module, choose M here: the
643 module will be called touchright.
645 config TOUCHSCREEN_TOUCHWIN
646 tristate "Touchwin serial touchscreen"
649 Say Y here if you have a Touchwin serial touchscreen connected to
654 To compile this driver as a module, choose M here: the
655 module will be called touchwin.
657 config TOUCHSCREEN_TI_AM335X_TSC
658 tristate "TI Touchscreen Interface"
659 depends on MFD_TI_AM335X_TSCADC
661 Say Y here if you have 4/5/8 wire touchscreen controller
662 to be connected to the ADC controller on your TI AM335x SoC.
666 To compile this driver as a module, choose M here: the
667 module will be called ti_am335x_tsc.
669 config TOUCHSCREEN_UCB1400
670 tristate "Philips UCB1400 touchscreen"
672 depends on UCB1400_CORE
674 This enables support for the Philips UCB1400 touchscreen interface.
675 The UCB1400 is an AC97 audio codec. The touchscreen interface
676 will be initialized only after the ALSA subsystem has been
677 brought up and the UCB1400 detected. You therefore have to
678 configure ALSA support as well (either built-in or modular,
679 independently of whether this driver is itself built-in or
680 modular) for this driver to work.
682 To compile this driver as a module, choose M here: the
683 module will be called ucb1400_ts.
685 config TOUCHSCREEN_PIXCIR
686 tristate "PIXCIR I2C touchscreens"
689 Say Y here if you have a pixcir i2c touchscreen
694 To compile this driver as a module, choose M here: the
695 module will be called pixcir_i2c_ts.
697 config TOUCHSCREEN_WDT87XX_I2C
698 tristate "Weida HiTech I2C touchscreen"
701 Say Y here if you have a Weida WDT87XX I2C touchscreen
702 connected to your system.
706 To compile this driver as a module, choose M here: the
707 module will be called wdt87xx_i2c.
709 config TOUCHSCREEN_WM831X
710 tristate "Support for WM831x touchscreen controllers"
711 depends on MFD_WM831X
713 This enables support for the touchscreen controller on the WM831x
716 To compile this driver as a module, choose M here: the
717 module will be called wm831x-ts.
719 config TOUCHSCREEN_WM97XX
720 tristate "Support for WM97xx AC97 touchscreen controllers"
723 Say Y here if you have a Wolfson Microelectronics WM97xx
724 touchscreen connected to your system. Note that this option
725 only enables core driver, you will also need to select
726 support for appropriate chip below.
730 To compile this driver as a module, choose M here: the
731 module will be called wm97xx-ts.
733 config TOUCHSCREEN_WM9705
734 bool "WM9705 Touchscreen interface support"
735 depends on TOUCHSCREEN_WM97XX
738 Say Y here to enable support for the Wolfson Microelectronics
739 WM9705 touchscreen controller.
741 config TOUCHSCREEN_WM9712
742 bool "WM9712 Touchscreen interface support"
743 depends on TOUCHSCREEN_WM97XX
746 Say Y here to enable support for the Wolfson Microelectronics
747 WM9712 touchscreen controller.
749 config TOUCHSCREEN_WM9713
750 bool "WM9713 Touchscreen interface support"
751 depends on TOUCHSCREEN_WM97XX
754 Say Y here to enable support for the Wolfson Microelectronics
755 WM9713 touchscreen controller.
757 config TOUCHSCREEN_WM97XX_ATMEL
758 tristate "WM97xx Atmel accelerated touch"
759 depends on TOUCHSCREEN_WM97XX && AVR32
761 Say Y here for support for streaming mode with WM97xx touchscreens
762 on Atmel AT91 or AVR32 systems with an AC97C module.
764 Be aware that this will use channel B in the controller for
765 streaming data, this must not conflict with other AC97C drivers.
769 To compile this driver as a module, choose M here: the module will
770 be called atmel-wm97xx.
772 config TOUCHSCREEN_WM97XX_MAINSTONE
773 tristate "WM97xx Mainstone/Palm accelerated touch"
774 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
776 Say Y here for support for streaming mode with WM97xx touchscreens
777 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
781 To compile this driver as a module, choose M here: the
782 module will be called mainstone-wm97xx.
784 config TOUCHSCREEN_WM97XX_ZYLONITE
785 tristate "Zylonite accelerated touch"
786 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
787 select TOUCHSCREEN_WM9713
789 Say Y here for support for streaming mode with the touchscreen
794 To compile this driver as a module, choose M here: the
795 module will be called zylonite-wm97xx.
797 config TOUCHSCREEN_USB_COMPOSITE
798 tristate "USB Touchscreen Driver"
799 depends on USB_ARCH_HAS_HCD
802 USB Touchscreen driver for:
803 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
804 - PanJit TouchSet USB
805 - 3M MicroTouch USB (EX II series)
807 - some other eTurboTouch
810 - IRTOUCHSYSTEMS/UNITOP
812 - GoTop Super_Q2/GogoPen/PenPower tablets
813 - JASTEC USB Touch Controller/DigiTech DTR-02U
814 - Zytronic controllers
815 - Elo TouchSystems 2700 IntelliTouch
816 - EasyTouch USB Touch Controller from Data Modul
817 - e2i (Mimo monitors)
819 Have a look at <http://linux.chapter7.ch/touchkit/> for
820 a usage description and the required user-space stuff.
822 To compile this driver as a module, choose M here: the
823 module will be called usbtouchscreen.
825 config TOUCHSCREEN_MC13783
826 tristate "Freescale MC13783 touchscreen input driver"
827 depends on MFD_MC13XXX
829 Say Y here if you have an Freescale MC13783 PMIC on your
830 board and want to use its touchscreen
834 To compile this driver as a module, choose M here: the
835 module will be called mc13783_ts.
837 config TOUCHSCREEN_USB_EGALAX
839 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
840 depends on TOUCHSCREEN_USB_COMPOSITE
842 config TOUCHSCREEN_USB_PANJIT
844 bool "PanJit device support" if EXPERT
845 depends on TOUCHSCREEN_USB_COMPOSITE
847 config TOUCHSCREEN_USB_3M
849 bool "3M/Microtouch EX II series device support" if EXPERT
850 depends on TOUCHSCREEN_USB_COMPOSITE
852 config TOUCHSCREEN_USB_ITM
854 bool "ITM device support" if EXPERT
855 depends on TOUCHSCREEN_USB_COMPOSITE
857 config TOUCHSCREEN_USB_ETURBO
859 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
860 depends on TOUCHSCREEN_USB_COMPOSITE
862 config TOUCHSCREEN_USB_GUNZE
864 bool "Gunze AHL61 device support" if EXPERT
865 depends on TOUCHSCREEN_USB_COMPOSITE
867 config TOUCHSCREEN_USB_DMC_TSC10
869 bool "DMC TSC-10/25 device support" if EXPERT
870 depends on TOUCHSCREEN_USB_COMPOSITE
872 config TOUCHSCREEN_USB_IRTOUCH
874 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
875 depends on TOUCHSCREEN_USB_COMPOSITE
877 config TOUCHSCREEN_USB_IDEALTEK
879 bool "IdealTEK URTC1000 device support" if EXPERT
880 depends on TOUCHSCREEN_USB_COMPOSITE
882 config TOUCHSCREEN_USB_GENERAL_TOUCH
884 bool "GeneralTouch Touchscreen device support" if EXPERT
885 depends on TOUCHSCREEN_USB_COMPOSITE
887 config TOUCHSCREEN_USB_GOTOP
889 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
890 depends on TOUCHSCREEN_USB_COMPOSITE
892 config TOUCHSCREEN_USB_JASTEC
894 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
895 depends on TOUCHSCREEN_USB_COMPOSITE
897 config TOUCHSCREEN_USB_ELO
899 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
900 depends on TOUCHSCREEN_USB_COMPOSITE
902 config TOUCHSCREEN_USB_E2I
904 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
905 depends on TOUCHSCREEN_USB_COMPOSITE
907 config TOUCHSCREEN_USB_ZYTRONIC
909 bool "Zytronic controller" if EXPERT
910 depends on TOUCHSCREEN_USB_COMPOSITE
912 config TOUCHSCREEN_USB_ETT_TC45USB
914 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
915 depends on TOUCHSCREEN_USB_COMPOSITE
917 config TOUCHSCREEN_USB_NEXIO
919 bool "NEXIO/iNexio device support" if EXPERT
920 depends on TOUCHSCREEN_USB_COMPOSITE
922 config TOUCHSCREEN_USB_EASYTOUCH
924 bool "EasyTouch USB Touch controller device support" if EMBEDDED
925 depends on TOUCHSCREEN_USB_COMPOSITE
927 Say Y here if you have an EasyTouch USB Touch controller.
930 config TOUCHSCREEN_TOUCHIT213
931 tristate "Sahara TouchIT-213 touchscreen"
934 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
938 To compile this driver as a module, choose M here: the
939 module will be called touchit213.
941 config TOUCHSCREEN_TS4800
942 tristate "TS-4800 touchscreen"
943 depends on HAS_IOMEM && OF
947 Say Y here if you have a touchscreen on a TS-4800 board.
949 On TS-4800, the touchscreen is not handled directly by Linux but by
954 To compile this driver as a module, choose M here: the
955 module will be called ts4800_ts.
957 config TOUCHSCREEN_TSC_SERIO
958 tristate "TSC-10/25/40 serial touchscreen support"
961 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
966 To compile this driver as a module, choose M here: the
967 module will be called tsc40.
969 config TOUCHSCREEN_TSC200X_CORE
972 config TOUCHSCREEN_TSC2004
973 tristate "TSC2004 based touchscreens"
976 select TOUCHSCREEN_TSC200X_CORE
978 Say Y here if you have a TSC2004 based touchscreen.
982 To compile this driver as a module, choose M here: the
983 module will be called tsc2004.
985 config TOUCHSCREEN_TSC2005
986 tristate "TSC2005 based touchscreens"
987 depends on SPI_MASTER
989 select TOUCHSCREEN_TSC200X_CORE
991 Say Y here if you have a TSC2005 based touchscreen.
995 To compile this driver as a module, choose M here: the
996 module will be called tsc2005.
998 config TOUCHSCREEN_TSC2007
999 tristate "TSC2007 based touchscreens"
1002 Say Y here if you have a TSC2007 based touchscreen.
1006 To compile this driver as a module, choose M here: the
1007 module will be called tsc2007.
1009 config TOUCHSCREEN_W90X900
1010 tristate "W90P910 touchscreen driver"
1011 depends on ARCH_W90X900
1013 Say Y here if you have a W90P910 based touchscreen.
1015 To compile this driver as a module, choose M here: the
1016 module will be called w90p910_ts.
1018 config TOUCHSCREEN_PCAP
1019 tristate "Motorola PCAP touchscreen"
1022 Say Y here if you have a Motorola EZX telephone and
1023 want to enable support for the built-in touchscreen.
1025 To compile this driver as a module, choose M here: the
1026 module will be called pcap_ts.
1028 config TOUCHSCREEN_ST1232
1029 tristate "Sitronix ST1232 touchscreen controllers"
1032 Say Y here if you want to support Sitronix ST1232
1033 touchscreen controller.
1037 To compile this driver as a module, choose M here: the
1038 module will be called st1232_ts.
1040 config TOUCHSCREEN_STMPE
1041 tristate "STMicroelectronics STMPE touchscreens"
1042 depends on MFD_STMPE
1043 depends on (OF || COMPILE_TEST)
1045 Say Y here if you want support for STMicroelectronics
1046 STMPE touchscreen controllers.
1048 To compile this driver as a module, choose M here: the
1049 module will be called stmpe-ts.
1051 config TOUCHSCREEN_SUN4I
1052 tristate "Allwinner sun4i resistive touchscreen controller support"
1053 depends on ARCH_SUNXI || COMPILE_TEST
1055 depends on THERMAL || !THERMAL_OF
1057 This selects support for the resistive touchscreen controller
1058 found on Allwinner sunxi SoCs.
1060 To compile this driver as a module, choose M here: the
1061 module will be called sun4i-ts.
1063 config TOUCHSCREEN_SUR40
1064 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
1065 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1066 depends on VIDEO_V4L2
1067 select INPUT_POLLDEV
1068 select VIDEOBUF2_DMA_SG
1070 Say Y here if you want support for the Samsung SUR40 touchscreen
1071 (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
1073 To compile this driver as a module, choose M here: the
1074 module will be called sur40.
1076 config TOUCHSCREEN_SX8654
1077 tristate "Semtech SX8654 touchscreen"
1080 Say Y here if you have a Semtech SX8654 touchscreen controller.
1084 To compile this driver as a module, choose M here: the
1085 module will be called sx8654.
1087 config TOUCHSCREEN_TPS6507X
1088 tristate "TPS6507x based touchscreens"
1090 select INPUT_POLLDEV
1092 Say Y here if you have a TPS6507x based touchscreen
1097 To compile this driver as a module, choose M here: the
1098 module will be called tps6507x_ts.
1100 config TOUCHSCREEN_ZFORCE
1101 tristate "Neonode zForce infrared touchscreens"
1103 depends on GPIOLIB || COMPILE_TEST
1105 Say Y here if you have a touchscreen using the zforce
1106 infraread technology from Neonode.
1110 To compile this driver as a module, choose M here: the
1111 module will be called zforce_ts.
1113 config TOUCHSCREEN_COLIBRI_VF50
1114 tristate "Toradex Colibri on board touchscreen driver"
1115 depends on IIO && VF610_ADC
1116 depends on GPIOLIB || COMPILE_TEST
1118 Say Y here if you have a Colibri VF50 and plan to use
1119 the on-board provided 4-wire touchscreen driver.
1123 To compile this driver as a module, choose M here: the
1124 module will be called colibri_vf50_ts.
1126 config TOUCHSCREEN_ROHM_BU21023
1127 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
1130 Say Y here if you have a touchscreen using ROHM BU21023/24.
1134 To compile this driver as a module, choose M here: the
1135 module will be called bu21023_ts.