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