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_88PM860X
15	tristate "Marvell 88PM860x touchscreen"
16	depends on MFD_88PM860X
17	help
18	  Say Y here if you have a 88PM860x PMIC and want to enable
19	  support for the built-in touchscreen.
20
21	  If unsure, say N.
22
23	  To compile this driver as a module, choose M here: the
24	  module will be called 88pm860x-ts.
25
26config TOUCHSCREEN_ADS7846
27	tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens"
28	depends on SPI_MASTER
29	depends on HWMON = n || HWMON
30	help
31	  Say Y here if you have a touchscreen interface using the
32	  ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
33	  and your board-specific setup code includes that in its
34	  table of SPI devices.
35
36	  If HWMON is selected, and the driver is told the reference voltage
37	  on your board, you will also get hwmon interfaces for the voltage
38	  (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
39
40	  If unsure, say N (but it's safe to say "Y").
41
42	  To compile this driver as a module, choose M here: the
43	  module will be called ads7846.
44
45config TOUCHSCREEN_AD7877
46	tristate "AD7877 based touchscreens"
47	depends on SPI_MASTER
48	help
49	  Say Y here if you have a touchscreen interface using the
50	  AD7877 controller, and your board-specific initialization
51	  code includes that in its table of SPI devices.
52
53	  If unsure, say N (but it's safe to say "Y").
54
55	  To compile this driver as a module, choose M here: the
56	  module will be called ad7877.
57
58config TOUCHSCREEN_AD7879
59	tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
60	help
61	  Say Y here if you want to support a touchscreen interface using
62	  the AD7879-1/AD7889-1 controller.
63
64	  You should select a bus connection too.
65
66	  To compile this driver as a module, choose M here: the
67	  module will be called ad7879.
68
69config TOUCHSCREEN_AD7879_I2C
70	tristate "support I2C bus connection"
71	depends on TOUCHSCREEN_AD7879 && I2C
72	help
73	  Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
74
75	  To compile this driver as a module, choose M here: the
76	  module will be called ad7879-i2c.
77
78config TOUCHSCREEN_AD7879_SPI
79	tristate "support SPI bus connection"
80	depends on TOUCHSCREEN_AD7879 && SPI_MASTER
81	help
82	  Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
83
84	  If unsure, say N (but it's safe to say "Y").
85
86	  To compile this driver as a module, choose M here: the
87	  module will be called ad7879-spi.
88
89config TOUCHSCREEN_ATMEL_MXT
90	tristate "Atmel mXT I2C Touchscreen"
91	depends on I2C
92	help
93	  Say Y here if you have Atmel mXT series I2C touchscreen,
94	  such as AT42QT602240/ATMXT224, connected to your system.
95
96	  If unsure, say N.
97
98	  To compile this driver as a module, choose M here: the
99	  module will be called atmel_mxt_ts.
100
101config TOUCHSCREEN_AUO_PIXCIR
102	tristate "AUO in-cell touchscreen using Pixcir ICs"
103	depends on I2C
104	depends on GPIOLIB
105	help
106	  Say Y here if you have a AUO display with in-cell touchscreen
107	  using Pixcir ICs.
108
109	  If unsure, say N.
110
111	  To compile this driver as a module, choose M here: the
112	  module will be called auo-pixcir-ts.
113
114config TOUCHSCREEN_BITSY
115	tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
116	depends on SA1100_BITSY
117	select SERIO
118	help
119	  Say Y here if you have the h3600 (Bitsy) touchscreen.
120
121	  If unsure, say N.
122
123	  To compile this driver as a module, choose M here: the
124	  module will be called h3600_ts_input.
125
126config TOUCHSCREEN_BU21013
127	tristate "BU21013 based touch panel controllers"
128	depends on I2C
129	help
130	  Say Y here if you have a bu21013 touchscreen connected to
131	  your system.
132
133	  If unsure, say N.
134
135	  To compile this driver as a module, choose M here: the
136	  module will be called bu21013_ts.
137
138config TOUCHSCREEN_CY8CTMG110
139	tristate "cy8ctmg110 touchscreen"
140	depends on I2C
141	depends on GPIOLIB
142	help
143	  Say Y here if you have a cy8ctmg110 capacitive touchscreen on
144	  an AAVA device.
145
146	  If unsure, say N.
147
148	  To compile this driver as a module, choose M here: the
149	  module will be called cy8ctmg110_ts.
150
151config TOUCHSCREEN_CYTTSP_CORE
152	tristate "Cypress TTSP touchscreen"
153	help
154	  Say Y here if you have a touchscreen using controller from
155	  the Cypress TrueTouch(tm) Standard Product family connected
156	  to your system. You will also need to select appropriate
157	  bus connection below.
158
159	  If unsure, say N.
160
161	  To compile this driver as a module, choose M here: the
162	  module will be called cyttsp_core.
163
164config TOUCHSCREEN_CYTTSP_I2C
165	tristate "support I2C bus connection"
166	depends on TOUCHSCREEN_CYTTSP_CORE && I2C
167	help
168	  Say Y here if the touchscreen is connected via I2C bus.
169
170	  To compile this driver as a module, choose M here: the
171	  module will be called cyttsp_i2c.
172
173config TOUCHSCREEN_CYTTSP_SPI
174	tristate "support SPI bus connection"
175	depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
176	help
177	  Say Y here if the touchscreen is connected via SPI bus.
178
179	  To compile this driver as a module, choose M here: the
180	  module will be called cyttsp_spi.
181
182config TOUCHSCREEN_DA9034
183	tristate "Touchscreen support for Dialog Semiconductor DA9034"
184	depends on PMIC_DA903X
185	default y
186	help
187	  Say Y here to enable the support for the touchscreen found
188	  on Dialog Semiconductor DA9034 PMIC.
189
190	  If unsure, say N.
191
192	  To compile this driver as a module, choose M here: the
193	  module will be called da9034-ts.
194
195config TOUCHSCREEN_DA9052
196	tristate "Dialog DA9052/DA9053 TSI"
197	depends on PMIC_DA9052
198	help
199	  Say Y here to support the touchscreen found on Dialog Semiconductor
200	  DA9052-BC and DA9053-AA/Bx PMICs.
201
202	  If unsure, say N.
203
204	  To compile this driver as a module, choose M here: the
205	  module will be called da9052_tsi.
206
207config TOUCHSCREEN_DYNAPRO
208	tristate "Dynapro serial touchscreen"
209	select SERIO
210	help
211	  Say Y here if you have a Dynapro serial touchscreen connected to
212	  your system.
213
214	  If unsure, say N.
215
216	  To compile this driver as a module, choose M here: the
217	  module will be called dynapro.
218
219config TOUCHSCREEN_HAMPSHIRE
220	tristate "Hampshire serial touchscreen"
221	select SERIO
222	help
223	  Say Y here if you have a Hampshire serial touchscreen connected to
224	  your system.
225
226	  If unsure, say N.
227
228	  To compile this driver as a module, choose M here: the
229	  module will be called hampshire.
230
231config TOUCHSCREEN_EETI
232	tristate "EETI touchscreen panel support"
233	depends on I2C
234	help
235	  Say Y here to enable support for I2C connected EETI touch panels.
236
237	  To compile this driver as a module, choose M here: the
238	  module will be called eeti_ts.
239
240config TOUCHSCREEN_EGALAX
241	tristate "EETI eGalax multi-touch panel support"
242	depends on I2C && OF
243	help
244	  Say Y here to enable support for I2C connected EETI
245	  eGalax multi-touch panels.
246
247	  To compile this driver as a module, choose M here: the
248	  module will be called egalax_ts.
249
250config TOUCHSCREEN_FUJITSU
251	tristate "Fujitsu serial touchscreen"
252	select SERIO
253	help
254	  Say Y here if you have the Fujitsu touchscreen (such as one
255	  installed in Lifebook P series laptop) connected to your
256	  system.
257
258	  If unsure, say N.
259
260	  To compile this driver as a module, choose M here: the
261	  module will be called fujitsu-ts.
262
263config TOUCHSCREEN_ILI210X
264	tristate "Ilitek ILI210X based touchscreen"
265	depends on I2C
266	help
267	  Say Y here if you have a ILI210X based touchscreen
268	  controller. This driver supports models ILI2102,
269	  ILI2102s, ILI2103, ILI2103s and ILI2105.
270	  Such kind of chipsets can be found in Amazon Kindle Fire
271	  touchscreens.
272
273	  If unsure, say N.
274
275	  To compile this driver as a module, choose M here: the
276	  module will be called ili210x.
277
278config TOUCHSCREEN_S3C2410
279	tristate "Samsung S3C2410/generic touchscreen input driver"
280	depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
281	select S3C_ADC
282	help
283	  Say Y here if you have the s3c2410 touchscreen.
284
285	  If unsure, say N.
286
287	  To compile this driver as a module, choose M here: the
288	  module will be called s3c2410_ts.
289
290config TOUCHSCREEN_GUNZE
291	tristate "Gunze AHL-51S touchscreen"
292	select SERIO
293	help
294	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
295	  your system.
296
297	  If unsure, say N.
298
299	  To compile this driver as a module, choose M here: the
300	  module will be called gunze.
301
302config TOUCHSCREEN_ELO
303	tristate "Elo serial touchscreens"
304	select SERIO
305	help
306	  Say Y here if you have an Elo serial touchscreen connected to
307	  your system.
308
309	  If unsure, say N.
310
311	  To compile this driver as a module, choose M here: the
312	  module will be called elo.
313
314config TOUCHSCREEN_WACOM_W8001
315	tristate "Wacom W8001 penabled serial touchscreen"
316	select SERIO
317	help
318	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
319	  connected to your system.
320
321	  If unsure, say N.
322
323	  To compile this driver as a module, choose M here: the
324	  module will be called wacom_w8001.
325
326config TOUCHSCREEN_WACOM_I2C
327	tristate "Wacom Tablet support (I2C)"
328	depends on I2C
329	help
330	  Say Y here if you want to use the I2C version of the Wacom
331	  Pen Tablet.
332
333	  If unsure, say N.
334
335	  To compile this driver as a module, choose M here: the module
336	  will be called wacom_i2c.
337
338config TOUCHSCREEN_LPC32XX
339	tristate "LPC32XX touchscreen controller"
340	depends on ARCH_LPC32XX
341	help
342	  Say Y here if you have a LPC32XX device and want
343	  to support the built-in touchscreen.
344
345	  To compile this driver as a module, choose M here: the
346	  module will be called lpc32xx_ts.
347
348config TOUCHSCREEN_MAX11801
349	tristate "MAX11801 based touchscreens"
350	depends on I2C
351	help
352	  Say Y here if you have a MAX11801 based touchscreen
353	  controller.
354
355	  If unsure, say N.
356
357	  To compile this driver as a module, choose M here: the
358	  module will be called max11801_ts.
359
360config TOUCHSCREEN_MCS5000
361	tristate "MELFAS MCS-5000 touchscreen"
362	depends on I2C
363	help
364	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
365	  chip in your system.
366
367	  If unsure, say N.
368
369	  To compile this driver as a module, choose M here: the
370	  module will be called mcs5000_ts.
371
372config TOUCHSCREEN_MMS114
373	tristate "MELFAS MMS114 touchscreen"
374	depends on I2C
375	help
376	  Say Y here if you have the MELFAS MMS114 touchscreen controller
377	  chip in your system.
378
379	  If unsure, say N.
380
381	  To compile this driver as a module, choose M here: the
382	  module will be called mms114.
383
384config TOUCHSCREEN_MTOUCH
385	tristate "MicroTouch serial touchscreens"
386	select SERIO
387	help
388	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
389	  your system.
390
391	  If unsure, say N.
392
393	  To compile this driver as a module, choose M here: the
394	  module will be called mtouch.
395
396config TOUCHSCREEN_INEXIO
397	tristate "iNexio serial touchscreens"
398	select SERIO
399	help
400	  Say Y here if you have an iNexio serial touchscreen connected to
401	  your system.
402
403	  If unsure, say N.
404
405	  To compile this driver as a module, choose M here: the
406	  module will be called inexio.
407
408config TOUCHSCREEN_INTEL_MID
409	tristate "Intel MID platform resistive touchscreen"
410	depends on INTEL_SCU_IPC
411	help
412	  Say Y here if you have a Intel MID based touchscreen in
413	  your system.
414
415	  If unsure, say N.
416
417	  To compile this driver as a module, choose M here: the
418	  module will be called intel_mid_touch.
419
420config TOUCHSCREEN_MK712
421	tristate "ICS MicroClock MK712 touchscreen"
422	help
423	  Say Y here if you have the ICS MicroClock MK712 touchscreen
424	  controller chip in your system.
425
426	  If unsure, say N.
427
428	  To compile this driver as a module, choose M here: the
429	  module will be called mk712.
430
431config TOUCHSCREEN_HP600
432	tristate "HP Jornada 6xx touchscreen"
433	depends on SH_HP6XX && SH_ADC
434	help
435	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
436          support the built-in touchscreen.
437
438	  To compile this driver as a module, choose M here: the
439	  module will be called hp680_ts_input.
440
441config TOUCHSCREEN_HP7XX
442	tristate "HP Jornada 7xx touchscreen"
443	depends on SA1100_JORNADA720_SSP
444	help
445	  Say Y here if you have a HP Jornada 710/720/728 and want
446	  to support the built-in touchscreen.
447
448	  To compile this driver as a module, choose M here: the
449	  module will be called jornada720_ts.
450
451config TOUCHSCREEN_HTCPEN
452	tristate "HTC Shift X9500 touchscreen"
453	depends on ISA
454	help
455	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
456	  Clio / Shangrila and want to support the built-in touchscreen.
457
458	  If unsure, say N.
459
460	  To compile this driver as a module, choose M here: the
461	  module will be called htcpen.
462
463config TOUCHSCREEN_PENMOUNT
464	tristate "Penmount serial touchscreen"
465	select SERIO
466	help
467	  Say Y here if you have a Penmount serial touchscreen connected to
468	  your system.
469
470	  If unsure, say N.
471
472	  To compile this driver as a module, choose M here: the
473	  module will be called penmount.
474
475config TOUCHSCREEN_EDT_FT5X06
476	tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
477	depends on I2C
478	help
479	  Say Y here if you have an EDT "Polytouch" touchscreen based
480	  on the FocalTech FT5x06 family of controllers connected to
481	  your system.
482
483	  If unsure, say N.
484
485	  To compile this driver as a module, choose M here: the
486	  module will be called edt-ft5x06.
487
488config TOUCHSCREEN_MIGOR
489	tristate "Renesas MIGO-R touchscreen"
490	depends on SH_MIGOR && I2C
491	help
492	  Say Y here to enable MIGO-R touchscreen support.
493
494	  If unsure, say N.
495
496	  To compile this driver as a module, choose M here: the
497	  module will be called migor_ts.
498
499config TOUCHSCREEN_TNETV107X
500	tristate "TI TNETV107X touchscreen support"
501	depends on ARCH_DAVINCI_TNETV107X
502	help
503	  Say Y here if you want to use the TNETV107X touchscreen.
504
505	  To compile this driver as a module, choose M here: the
506	  module will be called tnetv107x-ts.
507
508config TOUCHSCREEN_TOUCHRIGHT
509	tristate "Touchright serial touchscreen"
510	select SERIO
511	help
512	  Say Y here if you have a Touchright serial touchscreen connected to
513	  your system.
514
515	  If unsure, say N.
516
517	  To compile this driver as a module, choose M here: the
518	  module will be called touchright.
519
520config TOUCHSCREEN_TOUCHWIN
521	tristate "Touchwin serial touchscreen"
522	select SERIO
523	help
524	  Say Y here if you have a Touchwin serial touchscreen connected to
525	  your system.
526
527	  If unsure, say N.
528
529	  To compile this driver as a module, choose M here: the
530	  module will be called touchwin.
531
532config TOUCHSCREEN_TI_TSCADC
533	tristate "TI Touchscreen Interface"
534	depends on ARCH_OMAP2PLUS
535	help
536	  Say Y here if you have 4/5/8 wire touchscreen controller
537	  to be connected to the ADC controller on your TI AM335x SoC.
538
539	  If unsure, say N.
540
541	  To compile this driver as a module, choose M here: the
542	  module will be called ti_tscadc.
543
544config TOUCHSCREEN_ATMEL_TSADCC
545	tristate "Atmel Touchscreen Interface"
546	depends on ARCH_AT91
547	help
548	  Say Y here if you have a 4-wire touchscreen connected to the
549          ADC Controller on your Atmel SoC.
550
551	  If unsure, say N.
552
553	  To compile this driver as a module, choose M here: the
554	  module will be called atmel_tsadcc.
555
556config TOUCHSCREEN_UCB1400
557	tristate "Philips UCB1400 touchscreen"
558	depends on AC97_BUS
559	depends on UCB1400_CORE
560	help
561	  This enables support for the Philips UCB1400 touchscreen interface.
562	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
563	  will be initialized only after the ALSA subsystem has been
564	  brought up and the UCB1400 detected.  You therefore have to
565	  configure ALSA support as well (either built-in or modular,
566	  independently of whether this driver is itself built-in or
567	  modular) for this driver to work.
568
569	  To compile this driver as a module, choose M here: the
570	  module will be called ucb1400_ts.
571
572config TOUCHSCREEN_PIXCIR
573	tristate "PIXCIR I2C touchscreens"
574	depends on I2C
575	help
576	  Say Y here if you have a pixcir i2c touchscreen
577	  controller.
578
579	  If unsure, say N.
580
581	  To compile this driver as a module, choose M here: the
582	  module will be called pixcir_i2c_ts.
583
584config TOUCHSCREEN_WM831X
585	tristate "Support for WM831x touchscreen controllers"
586	depends on MFD_WM831X
587	help
588	  This enables support for the touchscreen controller on the WM831x
589	  series of PMICs.
590
591	  To compile this driver as a module, choose M here: the
592	  module will be called wm831x-ts.
593
594config TOUCHSCREEN_WM97XX
595	tristate "Support for WM97xx AC97 touchscreen controllers"
596	depends on AC97_BUS
597	help
598	  Say Y here if you have a Wolfson Microelectronics WM97xx
599	  touchscreen connected to your system. Note that this option
600	  only enables core driver, you will also need to select
601	  support for appropriate chip below.
602
603	  If unsure, say N.
604
605	  To compile this driver as a module, choose M here: the
606	  module will be called wm97xx-ts.
607
608config TOUCHSCREEN_WM9705
609	bool "WM9705 Touchscreen interface support"
610	depends on TOUCHSCREEN_WM97XX
611	default y
612	help
613	  Say Y here to enable support for the Wolfson Microelectronics
614	  WM9705 touchscreen controller.
615
616config TOUCHSCREEN_WM9712
617	bool "WM9712 Touchscreen interface support"
618	depends on TOUCHSCREEN_WM97XX
619	default y
620	help
621	  Say Y here to enable support for the Wolfson Microelectronics
622	  WM9712 touchscreen controller.
623
624config TOUCHSCREEN_WM9713
625	bool "WM9713 Touchscreen interface support"
626	depends on TOUCHSCREEN_WM97XX
627	default y
628	help
629	  Say Y here to enable support for the Wolfson Microelectronics
630	  WM9713 touchscreen controller.
631
632config TOUCHSCREEN_WM97XX_ATMEL
633	tristate "WM97xx Atmel accelerated touch"
634	depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
635	help
636	  Say Y here for support for streaming mode with WM97xx touchscreens
637	  on Atmel AT91 or AVR32 systems with an AC97C module.
638
639	  Be aware that this will use channel B in the controller for
640	  streaming data, this must not conflict with other AC97C drivers.
641
642	  If unsure, say N.
643
644	  To compile this driver as a module, choose M here: the module will
645	  be called atmel-wm97xx.
646
647config TOUCHSCREEN_WM97XX_MAINSTONE
648	tristate "WM97xx Mainstone/Palm accelerated touch"
649	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
650	help
651	  Say Y here for support for streaming mode with WM97xx touchscreens
652	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
653
654	  If unsure, say N.
655
656	  To compile this driver as a module, choose M here: the
657	  module will be called mainstone-wm97xx.
658
659config TOUCHSCREEN_WM97XX_ZYLONITE
660	tristate "Zylonite accelerated touch"
661	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
662	select TOUCHSCREEN_WM9713
663	help
664	  Say Y here for support for streaming mode with the touchscreen
665	  on Zylonite systems.
666
667	  If unsure, say N.
668
669	  To compile this driver as a module, choose M here: the
670	  module will be called zylonite-wm97xx.
671
672config TOUCHSCREEN_USB_COMPOSITE
673	tristate "USB Touchscreen Driver"
674	depends on USB_ARCH_HAS_HCD
675	select USB
676	help
677	  USB Touchscreen driver for:
678	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
679	  - PanJit TouchSet USB
680	  - 3M MicroTouch USB (EX II series)
681	  - ITM
682	  - some other eTurboTouch
683	  - Gunze AHL61
684	  - DMC TSC-10/25
685	  - IRTOUCHSYSTEMS/UNITOP
686	  - IdealTEK URTC1000
687	  - GoTop Super_Q2/GogoPen/PenPower tablets
688	  - JASTEC USB Touch Controller/DigiTech DTR-02U
689	  - Zytronic controllers
690	  - Elo TouchSystems 2700 IntelliTouch
691	  - EasyTouch USB Touch Controller from Data Modul
692	  - e2i (Mimo monitors)
693
694	  Have a look at <http://linux.chapter7.ch/touchkit/> for
695	  a usage description and the required user-space stuff.
696
697	  To compile this driver as a module, choose M here: the
698	  module will be called usbtouchscreen.
699
700config TOUCHSCREEN_MC13783
701	tristate "Freescale MC13783 touchscreen input driver"
702	depends on MFD_MC13783
703	help
704	  Say Y here if you have an Freescale MC13783 PMIC on your
705	  board and want to use its touchscreen
706
707	  If unsure, say N.
708
709	  To compile this driver as a module, choose M here: the
710	  module will be called mc13783_ts.
711
712config TOUCHSCREEN_USB_EGALAX
713	default y
714	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
715	depends on TOUCHSCREEN_USB_COMPOSITE
716
717config TOUCHSCREEN_USB_PANJIT
718	default y
719	bool "PanJit device support" if EXPERT
720	depends on TOUCHSCREEN_USB_COMPOSITE
721
722config TOUCHSCREEN_USB_3M
723	default y
724	bool "3M/Microtouch EX II series device support" if EXPERT
725	depends on TOUCHSCREEN_USB_COMPOSITE
726
727config TOUCHSCREEN_USB_ITM
728	default y
729	bool "ITM device support" if EXPERT
730	depends on TOUCHSCREEN_USB_COMPOSITE
731
732config TOUCHSCREEN_USB_ETURBO
733	default y
734	bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
735	depends on TOUCHSCREEN_USB_COMPOSITE
736
737config TOUCHSCREEN_USB_GUNZE
738	default y
739	bool "Gunze AHL61 device support" if EXPERT
740	depends on TOUCHSCREEN_USB_COMPOSITE
741
742config TOUCHSCREEN_USB_DMC_TSC10
743	default y
744	bool "DMC TSC-10/25 device support" if EXPERT
745	depends on TOUCHSCREEN_USB_COMPOSITE
746
747config TOUCHSCREEN_USB_IRTOUCH
748	default y
749	bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
750	depends on TOUCHSCREEN_USB_COMPOSITE
751
752config TOUCHSCREEN_USB_IDEALTEK
753	default y
754	bool "IdealTEK URTC1000 device support" if EXPERT
755	depends on TOUCHSCREEN_USB_COMPOSITE
756
757config TOUCHSCREEN_USB_GENERAL_TOUCH
758	default y
759	bool "GeneralTouch Touchscreen device support" if EXPERT
760	depends on TOUCHSCREEN_USB_COMPOSITE
761
762config TOUCHSCREEN_USB_GOTOP
763	default y
764	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
765	depends on TOUCHSCREEN_USB_COMPOSITE
766
767config TOUCHSCREEN_USB_JASTEC
768	default y
769	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
770	depends on TOUCHSCREEN_USB_COMPOSITE
771
772config TOUCHSCREEN_USB_ELO
773	default y
774	bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
775	depends on TOUCHSCREEN_USB_COMPOSITE
776
777config TOUCHSCREEN_USB_E2I
778	default y
779	bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
780	depends on TOUCHSCREEN_USB_COMPOSITE
781
782config TOUCHSCREEN_USB_ZYTRONIC
783	default y
784	bool "Zytronic controller" if EXPERT
785	depends on TOUCHSCREEN_USB_COMPOSITE
786
787config TOUCHSCREEN_USB_ETT_TC45USB
788	default y
789	bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
790	depends on TOUCHSCREEN_USB_COMPOSITE
791
792config TOUCHSCREEN_USB_NEXIO
793	default y
794	bool "NEXIO/iNexio device support" if EXPERT
795	depends on TOUCHSCREEN_USB_COMPOSITE
796
797config TOUCHSCREEN_USB_EASYTOUCH
798	default y
799	bool "EasyTouch USB Touch controller device support" if EMBEDDED
800	depends on TOUCHSCREEN_USB_COMPOSITE
801	help
802	  Say Y here if you have an EasyTouch USB Touch controller.
803	  If unsure, say N.
804
805config TOUCHSCREEN_TOUCHIT213
806	tristate "Sahara TouchIT-213 touchscreen"
807	select SERIO
808	help
809	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.
810
811	  If unsure, say N.
812
813	  To compile this driver as a module, choose M here: the
814	  module will be called touchit213.
815
816config TOUCHSCREEN_TSC_SERIO
817	tristate "TSC-10/25/40 serial touchscreen support"
818	select SERIO
819	help
820	  Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
821	  to your system.
822
823	  If unsure, say N.
824
825	  To compile this driver as a module, choose M here: the
826	  module will be called tsc40.
827
828config TOUCHSCREEN_TSC2005
829        tristate "TSC2005 based touchscreens"
830        depends on SPI_MASTER && GENERIC_HARDIRQS
831        help
832          Say Y here if you have a TSC2005 based touchscreen.
833
834	  If unsure, say N.
835
836	  To compile this driver as a module, choose M here: the
837	  module will be called tsc2005.
838
839config TOUCHSCREEN_TSC2007
840	tristate "TSC2007 based touchscreens"
841	depends on I2C
842	help
843	  Say Y here if you have a TSC2007 based touchscreen.
844
845	  If unsure, say N.
846
847	  To compile this driver as a module, choose M here: the
848	  module will be called tsc2007.
849
850config TOUCHSCREEN_W90X900
851	tristate "W90P910 touchscreen driver"
852	depends on HAVE_CLK
853	help
854	  Say Y here if you have a W90P910 based touchscreen.
855
856	  To compile this driver as a module, choose M here: the
857	  module will be called w90p910_ts.
858
859config TOUCHSCREEN_PCAP
860	tristate "Motorola PCAP touchscreen"
861	depends on EZX_PCAP
862	help
863	  Say Y here if you have a Motorola EZX telephone and
864	  want to enable support for the built-in touchscreen.
865
866	  To compile this driver as a module, choose M here: the
867	  module will be called pcap_ts.
868
869config TOUCHSCREEN_ST1232
870	tristate "Sitronix ST1232 touchscreen controllers"
871	depends on I2C
872	help
873	  Say Y here if you want to support Sitronix ST1232
874	  touchscreen controller.
875
876	  If unsure, say N.
877
878	  To compile this driver as a module, choose M here: the
879	  module will be called st1232_ts.
880
881config TOUCHSCREEN_STMPE
882	tristate "STMicroelectronics STMPE touchscreens"
883	depends on MFD_STMPE
884	help
885	  Say Y here if you want support for STMicroelectronics
886	  STMPE touchscreen controllers.
887
888	  To compile this driver as a module, choose M here: the
889	  module will be called stmpe-ts.
890
891config TOUCHSCREEN_TPS6507X
892	tristate "TPS6507x based touchscreens"
893	depends on I2C
894	help
895	  Say Y here if you have a TPS6507x based touchscreen
896	  controller.
897
898	  If unsure, say N.
899
900	  To compile this driver as a module, choose M here: the
901	  module will be called tps6507x_ts.
902
903endif
904