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