Lines Matching +full:i2c +full:- +full:controller
1 # SPDX-License-Identifier: GPL-2.0-only
24 support for the built-in touchscreen.
29 module will be called 88pm860x-ts.
37 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
38 and your board-specific setup code includes that in its
55 AD7877 controller, and your board-specific initialization
64 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
67 the AD7879-1/AD7889-1 controller.
75 tristate "support I2C bus connection"
76 depends on TOUCHSCREEN_AD7879 && I2C
79 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
82 module will be called ad7879-i2c.
89 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
94 module will be called ad7879-spi.
108 module will be called resistive-adc-touch.ko.
111 tristate "Microchip AR1020/1021 i2c touchscreen"
112 depends on I2C && OF
115 controller chip in your system.
123 tristate "Atmel mXT I2C Touchscreen"
124 depends on I2C
127 Say Y here if you have Atmel mXT series I2C touchscreen,
145 tristate "AUO in-cell touchscreen using Pixcir ICs"
146 depends on I2C
149 Say Y here if you have a AUO display with in-cell touchscreen
155 module will be called auo-pixcir-ts.
159 depends on I2C
171 depends on I2C
173 Say Y here if you have a Rohm BU21029 touchscreen controller
182 tristate "chipone icn8318 touchscreen controller"
184 depends on I2C
187 Say Y here if you have a ChipOne icn8318 based I2C touchscreen.
195 tristate "chipone icn8505 touchscreen controller"
196 depends on I2C && ACPI
198 Say Y here if you have a ChipOne icn8505 based I2C touchscreen.
207 depends on I2C
219 depends on I2C
233 Say Y here if you have a touchscreen using controller from
244 tristate "support I2C bus connection"
245 depends on TOUCHSCREEN_CYTTSP_CORE && I2C
247 Say Y here if the touchscreen is connected via I2C bus.
274 tristate "support I2C bus connection"
275 depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
277 Say Y here if the touchscreen is connected via I2C bus.
302 module will be called da9034-ts.
309 DA9052-BC and DA9053-AA/Bx PMICs.
342 depends on I2C
344 Say Y here to enable support for I2C connected EETI touch panels.
350 tristate "EETI eGalax multi-touch panel support"
351 depends on I2C && OF
353 Say Y here to enable support for I2C connected EETI
354 eGalax multi-touch panels.
370 tristate "EETI EXC3000 multi-touch panel support"
371 depends on I2C
373 Say Y here to enable support for I2C connected EETI
374 EXC3000 multi-touch panels.
381 depends on I2C
398 module will be called fujitsu-ts.
401 tristate "Goodix I2C touchscreen"
402 depends on I2C
407 system. It also supports 5-finger chip models, which can be
435 depends on I2C
446 depends on I2C
449 controller. This driver supports models ILI2102,
464 controller to your system.
485 depends on I2C
495 tristate "Gunze AHL-51S touchscreen"
498 Say Y here if you have the Gunze AHL-51 touchscreen connected to
507 tristate "Elan eKTF2127 I2C touchscreen"
508 depends on I2C
519 tristate "Elan eKTH I2C touchscreen"
520 depends on I2C
522 Say Y here if you have an Elan eKTH I2C touchscreen
532 depends on I2C
559 tristate "Wacom Tablet support (I2C)"
560 depends on I2C
562 Say Y here if you want to use the I2C version of the Wacom
571 tristate "LPC32XX touchscreen controller"
575 to support the built-in touchscreen.
582 depends on I2C
585 controller.
593 tristate "MELFAS MCS-5000 touchscreen"
594 depends on I2C
596 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
606 depends on I2C
608 Say Y here if you have the MELFAS MMS114 touchscreen controller
618 depends on I2C
640 tristate "Freescale i.MX6UL touchscreen controller"
644 use the internal touchscreen controller.
667 controller chip in your system.
679 support the built-in touchscreen.
689 to support the built-in touchscreen.
699 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
704 module will be called ipaq-micro-ts.
711 Clio / Shangrila and want to support the built-in touchscreen.
731 tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
732 depends on I2C
741 module will be called edt-ft5x06.
753 module will be called raspberrypi-ts.
756 tristate "Renesas MIGO-R touchscreen"
757 depends on (SH_MIGOR || COMPILE_TEST) && I2C
759 Say Y here to enable MIGO-R touchscreen support.
794 Say Y here if you have 4/5/8 wire touchscreen controller
795 to be connected to the ADC controller on your TI AM335x SoC.
811 configure ALSA support as well (either built-in or modular,
812 independently of whether this driver is itself built-in or
819 tristate "PIXCIR I2C touchscreens"
820 depends on I2C
822 Say Y here if you have a pixcir i2c touchscreen
823 controller.
831 tristate "Weida HiTech I2C touchscreen"
832 depends on I2C
834 Say Y here if you have a Weida WDT87XX I2C touchscreen
846 This enables support for the touchscreen controller on the WM831x
850 module will be called wm831x-ts.
864 module will be called wm97xx-ts.
872 WM9705 touchscreen controller.
880 WM9712 touchscreen controller.
888 WM9713 touchscreen controller.
900 module will be called mainstone-wm97xx.
913 module will be called zylonite-wm97xx.
921 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
922 - PanJit TouchSet USB
923 - 3M MicroTouch USB (EX II series)
924 - ITM
925 - some other eTurboTouch
926 - Gunze AHL61
927 - DMC TSC-10/25
928 - IRTOUCHSYSTEMS/UNITOP
929 - IdealTEK URTC1000
930 - GoTop Super_Q2/GogoPen/PenPower tablets
931 - JASTEC USB Touch Controller/DigiTech DTR-02U
932 - Zytronic controllers
933 - Elo TouchSystems 2700 IntelliTouch
934 - EasyTouch USB Touch Controller from Data Modul
935 - e2i (Mimo monitors)
938 a usage description and the required user-space stuff.
947 Say Y here if you have a touchscreen connected to the low-resolution
948 analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor.
951 called mxs-lradc-ts.
960 module will be called fsl-imx25-tcq.
976 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
996 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
1006 bool "DMC TSC-10/25 device support" if EXPERT
1031 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
1036 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
1041 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
1046 bool "Zytronic controller" if EXPERT
1051 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
1061 bool "EasyTouch USB Touch controller device support" if EXPERT
1064 Say Y here if you have an EasyTouch USB Touch controller.
1068 tristate "Sahara TouchIT-213 touchscreen"
1071 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
1079 tristate "TS-4800 touchscreen"
1084 Say Y here if you have a touchscreen on a TS-4800 board.
1086 On TS-4800, the touchscreen is not handled directly by Linux but by
1095 tristate "TSC-10/25/40 serial touchscreen support"
1098 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
1111 depends on I2C
1137 depends on I2C
1161 want to enable support for the built-in touchscreen.
1167 tristate "Raydium I2C Touchscreen"
1168 depends on I2C
1171 Say Y here if you have Raydium series I2C touchscreen,
1180 tristate "Silead I2C touchscreen"
1181 depends on I2C
1192 tristate "SiS 9200 family I2C touchscreen"
1193 depends on I2C
1197 This enables support for SiS 9200 family over I2C based touchscreens.
1206 depends on I2C
1209 or ST1633 touchscreen controller.
1218 depends on I2C
1236 module will be called stmpe-ts.
1239 tristate "Allwinner sun4i resistive touchscreen controller support"
1244 This selects support for the resistive touchscreen controller
1248 module will be called sun4i-ts.
1268 controller chip as found on the Surface 3 in your system.
1277 depends on I2C
1279 Say Y here if you have a Semtech SX8654 touchscreen controller.
1288 depends on I2C
1291 controller.
1300 depends on I2C
1311 depends on I2C
1328 the on-board provided 4-wire touchscreen driver.
1337 depends on I2C
1347 tristate "Azoteq IQS550/572/525 trackpad/touchscreen controller"
1348 depends on I2C
1358 depends on I2C