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
190config TOUCHSCREEN_DYNAPRO
191	tristate "Dynapro serial touchscreen"
192	select SERIO
193	help
194	  Say Y here if you have a Dynapro serial touchscreen connected to
195	  your system.
196
197	  If unsure, say N.
198
199	  To compile this driver as a module, choose M here: the
200	  module will be called dynapro.
201
202config TOUCHSCREEN_HAMPSHIRE
203	tristate "Hampshire serial touchscreen"
204	select SERIO
205	help
206	  Say Y here if you have a Hampshire serial touchscreen connected to
207	  your system.
208
209	  If unsure, say N.
210
211	  To compile this driver as a module, choose M here: the
212	  module will be called hampshire.
213
214config TOUCHSCREEN_EETI
215	tristate "EETI touchscreen panel support"
216	depends on I2C
217	help
218	  Say Y here to enable support for I2C connected EETI touch panels.
219
220	  To compile this driver as a module, choose M here: the
221	  module will be called eeti_ts.
222
223config TOUCHSCREEN_EGALAX
224	tristate "EETI eGalax multi-touch panel support"
225	depends on I2C
226	help
227	  Say Y here to enable support for I2C connected EETI
228	  eGalax multi-touch panels.
229
230	  To compile this driver as a module, choose M here: the
231	  module will be called egalax_ts.
232
233config TOUCHSCREEN_FUJITSU
234	tristate "Fujitsu serial touchscreen"
235	select SERIO
236	help
237	  Say Y here if you have the Fujitsu touchscreen (such as one
238	  installed in Lifebook P series laptop) connected to your
239	  system.
240
241	  If unsure, say N.
242
243	  To compile this driver as a module, choose M here: the
244	  module will be called fujitsu-ts.
245
246config TOUCHSCREEN_ILI210X
247	tristate "Ilitek ILI210X based touchscreen"
248	depends on I2C
249	help
250	  Say Y here if you have a ILI210X based touchscreen
251	  controller. This driver supports models ILI2102,
252	  ILI2102s, ILI2103, ILI2103s and ILI2105.
253	  Such kind of chipsets can be found in Amazon Kindle Fire
254	  touchscreens.
255
256	  If unsure, say N.
257
258	  To compile this driver as a module, choose M here: the
259	  module will be called ili210x.
260
261config TOUCHSCREEN_S3C2410
262	tristate "Samsung S3C2410/generic touchscreen input driver"
263	depends on ARCH_S3C2410 || SAMSUNG_DEV_TS
264	select S3C_ADC
265	help
266	  Say Y here if you have the s3c2410 touchscreen.
267
268	  If unsure, say N.
269
270	  To compile this driver as a module, choose M here: the
271	  module will be called s3c2410_ts.
272
273config TOUCHSCREEN_GUNZE
274	tristate "Gunze AHL-51S touchscreen"
275	select SERIO
276	help
277	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
278	  your system.
279
280	  If unsure, say N.
281
282	  To compile this driver as a module, choose M here: the
283	  module will be called gunze.
284
285config TOUCHSCREEN_ELO
286	tristate "Elo serial touchscreens"
287	select SERIO
288	help
289	  Say Y here if you have an Elo serial touchscreen connected to
290	  your system.
291
292	  If unsure, say N.
293
294	  To compile this driver as a module, choose M here: the
295	  module will be called elo.
296
297config TOUCHSCREEN_WACOM_W8001
298	tristate "Wacom W8001 penabled serial touchscreen"
299	select SERIO
300	help
301	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
302	  connected to your system.
303
304	  If unsure, say N.
305
306	  To compile this driver as a module, choose M here: the
307	  module will be called wacom_w8001.
308
309config TOUCHSCREEN_LPC32XX
310	tristate "LPC32XX touchscreen controller"
311	depends on ARCH_LPC32XX
312	help
313	  Say Y here if you have a LPC32XX device and want
314	  to support the built-in touchscreen.
315
316	  To compile this driver as a module, choose M here: the
317	  module will be called lpc32xx_ts.
318
319config TOUCHSCREEN_MAX11801
320	tristate "MAX11801 based touchscreens"
321	depends on I2C
322	help
323	  Say Y here if you have a MAX11801 based touchscreen
324	  controller.
325
326	  If unsure, say N.
327
328	  To compile this driver as a module, choose M here: the
329	  module will be called max11801_ts.
330
331config TOUCHSCREEN_MCS5000
332	tristate "MELFAS MCS-5000 touchscreen"
333	depends on I2C
334	help
335	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
336	  chip in your system.
337
338	  If unsure, say N.
339
340	  To compile this driver as a module, choose M here: the
341	  module will be called mcs5000_ts.
342
343config TOUCHSCREEN_MTOUCH
344	tristate "MicroTouch serial touchscreens"
345	select SERIO
346	help
347	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
348	  your system.
349
350	  If unsure, say N.
351
352	  To compile this driver as a module, choose M here: the
353	  module will be called mtouch.
354
355config TOUCHSCREEN_INEXIO
356	tristate "iNexio serial touchscreens"
357	select SERIO
358	help
359	  Say Y here if you have an iNexio serial touchscreen connected to
360	  your system.
361
362	  If unsure, say N.
363
364	  To compile this driver as a module, choose M here: the
365	  module will be called inexio.
366
367config TOUCHSCREEN_INTEL_MID
368	tristate "Intel MID platform resistive touchscreen"
369	depends on INTEL_SCU_IPC
370	help
371	  Say Y here if you have a Intel MID based touchscreen in
372	  your system.
373
374	  If unsure, say N.
375
376	  To compile this driver as a module, choose M here: the
377	  module will be called intel_mid_touch.
378
379config TOUCHSCREEN_MK712
380	tristate "ICS MicroClock MK712 touchscreen"
381	help
382	  Say Y here if you have the ICS MicroClock MK712 touchscreen
383	  controller chip in your system.
384
385	  If unsure, say N.
386
387	  To compile this driver as a module, choose M here: the
388	  module will be called mk712.
389
390config TOUCHSCREEN_HP600
391	tristate "HP Jornada 6xx touchscreen"
392	depends on SH_HP6XX && SH_ADC
393	help
394	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
395          support the built-in touchscreen.
396
397	  To compile this driver as a module, choose M here: the
398	  module will be called hp680_ts_input.
399
400config TOUCHSCREEN_HP7XX
401	tristate "HP Jornada 7xx touchscreen"
402	depends on SA1100_JORNADA720_SSP
403	help
404	  Say Y here if you have a HP Jornada 710/720/728 and want
405	  to support the built-in touchscreen.
406
407	  To compile this driver as a module, choose M here: the
408	  module will be called jornada720_ts.
409
410config TOUCHSCREEN_HTCPEN
411	tristate "HTC Shift X9500 touchscreen"
412	depends on ISA
413	help
414	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
415	  Clio / Shangrila and want to support the built-in touchscreen.
416
417	  If unsure, say N.
418
419	  To compile this driver as a module, choose M here: the
420	  module will be called htcpen.
421
422config TOUCHSCREEN_PENMOUNT
423	tristate "Penmount serial touchscreen"
424	select SERIO
425	help
426	  Say Y here if you have a Penmount serial touchscreen connected to
427	  your system.
428
429	  If unsure, say N.
430
431	  To compile this driver as a module, choose M here: the
432	  module will be called penmount.
433
434config TOUCHSCREEN_MIGOR
435	tristate "Renesas MIGO-R touchscreen"
436	depends on SH_MIGOR && I2C
437	help
438	  Say Y here to enable MIGO-R touchscreen support.
439
440	  If unsure, say N.
441
442	  To compile this driver as a module, choose M here: the
443	  module will be called migor_ts.
444
445config TOUCHSCREEN_TNETV107X
446	tristate "TI TNETV107X touchscreen support"
447	depends on ARCH_DAVINCI_TNETV107X
448	help
449	  Say Y here if you want to use the TNETV107X touchscreen.
450
451	  To compile this driver as a module, choose M here: the
452	  module will be called tnetv107x-ts.
453
454config TOUCHSCREEN_TOUCHRIGHT
455	tristate "Touchright serial touchscreen"
456	select SERIO
457	help
458	  Say Y here if you have a Touchright serial touchscreen connected to
459	  your system.
460
461	  If unsure, say N.
462
463	  To compile this driver as a module, choose M here: the
464	  module will be called touchright.
465
466config TOUCHSCREEN_TOUCHWIN
467	tristate "Touchwin serial touchscreen"
468	select SERIO
469	help
470	  Say Y here if you have a Touchwin serial touchscreen connected to
471	  your system.
472
473	  If unsure, say N.
474
475	  To compile this driver as a module, choose M here: the
476	  module will be called touchwin.
477
478config TOUCHSCREEN_TI_TSCADC
479	tristate "TI Touchscreen Interface"
480	depends on ARCH_OMAP2PLUS
481	help
482	  Say Y here if you have 4/5/8 wire touchscreen controller
483	  to be connected to the ADC controller on your TI AM335x SoC.
484
485	  If unsure, say N.
486
487	  To compile this driver as a module, choose M here: the
488	  module will be called ti_tscadc.
489
490config TOUCHSCREEN_ATMEL_TSADCC
491	tristate "Atmel Touchscreen Interface"
492	depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
493	help
494	  Say Y here if you have a 4-wire touchscreen connected to the
495          ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
496
497	  If unsure, say N.
498
499	  To compile this driver as a module, choose M here: the
500	  module will be called atmel_tsadcc.
501
502config TOUCHSCREEN_UCB1400
503	tristate "Philips UCB1400 touchscreen"
504	depends on AC97_BUS
505	depends on UCB1400_CORE
506	help
507	  This enables support for the Philips UCB1400 touchscreen interface.
508	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
509	  will be initialized only after the ALSA subsystem has been
510	  brought up and the UCB1400 detected.  You therefore have to
511	  configure ALSA support as well (either built-in or modular,
512	  independently of whether this driver is itself built-in or
513	  modular) for this driver to work.
514
515	  To compile this driver as a module, choose M here: the
516	  module will be called ucb1400_ts.
517
518config TOUCHSCREEN_PIXCIR
519	tristate "PIXCIR I2C touchscreens"
520	depends on I2C
521	help
522	  Say Y here if you have a pixcir i2c touchscreen
523	  controller.
524
525	  If unsure, say N.
526
527	  To compile this driver as a module, choose M here: the
528	  module will be called pixcir_i2c_ts.
529
530config TOUCHSCREEN_WM831X
531	tristate "Support for WM831x touchscreen controllers"
532	depends on MFD_WM831X
533	help
534	  This enables support for the touchscreen controller on the WM831x
535	  series of PMICs.
536
537	  To compile this driver as a module, choose M here: the
538	  module will be called wm831x-ts.
539
540config TOUCHSCREEN_WM97XX
541	tristate "Support for WM97xx AC97 touchscreen controllers"
542	depends on AC97_BUS
543	help
544	  Say Y here if you have a Wolfson Microelectronics WM97xx
545	  touchscreen connected to your system. Note that this option
546	  only enables core driver, you will also need to select
547	  support for appropriate chip below.
548
549	  If unsure, say N.
550
551	  To compile this driver as a module, choose M here: the
552	  module will be called wm97xx-ts.
553
554config TOUCHSCREEN_WM9705
555	bool "WM9705 Touchscreen interface support"
556	depends on TOUCHSCREEN_WM97XX
557	default y
558	help
559	  Say Y here to enable support for the Wolfson Microelectronics
560	  WM9705 touchscreen controller.
561
562config TOUCHSCREEN_WM9712
563	bool "WM9712 Touchscreen interface support"
564	depends on TOUCHSCREEN_WM97XX
565	default y
566	help
567	  Say Y here to enable support for the Wolfson Microelectronics
568	  WM9712 touchscreen controller.
569
570config TOUCHSCREEN_WM9713
571	bool "WM9713 Touchscreen interface support"
572	depends on TOUCHSCREEN_WM97XX
573	default y
574	help
575	  Say Y here to enable support for the Wolfson Microelectronics
576	  WM9713 touchscreen controller.
577
578config TOUCHSCREEN_WM97XX_ATMEL
579	tristate "WM97xx Atmel accelerated touch"
580	depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
581	help
582	  Say Y here for support for streaming mode with WM97xx touchscreens
583	  on Atmel AT91 or AVR32 systems with an AC97C module.
584
585	  Be aware that this will use channel B in the controller for
586	  streaming data, this must not conflict with other AC97C drivers.
587
588	  If unsure, say N.
589
590	  To compile this driver as a module, choose M here: the module will
591	  be called atmel-wm97xx.
592
593config TOUCHSCREEN_WM97XX_MAINSTONE
594	tristate "WM97xx Mainstone/Palm accelerated touch"
595	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
596	help
597	  Say Y here for support for streaming mode with WM97xx touchscreens
598	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
599
600	  If unsure, say N.
601
602	  To compile this driver as a module, choose M here: the
603	  module will be called mainstone-wm97xx.
604
605config TOUCHSCREEN_WM97XX_ZYLONITE
606	tristate "Zylonite accelerated touch"
607	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
608	select TOUCHSCREEN_WM9713
609	help
610	  Say Y here for support for streaming mode with the touchscreen
611	  on Zylonite systems.
612
613	  If unsure, say N.
614
615	  To compile this driver as a module, choose M here: the
616	  module will be called zylonite-wm97xx.
617
618config TOUCHSCREEN_USB_COMPOSITE
619	tristate "USB Touchscreen Driver"
620	depends on USB_ARCH_HAS_HCD
621	select USB
622	help
623	  USB Touchscreen driver for:
624	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
625	  - PanJit TouchSet USB
626	  - 3M MicroTouch USB (EX II series)
627	  - ITM
628	  - some other eTurboTouch
629	  - Gunze AHL61
630	  - DMC TSC-10/25
631	  - IRTOUCHSYSTEMS/UNITOP
632	  - IdealTEK URTC1000
633	  - GoTop Super_Q2/GogoPen/PenPower tablets
634	  - JASTEC USB Touch Controller/DigiTech DTR-02U
635	  - Zytronic controllers
636	  - Elo TouchSystems 2700 IntelliTouch
637	  - EasyTouch USB Touch Controller from Data Modul
638
639	  Have a look at <http://linux.chapter7.ch/touchkit/> for
640	  a usage description and the required user-space stuff.
641
642	  To compile this driver as a module, choose M here: the
643	  module will be called usbtouchscreen.
644
645config TOUCHSCREEN_MC13783
646	tristate "Freescale MC13783 touchscreen input driver"
647	depends on MFD_MC13783
648	help
649	  Say Y here if you have an Freescale MC13783 PMIC on your
650	  board and want to use its touchscreen
651
652	  If unsure, say N.
653
654	  To compile this driver as a module, choose M here: the
655	  module will be called mc13783_ts.
656
657config TOUCHSCREEN_USB_EGALAX
658	default y
659	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
660	depends on TOUCHSCREEN_USB_COMPOSITE
661
662config TOUCHSCREEN_USB_PANJIT
663	default y
664	bool "PanJit device support" if EXPERT
665	depends on TOUCHSCREEN_USB_COMPOSITE
666
667config TOUCHSCREEN_USB_3M
668	default y
669	bool "3M/Microtouch EX II series device support" if EXPERT
670	depends on TOUCHSCREEN_USB_COMPOSITE
671
672config TOUCHSCREEN_USB_ITM
673	default y
674	bool "ITM device support" if EXPERT
675	depends on TOUCHSCREEN_USB_COMPOSITE
676
677config TOUCHSCREEN_USB_ETURBO
678	default y
679	bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
680	depends on TOUCHSCREEN_USB_COMPOSITE
681
682config TOUCHSCREEN_USB_GUNZE
683	default y
684	bool "Gunze AHL61 device support" if EXPERT
685	depends on TOUCHSCREEN_USB_COMPOSITE
686
687config TOUCHSCREEN_USB_DMC_TSC10
688	default y
689	bool "DMC TSC-10/25 device support" if EXPERT
690	depends on TOUCHSCREEN_USB_COMPOSITE
691
692config TOUCHSCREEN_USB_IRTOUCH
693	default y
694	bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
695	depends on TOUCHSCREEN_USB_COMPOSITE
696
697config TOUCHSCREEN_USB_IDEALTEK
698	default y
699	bool "IdealTEK URTC1000 device support" if EXPERT
700	depends on TOUCHSCREEN_USB_COMPOSITE
701
702config TOUCHSCREEN_USB_GENERAL_TOUCH
703	default y
704	bool "GeneralTouch Touchscreen device support" if EXPERT
705	depends on TOUCHSCREEN_USB_COMPOSITE
706
707config TOUCHSCREEN_USB_GOTOP
708	default y
709	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
710	depends on TOUCHSCREEN_USB_COMPOSITE
711
712config TOUCHSCREEN_USB_JASTEC
713	default y
714	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
715	depends on TOUCHSCREEN_USB_COMPOSITE
716
717config TOUCHSCREEN_USB_ELO
718	default y
719	bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
720	depends on TOUCHSCREEN_USB_COMPOSITE
721
722config TOUCHSCREEN_USB_E2I
723	default y
724	bool "e2i Touchscreen controller (e.g. from Mimo 740)"
725	depends on TOUCHSCREEN_USB_COMPOSITE
726
727config TOUCHSCREEN_USB_ZYTRONIC
728	default y
729	bool "Zytronic controller" if EXPERT
730	depends on TOUCHSCREEN_USB_COMPOSITE
731
732config TOUCHSCREEN_USB_ETT_TC45USB
733	default y
734	bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
735	depends on TOUCHSCREEN_USB_COMPOSITE
736
737config TOUCHSCREEN_USB_NEXIO
738	default y
739	bool "NEXIO/iNexio device support" if EXPERT
740	depends on TOUCHSCREEN_USB_COMPOSITE
741
742config TOUCHSCREEN_USB_EASYTOUCH
743	default y
744	bool "EasyTouch USB Touch controller device support" if EMBEDDED
745	depends on TOUCHSCREEN_USB_COMPOSITE
746	help
747	  Say Y here if you have a EasyTouch USB Touch controller device support.
748	  If unsure, say N.
749
750config TOUCHSCREEN_TOUCHIT213
751	tristate "Sahara TouchIT-213 touchscreen"
752	select SERIO
753	help
754	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.
755
756	  If unsure, say N.
757
758	  To compile this driver as a module, choose M here: the
759	  module will be called touchit213.
760
761config TOUCHSCREEN_TSC_SERIO
762	tristate "TSC-10/25/40 serial touchscreen support"
763	select SERIO
764	help
765	  Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
766	  to your system.
767
768	  If unsure, say N.
769
770	  To compile this driver as a module, choose M here: the
771	  module will be called tsc40.
772
773config TOUCHSCREEN_TSC2005
774        tristate "TSC2005 based touchscreens"
775        depends on SPI_MASTER && GENERIC_HARDIRQS
776        help
777          Say Y here if you have a TSC2005 based touchscreen.
778
779	  If unsure, say N.
780
781	  To compile this driver as a module, choose M here: the
782	  module will be called tsc2005.
783
784config TOUCHSCREEN_TSC2007
785	tristate "TSC2007 based touchscreens"
786	depends on I2C
787	help
788	  Say Y here if you have a TSC2007 based touchscreen.
789
790	  If unsure, say N.
791
792	  To compile this driver as a module, choose M here: the
793	  module will be called tsc2007.
794
795config TOUCHSCREEN_W90X900
796	tristate "W90P910 touchscreen driver"
797	depends on HAVE_CLK
798	help
799	  Say Y here if you have a W90P910 based touchscreen.
800
801	  To compile this driver as a module, choose M here: the
802	  module will be called w90p910_ts.
803
804config TOUCHSCREEN_PCAP
805	tristate "Motorola PCAP touchscreen"
806	depends on EZX_PCAP
807	help
808	  Say Y here if you have a Motorola EZX telephone and
809	  want to enable support for the built-in touchscreen.
810
811	  To compile this driver as a module, choose M here: the
812	  module will be called pcap_ts.
813
814config TOUCHSCREEN_ST1232
815	tristate "Sitronix ST1232 touchscreen controllers"
816	depends on I2C
817	help
818	  Say Y here if you want to support Sitronix ST1232
819	  touchscreen controller.
820
821	  If unsure, say N.
822
823	  To compile this driver as a module, choose M here: the
824	  module will be called st1232_ts.
825
826config TOUCHSCREEN_STMPE
827	tristate "STMicroelectronics STMPE touchscreens"
828	depends on MFD_STMPE
829	help
830	  Say Y here if you want support for STMicroelectronics
831	  STMPE touchscreen controllers.
832
833	  To compile this driver as a module, choose M here: the
834	  module will be called stmpe-ts.
835
836config TOUCHSCREEN_TPS6507X
837	tristate "TPS6507x based touchscreens"
838	depends on I2C
839	help
840	  Say Y here if you have a TPS6507x based touchscreen
841	  controller.
842
843	  If unsure, say N.
844
845	  To compile this driver as a module, choose M here: the
846	  module will be called tps6507x_ts.
847
848endif
849