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