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