Lines Matching +full:system +full:- +full:on +full:- +full:a +full:- +full:chip
1 # SPDX-License-Identifier: GPL-2.0-only
8 Say Y here, and a list of supported touchscreens will be displayed.
17 depends on MFD_88PM860X
19 Say Y here if you have a 88PM860x PMIC and want to enable
20 support for the built-in touchscreen.
24 To compile this driver as a module, choose M here: the
25 module will be called 88pm860x-ts.
29 depends on SPI_MASTER
30 depends on HWMON = n || HWMON
32 Say Y here if you have a touchscreen interface using the
34 and your board-specific setup code includes that in its
38 on your board, you will also get hwmon interfaces for the voltage
39 (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
43 To compile this driver as a module, choose M here: the
48 depends on SPI_MASTER
50 Say Y here if you have a touchscreen interface using the
51 AD7877 controller, and your board-specific initialization
56 To compile this driver as a module, choose M here: the
60 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
62 Say Y here if you want to support a touchscreen interface using
63 the AD7879-1/AD7889-1 controller.
65 You should select a bus connection too.
67 To compile this driver as a module, choose M here: the
72 depends on TOUCHSCREEN_AD7879 && I2C
75 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
77 To compile this driver as a module, choose M here: the
78 module will be called ad7879-i2c.
82 depends on TOUCHSCREEN_AD7879 && SPI_MASTER
85 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
89 To compile this driver as a module, choose M here: the
90 module will be called ad7879-spi.
94 depends on IIO
103 To compile this driver as a module, choose M here: the
104 module will be called resistive-adc-touch.ko.
108 depends on I2C && OF
111 controller chip in your system.
115 To compile this driver as a module, choose M here: the
120 depends on I2C
124 such as AT42QT602240/ATMXT224, connected to your system.
128 To compile this driver as a module, choose M here: the
133 depends on TOUCHSCREEN_ATMEL_MXT
134 depends on VIDEO_V4L2=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_V4L2=m)
138 Diagnostic Data object using a V4L device.
141 tristate "AUO in-cell touchscreen using Pixcir ICs"
142 depends on I2C
143 depends on GPIOLIB || COMPILE_TEST
145 Say Y here if you have a AUO display with in-cell touchscreen
150 To compile this driver as a module, choose M here: the
151 module will be called auo-pixcir-ts.
155 depends on I2C
157 Say Y here if you have a bu21013 touchscreen connected to
158 your system.
162 To compile this driver as a module, choose M here: the
167 depends on I2C
169 Say Y here if you have a Rohm BU21029 touchscreen controller
170 connected to your system.
174 To compile this driver as a module, choose M here: the
179 depends on GPIOLIB || COMPILE_TEST
180 depends on I2C
181 depends on OF
183 Say Y here if you have a ChipOne icn8318 based I2C touchscreen.
187 To compile this driver as a module, choose M here: the
192 depends on I2C && ACPI
194 Say Y here if you have a ChipOne icn8505 based I2C touchscreen.
198 To compile this driver as a module, choose M here: the
203 depends on I2C
205 Say Y here if you have a Cypress CY8CTMA140 capacitive
210 To compile this driver as a module, choose M here: the
215 depends on I2C
216 depends on GPIOLIB || COMPILE_TEST
218 Say Y here if you have a cy8ctmg110 capacitive touchscreen on
223 To compile this driver as a module, choose M here: the
229 Say Y here if you have a touchscreen using controller from
231 to your system. You will also need to select appropriate
236 To compile this driver as a module, choose M here: the
241 depends on TOUCHSCREEN_CYTTSP_CORE && I2C
245 To compile this driver as a module, choose M here: the
250 depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
254 To compile this driver as a module, choose M here: the
263 Say Y here if you have a Cypress Gen4 touchscreen.
267 To compile this driver as a module, choose M here.
271 depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
275 To compile this driver as a module, choose M here: the
280 depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
284 To compile this driver as a module, choose M here: the
289 depends on PMIC_DA903X
293 on Dialog Semiconductor DA9034 PMIC.
297 To compile this driver as a module, choose M here: the
298 module will be called da9034-ts.
302 depends on PMIC_DA9052
304 Say Y here to support the touchscreen found on Dialog Semiconductor
305 DA9052-BC and DA9053-AA/Bx PMICs.
309 To compile this driver as a module, choose M here: the
316 Say Y here if you have a Dynapro serial touchscreen connected to
317 your system.
321 To compile this driver as a module, choose M here: the
328 Say Y here if you have a Hampshire serial touchscreen connected to
329 your system.
333 To compile this driver as a module, choose M here: the
338 depends on I2C
342 To compile this driver as a module, choose M here: the
346 tristate "EETI eGalax multi-touch panel support"
347 depends on I2C && OF
350 eGalax multi-touch panels.
352 To compile this driver as a module, choose M here: the
362 To compile this driver as a module, choose M here: the
366 tristate "EETI EXC3000 multi-touch panel support"
367 depends on I2C
370 EXC3000 multi-touch panels.
372 To compile this driver as a module, choose M here: the
381 system.
385 To compile this driver as a module, choose M here: the
386 module will be called fujitsu-ts.
390 depends on I2C
391 depends on GPIOLIB || COMPILE_TEST
395 system. It also supports 5-finger chip models, which can be
396 found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
400 To compile this driver as a module, choose M here: the
405 depends on I2C
407 Say Y here if you have a touchscreen using HiDeep.
411 To compile this driver as a module, choose M here : the
416 depends on I2C
418 Say Y here if you have a touchscreen using Hycon hy46xx
422 To compile this driver as a module, choose M here: the
423 module will be called hycon-hy46xx.
427 depends on I2C
429 Say Y here if you have a ILI210X based touchscreen
437 To compile this driver as a module, choose M here: the
442 depends on I2C
449 To compile this driver as a module, choose M here: the
454 depends on ARCH_BCM_IPROC || COMPILE_TEST
457 controller to your system.
461 To compile this driver as a module, choose M here: the
466 depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
467 depends on S3C_ADC
473 To compile this driver as a module, choose M here: the
478 depends on I2C
488 tristate "Gunze AHL-51S touchscreen"
491 Say Y here if you have the Gunze AHL-51 touchscreen connected to
492 your system.
496 To compile this driver as a module, choose M here: the
501 depends on I2C
504 connected to your system.
508 To compile this driver as a module, choose M here: the
513 depends on I2C
516 connected to your system.
520 To compile this driver as a module, choose M here: the
528 your system.
532 To compile this driver as a module, choose M here: the
540 connected to your system.
544 To compile this driver as a module, choose M here: the
549 depends on I2C
556 To compile this driver as a module, choose M here: the module
561 depends on ARCH_LPC32XX
563 Say Y here if you have a LPC32XX device and want
564 to support the built-in touchscreen.
566 To compile this driver as a module, choose M here: the
571 depends on I2C
573 Say Y here if you have a MAX11801 based touchscreen
578 To compile this driver as a module, choose M here: the
582 tristate "MELFAS MCS-5000 touchscreen"
583 depends on I2C
585 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
586 chip in your system.
590 To compile this driver as a module, choose M here: the
595 depends on I2C
598 chip in your system.
602 To compile this driver as a module, choose M here: the
607 depends on I2C
609 Say Y here if you have a MELFAS MIP4 Touchscreen device.
613 To compile this driver as a module, choose M here:
618 depends on I2C
619 depends on GPIOLIB || COMPILE_TEST
625 To compile this driver as a module, choose M here: the
632 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
633 your system.
637 To compile this driver as a module, choose M here: the
642 depends on ((OF && GPIOLIB) || COMPILE_TEST) && HAS_IOMEM
644 Say Y here if you have a Freescale i.MX6UL, and want to
649 To compile this driver as a module, choose M here: the
657 your system.
661 To compile this driver as a module, choose M here: the
668 controller chip in your system.
672 To compile this driver as a module, choose M here: the
677 depends on SH_HP6XX && SH_ADC
679 Say Y here if you have a HP Jornada 620/660/680/690 and want to
680 support the built-in touchscreen.
682 To compile this driver as a module, choose M here: the
687 depends on SA1100_JORNADA720_SSP
689 Say Y here if you have a HP Jornada 710/720/728 and want
690 to support the built-in touchscreen.
692 To compile this driver as a module, choose M here: the
697 depends on MFD_IPAQ_MICRO
700 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
704 To compile this driver as a module, choose M here: the
705 module will be called ipaq-micro-ts.
709 depends on ISA
712 Clio / Shangrila and want to support the built-in touchscreen.
716 To compile this driver as a module, choose M here: the
723 Say Y here if you have a Penmount serial touchscreen connected to
724 your system.
728 To compile this driver as a module, choose M here: the
733 depends on I2C
736 on the FocalTech FT5x06 family of controllers connected to
737 your system.
741 To compile this driver as a module, choose M here: the
742 module will be called edt-ft5x06.
746 depends on RASPBERRYPI_FIRMWARE || (RASPBERRYPI_FIRMWARE=n && COMPILE_TEST)
748 Say Y here if you have the official Raspberry Pi 7 inch screen on
749 your system.
753 To compile this driver as a module, choose M here: the
754 module will be called raspberrypi-ts.
757 tristate "Renesas MIGO-R touchscreen"
758 depends on (SH_MIGOR || COMPILE_TEST) && I2C
760 Say Y here to enable MIGO-R touchscreen support.
764 To compile this driver as a module, choose M here: the
771 Say Y here if you have a Touchright serial touchscreen connected to
772 your system.
776 To compile this driver as a module, choose M here: the
783 Say Y here if you have a Touchwin serial touchscreen connected to
784 your system.
788 To compile this driver as a module, choose M here: the
793 depends on MFD_TI_AM335X_TSCADC
796 to be connected to the ADC controller on your TI AM335x SoC.
800 To compile this driver as a module, choose M here: the
805 depends on AC97_BUS
806 depends on UCB1400_CORE
812 configure ALSA support as well (either built-in or modular,
813 independently of whether this driver is itself built-in or
816 To compile this driver as a module, choose M here: the
821 depends on I2C
823 Say Y here if you have a pixcir i2c touchscreen
828 To compile this driver as a module, choose M here: the
833 depends on I2C
835 Say Y here if you have a Weida WDT87XX I2C touchscreen
836 connected to your system.
840 To compile this driver as a module, choose M here: the
845 depends on MFD_WM831X
847 This enables support for the touchscreen controller on the WM831x
850 To compile this driver as a module, choose M here: the
851 module will be called wm831x-ts.
855 depends on AC97_BUS || AC97_BUS_NEW
857 Say Y here if you have a Wolfson Microelectronics WM97xx
858 touchscreen connected to your system. Note that this option
860 support for appropriate chip below.
864 To compile this driver as a module, choose M here: the
865 module will be called wm97xx-ts.
869 depends on TOUCHSCREEN_WM97XX
877 depends on TOUCHSCREEN_WM97XX
885 depends on TOUCHSCREEN_WM97XX
893 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
896 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
900 To compile this driver as a module, choose M here: the
901 module will be called mainstone-wm97xx.
905 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
909 on Zylonite systems.
913 To compile this driver as a module, choose M here: the
914 module will be called zylonite-wm97xx.
918 depends on USB_ARCH_HAS_HCD
922 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
923 - PanJit TouchSet USB
924 - 3M MicroTouch USB (EX II series)
925 - ITM
926 - some other eTurboTouch
927 - Gunze AHL61
928 - DMC TSC-10/25
929 - IRTOUCHSYSTEMS/UNITOP
930 - IdealTEK URTC1000
931 - GoTop Super_Q2/GogoPen/PenPower tablets
932 - JASTEC USB Touch Controller/DigiTech DTR-02U
933 - Zytronic controllers
934 - Elo TouchSystems 2700 IntelliTouch
935 - EasyTouch USB Touch Controller from Data Module
936 - e2i (Mimo monitors)
938 Have a look at <http://linux.chapter7.ch/touchkit/> for
939 a usage description and the required user-space stuff.
941 To compile this driver as a module, choose M here: the
946 depends on MFD_MXS_LRADC
948 Say Y here if you have a touchscreen connected to the low-resolution
949 analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor.
951 To compile this driver as a module, choose M here: the module will be
952 called mxs-lradc-ts.
956 depends on MFD_MX25_TSADC
960 To compile this driver as a module, choose M here: the
961 module will be called fsl-imx25-tcq.
965 depends on MFD_MC13XXX
967 Say Y here if you have an Freescale MC13783 PMIC on your
972 To compile this driver as a module, choose M here: the
977 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
978 depends on TOUCHSCREEN_USB_COMPOSITE
983 depends on TOUCHSCREEN_USB_COMPOSITE
988 depends on TOUCHSCREEN_USB_COMPOSITE
993 depends on TOUCHSCREEN_USB_COMPOSITE
997 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
998 depends on TOUCHSCREEN_USB_COMPOSITE
1003 depends on TOUCHSCREEN_USB_COMPOSITE
1007 bool "DMC TSC-10/25 device support" if EXPERT
1008 depends on TOUCHSCREEN_USB_COMPOSITE
1013 depends on TOUCHSCREEN_USB_COMPOSITE
1018 depends on TOUCHSCREEN_USB_COMPOSITE
1023 depends on TOUCHSCREEN_USB_COMPOSITE
1028 depends on TOUCHSCREEN_USB_COMPOSITE
1032 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
1033 depends on TOUCHSCREEN_USB_COMPOSITE
1038 depends on TOUCHSCREEN_USB_COMPOSITE
1043 depends on TOUCHSCREEN_USB_COMPOSITE
1048 depends on TOUCHSCREEN_USB_COMPOSITE
1053 depends on TOUCHSCREEN_USB_COMPOSITE
1058 depends on TOUCHSCREEN_USB_COMPOSITE
1063 depends on TOUCHSCREEN_USB_COMPOSITE
1069 tristate "Sahara TouchIT-213 touchscreen"
1072 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
1076 To compile this driver as a module, choose M here: the
1080 tristate "TS-4800 touchscreen"
1081 depends on HAS_IOMEM && OF
1082 depends on SOC_IMX51 || COMPILE_TEST
1085 Say Y here if you have a touchscreen on a TS-4800 board.
1087 On TS-4800, the touchscreen is not handled directly by Linux but by
1088 a companion FPGA.
1092 To compile this driver as a module, choose M here: the
1096 tristate "TSC-10/25/40 serial touchscreen support"
1099 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
1100 to your system.
1104 To compile this driver as a module, choose M here: the
1112 depends on I2C
1116 Say Y here if you have a TSC2004 based touchscreen.
1120 To compile this driver as a module, choose M here: the
1125 depends on SPI_MASTER
1129 Say Y here if you have a TSC2005 based touchscreen.
1133 To compile this driver as a module, choose M here: the
1138 depends on I2C
1140 Say Y here if you have a TSC2007 based touchscreen.
1144 To compile this driver as a module, choose M here: the
1149 depends on TOUCHSCREEN_TSC2007
1150 depends on IIO=y || IIO=TOUCHSCREEN_TSC2007
1159 depends on EZX_PCAP
1161 Say Y here if you have a Motorola EZX telephone and
1162 want to enable support for the built-in touchscreen.
1164 To compile this driver as a module, choose M here: the
1169 depends on I2C
1170 depends on GPIOLIB || COMPILE_TEST
1173 such as RM32380, connected to your system.
1177 To compile this driver as a module, choose M here: the
1182 depends on I2C
1185 your system.
1189 To compile this driver as a module, choose M here: the
1194 depends on I2C
1196 depends on GPIOLIB || COMPILE_TEST
1202 To compile this driver as a module, choose M here: the
1207 depends on I2C
1214 To compile this driver as a module, choose M here: the
1219 depends on I2C
1220 depends on LEDS_CLASS
1225 To compile this driver as a module, choose M here: the
1230 depends on MFD_STMPE
1231 depends on (OF || COMPILE_TEST)
1236 To compile this driver as a module, choose M here: the
1237 module will be called stmpe-ts.
1241 depends on ARCH_SUNXI || COMPILE_TEST
1242 depends on HWMON
1243 depends on THERMAL || !THERMAL_OF
1246 found on Allwinner sunxi SoCs.
1248 To compile this driver as a module, choose M here: the
1249 module will be called sun4i-ts.
1253 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1254 depends on VIDEO_V4L2
1260 To compile this driver as a module, choose M here: the
1265 depends on SPI
1266 depends on GPIOLIB || COMPILE_TEST
1269 controller chip as found on the Surface 3 in your system.
1273 To compile this driver as a module, choose M here: the
1278 depends on I2C
1280 Say Y here if you have a Semtech SX8654 touchscreen controller.
1284 To compile this driver as a module, choose M here: the
1289 depends on I2C
1291 Say Y here if you have a TPS6507x based touchscreen
1296 To compile this driver as a module, choose M here: the
1301 depends on I2C
1303 Say Y here if you have a touchscreen using Zeitec ZET6223
1307 To compile this driver as a module, choose M here: the
1312 depends on I2C
1313 depends on GPIOLIB || COMPILE_TEST
1315 Say Y here if you have a touchscreen using the zforce
1320 To compile this driver as a module, choose M here: the
1324 tristate "Toradex Colibri on board touchscreen driver"
1325 depends on IIO && VF610_ADC
1326 depends on GPIOLIB || COMPILE_TEST
1328 Say Y here if you have a Colibri VF50 and plan to use
1329 the on-board provided 4-wire touchscreen driver.
1333 To compile this driver as a module, choose M here: the
1338 depends on I2C
1340 Say Y here if you have a touchscreen using ROHM BU21023/24.
1344 To compile this driver as a module, choose M here: the
1349 depends on I2C
1354 To compile this driver as a module, choose M here: the
1359 depends on I2C
1361 Say Y here if you have a touchscreen using Zinitix bt541,
1366 To compile this driver as a module, choose M here: the