• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Touchscreen driver configuration
4#
5menuconfig INPUT_TOUCHSCREEN
6	bool "Touchscreens"
7	help
8	  Say Y here, and a list of supported touchscreens will be displayed.
9	  This option doesn't affect the kernel.
10
11	  If unsure, say Y.
12
13if INPUT_TOUCHSCREEN
14
15config TOUCHSCREEN_PROPERTIES
16	def_tristate INPUT
17	depends on INPUT
18
19config TOUCHSCREEN_88PM860X
20	tristate "Marvell 88PM860x touchscreen"
21	depends on MFD_88PM860X
22	help
23	  Say Y here if you have a 88PM860x PMIC and want to enable
24	  support for the built-in touchscreen.
25
26	  If unsure, say N.
27
28	  To compile this driver as a module, choose M here: the
29	  module will be called 88pm860x-ts.
30
31config TOUCHSCREEN_ADS7846
32	tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens"
33	depends on SPI_MASTER
34	depends on HWMON = n || HWMON
35	help
36	  Say Y here if you have a touchscreen interface using the
37	  ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
38	  and your board-specific setup code includes that in its
39	  table of SPI devices.
40
41	  If HWMON is selected, and the driver is told the reference voltage
42	  on your board, you will also get hwmon interfaces for the voltage
43	  (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
44
45	  If unsure, say N (but it's safe to say "Y").
46
47	  To compile this driver as a module, choose M here: the
48	  module will be called ads7846.
49
50config TOUCHSCREEN_AD7877
51	tristate "AD7877 based touchscreens"
52	depends on SPI_MASTER
53	help
54	  Say Y here if you have a touchscreen interface using the
55	  AD7877 controller, and your board-specific initialization
56	  code includes that in its table of SPI devices.
57
58	  If unsure, say N (but it's safe to say "Y").
59
60	  To compile this driver as a module, choose M here: the
61	  module will be called ad7877.
62
63config TOUCHSCREEN_AD7879
64	tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
65	help
66	  Say Y here if you want to support a touchscreen interface using
67	  the AD7879-1/AD7889-1 controller.
68
69	  You should select a bus connection too.
70
71	  To compile this driver as a module, choose M here: the
72	  module will be called ad7879.
73
74config TOUCHSCREEN_AD7879_I2C
75	tristate "support I2C bus connection"
76	depends on TOUCHSCREEN_AD7879 && I2C
77	select REGMAP_I2C
78	help
79	  Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
80
81	  To compile this driver as a module, choose M here: the
82	  module will be called ad7879-i2c.
83
84config TOUCHSCREEN_AD7879_SPI
85	tristate "support SPI bus connection"
86	depends on TOUCHSCREEN_AD7879 && SPI_MASTER
87	select REGMAP_SPI
88	help
89	  Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
90
91	  If unsure, say N (but it's safe to say "Y").
92
93	  To compile this driver as a module, choose M here: the
94	  module will be called ad7879-spi.
95
96config TOUCHSCREEN_ADC
97	tristate "Generic ADC based resistive touchscreen"
98	depends on IIO
99	select IIO_BUFFER
100	select IIO_BUFFER_CB
101	help
102	  Say Y here if you want to use the generic ADC
103	  resistive touchscreen driver.
104
105	  If unsure, say N (but it's safe to say "Y").
106
107	  To compile this driver as a module, choose M here: the
108	  module will be called resistive-adc-touch.ko.
109
110config TOUCHSCREEN_AR1021_I2C
111	tristate "Microchip AR1020/1021 i2c touchscreen"
112	depends on I2C && OF
113	help
114	  Say Y here if you have the Microchip AR1020 or AR1021 touchscreen
115	  controller chip in your system.
116
117	  If unsure, say N.
118
119	  To compile this driver as a module, choose M here: the
120	  module will be called ar1021_i2c.
121
122config TOUCHSCREEN_ATMEL_MXT
123	tristate "Atmel mXT I2C Touchscreen"
124	depends on I2C
125	select FW_LOADER
126	help
127	  Say Y here if you have Atmel mXT series I2C touchscreen,
128	  such as AT42QT602240/ATMXT224, connected to your system.
129
130	  If unsure, say N.
131
132	  To compile this driver as a module, choose M here: the
133	  module will be called atmel_mxt_ts.
134
135config TOUCHSCREEN_ATMEL_MXT_T37
136	bool "Support T37 Diagnostic Data"
137	depends on TOUCHSCREEN_ATMEL_MXT
138	depends on VIDEO_V4L2=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_V4L2=m)
139	select VIDEOBUF2_VMALLOC
140	help
141	  Say Y here if you want support to output data from the T37
142	  Diagnostic Data object using a V4L device.
143
144config TOUCHSCREEN_AUO_PIXCIR
145	tristate "AUO in-cell touchscreen using Pixcir ICs"
146	depends on I2C
147	depends on GPIOLIB || COMPILE_TEST
148	help
149	  Say Y here if you have a AUO display with in-cell touchscreen
150	  using Pixcir ICs.
151
152	  If unsure, say N.
153
154	  To compile this driver as a module, choose M here: the
155	  module will be called auo-pixcir-ts.
156
157config TOUCHSCREEN_BU21013
158	tristate "BU21013 based touch panel controllers"
159	depends on I2C
160	help
161	  Say Y here if you have a bu21013 touchscreen connected to
162	  your system.
163
164	  If unsure, say N.
165
166	  To compile this driver as a module, choose M here: the
167	  module will be called bu21013_ts.
168
169config TOUCHSCREEN_BU21029
170	tristate "Rohm BU21029 based touch panel controllers"
171	depends on I2C
172	help
173	  Say Y here if you have a Rohm BU21029 touchscreen controller
174	  connected to your system.
175
176	  If unsure, say N.
177
178	  To compile this driver as a module, choose M here: the
179	  module will be called bu21029_ts.
180
181config TOUCHSCREEN_CHIPONE_ICN8318
182	tristate "chipone icn8318 touchscreen controller"
183	depends on GPIOLIB || COMPILE_TEST
184	depends on I2C
185	depends on OF
186	help
187	  Say Y here if you have a ChipOne icn8318 based I2C touchscreen.
188
189	  If unsure, say N.
190
191	  To compile this driver as a module, choose M here: the
192	  module will be called chipone_icn8318.
193
194config TOUCHSCREEN_CHIPONE_ICN8505
195	tristate "chipone icn8505 touchscreen controller"
196	depends on I2C && ACPI
197	help
198	  Say Y here if you have a ChipOne icn8505 based I2C touchscreen.
199
200	  If unsure, say N.
201
202	  To compile this driver as a module, choose M here: the
203	  module will be called chipone_icn8505.
204
205config TOUCHSCREEN_CY8CTMG110
206	tristate "cy8ctmg110 touchscreen"
207	depends on I2C
208	depends on GPIOLIB || COMPILE_TEST
209	help
210	  Say Y here if you have a cy8ctmg110 capacitive touchscreen on
211	  an AAVA device.
212
213	  If unsure, say N.
214
215	  To compile this driver as a module, choose M here: the
216	  module will be called cy8ctmg110_ts.
217
218config TOUCHSCREEN_CYTTSP_CORE
219	tristate "Cypress TTSP touchscreen"
220	help
221	  Say Y here if you have a touchscreen using controller from
222	  the Cypress TrueTouch(tm) Standard Product family connected
223	  to your system. You will also need to select appropriate
224	  bus connection below.
225
226	  If unsure, say N.
227
228	  To compile this driver as a module, choose M here: the
229	  module will be called cyttsp_core.
230
231config TOUCHSCREEN_CYTTSP_I2C
232	tristate "support I2C bus connection"
233	depends on TOUCHSCREEN_CYTTSP_CORE && I2C
234	help
235	  Say Y here if the touchscreen is connected via I2C bus.
236
237	  To compile this driver as a module, choose M here: the
238	  module will be called cyttsp_i2c.
239
240config TOUCHSCREEN_CYTTSP_SPI
241	tristate "support SPI bus connection"
242	depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
243	help
244	  Say Y here if the touchscreen is connected via SPI bus.
245
246	  To compile this driver as a module, choose M here: the
247	  module will be called cyttsp_spi.
248
249config TOUCHSCREEN_CYTTSP4_CORE
250	tristate "Cypress TrueTouch Gen4 Touchscreen Driver"
251	help
252	  Core driver for Cypress TrueTouch(tm) Standard Product
253	  Generation4 touchscreen controllers.
254
255	  Say Y here if you have a Cypress Gen4 touchscreen.
256
257	  If unsure, say N.
258
259	  To compile this driver as a module, choose M here.
260
261config TOUCHSCREEN_CYTTSP4_I2C
262	tristate "support I2C bus connection"
263	depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
264	help
265	  Say Y here if the touchscreen is connected via I2C bus.
266
267	  To compile this driver as a module, choose M here: the
268	  module will be called cyttsp4_i2c.
269
270config TOUCHSCREEN_CYTTSP4_SPI
271	tristate "support SPI bus connection"
272	depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
273	help
274	  Say Y here if the touchscreen is connected via SPI bus.
275
276	  To compile this driver as a module, choose M here: the
277	  module will be called cyttsp4_spi.
278
279config TOUCHSCREEN_DA9034
280	tristate "Touchscreen support for Dialog Semiconductor DA9034"
281	depends on PMIC_DA903X
282	default y
283	help
284	  Say Y here to enable the support for the touchscreen found
285	  on Dialog Semiconductor DA9034 PMIC.
286
287	  If unsure, say N.
288
289	  To compile this driver as a module, choose M here: the
290	  module will be called da9034-ts.
291
292config TOUCHSCREEN_DA9052
293	tristate "Dialog DA9052/DA9053 TSI"
294	depends on PMIC_DA9052
295	help
296	  Say Y here to support the touchscreen found on Dialog Semiconductor
297	  DA9052-BC and DA9053-AA/Bx PMICs.
298
299	  If unsure, say N.
300
301	  To compile this driver as a module, choose M here: the
302	  module will be called da9052_tsi.
303
304config TOUCHSCREEN_DYNAPRO
305	tristate "Dynapro serial touchscreen"
306	select SERIO
307	help
308	  Say Y here if you have a Dynapro serial touchscreen connected to
309	  your system.
310
311	  If unsure, say N.
312
313	  To compile this driver as a module, choose M here: the
314	  module will be called dynapro.
315
316config TOUCHSCREEN_HAMPSHIRE
317	tristate "Hampshire serial touchscreen"
318	select SERIO
319	help
320	  Say Y here if you have a Hampshire serial touchscreen connected to
321	  your system.
322
323	  If unsure, say N.
324
325	  To compile this driver as a module, choose M here: the
326	  module will be called hampshire.
327
328config TOUCHSCREEN_EETI
329	tristate "EETI touchscreen panel support"
330	depends on I2C
331	help
332	  Say Y here to enable support for I2C connected EETI touch panels.
333
334	  To compile this driver as a module, choose M here: the
335	  module will be called eeti_ts.
336
337config TOUCHSCREEN_EGALAX
338	tristate "EETI eGalax multi-touch panel support"
339	depends on I2C && OF
340	help
341	  Say Y here to enable support for I2C connected EETI
342	  eGalax multi-touch panels.
343
344	  To compile this driver as a module, choose M here: the
345	  module will be called egalax_ts.
346
347config TOUCHSCREEN_EGALAX_SERIAL
348	tristate "EETI eGalax serial touchscreen"
349	select SERIO
350	help
351	  Say Y here to enable support for serial connected EETI
352	  eGalax touch panels.
353
354	  To compile this driver as a module, choose M here: the
355	  module will be called egalax_ts_serial.
356
357config TOUCHSCREEN_EXC3000
358	tristate "EETI EXC3000 multi-touch panel support"
359	depends on I2C
360	help
361	  Say Y here to enable support for I2C connected EETI
362	  EXC3000 multi-touch panels.
363
364	  To compile this driver as a module, choose M here: the
365	  module will be called exc3000.
366
367config TOUCHSCREEN_FUJITSU
368	tristate "Fujitsu serial touchscreen"
369	select SERIO
370	help
371	  Say Y here if you have the Fujitsu touchscreen (such as one
372	  installed in Lifebook P series laptop) connected to your
373	  system.
374
375	  If unsure, say N.
376
377	  To compile this driver as a module, choose M here: the
378	  module will be called fujitsu-ts.
379
380config TOUCHSCREEN_GOODIX
381	tristate "Goodix I2C touchscreen"
382	depends on I2C
383	depends on GPIOLIB || COMPILE_TEST
384	help
385	  Say Y here if you have the Goodix touchscreen (such as one
386	  installed in Onda v975w tablets) connected to your
387	  system. It also supports 5-finger chip models, which can be
388	  found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
389
390	  If unsure, say N.
391
392	  To compile this driver as a module, choose M here: the
393	  module will be called goodix.
394
395config TOUCHSCREEN_HIDEEP
396	tristate "HiDeep Touch IC"
397	depends on I2C
398	help
399	  Say Y here if you have a touchscreen using HiDeep.
400
401	  If unsure, say N.
402
403	  To compile this driver as a module, choose M here : the
404	  module will be called hideep_ts.
405
406config TOUCHSCREEN_ILI210X
407	tristate "Ilitek ILI210X based touchscreen"
408	depends on I2C
409	help
410	  Say Y here if you have a ILI210X based touchscreen
411	  controller. This driver supports models ILI2102,
412	  ILI2102s, ILI2103, ILI2103s and ILI2105.
413	  Such kind of chipsets can be found in Amazon Kindle Fire
414	  touchscreens.
415
416	  If unsure, say N.
417
418	  To compile this driver as a module, choose M here: the
419	  module will be called ili210x.
420
421config TOUCHSCREEN_IPROC
422	tristate "IPROC touch panel driver support"
423	depends on ARCH_BCM_IPROC || COMPILE_TEST
424	help
425	  Say Y here if you want to add support for the IPROC touch
426	  controller to your system.
427
428	  If unsure, say N.
429
430	  To compile this driver as a module, choose M here: the
431	  module will be called bcm_iproc_tsc.
432
433config TOUCHSCREEN_S3C2410
434	tristate "Samsung S3C2410/generic touchscreen input driver"
435	depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
436	depends on S3C_ADC
437	help
438	  Say Y here if you have the s3c2410 touchscreen.
439
440	  If unsure, say N.
441
442	  To compile this driver as a module, choose M here: the
443	  module will be called s3c2410_ts.
444
445config TOUCHSCREEN_S6SY761
446	tristate "Samsung S6SY761 Touchscreen driver"
447	depends on I2C
448	help
449	  Say Y if you have the Samsung S6SY761 driver
450
451	  If unsure, say N
452
453	  To compile this driver as module, choose M here: the
454	  module will be called s6sy761.
455
456config TOUCHSCREEN_GUNZE
457	tristate "Gunze AHL-51S touchscreen"
458	select SERIO
459	help
460	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
461	  your system.
462
463	  If unsure, say N.
464
465	  To compile this driver as a module, choose M here: the
466	  module will be called gunze.
467
468config TOUCHSCREEN_EKTF2127
469	tristate "Elan eKTF2127 I2C touchscreen"
470	depends on I2C
471	help
472	  Say Y here if you have an Elan eKTF2127 touchscreen
473	  connected to your system.
474
475	  If unsure, say N.
476
477	  To compile this driver as a module, choose M here: the
478	  module will be called ektf2127.
479
480config TOUCHSCREEN_ELAN
481	tristate "Elan eKTH I2C touchscreen"
482	depends on I2C
483	help
484	  Say Y here if you have an Elan eKTH I2C touchscreen
485	  connected to your system.
486
487	  If unsure, say N.
488
489	  To compile this driver as a module, choose M here: the
490	  module will be called elants_i2c.
491
492config TOUCHSCREEN_ELO
493	tristate "Elo serial touchscreens"
494	select SERIO
495	help
496	  Say Y here if you have an Elo serial touchscreen connected to
497	  your system.
498
499	  If unsure, say N.
500
501	  To compile this driver as a module, choose M here: the
502	  module will be called elo.
503
504config TOUCHSCREEN_WACOM_W8001
505	tristate "Wacom W8001 penabled serial touchscreen"
506	select SERIO
507	help
508	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
509	  connected to your system.
510
511	  If unsure, say N.
512
513	  To compile this driver as a module, choose M here: the
514	  module will be called wacom_w8001.
515
516config TOUCHSCREEN_WACOM_I2C
517	tristate "Wacom Tablet support (I2C)"
518	depends on I2C
519	help
520	  Say Y here if you want to use the I2C version of the Wacom
521	  Pen Tablet.
522
523	  If unsure, say N.
524
525	  To compile this driver as a module, choose M here: the module
526	  will be called wacom_i2c.
527
528config TOUCHSCREEN_LPC32XX
529	tristate "LPC32XX touchscreen controller"
530	depends on ARCH_LPC32XX
531	help
532	  Say Y here if you have a LPC32XX device and want
533	  to support the built-in touchscreen.
534
535	  To compile this driver as a module, choose M here: the
536	  module will be called lpc32xx_ts.
537
538config TOUCHSCREEN_MAX11801
539	tristate "MAX11801 based touchscreens"
540	depends on I2C
541	help
542	  Say Y here if you have a MAX11801 based touchscreen
543	  controller.
544
545	  If unsure, say N.
546
547	  To compile this driver as a module, choose M here: the
548	  module will be called max11801_ts.
549
550config TOUCHSCREEN_MCS5000
551	tristate "MELFAS MCS-5000 touchscreen"
552	depends on I2C
553	help
554	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
555	  chip in your system.
556
557	  If unsure, say N.
558
559	  To compile this driver as a module, choose M here: the
560	  module will be called mcs5000_ts.
561
562config TOUCHSCREEN_MMS114
563	tristate "MELFAS MMS114 touchscreen"
564	depends on I2C
565	help
566	  Say Y here if you have the MELFAS MMS114 touchscreen controller
567	  chip in your system.
568
569	  If unsure, say N.
570
571	  To compile this driver as a module, choose M here: the
572	  module will be called mms114.
573
574config TOUCHSCREEN_MELFAS_MIP4
575	tristate "MELFAS MIP4 Touchscreen"
576	depends on I2C
577	help
578	  Say Y here if you have a MELFAS MIP4 Touchscreen device.
579
580	  If unsure, say N.
581
582	  To compile this driver as a module, choose M here:
583	  the module will be called melfas_mip4.
584
585config TOUCHSCREEN_MTOUCH
586	tristate "MicroTouch serial touchscreens"
587	select SERIO
588	help
589	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
590	  your system.
591
592	  If unsure, say N.
593
594	  To compile this driver as a module, choose M here: the
595	  module will be called mtouch.
596
597config TOUCHSCREEN_IMX6UL_TSC
598	tristate "Freescale i.MX6UL touchscreen controller"
599	depends on (OF && GPIOLIB) || COMPILE_TEST
600	help
601	  Say Y here if you have a Freescale i.MX6UL, and want to
602	  use the internal touchscreen controller.
603
604	  If unsure, say N.
605
606	  To compile this driver as a module, choose M here: the
607	  module will be called imx6ul_tsc.
608
609config TOUCHSCREEN_INEXIO
610	tristate "iNexio serial touchscreens"
611	select SERIO
612	help
613	  Say Y here if you have an iNexio serial touchscreen connected to
614	  your system.
615
616	  If unsure, say N.
617
618	  To compile this driver as a module, choose M here: the
619	  module will be called inexio.
620
621config TOUCHSCREEN_MK712
622	tristate "ICS MicroClock MK712 touchscreen"
623	help
624	  Say Y here if you have the ICS MicroClock MK712 touchscreen
625	  controller chip in your system.
626
627	  If unsure, say N.
628
629	  To compile this driver as a module, choose M here: the
630	  module will be called mk712.
631
632config TOUCHSCREEN_HP600
633	tristate "HP Jornada 6xx touchscreen"
634	depends on SH_HP6XX && SH_ADC
635	help
636	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
637          support the built-in touchscreen.
638
639	  To compile this driver as a module, choose M here: the
640	  module will be called hp680_ts_input.
641
642config TOUCHSCREEN_HP7XX
643	tristate "HP Jornada 7xx touchscreen"
644	depends on SA1100_JORNADA720_SSP
645	help
646	  Say Y here if you have a HP Jornada 710/720/728 and want
647	  to support the built-in touchscreen.
648
649	  To compile this driver as a module, choose M here: the
650	  module will be called jornada720_ts.
651
652config TOUCHSCREEN_IPAQ_MICRO
653	tristate "HP iPAQ Atmel Micro ASIC touchscreen"
654	depends on MFD_IPAQ_MICRO
655	help
656	  Say Y here to enable support for the touchscreen attached to
657	  the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
658
659	  If unsure, say N.
660
661	  To compile this driver as a module, choose M here: the
662	  module will be called ipaq-micro-ts.
663
664config TOUCHSCREEN_HTCPEN
665	tristate "HTC Shift X9500 touchscreen"
666	depends on ISA
667	help
668	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
669	  Clio / Shangrila and want to support the built-in touchscreen.
670
671	  If unsure, say N.
672
673	  To compile this driver as a module, choose M here: the
674	  module will be called htcpen.
675
676config TOUCHSCREEN_PENMOUNT
677	tristate "Penmount serial touchscreen"
678	select SERIO
679	help
680	  Say Y here if you have a Penmount serial touchscreen connected to
681	  your system.
682
683	  If unsure, say N.
684
685	  To compile this driver as a module, choose M here: the
686	  module will be called penmount.
687
688config TOUCHSCREEN_EDT_FT5X06
689	tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
690	depends on I2C
691	help
692	  Say Y here if you have an EDT "Polytouch" touchscreen based
693	  on the FocalTech FT5x06 family of controllers connected to
694	  your system.
695
696	  If unsure, say N.
697
698	  To compile this driver as a module, choose M here: the
699	  module will be called edt-ft5x06.
700
701config TOUCHSCREEN_RASPBERRYPI_FW
702	tristate "Raspberry Pi's firmware base touch screen support"
703	depends on RASPBERRYPI_FIRMWARE || (RASPBERRYPI_FIRMWARE=n && COMPILE_TEST)
704	select INPUT_POLLDEV
705	help
706	  Say Y here if you have the official Raspberry Pi 7 inch screen on
707	  your system.
708
709	  If unsure, say N.
710
711	  To compile this driver as a module, choose M here: the
712	  module will be called raspberrypi-ts.
713
714config TOUCHSCREEN_MIGOR
715	tristate "Renesas MIGO-R touchscreen"
716	depends on (SH_MIGOR || COMPILE_TEST) && I2C
717	help
718	  Say Y here to enable MIGO-R touchscreen support.
719
720	  If unsure, say N.
721
722	  To compile this driver as a module, choose M here: the
723	  module will be called migor_ts.
724
725config TOUCHSCREEN_TOUCHRIGHT
726	tristate "Touchright serial touchscreen"
727	select SERIO
728	help
729	  Say Y here if you have a Touchright serial touchscreen connected to
730	  your system.
731
732	  If unsure, say N.
733
734	  To compile this driver as a module, choose M here: the
735	  module will be called touchright.
736
737config TOUCHSCREEN_TOUCHWIN
738	tristate "Touchwin serial touchscreen"
739	select SERIO
740	help
741	  Say Y here if you have a Touchwin serial touchscreen connected to
742	  your system.
743
744	  If unsure, say N.
745
746	  To compile this driver as a module, choose M here: the
747	  module will be called touchwin.
748
749config TOUCHSCREEN_TI_AM335X_TSC
750	tristate "TI Touchscreen Interface"
751	depends on MFD_TI_AM335X_TSCADC
752	help
753	  Say Y here if you have 4/5/8 wire touchscreen controller
754	  to be connected to the ADC controller on your TI AM335x SoC.
755
756	  If unsure, say N.
757
758	  To compile this driver as a module, choose M here: the
759	  module will be called ti_am335x_tsc.
760
761config TOUCHSCREEN_UCB1400
762	tristate "Philips UCB1400 touchscreen"
763	depends on AC97_BUS
764	depends on UCB1400_CORE
765	help
766	  This enables support for the Philips UCB1400 touchscreen interface.
767	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
768	  will be initialized only after the ALSA subsystem has been
769	  brought up and the UCB1400 detected.  You therefore have to
770	  configure ALSA support as well (either built-in or modular,
771	  independently of whether this driver is itself built-in or
772	  modular) for this driver to work.
773
774	  To compile this driver as a module, choose M here: the
775	  module will be called ucb1400_ts.
776
777config TOUCHSCREEN_PIXCIR
778	tristate "PIXCIR I2C touchscreens"
779	depends on I2C
780	help
781	  Say Y here if you have a pixcir i2c touchscreen
782	  controller.
783
784	  If unsure, say N.
785
786	  To compile this driver as a module, choose M here: the
787	  module will be called pixcir_i2c_ts.
788
789config TOUCHSCREEN_WDT87XX_I2C
790	tristate "Weida HiTech I2C touchscreen"
791	depends on I2C
792	help
793	  Say Y here if you have a Weida WDT87XX I2C touchscreen
794	  connected to your system.
795
796	  If unsure, say N.
797
798	  To compile this driver as a module, choose M here: the
799	  module will be called wdt87xx_i2c.
800
801config TOUCHSCREEN_WM831X
802	tristate "Support for WM831x touchscreen controllers"
803	depends on MFD_WM831X
804	help
805	  This enables support for the touchscreen controller on the WM831x
806	  series of PMICs.
807
808	  To compile this driver as a module, choose M here: the
809	  module will be called wm831x-ts.
810
811config TOUCHSCREEN_WM97XX
812	tristate "Support for WM97xx AC97 touchscreen controllers"
813	depends on AC97_BUS || AC97_BUS_NEW
814	help
815	  Say Y here if you have a Wolfson Microelectronics WM97xx
816	  touchscreen connected to your system. Note that this option
817	  only enables core driver, you will also need to select
818	  support for appropriate chip below.
819
820	  If unsure, say N.
821
822	  To compile this driver as a module, choose M here: the
823	  module will be called wm97xx-ts.
824
825config TOUCHSCREEN_WM9705
826	bool "WM9705 Touchscreen interface support"
827	depends on TOUCHSCREEN_WM97XX
828	default y
829	help
830	  Say Y here to enable support for the Wolfson Microelectronics
831	  WM9705 touchscreen controller.
832
833config TOUCHSCREEN_WM9712
834	bool "WM9712 Touchscreen interface support"
835	depends on TOUCHSCREEN_WM97XX
836	default y
837	help
838	  Say Y here to enable support for the Wolfson Microelectronics
839	  WM9712 touchscreen controller.
840
841config TOUCHSCREEN_WM9713
842	bool "WM9713 Touchscreen interface support"
843	depends on TOUCHSCREEN_WM97XX
844	default y
845	help
846	  Say Y here to enable support for the Wolfson Microelectronics
847	  WM9713 touchscreen controller.
848
849config TOUCHSCREEN_WM97XX_MAINSTONE
850	tristate "WM97xx Mainstone/Palm accelerated touch"
851	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
852	help
853	  Say Y here for support for streaming mode with WM97xx touchscreens
854	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
855
856	  If unsure, say N.
857
858	  To compile this driver as a module, choose M here: the
859	  module will be called mainstone-wm97xx.
860
861config TOUCHSCREEN_WM97XX_ZYLONITE
862	tristate "Zylonite accelerated touch"
863	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
864	select TOUCHSCREEN_WM9713
865	help
866	  Say Y here for support for streaming mode with the touchscreen
867	  on Zylonite systems.
868
869	  If unsure, say N.
870
871	  To compile this driver as a module, choose M here: the
872	  module will be called zylonite-wm97xx.
873
874config TOUCHSCREEN_USB_COMPOSITE
875	tristate "USB Touchscreen Driver"
876	depends on USB_ARCH_HAS_HCD
877	select USB
878	help
879	  USB Touchscreen driver for:
880	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
881	  - PanJit TouchSet USB
882	  - 3M MicroTouch USB (EX II series)
883	  - ITM
884	  - some other eTurboTouch
885	  - Gunze AHL61
886	  - DMC TSC-10/25
887	  - IRTOUCHSYSTEMS/UNITOP
888	  - IdealTEK URTC1000
889	  - GoTop Super_Q2/GogoPen/PenPower tablets
890	  - JASTEC USB Touch Controller/DigiTech DTR-02U
891	  - Zytronic controllers
892	  - Elo TouchSystems 2700 IntelliTouch
893	  - EasyTouch USB Touch Controller from Data Modul
894	  - e2i (Mimo monitors)
895
896	  Have a look at <http://linux.chapter7.ch/touchkit/> for
897	  a usage description and the required user-space stuff.
898
899	  To compile this driver as a module, choose M here: the
900	  module will be called usbtouchscreen.
901
902config TOUCHSCREEN_MXS_LRADC
903	tristate "Freescale i.MX23/i.MX28 LRADC touchscreen"
904	depends on MFD_MXS_LRADC
905	help
906	  Say Y here if you have a touchscreen connected to the low-resolution
907	  analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor.
908
909	  To compile this driver as a module, choose M here: the module will be
910	  called mxs-lradc-ts.
911
912config TOUCHSCREEN_MX25
913	tristate "Freescale i.MX25 touchscreen input driver"
914	depends on MFD_MX25_TSADC
915	help
916	  Enable support for touchscreen connected to your i.MX25.
917
918	  To compile this driver as a module, choose M here: the
919	  module will be called fsl-imx25-tcq.
920
921config TOUCHSCREEN_MC13783
922	tristate "Freescale MC13783 touchscreen input driver"
923	depends on MFD_MC13XXX
924	help
925	  Say Y here if you have an Freescale MC13783 PMIC on your
926	  board and want to use its touchscreen
927
928	  If unsure, say N.
929
930	  To compile this driver as a module, choose M here: the
931	  module will be called mc13783_ts.
932
933config TOUCHSCREEN_USB_EGALAX
934	default y
935	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
936	depends on TOUCHSCREEN_USB_COMPOSITE
937
938config TOUCHSCREEN_USB_PANJIT
939	default y
940	bool "PanJit device support" if EXPERT
941	depends on TOUCHSCREEN_USB_COMPOSITE
942
943config TOUCHSCREEN_USB_3M
944	default y
945	bool "3M/Microtouch EX II series device support" if EXPERT
946	depends on TOUCHSCREEN_USB_COMPOSITE
947
948config TOUCHSCREEN_USB_ITM
949	default y
950	bool "ITM device support" if EXPERT
951	depends on TOUCHSCREEN_USB_COMPOSITE
952
953config TOUCHSCREEN_USB_ETURBO
954	default y
955	bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
956	depends on TOUCHSCREEN_USB_COMPOSITE
957
958config TOUCHSCREEN_USB_GUNZE
959	default y
960	bool "Gunze AHL61 device support" if EXPERT
961	depends on TOUCHSCREEN_USB_COMPOSITE
962
963config TOUCHSCREEN_USB_DMC_TSC10
964	default y
965	bool "DMC TSC-10/25 device support" if EXPERT
966	depends on TOUCHSCREEN_USB_COMPOSITE
967
968config TOUCHSCREEN_USB_IRTOUCH
969	default y
970	bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
971	depends on TOUCHSCREEN_USB_COMPOSITE
972
973config TOUCHSCREEN_USB_IDEALTEK
974	default y
975	bool "IdealTEK URTC1000 device support" if EXPERT
976	depends on TOUCHSCREEN_USB_COMPOSITE
977
978config TOUCHSCREEN_USB_GENERAL_TOUCH
979	default y
980	bool "GeneralTouch Touchscreen device support" if EXPERT
981	depends on TOUCHSCREEN_USB_COMPOSITE
982
983config TOUCHSCREEN_USB_GOTOP
984	default y
985	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
986	depends on TOUCHSCREEN_USB_COMPOSITE
987
988config TOUCHSCREEN_USB_JASTEC
989	default y
990	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
991	depends on TOUCHSCREEN_USB_COMPOSITE
992
993config TOUCHSCREEN_USB_ELO
994	default y
995	bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
996	depends on TOUCHSCREEN_USB_COMPOSITE
997
998config TOUCHSCREEN_USB_E2I
999	default y
1000	bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
1001	depends on TOUCHSCREEN_USB_COMPOSITE
1002
1003config TOUCHSCREEN_USB_ZYTRONIC
1004	default y
1005	bool "Zytronic controller" if EXPERT
1006	depends on TOUCHSCREEN_USB_COMPOSITE
1007
1008config TOUCHSCREEN_USB_ETT_TC45USB
1009	default y
1010	bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
1011	depends on TOUCHSCREEN_USB_COMPOSITE
1012
1013config TOUCHSCREEN_USB_NEXIO
1014	default y
1015	bool "NEXIO/iNexio device support" if EXPERT
1016	depends on TOUCHSCREEN_USB_COMPOSITE
1017
1018config TOUCHSCREEN_USB_EASYTOUCH
1019	default y
1020	bool "EasyTouch USB Touch controller device support" if EXPERT
1021	depends on TOUCHSCREEN_USB_COMPOSITE
1022	help
1023	  Say Y here if you have an EasyTouch USB Touch controller.
1024	  If unsure, say N.
1025
1026config TOUCHSCREEN_TOUCHIT213
1027	tristate "Sahara TouchIT-213 touchscreen"
1028	select SERIO
1029	help
1030	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.
1031
1032	  If unsure, say N.
1033
1034	  To compile this driver as a module, choose M here: the
1035	  module will be called touchit213.
1036
1037config TOUCHSCREEN_TS4800
1038	tristate "TS-4800 touchscreen"
1039	depends on HAS_IOMEM && OF
1040	depends on SOC_IMX51 || COMPILE_TEST
1041	select MFD_SYSCON
1042	select INPUT_POLLDEV
1043	help
1044	  Say Y here if you have a touchscreen on a TS-4800 board.
1045
1046	  On TS-4800, the touchscreen is not handled directly by Linux but by
1047	  a companion FPGA.
1048
1049	  If unsure, say N.
1050
1051	  To compile this driver as a module, choose M here: the
1052	  module will be called ts4800_ts.
1053
1054config TOUCHSCREEN_TSC_SERIO
1055	tristate "TSC-10/25/40 serial touchscreen support"
1056	select SERIO
1057	help
1058	  Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
1059	  to your system.
1060
1061	  If unsure, say N.
1062
1063	  To compile this driver as a module, choose M here: the
1064	  module will be called tsc40.
1065
1066config TOUCHSCREEN_TSC200X_CORE
1067	tristate
1068
1069config TOUCHSCREEN_TSC2004
1070	tristate "TSC2004 based touchscreens"
1071	depends on I2C
1072	select REGMAP_I2C
1073	select TOUCHSCREEN_TSC200X_CORE
1074	help
1075	  Say Y here if you have a TSC2004 based touchscreen.
1076
1077	  If unsure, say N.
1078
1079	  To compile this driver as a module, choose M here: the
1080	  module will be called tsc2004.
1081
1082config TOUCHSCREEN_TSC2005
1083	tristate "TSC2005 based touchscreens"
1084	depends on SPI_MASTER
1085	select REGMAP_SPI
1086	select TOUCHSCREEN_TSC200X_CORE
1087	help
1088	  Say Y here if you have a TSC2005 based touchscreen.
1089
1090	  If unsure, say N.
1091
1092	  To compile this driver as a module, choose M here: the
1093	  module will be called tsc2005.
1094
1095config TOUCHSCREEN_TSC2007
1096	tristate "TSC2007 based touchscreens"
1097	depends on I2C
1098	help
1099	  Say Y here if you have a TSC2007 based touchscreen.
1100
1101	  If unsure, say N.
1102
1103	  To compile this driver as a module, choose M here: the
1104	  module will be called tsc2007.
1105
1106config TOUCHSCREEN_TSC2007_IIO
1107	bool "IIO interface for external ADC input and temperature"
1108	depends on TOUCHSCREEN_TSC2007
1109	depends on IIO=y || IIO=TOUCHSCREEN_TSC2007
1110	help
1111	  Saying Y here adds an iio interface to the tsc2007 which
1112	  provides values for the AUX input (used for e.g. battery
1113	  or ambient light monitoring), temperature and raw input
1114	  values.
1115
1116config TOUCHSCREEN_PCAP
1117	tristate "Motorola PCAP touchscreen"
1118	depends on EZX_PCAP
1119	help
1120	  Say Y here if you have a Motorola EZX telephone and
1121	  want to enable support for the built-in touchscreen.
1122
1123	  To compile this driver as a module, choose M here: the
1124	  module will be called pcap_ts.
1125
1126config TOUCHSCREEN_RM_TS
1127	tristate "Raydium I2C Touchscreen"
1128	depends on I2C
1129	depends on GPIOLIB || COMPILE_TEST
1130	help
1131	  Say Y here if you have Raydium series I2C touchscreen,
1132	  such as RM32380, connected to your system.
1133
1134	  If unsure, say N.
1135
1136	  To compile this driver as a module, choose M here: the
1137	  module will be called raydium_i2c_ts.
1138
1139config TOUCHSCREEN_SILEAD
1140	tristate "Silead I2C touchscreen"
1141	depends on I2C
1142	help
1143	  Say Y here if you have the Silead touchscreen connected to
1144	  your system.
1145
1146	  If unsure, say N.
1147
1148	  To compile this driver as a module, choose M here: the
1149	  module will be called silead.
1150
1151config TOUCHSCREEN_SIS_I2C
1152	tristate "SiS 9200 family I2C touchscreen"
1153	depends on I2C
1154	select CRC_ITU_T
1155	depends on GPIOLIB || COMPILE_TEST
1156	help
1157	  This enables support for SiS 9200 family over I2C based touchscreens.
1158
1159	  If unsure, say N.
1160
1161	  To compile this driver as a module, choose M here: the
1162	  module will be called sis_i2c.
1163
1164config TOUCHSCREEN_ST1232
1165	tristate "Sitronix ST1232 or ST1633 touchscreen controllers"
1166	depends on I2C
1167	help
1168	  Say Y here if you want to support the Sitronix ST1232
1169	  or ST1633 touchscreen controller.
1170
1171	  If unsure, say N.
1172
1173	  To compile this driver as a module, choose M here: the
1174	  module will be called st1232_ts.
1175
1176config TOUCHSCREEN_STMFTS
1177	tristate "STMicroelectronics STMFTS touchscreen"
1178	depends on I2C
1179	depends on LEDS_CLASS
1180	help
1181	  Say Y here if you want support for STMicroelectronics
1182	  STMFTS touchscreen.
1183
1184	  To compile this driver as a module, choose M here: the
1185	  module will be called stmfts.
1186
1187config TOUCHSCREEN_STMPE
1188	tristate "STMicroelectronics STMPE touchscreens"
1189	depends on MFD_STMPE
1190	depends on (OF || COMPILE_TEST)
1191	help
1192	  Say Y here if you want support for STMicroelectronics
1193	  STMPE touchscreen controllers.
1194
1195	  To compile this driver as a module, choose M here: the
1196	  module will be called stmpe-ts.
1197
1198config TOUCHSCREEN_SUN4I
1199	tristate "Allwinner sun4i resistive touchscreen controller support"
1200	depends on ARCH_SUNXI || COMPILE_TEST
1201	depends on HWMON
1202	depends on THERMAL || !THERMAL_OF
1203	help
1204	  This selects support for the resistive touchscreen controller
1205	  found on Allwinner sunxi SoCs.
1206
1207	  To compile this driver as a module, choose M here: the
1208	  module will be called sun4i-ts.
1209
1210config TOUCHSCREEN_SUR40
1211	tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
1212	depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1213	depends on VIDEO_V4L2
1214	select INPUT_POLLDEV
1215	select VIDEOBUF2_DMA_SG
1216	help
1217	  Say Y here if you want support for the Samsung SUR40 touchscreen
1218	  (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
1219
1220	  To compile this driver as a module, choose M here: the
1221	  module will be called sur40.
1222
1223config TOUCHSCREEN_SURFACE3_SPI
1224	tristate "Ntrig/Microsoft Surface 3 SPI touchscreen"
1225	depends on SPI
1226	depends on GPIOLIB || COMPILE_TEST
1227	help
1228	  Say Y here if you have the Ntrig/Microsoft SPI touchscreen
1229	  controller chip as found on the Surface 3 in your system.
1230
1231	  If unsure, say N.
1232
1233	  To compile this driver as a module, choose M here: the
1234	  module will be called surface3_spi.
1235
1236config TOUCHSCREEN_SX8654
1237	tristate "Semtech SX8654 touchscreen"
1238	depends on I2C
1239	help
1240	  Say Y here if you have a Semtech SX8654 touchscreen controller.
1241
1242	  If unsure, say N
1243
1244	  To compile this driver as a module, choose M here: the
1245	  module will be called sx8654.
1246
1247config TOUCHSCREEN_TPS6507X
1248	tristate "TPS6507x based touchscreens"
1249	depends on I2C
1250	select INPUT_POLLDEV
1251	help
1252	  Say Y here if you have a TPS6507x based touchscreen
1253	  controller.
1254
1255	  If unsure, say N.
1256
1257	  To compile this driver as a module, choose M here: the
1258	  module will be called tps6507x_ts.
1259
1260config TOUCHSCREEN_ZET6223
1261	tristate "Zeitec ZET6223 touchscreen driver"
1262	depends on I2C
1263	help
1264	  Say Y here if you have a touchscreen using Zeitec ZET6223
1265
1266	  If unsure, say N.
1267
1268	  To compile this driver as a module, choose M here: the
1269	  module will be called zet6223.
1270
1271config TOUCHSCREEN_ZFORCE
1272	tristate "Neonode zForce infrared touchscreens"
1273	depends on I2C
1274	depends on GPIOLIB || COMPILE_TEST
1275	help
1276	  Say Y here if you have a touchscreen using the zforce
1277	  infraread technology from Neonode.
1278
1279	  If unsure, say N.
1280
1281	  To compile this driver as a module, choose M here: the
1282	  module will be called zforce_ts.
1283
1284config TOUCHSCREEN_COLIBRI_VF50
1285	tristate "Toradex Colibri on board touchscreen driver"
1286	depends on IIO && VF610_ADC
1287	depends on GPIOLIB || COMPILE_TEST
1288	help
1289	  Say Y here if you have a Colibri VF50 and plan to use
1290	  the on-board provided 4-wire touchscreen driver.
1291
1292	  If unsure, say N.
1293
1294	  To compile this driver as a module, choose M here: the
1295	  module will be called colibri_vf50_ts.
1296
1297config TOUCHSCREEN_ROHM_BU21023
1298	tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
1299	depends on I2C
1300	help
1301	  Say Y here if you have a touchscreen using ROHM BU21023/24.
1302
1303	  If unsure, say N.
1304
1305	  To compile this driver as a module, choose M here: the
1306	  module will be called bu21023_ts.
1307
1308config TOUCHSCREEN_IQS5XX
1309	tristate "Azoteq IQS550/572/525 trackpad/touchscreen controller"
1310	depends on I2C
1311	help
1312	  Say Y to enable support for the Azoteq IQS550/572/525
1313	  family of trackpad/touchscreen controllers.
1314
1315	  To compile this driver as a module, choose M here: the
1316	  module will be called iqs5xx.
1317
1318endif
1319