Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
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_DA9034
171 tristate "Touchscreen support for Dialog Semiconductor DA9034"
172 depends on PMIC_DA903X
173 default y
174 help
175 Say Y here to enable the support for the touchscreen found
176 on Dialog Semiconductor DA9034 PMIC.
177
178 If unsure, say N.
179
180 To compile this driver as a module, choose M here: the
181 module will be called da9034-ts.
182
183config TOUCHSCREEN_DA9052
184 tristate "Dialog DA9052/DA9053 TSI"
185 depends on PMIC_DA9052
186 help
187 Say Y here to support the touchscreen found on Dialog Semiconductor
188 DA9052-BC and DA9053-AA/Bx PMICs.
189
190 If unsure, say N.
191
192 To compile this driver as a module, choose M here: the
193 module will be called da9052_tsi.
194
195config TOUCHSCREEN_DYNAPRO
196 tristate "Dynapro serial touchscreen"
197 select SERIO
198 help
199 Say Y here if you have a Dynapro serial touchscreen connected to
200 your system.
201
202 If unsure, say N.
203
204 To compile this driver as a module, choose M here: the
205 module will be called dynapro.
206
207config TOUCHSCREEN_HAMPSHIRE
208 tristate "Hampshire serial touchscreen"
209 select SERIO
210 help
211 Say Y here if you have a Hampshire 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 hampshire.
218
219config TOUCHSCREEN_EETI
220 tristate "EETI touchscreen panel support"
221 depends on I2C
222 help
223 Say Y here to enable support for I2C connected EETI touch panels.
224
225 To compile this driver as a module, choose M here: the
226 module will be called eeti_ts.
227
228config TOUCHSCREEN_EGALAX
229 tristate "EETI eGalax multi-touch panel support"
230 depends on I2C && OF
231 help
232 Say Y here to enable support for I2C connected EETI
233 eGalax multi-touch panels.
234
235 To compile this driver as a module, choose M here: the
236 module will be called egalax_ts.
237
238config TOUCHSCREEN_FUJITSU
239 tristate "Fujitsu serial touchscreen"
240 select SERIO
241 help
242 Say Y here if you have the Fujitsu touchscreen (such as one
243 installed in Lifebook P series laptop) connected to your
244 system.
245
246 If unsure, say N.
247
248 To compile this driver as a module, choose M here: the
249 module will be called fujitsu-ts.
250
251config TOUCHSCREEN_ILI210X
252 tristate "Ilitek ILI210X based touchscreen"
253 depends on I2C
254 help
255 Say Y here if you have a ILI210X based touchscreen
256 controller. This driver supports models ILI2102,
257 ILI2102s, ILI2103, ILI2103s and ILI2105.
258 Such kind of chipsets can be found in Amazon Kindle Fire
259 touchscreens.
260
261 If unsure, say N.
262
263 To compile this driver as a module, choose M here: the
264 module will be called ili210x.
265
266config TOUCHSCREEN_S3C2410
267 tristate "Samsung S3C2410/generic touchscreen input driver"
268 depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
269 select S3C_ADC
270 help
271 Say Y here if you have the s3c2410 touchscreen.
272
273 If unsure, say N.
274
275 To compile this driver as a module, choose M here: the
276 module will be called s3c2410_ts.
277
278config TOUCHSCREEN_GUNZE
279 tristate "Gunze AHL-51S touchscreen"
280 select SERIO
281 help
282 Say Y here if you have the Gunze AHL-51 touchscreen connected to
283 your system.
284
285 If unsure, say N.
286
287 To compile this driver as a module, choose M here: the
288 module will be called gunze.
289
290config TOUCHSCREEN_ELO
291 tristate "Elo serial touchscreens"
292 select SERIO
293 help
294 Say Y here if you have an Elo serial 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 elo.
301
302config TOUCHSCREEN_WACOM_W8001
303 tristate "Wacom W8001 penabled serial touchscreen"
304 select SERIO
305 help
306 Say Y here if you have an Wacom W8001 penabled serial touchscreen
307 connected to 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 wacom_w8001.
313
314config TOUCHSCREEN_WACOM_I2C
315 tristate "Wacom Tablet support (I2C)"
316 depends on I2C
317 help
318 Say Y here if you want to use the I2C version of the Wacom
319 Pen Tablet.
320
321 If unsure, say N.
322
323 To compile this driver as a module, choose M here: the module
324 will be called wacom_i2c.
325
326config TOUCHSCREEN_LPC32XX
327 tristate "LPC32XX touchscreen controller"
328 depends on ARCH_LPC32XX
329 help
330 Say Y here if you have a LPC32XX device and want
331 to support the built-in touchscreen.
332
333 To compile this driver as a module, choose M here: the
334 module will be called lpc32xx_ts.
335
336config TOUCHSCREEN_MAX11801
337 tristate "MAX11801 based touchscreens"
338 depends on I2C
339 help
340 Say Y here if you have a MAX11801 based touchscreen
341 controller.
342
343 If unsure, say N.
344
345 To compile this driver as a module, choose M here: the
346 module will be called max11801_ts.
347
348config TOUCHSCREEN_MCS5000
349 tristate "MELFAS MCS-5000 touchscreen"
350 depends on I2C
351 help
352 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
353 chip in your system.
354
355 If unsure, say N.
356
357 To compile this driver as a module, choose M here: the
358 module will be called mcs5000_ts.
359
360config TOUCHSCREEN_MMS114
361 tristate "MELFAS MMS114 touchscreen"
362 depends on I2C
363 help
364 Say Y here if you have the MELFAS MMS114 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 mms114.
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_EDT_FT5X06
464 tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
465 depends on I2C
466 help
467 Say Y here if you have an EDT "Polytouch" touchscreen based
468 on the FocalTech FT5x06 family of controllers connected to
469 your system.
470
471 If unsure, say N.
472
473 To compile this driver as a module, choose M here: the
474 module will be called edt-ft5x06.
475
476config TOUCHSCREEN_MIGOR
477 tristate "Renesas MIGO-R touchscreen"
478 depends on SH_MIGOR && I2C
479 help
480 Say Y here to enable MIGO-R touchscreen support.
481
482 If unsure, say N.
483
484 To compile this driver as a module, choose M here: the
485 module will be called migor_ts.
486
487config TOUCHSCREEN_TNETV107X
488 tristate "TI TNETV107X touchscreen support"
489 depends on ARCH_DAVINCI_TNETV107X
490 help
491 Say Y here if you want to use the TNETV107X touchscreen.
492
493 To compile this driver as a module, choose M here: the
494 module will be called tnetv107x-ts.
495
496config TOUCHSCREEN_TOUCHRIGHT
497 tristate "Touchright serial touchscreen"
498 select SERIO
499 help
500 Say Y here if you have a Touchright serial touchscreen connected to
501 your system.
502
503 If unsure, say N.
504
505 To compile this driver as a module, choose M here: the
506 module will be called touchright.
507
508config TOUCHSCREEN_TOUCHWIN
509 tristate "Touchwin serial touchscreen"
510 select SERIO
511 help
512 Say Y here if you have a Touchwin serial touchscreen connected to
513 your system.
514
515 If unsure, say N.
516
517 To compile this driver as a module, choose M here: the
518 module will be called touchwin.
519
520config TOUCHSCREEN_TI_AM335X_TSC
521 tristate "TI Touchscreen Interface"
522 depends on MFD_TI_AM335X_TSCADC
523 help
524 Say Y here if you have 4/5/8 wire touchscreen controller
525 to be connected to the ADC controller on your TI AM335x SoC.
526
527 If unsure, say N.
528
529 To compile this driver as a module, choose M here: the
530 module will be called ti_am335x_tsc.
531
532config TOUCHSCREEN_ATMEL_TSADCC
533 tristate "Atmel Touchscreen Interface"
534 depends on ARCH_AT91
535 help
536 Say Y here if you have a 4-wire touchscreen connected to the
537 ADC Controller on your Atmel SoC.
538
539 If unsure, say N.
540
541 To compile this driver as a module, choose M here: the
542 module will be called atmel_tsadcc.
543
544config TOUCHSCREEN_UCB1400
545 tristate "Philips UCB1400 touchscreen"
546 depends on AC97_BUS
547 depends on UCB1400_CORE
548 help
549 This enables support for the Philips UCB1400 touchscreen interface.
550 The UCB1400 is an AC97 audio codec. The touchscreen interface
551 will be initialized only after the ALSA subsystem has been
552 brought up and the UCB1400 detected. You therefore have to
553 configure ALSA support as well (either built-in or modular,
554 independently of whether this driver is itself built-in or
555 modular) for this driver to work.
556
557 To compile this driver as a module, choose M here: the
558 module will be called ucb1400_ts.
559
560config TOUCHSCREEN_PIXCIR
561 tristate "PIXCIR I2C touchscreens"
562 depends on I2C
563 help
564 Say Y here if you have a pixcir i2c touchscreen
565 controller.
566
567 If unsure, say N.
568
569 To compile this driver as a module, choose M here: the
570 module will be called pixcir_i2c_ts.
571
572config TOUCHSCREEN_WM831X
573 tristate "Support for WM831x touchscreen controllers"
574 depends on MFD_WM831X
575 help
576 This enables support for the touchscreen controller on the WM831x
577 series of PMICs.
578
579 To compile this driver as a module, choose M here: the
580 module will be called wm831x-ts.
581
582config TOUCHSCREEN_WM97XX
583 tristate "Support for WM97xx AC97 touchscreen controllers"
584 depends on AC97_BUS
585 help
586 Say Y here if you have a Wolfson Microelectronics WM97xx
587 touchscreen connected to your system. Note that this option
588 only enables core driver, you will also need to select
589 support for appropriate chip below.
590
591 If unsure, say N.
592
593 To compile this driver as a module, choose M here: the
594 module will be called wm97xx-ts.
595
596config TOUCHSCREEN_WM9705
597 bool "WM9705 Touchscreen interface support"
598 depends on TOUCHSCREEN_WM97XX
599 default y
600 help
601 Say Y here to enable support for the Wolfson Microelectronics
602 WM9705 touchscreen controller.
603
604config TOUCHSCREEN_WM9712
605 bool "WM9712 Touchscreen interface support"
606 depends on TOUCHSCREEN_WM97XX
607 default y
608 help
609 Say Y here to enable support for the Wolfson Microelectronics
610 WM9712 touchscreen controller.
611
612config TOUCHSCREEN_WM9713
613 bool "WM9713 Touchscreen interface support"
614 depends on TOUCHSCREEN_WM97XX
615 default y
616 help
617 Say Y here to enable support for the Wolfson Microelectronics
618 WM9713 touchscreen controller.
619
620config TOUCHSCREEN_WM97XX_ATMEL
621 tristate "WM97xx Atmel accelerated touch"
622 depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
623 help
624 Say Y here for support for streaming mode with WM97xx touchscreens
625 on Atmel AT91 or AVR32 systems with an AC97C module.
626
627 Be aware that this will use channel B in the controller for
628 streaming data, this must not conflict with other AC97C drivers.
629
630 If unsure, say N.
631
632 To compile this driver as a module, choose M here: the module will
633 be called atmel-wm97xx.
634
635config TOUCHSCREEN_WM97XX_MAINSTONE
636 tristate "WM97xx Mainstone/Palm accelerated touch"
637 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
638 help
639 Say Y here for support for streaming mode with WM97xx touchscreens
640 on Mainstone, Palm Tungsten T5, TX and LifeDrive 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 mainstone-wm97xx.
646
647config TOUCHSCREEN_WM97XX_ZYLONITE
648 tristate "Zylonite accelerated touch"
649 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
650 select TOUCHSCREEN_WM9713
651 help
652 Say Y here for support for streaming mode with the touchscreen
653 on Zylonite systems.
654
655 If unsure, say N.
656
657 To compile this driver as a module, choose M here: the
658 module will be called zylonite-wm97xx.
659
660config TOUCHSCREEN_USB_COMPOSITE
661 tristate "USB Touchscreen Driver"
662 depends on USB_ARCH_HAS_HCD
663 select USB
664 help
665 USB Touchscreen driver for:
666 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
667 - PanJit TouchSet USB
668 - 3M MicroTouch USB (EX II series)
669 - ITM
670 - some other eTurboTouch
671 - Gunze AHL61
672 - DMC TSC-10/25
673 - IRTOUCHSYSTEMS/UNITOP
674 - IdealTEK URTC1000
675 - GoTop Super_Q2/GogoPen/PenPower tablets
676 - JASTEC USB Touch Controller/DigiTech DTR-02U
677 - Zytronic controllers
678 - Elo TouchSystems 2700 IntelliTouch
679 - EasyTouch USB Touch Controller from Data Modul
680 - e2i (Mimo monitors)
681
682 Have a look at <http://linux.chapter7.ch/touchkit/> for
683 a usage description and the required user-space stuff.
684
685 To compile this driver as a module, choose M here: the
686 module will be called usbtouchscreen.
687
688config TOUCHSCREEN_MC13783
689 tristate "Freescale MC13783 touchscreen input driver"
690 depends on MFD_MC13783
691 help
692 Say Y here if you have an Freescale MC13783 PMIC on your
693 board and want to use its touchscreen
694
695 If unsure, say N.
696
697 To compile this driver as a module, choose M here: the
698 module will be called mc13783_ts.
699
700config TOUCHSCREEN_USB_EGALAX
701 default y
702 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
703 depends on TOUCHSCREEN_USB_COMPOSITE
704
705config TOUCHSCREEN_USB_PANJIT
706 default y
707 bool "PanJit device support" if EXPERT
708 depends on TOUCHSCREEN_USB_COMPOSITE
709
710config TOUCHSCREEN_USB_3M
711 default y
712 bool "3M/Microtouch EX II series device support" if EXPERT
713 depends on TOUCHSCREEN_USB_COMPOSITE
714
715config TOUCHSCREEN_USB_ITM
716 default y
717 bool "ITM device support" if EXPERT
718 depends on TOUCHSCREEN_USB_COMPOSITE
719
720config TOUCHSCREEN_USB_ETURBO
721 default y
722 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
723 depends on TOUCHSCREEN_USB_COMPOSITE
724
725config TOUCHSCREEN_USB_GUNZE
726 default y
727 bool "Gunze AHL61 device support" if EXPERT
728 depends on TOUCHSCREEN_USB_COMPOSITE
729
730config TOUCHSCREEN_USB_DMC_TSC10
731 default y
732 bool "DMC TSC-10/25 device support" if EXPERT
733 depends on TOUCHSCREEN_USB_COMPOSITE
734
735config TOUCHSCREEN_USB_IRTOUCH
736 default y
737 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
738 depends on TOUCHSCREEN_USB_COMPOSITE
739
740config TOUCHSCREEN_USB_IDEALTEK
741 default y
742 bool "IdealTEK URTC1000 device support" if EXPERT
743 depends on TOUCHSCREEN_USB_COMPOSITE
744
745config TOUCHSCREEN_USB_GENERAL_TOUCH
746 default y
747 bool "GeneralTouch Touchscreen device support" if EXPERT
748 depends on TOUCHSCREEN_USB_COMPOSITE
749
750config TOUCHSCREEN_USB_GOTOP
751 default y
752 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
753 depends on TOUCHSCREEN_USB_COMPOSITE
754
755config TOUCHSCREEN_USB_JASTEC
756 default y
757 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
758 depends on TOUCHSCREEN_USB_COMPOSITE
759
760config TOUCHSCREEN_USB_ELO
761 default y
762 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
763 depends on TOUCHSCREEN_USB_COMPOSITE
764
765config TOUCHSCREEN_USB_E2I
766 default y
767 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
768 depends on TOUCHSCREEN_USB_COMPOSITE
769
770config TOUCHSCREEN_USB_ZYTRONIC
771 default y
772 bool "Zytronic controller" if EXPERT
773 depends on TOUCHSCREEN_USB_COMPOSITE
774
775config TOUCHSCREEN_USB_ETT_TC45USB
776 default y
777 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
778 depends on TOUCHSCREEN_USB_COMPOSITE
779
780config TOUCHSCREEN_USB_NEXIO
781 default y
782 bool "NEXIO/iNexio device support" if EXPERT
783 depends on TOUCHSCREEN_USB_COMPOSITE
784
785config TOUCHSCREEN_USB_EASYTOUCH
786 default y
787 bool "EasyTouch USB Touch controller device support" if EMBEDDED
788 depends on TOUCHSCREEN_USB_COMPOSITE
789 help
790 Say Y here if you have an EasyTouch USB Touch controller.
791 If unsure, say N.
792
793config TOUCHSCREEN_TOUCHIT213
794 tristate "Sahara TouchIT-213 touchscreen"
795 select SERIO
796 help
797 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
798
799 If unsure, say N.
800
801 To compile this driver as a module, choose M here: the
802 module will be called touchit213.
803
804config TOUCHSCREEN_TSC_SERIO
805 tristate "TSC-10/25/40 serial touchscreen support"
806 select SERIO
807 help
808 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
809 to your system.
810
811 If unsure, say N.
812
813 To compile this driver as a module, choose M here: the
814 module will be called tsc40.
815
816config TOUCHSCREEN_TSC2005
817 tristate "TSC2005 based touchscreens"
818 depends on SPI_MASTER && GENERIC_HARDIRQS
819 help
820 Say Y here if you have a TSC2005 based touchscreen.
821
822 If unsure, say N.
823
824 To compile this driver as a module, choose M here: the
825 module will be called tsc2005.
826
827config TOUCHSCREEN_TSC2007
828 tristate "TSC2007 based touchscreens"
829 depends on I2C
830 help
831 Say Y here if you have a TSC2007 based touchscreen.
832
833 If unsure, say N.
834
835 To compile this driver as a module, choose M here: the
836 module will be called tsc2007.
837
838config TOUCHSCREEN_W90X900
839 tristate "W90P910 touchscreen driver"
840 depends on HAVE_CLK
841 help
842 Say Y here if you have a W90P910 based touchscreen.
843
844 To compile this driver as a module, choose M here: the
845 module will be called w90p910_ts.
846
847config TOUCHSCREEN_PCAP
848 tristate "Motorola PCAP touchscreen"
849 depends on EZX_PCAP
850 help
851 Say Y here if you have a Motorola EZX telephone and
852 want to enable support for the built-in touchscreen.
853
854 To compile this driver as a module, choose M here: the
855 module will be called pcap_ts.
856
857config TOUCHSCREEN_ST1232
858 tristate "Sitronix ST1232 touchscreen controllers"
859 depends on I2C
860 help
861 Say Y here if you want to support Sitronix ST1232
862 touchscreen controller.
863
864 If unsure, say N.
865
866 To compile this driver as a module, choose M here: the
867 module will be called st1232_ts.
868
869config TOUCHSCREEN_STMPE
870 tristate "STMicroelectronics STMPE touchscreens"
871 depends on MFD_STMPE
872 help
873 Say Y here if you want support for STMicroelectronics
874 STMPE touchscreen controllers.
875
876 To compile this driver as a module, choose M here: the
877 module will be called stmpe-ts.
878
879config TOUCHSCREEN_TPS6507X
880 tristate "TPS6507x based touchscreens"
881 depends on I2C
882 help
883 Say Y here if you have a TPS6507x based touchscreen
884 controller.
885
886 If unsure, say N.
887
888 To compile this driver as a module, choose M here: the
889 module will be called tps6507x_ts.
890
891endif