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