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