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	help
77	  Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
78
79	  To compile this driver as a module, choose M here: the
80	  module will be called ad7879-i2c.
81
82config TOUCHSCREEN_AD7879_SPI
83	tristate "support SPI bus connection"
84	depends on TOUCHSCREEN_AD7879 && SPI_MASTER
85	help
86	  Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
87
88	  If unsure, say N (but it's safe to say "Y").
89
90	  To compile this driver as a module, choose M here: the
91	  module will be called ad7879-spi.
92
93config TOUCHSCREEN_AR1021_I2C
94	tristate "Microchip AR1021 i2c touchscreen"
95	depends on I2C && OF
96	help
97	  Say Y here if you have the Microchip AR1021 touchscreen controller
98	  chip in your system.
99
100	  If unsure, say N.
101
102	  To compile this driver as a module, choose M here: the
103	  module will be called ar1021_i2c.
104
105config TOUCHSCREEN_ATMEL_MXT
106	tristate "Atmel mXT I2C Touchscreen"
107	depends on I2C
108	select FW_LOADER
109	help
110	  Say Y here if you have Atmel mXT series I2C touchscreen,
111	  such as AT42QT602240/ATMXT224, connected to your system.
112
113	  If unsure, say N.
114
115	  To compile this driver as a module, choose M here: the
116	  module will be called atmel_mxt_ts.
117
118config TOUCHSCREEN_AUO_PIXCIR
119	tristate "AUO in-cell touchscreen using Pixcir ICs"
120	depends on I2C
121	depends on GPIOLIB || COMPILE_TEST
122	help
123	  Say Y here if you have a AUO display with in-cell touchscreen
124	  using Pixcir ICs.
125
126	  If unsure, say N.
127
128	  To compile this driver as a module, choose M here: the
129	  module will be called auo-pixcir-ts.
130
131config TOUCHSCREEN_BU21013
132	tristate "BU21013 based touch panel controllers"
133	depends on I2C
134	help
135	  Say Y here if you have a bu21013 touchscreen connected to
136	  your system.
137
138	  If unsure, say N.
139
140	  To compile this driver as a module, choose M here: the
141	  module will be called bu21013_ts.
142
143config TOUCHSCREEN_CHIPONE_ICN8318
144	tristate "chipone icn8318 touchscreen controller"
145	depends on GPIOLIB || COMPILE_TEST
146	depends on I2C
147	depends on OF
148	help
149	  Say Y here if you have a ChipOne icn8318 based I2C touchscreen.
150
151	  If unsure, say N.
152
153	  To compile this driver as a module, choose M here: the
154	  module will be called chipone_icn8318.
155
156config TOUCHSCREEN_CY8CTMG110
157	tristate "cy8ctmg110 touchscreen"
158	depends on I2C
159	depends on GPIOLIB || COMPILE_TEST
160	help
161	  Say Y here if you have a cy8ctmg110 capacitive touchscreen on
162	  an AAVA device.
163
164	  If unsure, say N.
165
166	  To compile this driver as a module, choose M here: the
167	  module will be called cy8ctmg110_ts.
168
169config TOUCHSCREEN_CYTTSP_CORE
170	tristate "Cypress TTSP touchscreen"
171	help
172	  Say Y here if you have a touchscreen using controller from
173	  the Cypress TrueTouch(tm) Standard Product family connected
174	  to your system. You will also need to select appropriate
175	  bus connection below.
176
177	  If unsure, say N.
178
179	  To compile this driver as a module, choose M here: the
180	  module will be called cyttsp_core.
181
182config TOUCHSCREEN_CYTTSP_I2C
183	tristate "support I2C bus connection"
184	depends on TOUCHSCREEN_CYTTSP_CORE && I2C
185	help
186	  Say Y here if the touchscreen is connected via I2C bus.
187
188	  To compile this driver as a module, choose M here: the
189	  module will be called cyttsp_i2c.
190
191config TOUCHSCREEN_CYTTSP_SPI
192	tristate "support SPI bus connection"
193	depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
194	help
195	  Say Y here if the touchscreen is connected via SPI bus.
196
197	  To compile this driver as a module, choose M here: the
198	  module will be called cyttsp_spi.
199
200config TOUCHSCREEN_CYTTSP4_CORE
201	tristate "Cypress TrueTouch Gen4 Touchscreen Driver"
202	help
203	  Core driver for Cypress TrueTouch(tm) Standard Product
204	  Generation4 touchscreen controllers.
205
206	  Say Y here if you have a Cypress Gen4 touchscreen.
207
208	  If unsure, say N.
209
210	  To compile this driver as a module, choose M here.
211
212config TOUCHSCREEN_CYTTSP4_I2C
213	tristate "support I2C bus connection"
214	depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
215	help
216	  Say Y here if the touchscreen is connected via I2C bus.
217
218	  To compile this driver as a module, choose M here: the
219	  module will be called cyttsp4_i2c.
220
221config TOUCHSCREEN_CYTTSP4_SPI
222	tristate "support SPI bus connection"
223	depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
224	help
225	  Say Y here if the touchscreen is connected via SPI bus.
226
227	  To compile this driver as a module, choose M here: the
228	  module will be called cyttsp4_spi.
229
230config TOUCHSCREEN_DA9034
231	tristate "Touchscreen support for Dialog Semiconductor DA9034"
232	depends on PMIC_DA903X
233	default y
234	help
235	  Say Y here to enable the support for the touchscreen found
236	  on Dialog Semiconductor DA9034 PMIC.
237
238	  If unsure, say N.
239
240	  To compile this driver as a module, choose M here: the
241	  module will be called da9034-ts.
242
243config TOUCHSCREEN_DA9052
244	tristate "Dialog DA9052/DA9053 TSI"
245	depends on PMIC_DA9052
246	help
247	  Say Y here to support the touchscreen found on Dialog Semiconductor
248	  DA9052-BC and DA9053-AA/Bx PMICs.
249
250	  If unsure, say N.
251
252	  To compile this driver as a module, choose M here: the
253	  module will be called da9052_tsi.
254
255config TOUCHSCREEN_DYNAPRO
256	tristate "Dynapro serial touchscreen"
257	select SERIO
258	help
259	  Say Y here if you have a Dynapro serial touchscreen connected to
260	  your system.
261
262	  If unsure, say N.
263
264	  To compile this driver as a module, choose M here: the
265	  module will be called dynapro.
266
267config TOUCHSCREEN_HAMPSHIRE
268	tristate "Hampshire serial touchscreen"
269	select SERIO
270	help
271	  Say Y here if you have a Hampshire serial touchscreen connected to
272	  your system.
273
274	  If unsure, say N.
275
276	  To compile this driver as a module, choose M here: the
277	  module will be called hampshire.
278
279config TOUCHSCREEN_EETI
280	tristate "EETI touchscreen panel support"
281	depends on I2C
282	help
283	  Say Y here to enable support for I2C connected EETI touch panels.
284
285	  To compile this driver as a module, choose M here: the
286	  module will be called eeti_ts.
287
288config TOUCHSCREEN_EGALAX
289	tristate "EETI eGalax multi-touch panel support"
290	depends on I2C && OF
291	help
292	  Say Y here to enable support for I2C connected EETI
293	  eGalax multi-touch panels.
294
295	  To compile this driver as a module, choose M here: the
296	  module will be called egalax_ts.
297
298config TOUCHSCREEN_FUJITSU
299	tristate "Fujitsu serial touchscreen"
300	select SERIO
301	help
302	  Say Y here if you have the Fujitsu touchscreen (such as one
303	  installed in Lifebook P series laptop) connected to your
304	  system.
305
306	  If unsure, say N.
307
308	  To compile this driver as a module, choose M here: the
309	  module will be called fujitsu-ts.
310
311config TOUCHSCREEN_GOODIX
312	tristate "Goodix I2C touchscreen"
313	depends on I2C
314	help
315	  Say Y here if you have the Goodix touchscreen (such as one
316	  installed in Onda v975w tablets) connected to your
317	  system. It also supports 5-finger chip models, which can be
318	  found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
319
320	  If unsure, say N.
321
322	  To compile this driver as a module, choose M here: the
323	  module will be called goodix.
324
325config TOUCHSCREEN_ILI210X
326	tristate "Ilitek ILI210X based touchscreen"
327	depends on I2C
328	help
329	  Say Y here if you have a ILI210X based touchscreen
330	  controller. This driver supports models ILI2102,
331	  ILI2102s, ILI2103, ILI2103s and ILI2105.
332	  Such kind of chipsets can be found in Amazon Kindle Fire
333	  touchscreens.
334
335	  If unsure, say N.
336
337	  To compile this driver as a module, choose M here: the
338	  module will be called ili210x.
339
340config TOUCHSCREEN_IPROC
341	tristate "IPROC touch panel driver support"
342	depends on ARCH_BCM_IPROC || COMPILE_TEST
343	help
344	  Say Y here if you want to add support for the IPROC touch
345	  controller to your system.
346
347	  If unsure, say N.
348
349	  To compile this driver as a module, choose M here: the
350	  module will be called bcm_iproc_tsc.
351
352config TOUCHSCREEN_S3C2410
353	tristate "Samsung S3C2410/generic touchscreen input driver"
354	depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
355	select S3C_ADC
356	help
357	  Say Y here if you have the s3c2410 touchscreen.
358
359	  If unsure, say N.
360
361	  To compile this driver as a module, choose M here: the
362	  module will be called s3c2410_ts.
363
364config TOUCHSCREEN_GUNZE
365	tristate "Gunze AHL-51S touchscreen"
366	select SERIO
367	help
368	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
369	  your system.
370
371	  If unsure, say N.
372
373	  To compile this driver as a module, choose M here: the
374	  module will be called gunze.
375
376config TOUCHSCREEN_ELAN
377	tristate "Elan eKTH I2C touchscreen"
378	depends on I2C
379	help
380	  Say Y here if you have an Elan eKTH I2C touchscreen
381	  connected to your system.
382
383	  If unsure, say N.
384
385	  To compile this driver as a module, choose M here: the
386	  module will be called elants_i2c.
387
388config TOUCHSCREEN_ELO
389	tristate "Elo serial touchscreens"
390	select SERIO
391	help
392	  Say Y here if you have an Elo serial touchscreen connected to
393	  your system.
394
395	  If unsure, say N.
396
397	  To compile this driver as a module, choose M here: the
398	  module will be called elo.
399
400config TOUCHSCREEN_WACOM_W8001
401	tristate "Wacom W8001 penabled serial touchscreen"
402	select SERIO
403	help
404	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
405	  connected to your system.
406
407	  If unsure, say N.
408
409	  To compile this driver as a module, choose M here: the
410	  module will be called wacom_w8001.
411
412config TOUCHSCREEN_WACOM_I2C
413	tristate "Wacom Tablet support (I2C)"
414	depends on I2C
415	help
416	  Say Y here if you want to use the I2C version of the Wacom
417	  Pen Tablet.
418
419	  If unsure, say N.
420
421	  To compile this driver as a module, choose M here: the module
422	  will be called wacom_i2c.
423
424config TOUCHSCREEN_LPC32XX
425	tristate "LPC32XX touchscreen controller"
426	depends on ARCH_LPC32XX
427	help
428	  Say Y here if you have a LPC32XX device and want
429	  to support the built-in touchscreen.
430
431	  To compile this driver as a module, choose M here: the
432	  module will be called lpc32xx_ts.
433
434config TOUCHSCREEN_MAX11801
435	tristate "MAX11801 based touchscreens"
436	depends on I2C
437	help
438	  Say Y here if you have a MAX11801 based touchscreen
439	  controller.
440
441	  If unsure, say N.
442
443	  To compile this driver as a module, choose M here: the
444	  module will be called max11801_ts.
445
446config TOUCHSCREEN_MCS5000
447	tristate "MELFAS MCS-5000 touchscreen"
448	depends on I2C
449	help
450	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
451	  chip in your system.
452
453	  If unsure, say N.
454
455	  To compile this driver as a module, choose M here: the
456	  module will be called mcs5000_ts.
457
458config TOUCHSCREEN_MMS114
459	tristate "MELFAS MMS114 touchscreen"
460	depends on I2C
461	help
462	  Say Y here if you have the MELFAS MMS114 touchscreen controller
463	  chip in your system.
464
465	  If unsure, say N.
466
467	  To compile this driver as a module, choose M here: the
468	  module will be called mms114.
469
470config TOUCHSCREEN_MTOUCH
471	tristate "MicroTouch serial touchscreens"
472	select SERIO
473	help
474	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
475	  your system.
476
477	  If unsure, say N.
478
479	  To compile this driver as a module, choose M here: the
480	  module will be called mtouch.
481
482config TOUCHSCREEN_IMX6UL_TSC
483	tristate "Freescale i.MX6UL touchscreen controller"
484	depends on (OF && GPIOLIB) || COMPILE_TEST
485	help
486	  Say Y here if you have a Freescale i.MX6UL, and want to
487	  use the internal touchscreen controller.
488
489	  If unsure, say N.
490
491	  To compile this driver as a module, choose M here: the
492	  module will be called imx6ul_tsc.
493
494config TOUCHSCREEN_INEXIO
495	tristate "iNexio serial touchscreens"
496	select SERIO
497	help
498	  Say Y here if you have an iNexio serial touchscreen connected to
499	  your system.
500
501	  If unsure, say N.
502
503	  To compile this driver as a module, choose M here: the
504	  module will be called inexio.
505
506config TOUCHSCREEN_INTEL_MID
507	tristate "Intel MID platform resistive touchscreen"
508	depends on INTEL_SCU_IPC
509	help
510	  Say Y here if you have a Intel MID based touchscreen in
511	  your system.
512
513	  If unsure, say N.
514
515	  To compile this driver as a module, choose M here: the
516	  module will be called intel_mid_touch.
517
518config TOUCHSCREEN_MK712
519	tristate "ICS MicroClock MK712 touchscreen"
520	help
521	  Say Y here if you have the ICS MicroClock MK712 touchscreen
522	  controller chip in your system.
523
524	  If unsure, say N.
525
526	  To compile this driver as a module, choose M here: the
527	  module will be called mk712.
528
529config TOUCHSCREEN_HP600
530	tristate "HP Jornada 6xx touchscreen"
531	depends on SH_HP6XX && SH_ADC
532	help
533	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
534          support the built-in touchscreen.
535
536	  To compile this driver as a module, choose M here: the
537	  module will be called hp680_ts_input.
538
539config TOUCHSCREEN_HP7XX
540	tristate "HP Jornada 7xx touchscreen"
541	depends on SA1100_JORNADA720_SSP
542	help
543	  Say Y here if you have a HP Jornada 710/720/728 and want
544	  to support the built-in touchscreen.
545
546	  To compile this driver as a module, choose M here: the
547	  module will be called jornada720_ts.
548
549config TOUCHSCREEN_IPAQ_MICRO
550	tristate "HP iPAQ Atmel Micro ASIC touchscreen"
551	depends on MFD_IPAQ_MICRO
552	help
553	  Say Y here to enable support for the touchscreen attached to
554	  the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
555
556	  If unsure, say N.
557
558	  To compile this driver as a module, choose M here: the
559	  module will be called ipaq-micro-ts.
560
561config TOUCHSCREEN_HTCPEN
562	tristate "HTC Shift X9500 touchscreen"
563	depends on ISA
564	help
565	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
566	  Clio / Shangrila and want to support the built-in touchscreen.
567
568	  If unsure, say N.
569
570	  To compile this driver as a module, choose M here: the
571	  module will be called htcpen.
572
573config TOUCHSCREEN_PENMOUNT
574	tristate "Penmount serial touchscreen"
575	select SERIO
576	help
577	  Say Y here if you have a Penmount serial touchscreen connected to
578	  your system.
579
580	  If unsure, say N.
581
582	  To compile this driver as a module, choose M here: the
583	  module will be called penmount.
584
585config TOUCHSCREEN_EDT_FT5X06
586	tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
587	depends on I2C
588	help
589	  Say Y here if you have an EDT "Polytouch" touchscreen based
590	  on the FocalTech FT5x06 family of controllers connected to
591	  your system.
592
593	  If unsure, say N.
594
595	  To compile this driver as a module, choose M here: the
596	  module will be called edt-ft5x06.
597
598config TOUCHSCREEN_MIGOR
599	tristate "Renesas MIGO-R touchscreen"
600	depends on SH_MIGOR && I2C
601	help
602	  Say Y here to enable MIGO-R touchscreen support.
603
604	  If unsure, say N.
605
606	  To compile this driver as a module, choose M here: the
607	  module will be called migor_ts.
608
609config TOUCHSCREEN_TOUCHRIGHT
610	tristate "Touchright serial touchscreen"
611	select SERIO
612	help
613	  Say Y here if you have a Touchright 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 touchright.
620
621config TOUCHSCREEN_TOUCHWIN
622	tristate "Touchwin serial touchscreen"
623	select SERIO
624	help
625	  Say Y here if you have a Touchwin serial touchscreen connected to
626	  your system.
627
628	  If unsure, say N.
629
630	  To compile this driver as a module, choose M here: the
631	  module will be called touchwin.
632
633config TOUCHSCREEN_TI_AM335X_TSC
634	tristate "TI Touchscreen Interface"
635	depends on MFD_TI_AM335X_TSCADC
636	help
637	  Say Y here if you have 4/5/8 wire touchscreen controller
638	  to be connected to the ADC controller on your TI AM335x SoC.
639
640	  If unsure, say N.
641
642	  To compile this driver as a module, choose M here: the
643	  module will be called ti_am335x_tsc.
644
645config TOUCHSCREEN_UCB1400
646	tristate "Philips UCB1400 touchscreen"
647	depends on AC97_BUS
648	depends on UCB1400_CORE
649	help
650	  This enables support for the Philips UCB1400 touchscreen interface.
651	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
652	  will be initialized only after the ALSA subsystem has been
653	  brought up and the UCB1400 detected.  You therefore have to
654	  configure ALSA support as well (either built-in or modular,
655	  independently of whether this driver is itself built-in or
656	  modular) for this driver to work.
657
658	  To compile this driver as a module, choose M here: the
659	  module will be called ucb1400_ts.
660
661config TOUCHSCREEN_PIXCIR
662	tristate "PIXCIR I2C touchscreens"
663	depends on I2C
664	help
665	  Say Y here if you have a pixcir i2c touchscreen
666	  controller.
667
668	  If unsure, say N.
669
670	  To compile this driver as a module, choose M here: the
671	  module will be called pixcir_i2c_ts.
672
673config TOUCHSCREEN_WDT87XX_I2C
674	tristate "Weida HiTech I2C touchscreen"
675	depends on I2C
676	help
677	  Say Y here if you have a Weida WDT87XX I2C touchscreen
678	  connected to your system.
679
680	  If unsure, say N.
681
682	  To compile this driver as a module, choose M here: the
683	  module will be called wdt87xx_i2c.
684
685config TOUCHSCREEN_WM831X
686	tristate "Support for WM831x touchscreen controllers"
687	depends on MFD_WM831X
688	help
689	  This enables support for the touchscreen controller on the WM831x
690	  series of PMICs.
691
692	  To compile this driver as a module, choose M here: the
693	  module will be called wm831x-ts.
694
695config TOUCHSCREEN_WM97XX
696	tristate "Support for WM97xx AC97 touchscreen controllers"
697	depends on AC97_BUS
698	help
699	  Say Y here if you have a Wolfson Microelectronics WM97xx
700	  touchscreen connected to your system. Note that this option
701	  only enables core driver, you will also need to select
702	  support for appropriate chip below.
703
704	  If unsure, say N.
705
706	  To compile this driver as a module, choose M here: the
707	  module will be called wm97xx-ts.
708
709config TOUCHSCREEN_WM9705
710	bool "WM9705 Touchscreen interface support"
711	depends on TOUCHSCREEN_WM97XX
712	default y
713	help
714	  Say Y here to enable support for the Wolfson Microelectronics
715	  WM9705 touchscreen controller.
716
717config TOUCHSCREEN_WM9712
718	bool "WM9712 Touchscreen interface support"
719	depends on TOUCHSCREEN_WM97XX
720	default y
721	help
722	  Say Y here to enable support for the Wolfson Microelectronics
723	  WM9712 touchscreen controller.
724
725config TOUCHSCREEN_WM9713
726	bool "WM9713 Touchscreen interface support"
727	depends on TOUCHSCREEN_WM97XX
728	default y
729	help
730	  Say Y here to enable support for the Wolfson Microelectronics
731	  WM9713 touchscreen controller.
732
733config TOUCHSCREEN_WM97XX_ATMEL
734	tristate "WM97xx Atmel accelerated touch"
735	depends on TOUCHSCREEN_WM97XX && AVR32
736	help
737	  Say Y here for support for streaming mode with WM97xx touchscreens
738	  on Atmel AT91 or AVR32 systems with an AC97C module.
739
740	  Be aware that this will use channel B in the controller for
741	  streaming data, this must not conflict with other AC97C drivers.
742
743	  If unsure, say N.
744
745	  To compile this driver as a module, choose M here: the module will
746	  be called atmel-wm97xx.
747
748config TOUCHSCREEN_WM97XX_MAINSTONE
749	tristate "WM97xx Mainstone/Palm accelerated touch"
750	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
751	help
752	  Say Y here for support for streaming mode with WM97xx touchscreens
753	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
754
755	  If unsure, say N.
756
757	  To compile this driver as a module, choose M here: the
758	  module will be called mainstone-wm97xx.
759
760config TOUCHSCREEN_WM97XX_ZYLONITE
761	tristate "Zylonite accelerated touch"
762	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
763	select TOUCHSCREEN_WM9713
764	help
765	  Say Y here for support for streaming mode with the touchscreen
766	  on Zylonite systems.
767
768	  If unsure, say N.
769
770	  To compile this driver as a module, choose M here: the
771	  module will be called zylonite-wm97xx.
772
773config TOUCHSCREEN_USB_COMPOSITE
774	tristate "USB Touchscreen Driver"
775	depends on USB_ARCH_HAS_HCD
776	select USB
777	help
778	  USB Touchscreen driver for:
779	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
780	  - PanJit TouchSet USB
781	  - 3M MicroTouch USB (EX II series)
782	  - ITM
783	  - some other eTurboTouch
784	  - Gunze AHL61
785	  - DMC TSC-10/25
786	  - IRTOUCHSYSTEMS/UNITOP
787	  - IdealTEK URTC1000
788	  - GoTop Super_Q2/GogoPen/PenPower tablets
789	  - JASTEC USB Touch Controller/DigiTech DTR-02U
790	  - Zytronic controllers
791	  - Elo TouchSystems 2700 IntelliTouch
792	  - EasyTouch USB Touch Controller from Data Modul
793	  - e2i (Mimo monitors)
794
795	  Have a look at <http://linux.chapter7.ch/touchkit/> for
796	  a usage description and the required user-space stuff.
797
798	  To compile this driver as a module, choose M here: the
799	  module will be called usbtouchscreen.
800
801config TOUCHSCREEN_MC13783
802	tristate "Freescale MC13783 touchscreen input driver"
803	depends on MFD_MC13XXX
804	help
805	  Say Y here if you have an Freescale MC13783 PMIC on your
806	  board and want to use its touchscreen
807
808	  If unsure, say N.
809
810	  To compile this driver as a module, choose M here: the
811	  module will be called mc13783_ts.
812
813config TOUCHSCREEN_USB_EGALAX
814	default y
815	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
816	depends on TOUCHSCREEN_USB_COMPOSITE
817
818config TOUCHSCREEN_USB_PANJIT
819	default y
820	bool "PanJit device support" if EXPERT
821	depends on TOUCHSCREEN_USB_COMPOSITE
822
823config TOUCHSCREEN_USB_3M
824	default y
825	bool "3M/Microtouch EX II series device support" if EXPERT
826	depends on TOUCHSCREEN_USB_COMPOSITE
827
828config TOUCHSCREEN_USB_ITM
829	default y
830	bool "ITM device support" if EXPERT
831	depends on TOUCHSCREEN_USB_COMPOSITE
832
833config TOUCHSCREEN_USB_ETURBO
834	default y
835	bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
836	depends on TOUCHSCREEN_USB_COMPOSITE
837
838config TOUCHSCREEN_USB_GUNZE
839	default y
840	bool "Gunze AHL61 device support" if EXPERT
841	depends on TOUCHSCREEN_USB_COMPOSITE
842
843config TOUCHSCREEN_USB_DMC_TSC10
844	default y
845	bool "DMC TSC-10/25 device support" if EXPERT
846	depends on TOUCHSCREEN_USB_COMPOSITE
847
848config TOUCHSCREEN_USB_IRTOUCH
849	default y
850	bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
851	depends on TOUCHSCREEN_USB_COMPOSITE
852
853config TOUCHSCREEN_USB_IDEALTEK
854	default y
855	bool "IdealTEK URTC1000 device support" if EXPERT
856	depends on TOUCHSCREEN_USB_COMPOSITE
857
858config TOUCHSCREEN_USB_GENERAL_TOUCH
859	default y
860	bool "GeneralTouch Touchscreen device support" if EXPERT
861	depends on TOUCHSCREEN_USB_COMPOSITE
862
863config TOUCHSCREEN_USB_GOTOP
864	default y
865	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
866	depends on TOUCHSCREEN_USB_COMPOSITE
867
868config TOUCHSCREEN_USB_JASTEC
869	default y
870	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
871	depends on TOUCHSCREEN_USB_COMPOSITE
872
873config TOUCHSCREEN_USB_ELO
874	default y
875	bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
876	depends on TOUCHSCREEN_USB_COMPOSITE
877
878config TOUCHSCREEN_USB_E2I
879	default y
880	bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
881	depends on TOUCHSCREEN_USB_COMPOSITE
882
883config TOUCHSCREEN_USB_ZYTRONIC
884	default y
885	bool "Zytronic controller" if EXPERT
886	depends on TOUCHSCREEN_USB_COMPOSITE
887
888config TOUCHSCREEN_USB_ETT_TC45USB
889	default y
890	bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
891	depends on TOUCHSCREEN_USB_COMPOSITE
892
893config TOUCHSCREEN_USB_NEXIO
894	default y
895	bool "NEXIO/iNexio device support" if EXPERT
896	depends on TOUCHSCREEN_USB_COMPOSITE
897
898config TOUCHSCREEN_USB_EASYTOUCH
899	default y
900	bool "EasyTouch USB Touch controller device support" if EMBEDDED
901	depends on TOUCHSCREEN_USB_COMPOSITE
902	help
903	  Say Y here if you have an EasyTouch USB Touch controller.
904	  If unsure, say N.
905
906config TOUCHSCREEN_TOUCHIT213
907	tristate "Sahara TouchIT-213 touchscreen"
908	select SERIO
909	help
910	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.
911
912	  If unsure, say N.
913
914	  To compile this driver as a module, choose M here: the
915	  module will be called touchit213.
916
917config TOUCHSCREEN_TSC_SERIO
918	tristate "TSC-10/25/40 serial touchscreen support"
919	select SERIO
920	help
921	  Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
922	  to your system.
923
924	  If unsure, say N.
925
926	  To compile this driver as a module, choose M here: the
927	  module will be called tsc40.
928
929config TOUCHSCREEN_TSC2005
930	tristate "TSC2005 based touchscreens"
931	depends on SPI_MASTER
932	select REGMAP_SPI
933	help
934	  Say Y here if you have a TSC2005 based touchscreen.
935
936	  If unsure, say N.
937
938	  To compile this driver as a module, choose M here: the
939	  module will be called tsc2005.
940
941config TOUCHSCREEN_TSC2007
942	tristate "TSC2007 based touchscreens"
943	depends on I2C
944	help
945	  Say Y here if you have a TSC2007 based touchscreen.
946
947	  If unsure, say N.
948
949	  To compile this driver as a module, choose M here: the
950	  module will be called tsc2007.
951
952config TOUCHSCREEN_W90X900
953	tristate "W90P910 touchscreen driver"
954	depends on ARCH_W90X900
955	help
956	  Say Y here if you have a W90P910 based touchscreen.
957
958	  To compile this driver as a module, choose M here: the
959	  module will be called w90p910_ts.
960
961config TOUCHSCREEN_PCAP
962	tristate "Motorola PCAP touchscreen"
963	depends on EZX_PCAP
964	help
965	  Say Y here if you have a Motorola EZX telephone and
966	  want to enable support for the built-in touchscreen.
967
968	  To compile this driver as a module, choose M here: the
969	  module will be called pcap_ts.
970
971config TOUCHSCREEN_ST1232
972	tristate "Sitronix ST1232 touchscreen controllers"
973	depends on I2C
974	help
975	  Say Y here if you want to support Sitronix ST1232
976	  touchscreen controller.
977
978	  If unsure, say N.
979
980	  To compile this driver as a module, choose M here: the
981	  module will be called st1232_ts.
982
983config TOUCHSCREEN_STMPE
984	tristate "STMicroelectronics STMPE touchscreens"
985	depends on MFD_STMPE
986	depends on (OF || COMPILE_TEST)
987	help
988	  Say Y here if you want support for STMicroelectronics
989	  STMPE touchscreen controllers.
990
991	  To compile this driver as a module, choose M here: the
992	  module will be called stmpe-ts.
993
994config TOUCHSCREEN_SUN4I
995	tristate "Allwinner sun4i resistive touchscreen controller support"
996	depends on ARCH_SUNXI || COMPILE_TEST
997	depends on HWMON
998	depends on THERMAL || !THERMAL_OF
999	help
1000	  This selects support for the resistive touchscreen controller
1001	  found on Allwinner sunxi SoCs.
1002
1003	  To compile this driver as a module, choose M here: the
1004	  module will be called sun4i-ts.
1005
1006config TOUCHSCREEN_SUR40
1007	tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
1008	depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1009	depends on VIDEO_V4L2
1010	select INPUT_POLLDEV
1011	select VIDEOBUF2_DMA_SG
1012	help
1013	  Say Y here if you want support for the Samsung SUR40 touchscreen
1014	  (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
1015
1016	  To compile this driver as a module, choose M here: the
1017	  module will be called sur40.
1018
1019config TOUCHSCREEN_SX8654
1020	tristate "Semtech SX8654 touchscreen"
1021	depends on I2C
1022	help
1023	  Say Y here if you have a Semtech SX8654 touchscreen controller.
1024
1025	  If unsure, say N
1026
1027	  To compile this driver as a module, choose M here: the
1028	  module will be called sx8654.
1029
1030config TOUCHSCREEN_TPS6507X
1031	tristate "TPS6507x based touchscreens"
1032	depends on I2C
1033	select INPUT_POLLDEV
1034	help
1035	  Say Y here if you have a TPS6507x based touchscreen
1036	  controller.
1037
1038	  If unsure, say N.
1039
1040	  To compile this driver as a module, choose M here: the
1041	  module will be called tps6507x_ts.
1042
1043config TOUCHSCREEN_ZFORCE
1044	tristate "Neonode zForce infrared touchscreens"
1045	depends on I2C
1046	depends on GPIOLIB || COMPILE_TEST
1047	help
1048	  Say Y here if you have a touchscreen using the zforce
1049	  infraread technology from Neonode.
1050
1051	  If unsure, say N.
1052
1053	  To compile this driver as a module, choose M here: the
1054	  module will be called zforce_ts.
1055
1056config TOUCHSCREEN_COLIBRI_VF50
1057	tristate "Toradex Colibri on board touchscreen driver"
1058	depends on GPIOLIB && IIO && VF610_ADC
1059	help
1060	  Say Y here if you have a Colibri VF50 and plan to use
1061	  the on-board provided 4-wire touchscreen driver.
1062
1063	  If unsure, say N.
1064
1065	  To compile this driver as a module, choose M here: the
1066	  module will be called colibri_vf50_ts.
1067
1068endif
1069