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