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_DEV=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_DEV=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
259 depends on I2C
266 Say Y here if you have a Cypress Gen5 touchscreen.
270 To compile this driver as a module, choose M here: the
275 depends on PMIC_DA903X
279 on Dialog Semiconductor DA9034 PMIC.
283 To compile this driver as a module, choose M here: the
284 module will be called da9034-ts.
288 depends on PMIC_DA9052
290 Say Y here to support the touchscreen found on Dialog Semiconductor
291 DA9052-BC and DA9053-AA/Bx PMICs.
295 To compile this driver as a module, choose M here: the
302 Say Y here if you have a Dynapro serial touchscreen connected to
303 your system.
307 To compile this driver as a module, choose M here: the
314 Say Y here if you have a Hampshire serial touchscreen connected to
315 your system.
319 To compile this driver as a module, choose M here: the
324 depends on I2C
328 To compile this driver as a module, choose M here: the
332 tristate "EETI eGalax multi-touch panel support"
333 depends on I2C && OF
336 eGalax multi-touch panels.
338 To compile this driver as a module, choose M here: the
348 To compile this driver as a module, choose M here: the
352 tristate "EETI EXC3000 multi-touch panel support"
353 depends on I2C
356 EXC3000 multi-touch panels.
358 To compile this driver as a module, choose M here: the
367 system.
371 To compile this driver as a module, choose M here: the
372 module will be called fujitsu-ts.
376 depends on I2C
377 depends on GPIOLIB || COMPILE_TEST
381 system. It also supports 5-finger chip models, which can be
382 found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
386 To compile this driver as a module, choose M here: the
394 depends on I2C
398 Say Y here if you have a Goodix Berlin IC connected to
399 your system via I2C.
403 To compile this driver as a module, choose M here: the
408 depends on SPI_MASTER
412 Say Y here if you have a Goodix Berlin IC connected to
413 your system via SPI.
417 To compile this driver as a module, choose M here: the
422 depends on I2C
425 Say Y here if you have a touchscreen using HiDeep.
429 To compile this driver as a module, choose M here : the
434 depends on I2C
437 Say Y here if you have a touchscreen using Hycon hy46xx
441 To compile this driver as a module, choose M here: the
442 module will be called hycon-hy46xx.
446 depends on I2C
448 Say Y here if you have a touchscreen using a Hynitron
453 To compile this driver as a module, choose M here: the
454 module will be called hynitron-cstxxx.
458 depends on I2C
461 Say Y here if you have a ILI210X based touchscreen
469 To compile this driver as a module, choose M here: the
474 depends on I2C
481 To compile this driver as a module, choose M here: the
486 depends on ARCH_BCM_IPROC || COMPILE_TEST
489 controller to your system.
493 To compile this driver as a module, choose M here: the
498 depends on I2C
508 tristate "Gunze AHL-51S touchscreen"
511 Say Y here if you have the Gunze AHL-51 touchscreen connected to
512 your system.
516 To compile this driver as a module, choose M here: the
521 depends on I2C
524 connected to your system.
528 To compile this driver as a module, choose M here: the
533 depends on I2C
536 connected to your system.
540 To compile this driver as a module, choose M here: the
548 your system.
552 To compile this driver as a module, choose M here: the
560 connected to your system.
564 To compile this driver as a module, choose M here: the
569 depends on I2C
576 To compile this driver as a module, choose M here: the module
581 depends on ARCH_LPC32XX
583 Say Y here if you have a LPC32XX device and want
584 to support the built-in touchscreen.
586 To compile this driver as a module, choose M here: the
591 depends on I2C
593 Say Y here if you have a MAX11801 based touchscreen
598 To compile this driver as a module, choose M here: the
603 depends on I2C
606 chip in your system.
610 To compile this driver as a module, choose M here: the
615 depends on I2C
617 Say Y here if you have a MELFAS MIP4 Touchscreen device.
621 To compile this driver as a module, choose M here:
626 depends on I2C
627 depends on GPIOLIB || COMPILE_TEST
633 To compile this driver as a module, choose M here: the
640 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
641 your system.
645 To compile this driver as a module, choose M here: the
650 depends on I2C
652 Say Y here if you have a Novatek NT11205 touchscreen.
655 To compile this driver as a module, choose M here: the
656 module will be called novatek-nvt-ts.
660 depends on I2C
665 To compile this driver as a module, choose M here: the
670 depends on ((OF && GPIOLIB) || COMPILE_TEST) && HAS_IOMEM
672 Say Y here if you have a Freescale i.MX6UL, and want to
677 To compile this driver as a module, choose M here: the
685 your system.
689 To compile this driver as a module, choose M here: the
694 depends on ISA
697 controller chip in your system.
701 To compile this driver as a module, choose M here: the
706 depends on SH_HP6XX && SH_ADC
708 Say Y here if you have a HP Jornada 620/660/680/690 and want to
709 support the built-in touchscreen.
711 To compile this driver as a module, choose M here: the
716 depends on SA1100_JORNADA720_SSP
718 Say Y here if you have a HP Jornada 710/720/728 and want
719 to support the built-in touchscreen.
721 To compile this driver as a module, choose M here: the
726 depends on MFD_IPAQ_MICRO
729 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
733 To compile this driver as a module, choose M here: the
734 module will be called ipaq-micro-ts.
738 depends on ISA
741 Clio / Shangrila and want to support the built-in touchscreen.
745 To compile this driver as a module, choose M here: the
752 Say Y here if you have a Penmount serial touchscreen connected to
753 your system.
757 To compile this driver as a module, choose M here: the
762 depends on I2C
766 on the FocalTech FT5x06 family of controllers connected to
767 your system.
771 To compile this driver as a module, choose M here: the
772 module will be called edt-ft5x06.
776 depends on RASPBERRYPI_FIRMWARE || (RASPBERRYPI_FIRMWARE=n && COMPILE_TEST)
778 Say Y here if you have the official Raspberry Pi 7 inch screen on
779 your system.
783 To compile this driver as a module, choose M here: the
784 module will be called raspberrypi-ts.
787 tristate "Renesas MIGO-R touchscreen"
788 depends on (SH_MIGOR || COMPILE_TEST) && I2C
790 Say Y here to enable MIGO-R touchscreen support.
794 To compile this driver as a module, choose M here: the
801 Say Y here if you have a Touchright serial touchscreen connected to
802 your system.
806 To compile this driver as a module, choose M here: the
813 Say Y here if you have a Touchwin serial touchscreen connected to
814 your system.
818 To compile this driver as a module, choose M here: the
823 depends on MFD_TI_AM335X_TSCADC
826 to be connected to the ADC controller on your TI AM335x SoC.
830 To compile this driver as a module, choose M here: the
835 depends on I2C
837 Say Y here if you have a pixcir i2c touchscreen
842 To compile this driver as a module, choose M here: the
847 depends on I2C
849 Say Y here if you have a Weida WDT87XX I2C touchscreen
850 connected to your system.
854 To compile this driver as a module, choose M here: the
859 depends on MFD_WM831X
861 This enables support for the touchscreen controller on the WM831x
864 To compile this driver as a module, choose M here: the
865 module will be called wm831x-ts.
869 depends on AC97_BUS || AC97_BUS_NEW
871 Say Y here if you have a Wolfson Microelectronics WM97xx
872 touchscreen connected to your system. Note that this option
874 support for appropriate chip below.
878 To compile this driver as a module, choose M here: the
879 module will be called wm97xx-ts.
883 depends on TOUCHSCREEN_WM97XX
891 depends on TOUCHSCREEN_WM97XX
899 depends on TOUCHSCREEN_WM97XX
907 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
908 depends on SND_PXA2XX_LIB_AC97
911 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
915 To compile this driver as a module, choose M here: the
916 module will be called mainstone-wm97xx.
920 depends on USB_ARCH_HAS_HCD
924 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
925 - PanJit TouchSet USB
926 - 3M MicroTouch USB (EX II series)
927 - ITM
928 - some other eTurboTouch
929 - Gunze AHL61
930 - DMC TSC-10/25
931 - IRTOUCHSYSTEMS/UNITOP
932 - IdealTEK URTC1000
933 - GoTop Super_Q2/GogoPen/PenPower tablets
934 - JASTEC USB Touch Controller/DigiTech DTR-02U
935 - Zytronic controllers
936 - Elo TouchSystems 2700 IntelliTouch
937 - EasyTouch USB Touch Controller from Data Module
938 - e2i (Mimo monitors)
940 Have a look at <http://linux.chapter7.ch/touchkit/> for
941 a usage description and the required user-space stuff.
943 To compile this driver as a module, choose M here: the
948 depends on MFD_MXS_LRADC
950 Say Y here if you have a touchscreen connected to the low-resolution
951 analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor.
953 To compile this driver as a module, choose M here: the module will be
954 called mxs-lradc-ts.
958 depends on MFD_MX25_TSADC
962 To compile this driver as a module, choose M here: the
963 module will be called fsl-imx25-tcq.
967 depends on MFD_MC13XXX
969 Say Y here if you have an Freescale MC13783 PMIC on your
974 To compile this driver as a module, choose M here: the
979 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
980 depends on TOUCHSCREEN_USB_COMPOSITE
985 depends on TOUCHSCREEN_USB_COMPOSITE
990 depends on TOUCHSCREEN_USB_COMPOSITE
995 depends on TOUCHSCREEN_USB_COMPOSITE
999 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
1000 depends on TOUCHSCREEN_USB_COMPOSITE
1005 depends on TOUCHSCREEN_USB_COMPOSITE
1009 bool "DMC TSC-10/25 device support" if EXPERT
1010 depends on TOUCHSCREEN_USB_COMPOSITE
1015 depends on TOUCHSCREEN_USB_COMPOSITE
1020 depends on TOUCHSCREEN_USB_COMPOSITE
1025 depends on TOUCHSCREEN_USB_COMPOSITE
1030 depends on TOUCHSCREEN_USB_COMPOSITE
1034 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
1035 depends on TOUCHSCREEN_USB_COMPOSITE
1040 depends on TOUCHSCREEN_USB_COMPOSITE
1045 depends on TOUCHSCREEN_USB_COMPOSITE
1050 depends on TOUCHSCREEN_USB_COMPOSITE
1055 depends on TOUCHSCREEN_USB_COMPOSITE
1060 depends on TOUCHSCREEN_USB_COMPOSITE
1065 depends on TOUCHSCREEN_USB_COMPOSITE
1071 tristate "Sahara TouchIT-213 touchscreen"
1074 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
1078 To compile this driver as a module, choose M here: the
1082 tristate "TS-4800 touchscreen"
1083 depends on HAS_IOMEM && OF
1084 depends on SOC_IMX51 || COMPILE_TEST
1087 Say Y here if you have a touchscreen on a TS-4800 board.
1089 On TS-4800, the touchscreen is not handled directly by Linux but by
1090 a companion FPGA.
1094 To compile this driver as a module, choose M here: the
1098 tristate "TSC-10/25/40 serial touchscreen support"
1101 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
1102 to your system.
1106 To compile this driver as a module, choose M here: the
1114 depends on I2C
1118 Say Y here if you have a TSC2004 based touchscreen.
1122 To compile this driver as a module, choose M here: the
1127 depends on SPI_MASTER
1131 Say Y here if you have a TSC2005 based touchscreen.
1135 To compile this driver as a module, choose M here: the
1140 depends on I2C
1142 Say Y here if you have a TSC2007 based touchscreen.
1146 To compile this driver as a module, choose M here: the
1151 depends on TOUCHSCREEN_TSC2007
1152 depends on IIO=y || IIO=TOUCHSCREEN_TSC2007
1161 depends on EZX_PCAP
1163 Say Y here if you have a Motorola EZX telephone and
1164 want to enable support for the built-in touchscreen.
1166 To compile this driver as a module, choose M here: the
1171 depends on I2C
1172 depends on GPIOLIB || COMPILE_TEST
1175 such as RM32380, connected to your system.
1179 To compile this driver as a module, choose M here: the
1184 depends on I2C
1187 your system.
1191 To compile this driver as a module, choose M here: the
1196 depends on I2C
1198 depends on GPIOLIB || COMPILE_TEST
1204 To compile this driver as a module, choose M here: the
1209 depends on I2C
1216 To compile this driver as a module, choose M here: the
1221 depends on I2C
1222 depends on LEDS_CLASS
1227 To compile this driver as a module, choose M here: the
1232 depends on MFD_STMPE
1233 depends on OF
1238 To compile this driver as a module, choose M here: the
1239 module will be called stmpe-ts.
1243 depends on ARCH_SUNXI || COMPILE_TEST
1244 depends on HWMON
1245 depends on THERMAL || !THERMAL_OF
1248 found on Allwinner sunxi SoCs.
1250 To compile this driver as a module, choose M here: the
1251 module will be called sun4i-ts.
1255 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1256 depends on VIDEO_DEV
1262 To compile this driver as a module, choose M here: the
1267 depends on SPI
1268 depends on GPIOLIB || COMPILE_TEST
1271 controller chip as found on the Surface 3 in your system.
1275 To compile this driver as a module, choose M here: the
1280 depends on I2C
1282 Say Y here if you have a Semtech SX8654 touchscreen controller.
1286 To compile this driver as a module, choose M here: the
1291 depends on I2C
1293 Say Y here if you have a TPS6507x based touchscreen
1298 To compile this driver as a module, choose M here: the
1303 depends on I2C
1305 Say Y here if you have a touchscreen using Zeitec ZET6223
1309 To compile this driver as a module, choose M here: the
1314 depends on I2C
1315 depends on GPIOLIB || COMPILE_TEST
1317 Say Y here if you have a touchscreen using the zforce
1322 To compile this driver as a module, choose M here: the
1326 tristate "Toradex Colibri on board touchscreen driver"
1327 depends on IIO
1328 depends on GPIOLIB || COMPILE_TEST
1330 Say Y here if you have a Colibri VF50 and plan to use
1331 the on-board provided 4-wire touchscreen driver.
1335 To compile this driver as a module, choose M here: the
1340 depends on I2C
1342 Say Y here if you have a touchscreen using ROHM BU21023/24.
1346 To compile this driver as a module, choose M here: the
1351 depends on I2C
1356 To compile this driver as a module, choose M here: the
1360 tristate "Azoteq IQS7210A/7211A/E trackpad/touchscreen controller"
1361 depends on I2C
1363 Say Y to enable support for the Azoteq IQS7210A/7211A/E
1366 To compile this driver as a module, choose M here: the
1371 depends on I2C
1373 Say Y here if you have a touchscreen using Zinitix bt541,
1378 To compile this driver as a module, choose M here: the
1383 depends on I2C
1390 To compile this driver as a module, choose M here: the