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.
390 module will be called fujitsu-ts.
393 tristate "Goodix I2C touchscreen"
394 depends on I2C
399 system. It also supports 5-finger chip models, which can be
409 depends on I2C
420 depends on I2C
423 controller. This driver supports models ILI2102,
438 controller to your system.
459 depends on I2C
469 tristate "Gunze AHL-51S touchscreen"
472 Say Y here if you have the Gunze AHL-51 touchscreen connected to
481 tristate "Elan eKTF2127 I2C touchscreen"
482 depends on I2C
493 tristate "Elan eKTH I2C touchscreen"
494 depends on I2C
496 Say Y here if you have an Elan eKTH I2C touchscreen
529 tristate "Wacom Tablet support (I2C)"
530 depends on I2C
532 Say Y here if you want to use the I2C version of the Wacom
541 tristate "LPC32XX touchscreen controller"
545 to support the built-in touchscreen.
552 depends on I2C
555 controller.
563 tristate "MELFAS MCS-5000 touchscreen"
564 depends on I2C
566 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
576 depends on I2C
578 Say Y here if you have the MELFAS MMS114 touchscreen controller
588 depends on I2C
610 tristate "Freescale i.MX6UL touchscreen controller"
614 use the internal touchscreen controller.
637 controller chip in your system.
649 support the built-in touchscreen.
659 to support the built-in touchscreen.
669 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
674 module will be called ipaq-micro-ts.
681 Clio / Shangrila and want to support the built-in touchscreen.
701 tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
702 depends on I2C
711 module will be called edt-ft5x06.
723 module will be called raspberrypi-ts.
726 tristate "Renesas MIGO-R touchscreen"
727 depends on (SH_MIGOR || COMPILE_TEST) && I2C
729 Say Y here to enable MIGO-R touchscreen support.
764 Say Y here if you have 4/5/8 wire touchscreen controller
765 to be connected to the ADC controller on your TI AM335x SoC.
781 configure ALSA support as well (either built-in or modular,
782 independently of whether this driver is itself built-in or
789 tristate "PIXCIR I2C touchscreens"
790 depends on I2C
792 Say Y here if you have a pixcir i2c touchscreen
793 controller.
801 tristate "Weida HiTech I2C touchscreen"
802 depends on I2C
804 Say Y here if you have a Weida WDT87XX I2C touchscreen
816 This enables support for the touchscreen controller on the WM831x
820 module will be called wm831x-ts.
834 module will be called wm97xx-ts.
842 WM9705 touchscreen controller.
850 WM9712 touchscreen controller.
858 WM9713 touchscreen controller.
870 module will be called mainstone-wm97xx.
883 module will be called zylonite-wm97xx.
891 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
892 - PanJit TouchSet USB
893 - 3M MicroTouch USB (EX II series)
894 - ITM
895 - some other eTurboTouch
896 - Gunze AHL61
897 - DMC TSC-10/25
898 - IRTOUCHSYSTEMS/UNITOP
899 - IdealTEK URTC1000
900 - GoTop Super_Q2/GogoPen/PenPower tablets
901 - JASTEC USB Touch Controller/DigiTech DTR-02U
902 - Zytronic controllers
903 - Elo TouchSystems 2700 IntelliTouch
904 - EasyTouch USB Touch Controller from Data Modul
905 - e2i (Mimo monitors)
908 a usage description and the required user-space stuff.
917 Say Y here if you have a touchscreen connected to the low-resolution
918 analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor.
921 called mxs-lradc-ts.
930 module will be called fsl-imx25-tcq.
946 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
966 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
976 bool "DMC TSC-10/25 device support" if EXPERT
1001 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
1006 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
1011 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
1016 bool "Zytronic controller" if EXPERT
1021 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
1031 bool "EasyTouch USB Touch controller device support" if EXPERT
1034 Say Y here if you have an EasyTouch USB Touch controller.
1038 tristate "Sahara TouchIT-213 touchscreen"
1041 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
1049 tristate "TS-4800 touchscreen"
1054 Say Y here if you have a touchscreen on a TS-4800 board.
1056 On TS-4800, the touchscreen is not handled directly by Linux but by
1065 tristate "TSC-10/25/40 serial touchscreen support"
1068 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
1081 depends on I2C
1107 depends on I2C
1131 want to enable support for the built-in touchscreen.
1137 tristate "Raydium I2C Touchscreen"
1138 depends on I2C
1141 Say Y here if you have Raydium series I2C touchscreen,
1150 tristate "Silead I2C touchscreen"
1151 depends on I2C
1162 tristate "SiS 9200 family I2C touchscreen"
1163 depends on I2C
1167 This enables support for SiS 9200 family over I2C based touchscreens.
1176 depends on I2C
1179 or ST1633 touchscreen controller.
1188 depends on I2C
1206 module will be called stmpe-ts.
1209 tristate "Allwinner sun4i resistive touchscreen controller support"
1214 This selects support for the resistive touchscreen controller
1218 module will be called sun4i-ts.
1238 controller chip as found on the Surface 3 in your system.
1247 depends on I2C
1249 Say Y here if you have a Semtech SX8654 touchscreen controller.
1258 depends on I2C
1261 controller.
1270 depends on I2C
1281 depends on I2C
1298 the on-board provided 4-wire touchscreen driver.
1307 depends on I2C
1317 tristate "Azoteq IQS550/572/525 trackpad/touchscreen controller"
1318 depends on I2C
1328 depends on I2C