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_EETI
115	tristate "EETI touchscreen panel support"
116	depends on I2C
117	help
118	  Say Y here to enable support for I2C connected EETI touch panels.
119
120	  To compile this driver as a module, choose M here: the
121	  module will be called eeti_ts.
122
123config TOUCHSCREEN_FUJITSU
124	tristate "Fujitsu serial touchscreen"
125	select SERIO
126	help
127	  Say Y here if you have the Fujitsu touchscreen (such as one
128	  installed in Lifebook P series laptop) connected to your
129	  system.
130
131	  If unsure, say N.
132
133	  To compile this driver as a module, choose M here: the
134	  module will be called fujitsu-ts.
135
136config TOUCHSCREEN_GUNZE
137	tristate "Gunze AHL-51S touchscreen"
138	select SERIO
139	help
140	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
141	  your 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 gunze.
147
148config TOUCHSCREEN_ELO
149	tristate "Elo serial touchscreens"
150	select SERIO
151	help
152	  Say Y here if you have an Elo serial touchscreen connected to
153	  your system.
154
155	  If unsure, say N.
156
157	  To compile this driver as a module, choose M here: the
158	  module will be called elo.
159
160config TOUCHSCREEN_WACOM_W8001
161	tristate "Wacom W8001 penabled serial touchscreen"
162	select SERIO
163	help
164	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
165	  connected to 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 wacom_w8001.
171
172config TOUCHSCREEN_MCS5000
173	tristate "MELFAS MCS-5000 touchscreen"
174	depends on I2C
175	help
176	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
177	  chip in 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 mcs5000_ts.
183
184config TOUCHSCREEN_MTOUCH
185	tristate "MicroTouch serial touchscreens"
186	select SERIO
187	help
188	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
189	  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 mtouch.
195
196config TOUCHSCREEN_INEXIO
197	tristate "iNexio serial touchscreens"
198	select SERIO
199	help
200	  Say Y here if you have an iNexio serial touchscreen connected to
201	  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 inexio.
207
208config TOUCHSCREEN_MK712
209	tristate "ICS MicroClock MK712 touchscreen"
210	help
211	  Say Y here if you have the ICS MicroClock MK712 touchscreen
212	  controller chip in your system.
213
214	  If unsure, say N.
215
216	  To compile this driver as a module, choose M here: the
217	  module will be called mk712.
218
219config TOUCHSCREEN_HP600
220	tristate "HP Jornada 6xx touchscreen"
221	depends on SH_HP6XX && SH_ADC
222	help
223	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
224          support the built-in touchscreen.
225
226	  To compile this driver as a module, choose M here: the
227	  module will be called hp680_ts_input.
228
229config TOUCHSCREEN_HP7XX
230	tristate "HP Jornada 7xx touchscreen"
231	depends on SA1100_JORNADA720_SSP
232	help
233	  Say Y here if you have a HP Jornada 710/720/728 and want
234	  to support the built-in touchscreen.
235
236	  To compile this driver as a module, choose M here: the
237	  module will be called jornada720_ts.
238
239config TOUCHSCREEN_HTCPEN
240	tristate "HTC Shift X9500 touchscreen"
241	depends on ISA
242	help
243	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
244	  Clio / Shangrila and want to support the built-in touchscreen.
245
246	  If unsure, say N.
247
248	  To compile this driver as a module, choose M here: the
249	  module will be called htcpen.
250
251config TOUCHSCREEN_PENMOUNT
252	tristate "Penmount serial touchscreen"
253	select SERIO
254	help
255	  Say Y here if you have a Penmount serial touchscreen connected to
256	  your system.
257
258	  If unsure, say N.
259
260	  To compile this driver as a module, choose M here: the
261	  module will be called penmount.
262
263config TOUCHSCREEN_MIGOR
264	tristate "Renesas MIGO-R touchscreen"
265	depends on SH_MIGOR && I2C
266	help
267	  Say Y here to enable MIGO-R touchscreen support.
268
269	  If unsure, say N.
270
271	  To compile this driver as a module, choose M here: the
272	  module will be called migor_ts.
273
274config TOUCHSCREEN_TOUCHRIGHT
275	tristate "Touchright serial touchscreen"
276	select SERIO
277	help
278	  Say Y here if you have a Touchright serial touchscreen connected to
279	  your system.
280
281	  If unsure, say N.
282
283	  To compile this driver as a module, choose M here: the
284	  module will be called touchright.
285
286config TOUCHSCREEN_TOUCHWIN
287	tristate "Touchwin serial touchscreen"
288	select SERIO
289	help
290	  Say Y here if you have a Touchwin serial touchscreen connected to
291	  your 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 touchwin.
297
298config TOUCHSCREEN_ATMEL_TSADCC
299	tristate "Atmel Touchscreen Interface"
300	depends on ARCH_AT91SAM9RL
301	help
302	  Say Y here if you have a 4-wire touchscreen connected to the
303          ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
304
305	  If unsure, say N.
306
307	  To compile this driver as a module, choose M here: the
308	  module will be called atmel_tsadcc.
309
310config TOUCHSCREEN_UCB1400
311	tristate "Philips UCB1400 touchscreen"
312	depends on AC97_BUS
313	depends on UCB1400_CORE
314	help
315	  This enables support for the Philips UCB1400 touchscreen interface.
316	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
317	  will be initialized only after the ALSA subsystem has been
318	  brought up and the UCB1400 detected.  You therefore have to
319	  configure ALSA support as well (either built-in or modular,
320	  independently of whether this driver is itself built-in or
321	  modular) for this driver to work.
322
323	  To compile this driver as a module, choose M here: the
324	  module will be called ucb1400_ts.
325
326config TOUCHSCREEN_WM97XX
327	tristate "Support for WM97xx AC97 touchscreen controllers"
328	depends on AC97_BUS
329	help
330	  Say Y here if you have a Wolfson Microelectronics WM97xx
331	  touchscreen connected to your system. Note that this option
332	  only enables core driver, you will also need to select
333	  support for appropriate chip below.
334
335	  If unsure, say N.
336
337	  To compile this driver as a module, choose M here: the
338	  module will be called wm97xx-ts.
339
340config TOUCHSCREEN_WM9705
341	bool "WM9705 Touchscreen interface support"
342	depends on TOUCHSCREEN_WM97XX
343	default y
344	help
345	  Say Y here to enable support for the Wolfson Microelectronics
346	  WM9705 touchscreen controller.
347
348config TOUCHSCREEN_WM9712
349	bool "WM9712 Touchscreen interface support"
350	depends on TOUCHSCREEN_WM97XX
351	default y
352	help
353	  Say Y here to enable support for the Wolfson Microelectronics
354	  WM9712 touchscreen controller.
355
356config TOUCHSCREEN_WM9713
357	bool "WM9713 Touchscreen interface support"
358	depends on TOUCHSCREEN_WM97XX
359	default y
360	help
361	  Say Y here to enable support for the Wolfson Microelectronics
362	  WM9713 touchscreen controller.
363
364config TOUCHSCREEN_WM97XX_ATMEL
365	tristate "WM97xx Atmel accelerated touch"
366	depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
367	help
368	  Say Y here for support for streaming mode with WM97xx touchscreens
369	  on Atmel AT91 or AVR32 systems with an AC97C module.
370
371	  Be aware that this will use channel B in the controller for
372	  streaming data, this must not conflict with other AC97C drivers.
373
374	  If unsure, say N.
375
376	  To compile this driver as a module, choose M here: the module will
377	  be called atmel-wm97xx.
378
379config TOUCHSCREEN_WM97XX_MAINSTONE
380	tristate "WM97xx Mainstone/Palm accelerated touch"
381	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
382	help
383	  Say Y here for support for streaming mode with WM97xx touchscreens
384	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
385
386	  If unsure, say N.
387
388	  To compile this driver as a module, choose M here: the
389	  module will be called mainstone-wm97xx.
390
391config TOUCHSCREEN_WM97XX_ZYLONITE
392	tristate "Zylonite accelerated touch"
393	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
394	select TOUCHSCREEN_WM9713
395	help
396	  Say Y here for support for streaming mode with the touchscreen
397	  on Zylonite systems.
398
399	  If unsure, say N.
400
401	  To compile this driver as a module, choose M here: the
402	  module will be called zylonite-wm97xx.
403
404config TOUCHSCREEN_USB_COMPOSITE
405	tristate "USB Touchscreen Driver"
406	depends on USB_ARCH_HAS_HCD
407	select USB
408	help
409	  USB Touchscreen driver for:
410	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
411	  - PanJit TouchSet USB
412	  - 3M MicroTouch USB (EX II series)
413	  - ITM
414	  - some other eTurboTouch
415	  - Gunze AHL61
416	  - DMC TSC-10/25
417	  - IRTOUCHSYSTEMS/UNITOP
418	  - IdealTEK URTC1000
419	  - GoTop Super_Q2/GogoPen/PenPower tablets
420	  - JASTEC USB Touch Controller/DigiTech DTR-02U
421
422	  Have a look at <http://linux.chapter7.ch/touchkit/> for
423	  a usage description and the required user-space stuff.
424
425	  To compile this driver as a module, choose M here: the
426	  module will be called usbtouchscreen.
427
428config TOUCHSCREEN_USB_EGALAX
429	default y
430	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
431	depends on TOUCHSCREEN_USB_COMPOSITE
432
433config TOUCHSCREEN_USB_PANJIT
434	default y
435	bool "PanJit device support" if EMBEDDED
436	depends on TOUCHSCREEN_USB_COMPOSITE
437
438config TOUCHSCREEN_USB_3M
439	default y
440	bool "3M/Microtouch EX II series device support" if EMBEDDED
441	depends on TOUCHSCREEN_USB_COMPOSITE
442
443config TOUCHSCREEN_USB_ITM
444	default y
445	bool "ITM device support" if EMBEDDED
446	depends on TOUCHSCREEN_USB_COMPOSITE
447
448config TOUCHSCREEN_USB_ETURBO
449	default y
450	bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
451	depends on TOUCHSCREEN_USB_COMPOSITE
452
453config TOUCHSCREEN_USB_GUNZE
454	default y
455	bool "Gunze AHL61 device support" if EMBEDDED
456	depends on TOUCHSCREEN_USB_COMPOSITE
457
458config TOUCHSCREEN_USB_DMC_TSC10
459	default y
460	bool "DMC TSC-10/25 device support" if EMBEDDED
461	depends on TOUCHSCREEN_USB_COMPOSITE
462
463config TOUCHSCREEN_USB_IRTOUCH
464	default y
465	bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED
466	depends on TOUCHSCREEN_USB_COMPOSITE
467
468config TOUCHSCREEN_USB_IDEALTEK
469	default y
470	bool "IdealTEK URTC1000 device support" if EMBEDDED
471	depends on TOUCHSCREEN_USB_COMPOSITE
472
473config TOUCHSCREEN_USB_GENERAL_TOUCH
474	default y
475	bool "GeneralTouch Touchscreen device support" if EMBEDDED
476	depends on TOUCHSCREEN_USB_COMPOSITE
477
478config TOUCHSCREEN_USB_GOTOP
479	default y
480	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED
481	depends on TOUCHSCREEN_USB_COMPOSITE
482
483config TOUCHSCREEN_USB_JASTEC
484	default y
485	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EMBEDDED
486	depends on TOUCHSCREEN_USB_COMPOSITE
487
488config TOUCHSCREEN_USB_E2I
489	default y
490	bool "e2i Touchscreen controller (e.g. from Mimo 740)"
491	depends on TOUCHSCREEN_USB_COMPOSITE
492
493config TOUCHSCREEN_TOUCHIT213
494	tristate "Sahara TouchIT-213 touchscreen"
495	select SERIO
496	help
497	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.
498
499	  If unsure, say N.
500
501	  To compile this driver as a module, choose M here: the
502	  module will be called touchit213.
503
504config TOUCHSCREEN_TSC2007
505	tristate "TSC2007 based touchscreens"
506	depends on I2C
507	help
508	  Say Y here if you have a TSC2007 based touchscreen.
509
510	  If unsure, say N.
511
512	  To compile this driver as a module, choose M here: the
513	  module will be called tsc2007.
514
515config TOUCHSCREEN_W90X900
516	tristate "W90P910 touchscreen driver"
517	depends on HAVE_CLK
518	help
519	  Say Y here if you have a W90P910 based touchscreen.
520
521	  To compile this driver as a module, choose M here: the
522	  module will be called w90p910_ts.
523
524config TOUCHSCREEN_PCAP
525	tristate "Motorola PCAP touchscreen"
526	depends on EZX_PCAP
527	help
528	  Say Y here if you have a Motorola EZX telephone and
529	  want to enable support for the built-in touchscreen.
530
531	  To compile this driver as a module, choose M here: the
532	  module will be called pcap_ts.
533endif
534