• Home
  • History
  • Annotate
  • Line#
  • Navigate
  • Raw
  • Download
  • only in /netgear-R7000-V1.0.7.12_1.2.5/components/opensource/linux/linux-2.6.36/drivers/input/touchscreen/
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_BITSY
90	tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
91	depends on SA1100_BITSY
92	select SERIO
93	help
94	  Say Y here if you have the h3600 (Bitsy) touchscreen.
95
96	  If unsure, say N.
97
98	  To compile this driver as a module, choose M here: the
99	  module will be called h3600_ts_input.
100
101config TOUCHSCREEN_CY8CTMG110
102	tristate "cy8ctmg110 touchscreen"
103	depends on I2C
104	depends on GPIOLIB
105
106	help
107	  Say Y here if you have a cy8ctmg110 capacitive touchscreen on
108	  an AAVA device.
109
110	  If unsure, say N.
111
112	  To compile this driver as a module, choose M here: the
113	  module will be called cy8ctmg110_ts.
114
115config TOUCHSCREEN_DA9034
116	tristate "Touchscreen support for Dialog Semiconductor DA9034"
117	depends on PMIC_DA903X
118	default y
119	help
120	  Say Y here to enable the support for the touchscreen found
121	  on Dialog Semiconductor DA9034 PMIC.
122
123config TOUCHSCREEN_DYNAPRO
124	tristate "Dynapro serial touchscreen"
125	select SERIO
126	help
127	  Say Y here if you have a Dynapro serial touchscreen connected to
128	  your system.
129
130	  If unsure, say N.
131
132	  To compile this driver as a module, choose M here: the
133	  module will be called dynapro.
134
135config TOUCHSCREEN_HAMPSHIRE
136	tristate "Hampshire serial touchscreen"
137	select SERIO
138	help
139	  Say Y here if you have a Hampshire serial touchscreen connected to
140	  your system.
141
142	  If unsure, say N.
143
144	  To compile this driver as a module, choose M here: the
145	  module will be called hampshire.
146
147config TOUCHSCREEN_EETI
148	tristate "EETI touchscreen panel support"
149	depends on I2C
150	help
151	  Say Y here to enable support for I2C connected EETI touch panels.
152
153	  To compile this driver as a module, choose M here: the
154	  module will be called eeti_ts.
155
156config TOUCHSCREEN_FUJITSU
157	tristate "Fujitsu serial touchscreen"
158	select SERIO
159	help
160	  Say Y here if you have the Fujitsu touchscreen (such as one
161	  installed in Lifebook P series laptop) connected to your
162	  system.
163
164	  If unsure, say N.
165
166	  To compile this driver as a module, choose M here: the
167	  module will be called fujitsu-ts.
168
169config TOUCHSCREEN_S3C2410
170	tristate "Samsung S3C2410/generic touchscreen input driver"
171	depends on ARCH_S3C2410 || SAMSUNG_DEV_TS
172	select S3C_ADC
173	help
174	  Say Y here if you have the s3c2410 touchscreen.
175
176	  If unsure, say N.
177
178	  To compile this driver as a module, choose M here: the
179	  module will be called s3c2410_ts.
180
181config TOUCHSCREEN_GUNZE
182	tristate "Gunze AHL-51S touchscreen"
183	select SERIO
184	help
185	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
186	  your system.
187
188	  If unsure, say N.
189
190	  To compile this driver as a module, choose M here: the
191	  module will be called gunze.
192
193config TOUCHSCREEN_ELO
194	tristate "Elo serial touchscreens"
195	select SERIO
196	help
197	  Say Y here if you have an Elo serial touchscreen connected to
198	  your system.
199
200	  If unsure, say N.
201
202	  To compile this driver as a module, choose M here: the
203	  module will be called elo.
204
205config TOUCHSCREEN_WACOM_W8001
206	tristate "Wacom W8001 penabled serial touchscreen"
207	select SERIO
208	help
209	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
210	  connected to your system.
211
212	  If unsure, say N.
213
214	  To compile this driver as a module, choose M here: the
215	  module will be called wacom_w8001.
216
217config TOUCHSCREEN_MCS5000
218	tristate "MELFAS MCS-5000 touchscreen"
219	depends on I2C
220	help
221	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
222	  chip in your system.
223
224	  If unsure, say N.
225
226	  To compile this driver as a module, choose M here: the
227	  module will be called mcs5000_ts.
228
229config TOUCHSCREEN_MTOUCH
230	tristate "MicroTouch serial touchscreens"
231	select SERIO
232	help
233	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
234	  your system.
235
236	  If unsure, say N.
237
238	  To compile this driver as a module, choose M here: the
239	  module will be called mtouch.
240
241config TOUCHSCREEN_INEXIO
242	tristate "iNexio serial touchscreens"
243	select SERIO
244	help
245	  Say Y here if you have an iNexio serial touchscreen connected to
246	  your system.
247
248	  If unsure, say N.
249
250	  To compile this driver as a module, choose M here: the
251	  module will be called inexio.
252
253config TOUCHSCREEN_MK712
254	tristate "ICS MicroClock MK712 touchscreen"
255	help
256	  Say Y here if you have the ICS MicroClock MK712 touchscreen
257	  controller chip in your system.
258
259	  If unsure, say N.
260
261	  To compile this driver as a module, choose M here: the
262	  module will be called mk712.
263
264config TOUCHSCREEN_HP600
265	tristate "HP Jornada 6xx touchscreen"
266	depends on SH_HP6XX && SH_ADC
267	help
268	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
269          support the built-in touchscreen.
270
271	  To compile this driver as a module, choose M here: the
272	  module will be called hp680_ts_input.
273
274config TOUCHSCREEN_HP7XX
275	tristate "HP Jornada 7xx touchscreen"
276	depends on SA1100_JORNADA720_SSP
277	help
278	  Say Y here if you have a HP Jornada 710/720/728 and want
279	  to support the built-in touchscreen.
280
281	  To compile this driver as a module, choose M here: the
282	  module will be called jornada720_ts.
283
284config TOUCHSCREEN_HTCPEN
285	tristate "HTC Shift X9500 touchscreen"
286	depends on ISA
287	help
288	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
289	  Clio / Shangrila and want to support the built-in touchscreen.
290
291	  If unsure, say N.
292
293	  To compile this driver as a module, choose M here: the
294	  module will be called htcpen.
295
296config TOUCHSCREEN_PENMOUNT
297	tristate "Penmount serial touchscreen"
298	select SERIO
299	help
300	  Say Y here if you have a Penmount serial touchscreen connected to
301	  your system.
302
303	  If unsure, say N.
304
305	  To compile this driver as a module, choose M here: the
306	  module will be called penmount.
307
308config TOUCHSCREEN_QT602240
309	tristate "QT602240 I2C Touchscreen"
310	depends on I2C
311	help
312	  Say Y here if you have the AT42QT602240/ATMXT224 I2C touchscreen
313	  connected to 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 qt602240_ts.
319
320config TOUCHSCREEN_MIGOR
321	tristate "Renesas MIGO-R touchscreen"
322	depends on SH_MIGOR && I2C
323	help
324	  Say Y here to enable MIGO-R touchscreen support.
325
326	  If unsure, say N.
327
328	  To compile this driver as a module, choose M here: the
329	  module will be called migor_ts.
330
331config TOUCHSCREEN_TOUCHRIGHT
332	tristate "Touchright serial touchscreen"
333	select SERIO
334	help
335	  Say Y here if you have a Touchright serial touchscreen connected to
336	  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 touchright.
342
343config TOUCHSCREEN_TOUCHWIN
344	tristate "Touchwin serial touchscreen"
345	select SERIO
346	help
347	  Say Y here if you have a Touchwin 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 touchwin.
354
355config TOUCHSCREEN_ATMEL_TSADCC
356	tristate "Atmel Touchscreen Interface"
357	depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
358	help
359	  Say Y here if you have a 4-wire touchscreen connected to the
360          ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
361
362	  If unsure, say N.
363
364	  To compile this driver as a module, choose M here: the
365	  module will be called atmel_tsadcc.
366
367config TOUCHSCREEN_UCB1400
368	tristate "Philips UCB1400 touchscreen"
369	depends on AC97_BUS
370	depends on UCB1400_CORE
371	help
372	  This enables support for the Philips UCB1400 touchscreen interface.
373	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
374	  will be initialized only after the ALSA subsystem has been
375	  brought up and the UCB1400 detected.  You therefore have to
376	  configure ALSA support as well (either built-in or modular,
377	  independently of whether this driver is itself built-in or
378	  modular) for this driver to work.
379
380	  To compile this driver as a module, choose M here: the
381	  module will be called ucb1400_ts.
382
383config TOUCHSCREEN_WM97XX
384	tristate "Support for WM97xx AC97 touchscreen controllers"
385	depends on AC97_BUS
386	help
387	  Say Y here if you have a Wolfson Microelectronics WM97xx
388	  touchscreen connected to your system. Note that this option
389	  only enables core driver, you will also need to select
390	  support for appropriate chip below.
391
392	  If unsure, say N.
393
394	  To compile this driver as a module, choose M here: the
395	  module will be called wm97xx-ts.
396
397config TOUCHSCREEN_WM9705
398	bool "WM9705 Touchscreen interface support"
399	depends on TOUCHSCREEN_WM97XX
400	default y
401	help
402	  Say Y here to enable support for the Wolfson Microelectronics
403	  WM9705 touchscreen controller.
404
405config TOUCHSCREEN_WM9712
406	bool "WM9712 Touchscreen interface support"
407	depends on TOUCHSCREEN_WM97XX
408	default y
409	help
410	  Say Y here to enable support for the Wolfson Microelectronics
411	  WM9712 touchscreen controller.
412
413config TOUCHSCREEN_WM9713
414	bool "WM9713 Touchscreen interface support"
415	depends on TOUCHSCREEN_WM97XX
416	default y
417	help
418	  Say Y here to enable support for the Wolfson Microelectronics
419	  WM9713 touchscreen controller.
420
421config TOUCHSCREEN_WM97XX_ATMEL
422	tristate "WM97xx Atmel accelerated touch"
423	depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
424	help
425	  Say Y here for support for streaming mode with WM97xx touchscreens
426	  on Atmel AT91 or AVR32 systems with an AC97C module.
427
428	  Be aware that this will use channel B in the controller for
429	  streaming data, this must not conflict with other AC97C drivers.
430
431	  If unsure, say N.
432
433	  To compile this driver as a module, choose M here: the module will
434	  be called atmel-wm97xx.
435
436config TOUCHSCREEN_WM97XX_MAINSTONE
437	tristate "WM97xx Mainstone/Palm accelerated touch"
438	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
439	help
440	  Say Y here for support for streaming mode with WM97xx touchscreens
441	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
442
443	  If unsure, say N.
444
445	  To compile this driver as a module, choose M here: the
446	  module will be called mainstone-wm97xx.
447
448config TOUCHSCREEN_WM97XX_ZYLONITE
449	tristate "Zylonite accelerated touch"
450	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
451	select TOUCHSCREEN_WM9713
452	help
453	  Say Y here for support for streaming mode with the touchscreen
454	  on Zylonite systems.
455
456	  If unsure, say N.
457
458	  To compile this driver as a module, choose M here: the
459	  module will be called zylonite-wm97xx.
460
461config TOUCHSCREEN_USB_COMPOSITE
462	tristate "USB Touchscreen Driver"
463	depends on USB_ARCH_HAS_HCD
464	select USB
465	help
466	  USB Touchscreen driver for:
467	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
468	  - PanJit TouchSet USB
469	  - 3M MicroTouch USB (EX II series)
470	  - ITM
471	  - some other eTurboTouch
472	  - Gunze AHL61
473	  - DMC TSC-10/25
474	  - IRTOUCHSYSTEMS/UNITOP
475	  - IdealTEK URTC1000
476	  - GoTop Super_Q2/GogoPen/PenPower tablets
477	  - JASTEC USB Touch Controller/DigiTech DTR-02U
478	  - Zytronic controllers
479
480	  Have a look at <http://linux.chapter7.ch/touchkit/> for
481	  a usage description and the required user-space stuff.
482
483	  To compile this driver as a module, choose M here: the
484	  module will be called usbtouchscreen.
485
486config TOUCHSCREEN_MC13783
487	tristate "Freescale MC13783 touchscreen input driver"
488	depends on MFD_MC13783
489	help
490	  Say Y here if you have an Freescale MC13783 PMIC on your
491	  board and want to use its touchscreen
492
493	  If unsure, say N.
494
495	  To compile this driver as a module, choose M here: the
496	  module will be called mc13783_ts.
497
498config TOUCHSCREEN_USB_EGALAX
499	default y
500	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
501	depends on TOUCHSCREEN_USB_COMPOSITE
502
503config TOUCHSCREEN_USB_PANJIT
504	default y
505	bool "PanJit device support" if EMBEDDED
506	depends on TOUCHSCREEN_USB_COMPOSITE
507
508config TOUCHSCREEN_USB_3M
509	default y
510	bool "3M/Microtouch EX II series device support" if EMBEDDED
511	depends on TOUCHSCREEN_USB_COMPOSITE
512
513config TOUCHSCREEN_USB_ITM
514	default y
515	bool "ITM device support" if EMBEDDED
516	depends on TOUCHSCREEN_USB_COMPOSITE
517
518config TOUCHSCREEN_USB_ETURBO
519	default y
520	bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
521	depends on TOUCHSCREEN_USB_COMPOSITE
522
523config TOUCHSCREEN_USB_GUNZE
524	default y
525	bool "Gunze AHL61 device support" if EMBEDDED
526	depends on TOUCHSCREEN_USB_COMPOSITE
527
528config TOUCHSCREEN_USB_DMC_TSC10
529	default y
530	bool "DMC TSC-10/25 device support" if EMBEDDED
531	depends on TOUCHSCREEN_USB_COMPOSITE
532
533config TOUCHSCREEN_USB_IRTOUCH
534	default y
535	bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED
536	depends on TOUCHSCREEN_USB_COMPOSITE
537
538config TOUCHSCREEN_USB_IDEALTEK
539	default y
540	bool "IdealTEK URTC1000 device support" if EMBEDDED
541	depends on TOUCHSCREEN_USB_COMPOSITE
542
543config TOUCHSCREEN_USB_GENERAL_TOUCH
544	default y
545	bool "GeneralTouch Touchscreen device support" if EMBEDDED
546	depends on TOUCHSCREEN_USB_COMPOSITE
547
548config TOUCHSCREEN_USB_GOTOP
549	default y
550	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED
551	depends on TOUCHSCREEN_USB_COMPOSITE
552
553config TOUCHSCREEN_USB_JASTEC
554	default y
555	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EMBEDDED
556	depends on TOUCHSCREEN_USB_COMPOSITE
557
558config TOUCHSCREEN_USB_E2I
559	default y
560	bool "e2i Touchscreen controller (e.g. from Mimo 740)"
561	depends on TOUCHSCREEN_USB_COMPOSITE
562
563config TOUCHSCREEN_USB_ZYTRONIC
564	default y
565	bool "Zytronic controller" if EMBEDDED
566	depends on TOUCHSCREEN_USB_COMPOSITE
567
568config TOUCHSCREEN_USB_ETT_TC45USB
569	default y
570	bool "ET&T USB series TC4UM/TC5UH touchscreen controler support" if EMBEDDED
571	depends on TOUCHSCREEN_USB_COMPOSITE
572
573config TOUCHSCREEN_USB_NEXIO
574	default y
575	bool "NEXIO/iNexio device support" if EMBEDDED
576	depends on TOUCHSCREEN_USB_COMPOSITE
577
578config TOUCHSCREEN_TOUCHIT213
579	tristate "Sahara TouchIT-213 touchscreen"
580	select SERIO
581	help
582	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.
583
584	  If unsure, say N.
585
586	  To compile this driver as a module, choose M here: the
587	  module will be called touchit213.
588
589config TOUCHSCREEN_TSC2007
590	tristate "TSC2007 based touchscreens"
591	depends on I2C
592	help
593	  Say Y here if you have a TSC2007 based touchscreen.
594
595	  If unsure, say N.
596
597	  To compile this driver as a module, choose M here: the
598	  module will be called tsc2007.
599
600config TOUCHSCREEN_W90X900
601	tristate "W90P910 touchscreen driver"
602	depends on HAVE_CLK
603	help
604	  Say Y here if you have a W90P910 based touchscreen.
605
606	  To compile this driver as a module, choose M here: the
607	  module will be called w90p910_ts.
608
609config TOUCHSCREEN_PCAP
610	tristate "Motorola PCAP touchscreen"
611	depends on EZX_PCAP
612	help
613	  Say Y here if you have a Motorola EZX telephone and
614	  want to enable support for the built-in touchscreen.
615
616	  To compile this driver as a module, choose M here: the
617	  module will be called pcap_ts.
618
619config TOUCHSCREEN_TPS6507X
620	tristate "TPS6507x based touchscreens"
621	depends on I2C
622	help
623	  Say Y here if you have a TPS6507x based touchscreen
624	  controller.
625
626	  If unsure, say N.
627
628	  To compile this driver as a module, choose M here: the
629	  module will be called tps6507x_ts.
630
631config TOUCHSCREEN_STMPE
632	tristate "STMicroelectronics STMPE touchscreens"
633	depends on MFD_STMPE
634	help
635	  Say Y here if you want support for STMicroelectronics
636	  STMPE touchscreen controllers.
637
638	  To compile this driver as a module, choose M here: the
639	  module will be called stmpe-ts.
640
641endif
642