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