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_ADS7846
15	tristate "ADS7846/TSC2046 and ADS7843 based touchscreens"
16	depends on SPI_MASTER
17	depends on HWMON = n || HWMON
18	help
19	  Say Y here if you have a touchscreen interface using the
20	  ADS7846/TSC2046 or ADS7843 controller, and your board-specific
21	  setup code includes that in its table of SPI devices.
22
23	  If HWMON is selected, and the driver is told the reference voltage
24	  on your board, you will also get hwmon interfaces for the voltage
25	  (and on ads7846/tsc2046, temperature) sensors of this chip.
26
27	  If unsure, say N (but it's safe to say "Y").
28
29	  To compile this driver as a module, choose M here: the
30	  module will be called ads7846.
31
32config TOUCHSCREEN_AD7877
33	tristate "AD7877 based touchscreens"
34	depends on SPI_MASTER
35	help
36	  Say Y here if you have a touchscreen interface using the
37	  AD7877 controller, and your board-specific initialization
38	  code includes that in its table of SPI devices.
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 ad7877.
44
45config TOUCHSCREEN_AD7879_I2C
46	tristate "AD7879 based touchscreens: AD7879-1 I2C Interface"
47	depends on I2C
48	select TOUCHSCREEN_AD7879
49	help
50	  Say Y here if you have a touchscreen interface using the
51	  AD7879-1/AD7889-1 controller, and your board-specific
52	  initialization code includes that in its table of I2C devices.
53
54	  If unsure, say N (but it's safe to say "Y").
55
56	  To compile this driver as a module, choose M here: the
57	  module will be called ad7879.
58
59config TOUCHSCREEN_AD7879_SPI
60	tristate "AD7879 based touchscreens: AD7879 SPI Interface"
61	depends on SPI_MASTER && TOUCHSCREEN_AD7879_I2C = n
62	select TOUCHSCREEN_AD7879
63	help
64	  Say Y here if you have a touchscreen interface using the
65	  AD7879/AD7889 controller, and your board-specific initialization
66	  code includes that in its table of SPI devices.
67
68	  If unsure, say N (but it's safe to say "Y").
69
70	  To compile this driver as a module, choose M here: the
71	  module will be called ad7879.
72
73config TOUCHSCREEN_AD7879
74	tristate
75	default n
76
77config TOUCHSCREEN_BITSY
78	tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
79	depends on SA1100_BITSY
80	select SERIO
81	help
82	  Say Y here if you have the h3600 (Bitsy) touchscreen.
83
84	  If unsure, say N.
85
86	  To compile this driver as a module, choose M here: the
87	  module will be called h3600_ts_input.
88
89config TOUCHSCREEN_CORGI
90	tristate "SharpSL (Corgi and Spitz series) touchscreen driver (DEPRECATED)"
91	depends on PXA_SHARPSL
92	select CORGI_SSP_DEPRECATED
93	default y
94	help
95	  Say Y here to enable the driver for the touchscreen on the
96	  Sharp SL-C7xx and SL-Cxx00 series of PDAs.
97
98	  If unsure, say N.
99
100	  To compile this driver as a module, choose M here: the
101	  module will be called corgi_ts.
102
103	  NOTE: this driver is deprecated, try enable SPI and generic
104	  ADS7846-based touchscreen driver.
105
106config TOUCHSCREEN_DA9034
107	tristate "Touchscreen support for Dialog Semiconductor DA9034"
108	depends on PMIC_DA903X
109	default y
110	help
111	  Say Y here to enable the support for the touchscreen found
112	  on Dialog Semiconductor DA9034 PMIC.
113
114config TOUCHSCREEN_DYNAPRO
115	tristate "Dynapro serial touchscreen"
116	select SERIO
117	help
118	  Say Y here if you have a Dynapro serial 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 dynapro.
125
126config TOUCHSCREEN_EETI
127	tristate "EETI touchscreen panel support"
128	depends on I2C
129	help
130	  Say Y here to enable support for I2C connected EETI touch panels.
131
132	  To compile this driver as a module, choose M here: the
133	  module will be called eeti_ts.
134
135config TOUCHSCREEN_FUJITSU
136	tristate "Fujitsu serial touchscreen"
137	select SERIO
138	help
139	  Say Y here if you have the Fujitsu touchscreen (such as one
140	  installed in Lifebook P series laptop) connected to your
141	  system.
142
143	  If unsure, say N.
144
145	  To compile this driver as a module, choose M here: the
146	  module will be called fujitsu-ts.
147
148config TOUCHSCREEN_S3C2410
149	tristate "Samsung S3C2410 touchscreen input driver"
150	depends on ARCH_S3C2410
151	select S3C24XX_ADC
152	help
153	  Say Y here if you have the s3c2410 touchscreen.
154
155	  If unsure, say N.
156
157	  To compile this driver as a module, choose M here: the
158	  module will be called s3c2410_ts.
159
160config TOUCHSCREEN_GUNZE
161	tristate "Gunze AHL-51S touchscreen"
162	select SERIO
163	help
164	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
165	  your system.
166
167	  If unsure, say N.
168
169	  To compile this driver as a module, choose M here: the
170	  module will be called gunze.
171
172config TOUCHSCREEN_ELO
173	tristate "Elo serial touchscreens"
174	select SERIO
175	help
176	  Say Y here if you have an Elo serial touchscreen connected to
177	  your system.
178
179	  If unsure, say N.
180
181	  To compile this driver as a module, choose M here: the
182	  module will be called elo.
183
184config TOUCHSCREEN_WACOM_W8001
185	tristate "Wacom W8001 penabled serial touchscreen"
186	select SERIO
187	help
188	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
189	  connected to your system.
190
191	  If unsure, say N.
192
193	  To compile this driver as a module, choose M here: the
194	  module will be called wacom_w8001.
195
196config TOUCHSCREEN_MCS5000
197	tristate "MELFAS MCS-5000 touchscreen"
198	depends on I2C
199	help
200	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
201	  chip in your system.
202
203	  If unsure, say N.
204
205	  To compile this driver as a module, choose M here: the
206	  module will be called mcs5000_ts.
207
208config TOUCHSCREEN_MTOUCH
209	tristate "MicroTouch serial touchscreens"
210	select SERIO
211	help
212	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
213	  your system.
214
215	  If unsure, say N.
216
217	  To compile this driver as a module, choose M here: the
218	  module will be called mtouch.
219
220config TOUCHSCREEN_INEXIO
221	tristate "iNexio serial touchscreens"
222	select SERIO
223	help
224	  Say Y here if you have an iNexio serial touchscreen connected to
225	  your system.
226
227	  If unsure, say N.
228
229	  To compile this driver as a module, choose M here: the
230	  module will be called inexio.
231
232config TOUCHSCREEN_MK712
233	tristate "ICS MicroClock MK712 touchscreen"
234	help
235	  Say Y here if you have the ICS MicroClock MK712 touchscreen
236	  controller chip in your system.
237
238	  If unsure, say N.
239
240	  To compile this driver as a module, choose M here: the
241	  module will be called mk712.
242
243config TOUCHSCREEN_HP600
244	tristate "HP Jornada 6xx touchscreen"
245	depends on SH_HP6XX && SH_ADC
246	help
247	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
248          support the built-in touchscreen.
249
250	  To compile this driver as a module, choose M here: the
251	  module will be called hp680_ts_input.
252
253config TOUCHSCREEN_HP7XX
254	tristate "HP Jornada 7xx touchscreen"
255	depends on SA1100_JORNADA720_SSP
256	help
257	  Say Y here if you have a HP Jornada 710/720/728 and want
258	  to support the built-in touchscreen.
259
260	  To compile this driver as a module, choose M here: the
261	  module will be called jornada720_ts.
262
263config TOUCHSCREEN_HTCPEN
264	tristate "HTC Shift X9500 touchscreen"
265	depends on ISA
266	help
267	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
268	  Clio / Shangrila and want to support the built-in touchscreen.
269
270	  If unsure, say N.
271
272	  To compile this driver as a module, choose M here: the
273	  module will be called htcpen.
274
275config TOUCHSCREEN_PENMOUNT
276	tristate "Penmount serial touchscreen"
277	select SERIO
278	help
279	  Say Y here if you have a Penmount serial touchscreen connected to
280	  your system.
281
282	  If unsure, say N.
283
284	  To compile this driver as a module, choose M here: the
285	  module will be called penmount.
286
287config TOUCHSCREEN_MIGOR
288	tristate "Renesas MIGO-R touchscreen"
289	depends on SH_MIGOR && I2C
290	help
291	  Say Y here to enable MIGO-R touchscreen support.
292
293	  If unsure, say N.
294
295	  To compile this driver as a module, choose M here: the
296	  module will be called migor_ts.
297
298config TOUCHSCREEN_TOUCHRIGHT
299	tristate "Touchright serial touchscreen"
300	select SERIO
301	help
302	  Say Y here if you have a Touchright serial touchscreen connected to
303	  your system.
304
305	  If unsure, say N.
306
307	  To compile this driver as a module, choose M here: the
308	  module will be called touchright.
309
310config TOUCHSCREEN_TOUCHWIN
311	tristate "Touchwin serial touchscreen"
312	select SERIO
313	help
314	  Say Y here if you have a Touchwin serial touchscreen connected to
315	  your system.
316
317	  If unsure, say N.
318
319	  To compile this driver as a module, choose M here: the
320	  module will be called touchwin.
321
322config TOUCHSCREEN_ATMEL_TSADCC
323	tristate "Atmel Touchscreen Interface"
324	depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
325	help
326	  Say Y here if you have a 4-wire touchscreen connected to the
327          ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
328
329	  If unsure, say N.
330
331	  To compile this driver as a module, choose M here: the
332	  module will be called atmel_tsadcc.
333
334config TOUCHSCREEN_UCB1400
335	tristate "Philips UCB1400 touchscreen"
336	depends on AC97_BUS
337	depends on UCB1400_CORE
338	help
339	  This enables support for the Philips UCB1400 touchscreen interface.
340	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
341	  will be initialized only after the ALSA subsystem has been
342	  brought up and the UCB1400 detected.  You therefore have to
343	  configure ALSA support as well (either built-in or modular,
344	  independently of whether this driver is itself built-in or
345	  modular) for this driver to work.
346
347	  To compile this driver as a module, choose M here: the
348	  module will be called ucb1400_ts.
349
350config TOUCHSCREEN_WM97XX
351	tristate "Support for WM97xx AC97 touchscreen controllers"
352	depends on AC97_BUS
353	help
354	  Say Y here if you have a Wolfson Microelectronics WM97xx
355	  touchscreen connected to your system. Note that this option
356	  only enables core driver, you will also need to select
357	  support for appropriate chip below.
358
359	  If unsure, say N.
360
361	  To compile this driver as a module, choose M here: the
362	  module will be called wm97xx-ts.
363
364config TOUCHSCREEN_WM9705
365	bool "WM9705 Touchscreen interface support"
366	depends on TOUCHSCREEN_WM97XX
367	default y
368	help
369	  Say Y here to enable support for the Wolfson Microelectronics
370	  WM9705 touchscreen controller.
371
372config TOUCHSCREEN_WM9712
373	bool "WM9712 Touchscreen interface support"
374	depends on TOUCHSCREEN_WM97XX
375	default y
376	help
377	  Say Y here to enable support for the Wolfson Microelectronics
378	  WM9712 touchscreen controller.
379
380config TOUCHSCREEN_WM9713
381	bool "WM9713 Touchscreen interface support"
382	depends on TOUCHSCREEN_WM97XX
383	default y
384	help
385	  Say Y here to enable support for the Wolfson Microelectronics
386	  WM9713 touchscreen controller.
387
388config TOUCHSCREEN_WM97XX_ATMEL
389	tristate "WM97xx Atmel accelerated touch"
390	depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
391	help
392	  Say Y here for support for streaming mode with WM97xx touchscreens
393	  on Atmel AT91 or AVR32 systems with an AC97C module.
394
395	  Be aware that this will use channel B in the controller for
396	  streaming data, this must not conflict with other AC97C drivers.
397
398	  If unsure, say N.
399
400	  To compile this driver as a module, choose M here: the module will
401	  be called atmel-wm97xx.
402
403config TOUCHSCREEN_WM97XX_MAINSTONE
404	tristate "WM97xx Mainstone/Palm accelerated touch"
405	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
406	help
407	  Say Y here for support for streaming mode with WM97xx touchscreens
408	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
409
410	  If unsure, say N.
411
412	  To compile this driver as a module, choose M here: the
413	  module will be called mainstone-wm97xx.
414
415config TOUCHSCREEN_WM97XX_ZYLONITE
416	tristate "Zylonite accelerated touch"
417	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
418	select TOUCHSCREEN_WM9713
419	help
420	  Say Y here for support for streaming mode with the touchscreen
421	  on Zylonite systems.
422
423	  If unsure, say N.
424
425	  To compile this driver as a module, choose M here: the
426	  module will be called zylonite-wm97xx.
427
428config TOUCHSCREEN_USB_COMPOSITE
429	tristate "USB Touchscreen Driver"
430	depends on USB_ARCH_HAS_HCD
431	select USB
432	help
433	  USB Touchscreen driver for:
434	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
435	  - PanJit TouchSet USB
436	  - 3M MicroTouch USB (EX II series)
437	  - ITM
438	  - some other eTurboTouch
439	  - Gunze AHL61
440	  - DMC TSC-10/25
441	  - IRTOUCHSYSTEMS/UNITOP
442	  - IdealTEK URTC1000
443	  - GoTop Super_Q2/GogoPen/PenPower tablets
444	  - JASTEC USB Touch Controller/DigiTech DTR-02U
445	  - Zytronic controllers
446
447	  Have a look at <http://linux.chapter7.ch/touchkit/> for
448	  a usage description and the required user-space stuff.
449
450	  To compile this driver as a module, choose M here: the
451	  module will be called usbtouchscreen.
452
453config TOUCHSCREEN_MC13783
454	tristate "Freescale MC13783 touchscreen input driver"
455	depends on MFD_MC13783
456	help
457	  Say Y here if you have an Freescale MC13783 PMIC on your
458	  board and want to use its touchscreen
459
460	  If unsure, say N.
461
462	  To compile this driver as a module, choose M here: the
463	  module will be called mc13783_ts.
464
465config TOUCHSCREEN_USB_EGALAX
466	default y
467	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
468	depends on TOUCHSCREEN_USB_COMPOSITE
469
470config TOUCHSCREEN_USB_PANJIT
471	default y
472	bool "PanJit device support" if EMBEDDED
473	depends on TOUCHSCREEN_USB_COMPOSITE
474
475config TOUCHSCREEN_USB_3M
476	default y
477	bool "3M/Microtouch EX II series device support" if EMBEDDED
478	depends on TOUCHSCREEN_USB_COMPOSITE
479
480config TOUCHSCREEN_USB_ITM
481	default y
482	bool "ITM device support" if EMBEDDED
483	depends on TOUCHSCREEN_USB_COMPOSITE
484
485config TOUCHSCREEN_USB_ETURBO
486	default y
487	bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
488	depends on TOUCHSCREEN_USB_COMPOSITE
489
490config TOUCHSCREEN_USB_GUNZE
491	default y
492	bool "Gunze AHL61 device support" if EMBEDDED
493	depends on TOUCHSCREEN_USB_COMPOSITE
494
495config TOUCHSCREEN_USB_DMC_TSC10
496	default y
497	bool "DMC TSC-10/25 device support" if EMBEDDED
498	depends on TOUCHSCREEN_USB_COMPOSITE
499
500config TOUCHSCREEN_USB_IRTOUCH
501	default y
502	bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED
503	depends on TOUCHSCREEN_USB_COMPOSITE
504
505config TOUCHSCREEN_USB_IDEALTEK
506	default y
507	bool "IdealTEK URTC1000 device support" if EMBEDDED
508	depends on TOUCHSCREEN_USB_COMPOSITE
509
510config TOUCHSCREEN_USB_GENERAL_TOUCH
511	default y
512	bool "GeneralTouch Touchscreen device support" if EMBEDDED
513	depends on TOUCHSCREEN_USB_COMPOSITE
514
515config TOUCHSCREEN_USB_GOTOP
516	default y
517	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED
518	depends on TOUCHSCREEN_USB_COMPOSITE
519
520config TOUCHSCREEN_USB_JASTEC
521	default y
522	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EMBEDDED
523	depends on TOUCHSCREEN_USB_COMPOSITE
524
525config TOUCHSCREEN_USB_E2I
526	default y
527	bool "e2i Touchscreen controller (e.g. from Mimo 740)"
528	depends on TOUCHSCREEN_USB_COMPOSITE
529
530config TOUCHSCREEN_USB_ZYTRONIC
531	default y
532	bool "Zytronic controller" if EMBEDDED
533	depends on TOUCHSCREEN_USB_COMPOSITE
534
535config TOUCHSCREEN_USB_ETT_TC5UH
536	default y
537	bool "ET&T TC5UH touchscreen controler support" if EMBEDDED
538	depends on TOUCHSCREEN_USB_COMPOSITE
539
540config TOUCHSCREEN_TOUCHIT213
541	tristate "Sahara TouchIT-213 touchscreen"
542	select SERIO
543	help
544	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.
545
546	  If unsure, say N.
547
548	  To compile this driver as a module, choose M here: the
549	  module will be called touchit213.
550
551config TOUCHSCREEN_TSC2007
552	tristate "TSC2007 based touchscreens"
553	depends on I2C
554	help
555	  Say Y here if you have a TSC2007 based touchscreen.
556
557	  If unsure, say N.
558
559	  To compile this driver as a module, choose M here: the
560	  module will be called tsc2007.
561
562config TOUCHSCREEN_W90X900
563	tristate "W90P910 touchscreen driver"
564	depends on HAVE_CLK
565	help
566	  Say Y here if you have a W90P910 based touchscreen.
567
568	  To compile this driver as a module, choose M here: the
569	  module will be called w90p910_ts.
570
571config TOUCHSCREEN_PCAP
572	tristate "Motorola PCAP touchscreen"
573	depends on EZX_PCAP
574	help
575	  Say Y here if you have a Motorola EZX telephone and
576	  want to enable support for the built-in touchscreen.
577
578	  To compile this driver as a module, choose M here: the
579	  module will be called pcap_ts.
580endif
581