Input: add driver for the Goodix touchpanel
[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_GOODIX
299 tristate "Goodix I2C touchscreen"
300 depends on I2C && ACPI
301 help
302 Say Y here if you have the Goodix touchscreen (such as one
303 installed in Onda v975w tablets) connected to your
304 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 goodix.
310
311 config TOUCHSCREEN_ILI210X
312 tristate "Ilitek ILI210X based touchscreen"
313 depends on I2C
314 help
315 Say Y here if you have a ILI210X based touchscreen
316 controller. This driver supports models ILI2102,
317 ILI2102s, ILI2103, ILI2103s and ILI2105.
318 Such kind of chipsets can be found in Amazon Kindle Fire
319 touchscreens.
320
321 If unsure, say N.
322
323 To compile this driver as a module, choose M here: the
324 module will be called ili210x.
325
326 config TOUCHSCREEN_S3C2410
327 tristate "Samsung S3C2410/generic touchscreen input driver"
328 depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
329 select S3C_ADC
330 help
331 Say Y here if you have the s3c2410 touchscreen.
332
333 If unsure, say N.
334
335 To compile this driver as a module, choose M here: the
336 module will be called s3c2410_ts.
337
338 config TOUCHSCREEN_GUNZE
339 tristate "Gunze AHL-51S touchscreen"
340 select SERIO
341 help
342 Say Y here if you have the Gunze AHL-51 touchscreen connected to
343 your system.
344
345 If unsure, say N.
346
347 To compile this driver as a module, choose M here: the
348 module will be called gunze.
349
350 config TOUCHSCREEN_ELO
351 tristate "Elo serial touchscreens"
352 select SERIO
353 help
354 Say Y here if you have an Elo serial touchscreen connected to
355 your system.
356
357 If unsure, say N.
358
359 To compile this driver as a module, choose M here: the
360 module will be called elo.
361
362 config TOUCHSCREEN_WACOM_W8001
363 tristate "Wacom W8001 penabled serial touchscreen"
364 select SERIO
365 help
366 Say Y here if you have an Wacom W8001 penabled serial touchscreen
367 connected to your system.
368
369 If unsure, say N.
370
371 To compile this driver as a module, choose M here: the
372 module will be called wacom_w8001.
373
374 config TOUCHSCREEN_WACOM_I2C
375 tristate "Wacom Tablet support (I2C)"
376 depends on I2C
377 help
378 Say Y here if you want to use the I2C version of the Wacom
379 Pen Tablet.
380
381 If unsure, say N.
382
383 To compile this driver as a module, choose M here: the module
384 will be called wacom_i2c.
385
386 config TOUCHSCREEN_LPC32XX
387 tristate "LPC32XX touchscreen controller"
388 depends on ARCH_LPC32XX
389 help
390 Say Y here if you have a LPC32XX device and want
391 to support the built-in touchscreen.
392
393 To compile this driver as a module, choose M here: the
394 module will be called lpc32xx_ts.
395
396 config TOUCHSCREEN_MAX11801
397 tristate "MAX11801 based touchscreens"
398 depends on I2C
399 help
400 Say Y here if you have a MAX11801 based touchscreen
401 controller.
402
403 If unsure, say N.
404
405 To compile this driver as a module, choose M here: the
406 module will be called max11801_ts.
407
408 config TOUCHSCREEN_MCS5000
409 tristate "MELFAS MCS-5000 touchscreen"
410 depends on I2C
411 help
412 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
413 chip in your system.
414
415 If unsure, say N.
416
417 To compile this driver as a module, choose M here: the
418 module will be called mcs5000_ts.
419
420 config TOUCHSCREEN_MMS114
421 tristate "MELFAS MMS114 touchscreen"
422 depends on I2C
423 help
424 Say Y here if you have the MELFAS MMS114 touchscreen controller
425 chip in your system.
426
427 If unsure, say N.
428
429 To compile this driver as a module, choose M here: the
430 module will be called mms114.
431
432 config TOUCHSCREEN_MTOUCH
433 tristate "MicroTouch serial touchscreens"
434 select SERIO
435 help
436 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
437 your system.
438
439 If unsure, say N.
440
441 To compile this driver as a module, choose M here: the
442 module will be called mtouch.
443
444 config TOUCHSCREEN_INEXIO
445 tristate "iNexio serial touchscreens"
446 select SERIO
447 help
448 Say Y here if you have an iNexio serial touchscreen connected to
449 your system.
450
451 If unsure, say N.
452
453 To compile this driver as a module, choose M here: the
454 module will be called inexio.
455
456 config TOUCHSCREEN_INTEL_MID
457 tristate "Intel MID platform resistive touchscreen"
458 depends on INTEL_SCU_IPC
459 help
460 Say Y here if you have a Intel MID based touchscreen in
461 your system.
462
463 If unsure, say N.
464
465 To compile this driver as a module, choose M here: the
466 module will be called intel_mid_touch.
467
468 config TOUCHSCREEN_MK712
469 tristate "ICS MicroClock MK712 touchscreen"
470 help
471 Say Y here if you have the ICS MicroClock MK712 touchscreen
472 controller chip in your system.
473
474 If unsure, say N.
475
476 To compile this driver as a module, choose M here: the
477 module will be called mk712.
478
479 config TOUCHSCREEN_HP600
480 tristate "HP Jornada 6xx touchscreen"
481 depends on SH_HP6XX && SH_ADC
482 help
483 Say Y here if you have a HP Jornada 620/660/680/690 and want to
484 support the built-in touchscreen.
485
486 To compile this driver as a module, choose M here: the
487 module will be called hp680_ts_input.
488
489 config TOUCHSCREEN_HP7XX
490 tristate "HP Jornada 7xx touchscreen"
491 depends on SA1100_JORNADA720_SSP
492 help
493 Say Y here if you have a HP Jornada 710/720/728 and want
494 to support the built-in touchscreen.
495
496 To compile this driver as a module, choose M here: the
497 module will be called jornada720_ts.
498
499 config TOUCHSCREEN_IPAQ_MICRO
500 tristate "HP iPAQ Atmel Micro ASIC touchscreen"
501 depends on MFD_IPAQ_MICRO
502 help
503 Say Y here to enable support for the touchscreen attached to
504 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
505
506 If unsure, say N.
507
508 To compile this driver as a module, choose M here: the
509 module will be called ipaq-micro-ts.
510
511 config TOUCHSCREEN_HTCPEN
512 tristate "HTC Shift X9500 touchscreen"
513 depends on ISA
514 help
515 Say Y here if you have an HTC Shift UMPC also known as HTC X9500
516 Clio / Shangrila and want to support the built-in touchscreen.
517
518 If unsure, say N.
519
520 To compile this driver as a module, choose M here: the
521 module will be called htcpen.
522
523 config TOUCHSCREEN_PENMOUNT
524 tristate "Penmount serial touchscreen"
525 select SERIO
526 help
527 Say Y here if you have a Penmount serial touchscreen 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 penmount.
534
535 config TOUCHSCREEN_EDT_FT5X06
536 tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
537 depends on I2C
538 help
539 Say Y here if you have an EDT "Polytouch" touchscreen based
540 on the FocalTech FT5x06 family of controllers connected to
541 your system.
542
543 If unsure, say N.
544
545 To compile this driver as a module, choose M here: the
546 module will be called edt-ft5x06.
547
548 config TOUCHSCREEN_MIGOR
549 tristate "Renesas MIGO-R touchscreen"
550 depends on SH_MIGOR && I2C
551 help
552 Say Y here to enable MIGO-R touchscreen support.
553
554 If unsure, say N.
555
556 To compile this driver as a module, choose M here: the
557 module will be called migor_ts.
558
559 config TOUCHSCREEN_TOUCHRIGHT
560 tristate "Touchright serial touchscreen"
561 select SERIO
562 help
563 Say Y here if you have a Touchright serial touchscreen connected to
564 your system.
565
566 If unsure, say N.
567
568 To compile this driver as a module, choose M here: the
569 module will be called touchright.
570
571 config TOUCHSCREEN_TOUCHWIN
572 tristate "Touchwin serial touchscreen"
573 select SERIO
574 help
575 Say Y here if you have a Touchwin serial touchscreen connected to
576 your system.
577
578 If unsure, say N.
579
580 To compile this driver as a module, choose M here: the
581 module will be called touchwin.
582
583 config TOUCHSCREEN_TI_AM335X_TSC
584 tristate "TI Touchscreen Interface"
585 depends on MFD_TI_AM335X_TSCADC
586 help
587 Say Y here if you have 4/5/8 wire touchscreen controller
588 to be connected to the ADC controller on your TI AM335x SoC.
589
590 If unsure, say N.
591
592 To compile this driver as a module, choose M here: the
593 module will be called ti_am335x_tsc.
594
595 config TOUCHSCREEN_UCB1400
596 tristate "Philips UCB1400 touchscreen"
597 depends on AC97_BUS
598 depends on UCB1400_CORE
599 help
600 This enables support for the Philips UCB1400 touchscreen interface.
601 The UCB1400 is an AC97 audio codec. The touchscreen interface
602 will be initialized only after the ALSA subsystem has been
603 brought up and the UCB1400 detected. You therefore have to
604 configure ALSA support as well (either built-in or modular,
605 independently of whether this driver is itself built-in or
606 modular) for this driver to work.
607
608 To compile this driver as a module, choose M here: the
609 module will be called ucb1400_ts.
610
611 config TOUCHSCREEN_PIXCIR
612 tristate "PIXCIR I2C touchscreens"
613 depends on I2C
614 help
615 Say Y here if you have a pixcir i2c touchscreen
616 controller.
617
618 If unsure, say N.
619
620 To compile this driver as a module, choose M here: the
621 module will be called pixcir_i2c_ts.
622
623 config TOUCHSCREEN_WM831X
624 tristate "Support for WM831x touchscreen controllers"
625 depends on MFD_WM831X
626 help
627 This enables support for the touchscreen controller on the WM831x
628 series of PMICs.
629
630 To compile this driver as a module, choose M here: the
631 module will be called wm831x-ts.
632
633 config TOUCHSCREEN_WM97XX
634 tristate "Support for WM97xx AC97 touchscreen controllers"
635 depends on AC97_BUS
636 help
637 Say Y here if you have a Wolfson Microelectronics WM97xx
638 touchscreen connected to your system. Note that this option
639 only enables core driver, you will also need to select
640 support for appropriate chip below.
641
642 If unsure, say N.
643
644 To compile this driver as a module, choose M here: the
645 module will be called wm97xx-ts.
646
647 config TOUCHSCREEN_WM9705
648 bool "WM9705 Touchscreen interface support"
649 depends on TOUCHSCREEN_WM97XX
650 default y
651 help
652 Say Y here to enable support for the Wolfson Microelectronics
653 WM9705 touchscreen controller.
654
655 config TOUCHSCREEN_WM9712
656 bool "WM9712 Touchscreen interface support"
657 depends on TOUCHSCREEN_WM97XX
658 default y
659 help
660 Say Y here to enable support for the Wolfson Microelectronics
661 WM9712 touchscreen controller.
662
663 config TOUCHSCREEN_WM9713
664 bool "WM9713 Touchscreen interface support"
665 depends on TOUCHSCREEN_WM97XX
666 default y
667 help
668 Say Y here to enable support for the Wolfson Microelectronics
669 WM9713 touchscreen controller.
670
671 config TOUCHSCREEN_WM97XX_ATMEL
672 tristate "WM97xx Atmel accelerated touch"
673 depends on TOUCHSCREEN_WM97XX && AVR32
674 help
675 Say Y here for support for streaming mode with WM97xx touchscreens
676 on Atmel AT91 or AVR32 systems with an AC97C module.
677
678 Be aware that this will use channel B in the controller for
679 streaming data, this must not conflict with other AC97C drivers.
680
681 If unsure, say N.
682
683 To compile this driver as a module, choose M here: the module will
684 be called atmel-wm97xx.
685
686 config TOUCHSCREEN_WM97XX_MAINSTONE
687 tristate "WM97xx Mainstone/Palm accelerated touch"
688 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
689 help
690 Say Y here for support for streaming mode with WM97xx touchscreens
691 on Mainstone, Palm Tungsten T5, TX and LifeDrive 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 mainstone-wm97xx.
697
698 config TOUCHSCREEN_WM97XX_ZYLONITE
699 tristate "Zylonite accelerated touch"
700 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
701 select TOUCHSCREEN_WM9713
702 help
703 Say Y here for support for streaming mode with the touchscreen
704 on Zylonite systems.
705
706 If unsure, say N.
707
708 To compile this driver as a module, choose M here: the
709 module will be called zylonite-wm97xx.
710
711 config TOUCHSCREEN_USB_COMPOSITE
712 tristate "USB Touchscreen Driver"
713 depends on USB_ARCH_HAS_HCD
714 select USB
715 help
716 USB Touchscreen driver for:
717 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
718 - PanJit TouchSet USB
719 - 3M MicroTouch USB (EX II series)
720 - ITM
721 - some other eTurboTouch
722 - Gunze AHL61
723 - DMC TSC-10/25
724 - IRTOUCHSYSTEMS/UNITOP
725 - IdealTEK URTC1000
726 - GoTop Super_Q2/GogoPen/PenPower tablets
727 - JASTEC USB Touch Controller/DigiTech DTR-02U
728 - Zytronic controllers
729 - Elo TouchSystems 2700 IntelliTouch
730 - EasyTouch USB Touch Controller from Data Modul
731 - e2i (Mimo monitors)
732
733 Have a look at <http://linux.chapter7.ch/touchkit/> for
734 a usage description and the required user-space stuff.
735
736 To compile this driver as a module, choose M here: the
737 module will be called usbtouchscreen.
738
739 config TOUCHSCREEN_MC13783
740 tristate "Freescale MC13783 touchscreen input driver"
741 depends on MFD_MC13XXX
742 help
743 Say Y here if you have an Freescale MC13783 PMIC on your
744 board and want to use its touchscreen
745
746 If unsure, say N.
747
748 To compile this driver as a module, choose M here: the
749 module will be called mc13783_ts.
750
751 config TOUCHSCREEN_USB_EGALAX
752 default y
753 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
754 depends on TOUCHSCREEN_USB_COMPOSITE
755
756 config TOUCHSCREEN_USB_PANJIT
757 default y
758 bool "PanJit device support" if EXPERT
759 depends on TOUCHSCREEN_USB_COMPOSITE
760
761 config TOUCHSCREEN_USB_3M
762 default y
763 bool "3M/Microtouch EX II series device support" if EXPERT
764 depends on TOUCHSCREEN_USB_COMPOSITE
765
766 config TOUCHSCREEN_USB_ITM
767 default y
768 bool "ITM device support" if EXPERT
769 depends on TOUCHSCREEN_USB_COMPOSITE
770
771 config TOUCHSCREEN_USB_ETURBO
772 default y
773 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
774 depends on TOUCHSCREEN_USB_COMPOSITE
775
776 config TOUCHSCREEN_USB_GUNZE
777 default y
778 bool "Gunze AHL61 device support" if EXPERT
779 depends on TOUCHSCREEN_USB_COMPOSITE
780
781 config TOUCHSCREEN_USB_DMC_TSC10
782 default y
783 bool "DMC TSC-10/25 device support" if EXPERT
784 depends on TOUCHSCREEN_USB_COMPOSITE
785
786 config TOUCHSCREEN_USB_IRTOUCH
787 default y
788 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
789 depends on TOUCHSCREEN_USB_COMPOSITE
790
791 config TOUCHSCREEN_USB_IDEALTEK
792 default y
793 bool "IdealTEK URTC1000 device support" if EXPERT
794 depends on TOUCHSCREEN_USB_COMPOSITE
795
796 config TOUCHSCREEN_USB_GENERAL_TOUCH
797 default y
798 bool "GeneralTouch Touchscreen device support" if EXPERT
799 depends on TOUCHSCREEN_USB_COMPOSITE
800
801 config TOUCHSCREEN_USB_GOTOP
802 default y
803 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
804 depends on TOUCHSCREEN_USB_COMPOSITE
805
806 config TOUCHSCREEN_USB_JASTEC
807 default y
808 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
809 depends on TOUCHSCREEN_USB_COMPOSITE
810
811 config TOUCHSCREEN_USB_ELO
812 default y
813 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
814 depends on TOUCHSCREEN_USB_COMPOSITE
815
816 config TOUCHSCREEN_USB_E2I
817 default y
818 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
819 depends on TOUCHSCREEN_USB_COMPOSITE
820
821 config TOUCHSCREEN_USB_ZYTRONIC
822 default y
823 bool "Zytronic controller" if EXPERT
824 depends on TOUCHSCREEN_USB_COMPOSITE
825
826 config TOUCHSCREEN_USB_ETT_TC45USB
827 default y
828 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
829 depends on TOUCHSCREEN_USB_COMPOSITE
830
831 config TOUCHSCREEN_USB_NEXIO
832 default y
833 bool "NEXIO/iNexio device support" if EXPERT
834 depends on TOUCHSCREEN_USB_COMPOSITE
835
836 config TOUCHSCREEN_USB_EASYTOUCH
837 default y
838 bool "EasyTouch USB Touch controller device support" if EMBEDDED
839 depends on TOUCHSCREEN_USB_COMPOSITE
840 help
841 Say Y here if you have an EasyTouch USB Touch controller.
842 If unsure, say N.
843
844 config TOUCHSCREEN_TOUCHIT213
845 tristate "Sahara TouchIT-213 touchscreen"
846 select SERIO
847 help
848 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
849
850 If unsure, say N.
851
852 To compile this driver as a module, choose M here: the
853 module will be called touchit213.
854
855 config TOUCHSCREEN_TSC_SERIO
856 tristate "TSC-10/25/40 serial touchscreen support"
857 select SERIO
858 help
859 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
860 to your system.
861
862 If unsure, say N.
863
864 To compile this driver as a module, choose M here: the
865 module will be called tsc40.
866
867 config TOUCHSCREEN_TSC2005
868 tristate "TSC2005 based touchscreens"
869 depends on SPI_MASTER
870 help
871 Say Y here if you have a TSC2005 based touchscreen.
872
873 If unsure, say N.
874
875 To compile this driver as a module, choose M here: the
876 module will be called tsc2005.
877
878 config TOUCHSCREEN_TSC2007
879 tristate "TSC2007 based touchscreens"
880 depends on I2C
881 help
882 Say Y here if you have a TSC2007 based touchscreen.
883
884 If unsure, say N.
885
886 To compile this driver as a module, choose M here: the
887 module will be called tsc2007.
888
889 config TOUCHSCREEN_W90X900
890 tristate "W90P910 touchscreen driver"
891 depends on ARCH_W90X900
892 help
893 Say Y here if you have a W90P910 based touchscreen.
894
895 To compile this driver as a module, choose M here: the
896 module will be called w90p910_ts.
897
898 config TOUCHSCREEN_PCAP
899 tristate "Motorola PCAP touchscreen"
900 depends on EZX_PCAP
901 help
902 Say Y here if you have a Motorola EZX telephone and
903 want to enable support for the built-in touchscreen.
904
905 To compile this driver as a module, choose M here: the
906 module will be called pcap_ts.
907
908 config TOUCHSCREEN_ST1232
909 tristate "Sitronix ST1232 touchscreen controllers"
910 depends on I2C
911 help
912 Say Y here if you want to support Sitronix ST1232
913 touchscreen controller.
914
915 If unsure, say N.
916
917 To compile this driver as a module, choose M here: the
918 module will be called st1232_ts.
919
920 config TOUCHSCREEN_STMPE
921 tristate "STMicroelectronics STMPE touchscreens"
922 depends on MFD_STMPE
923 help
924 Say Y here if you want support for STMicroelectronics
925 STMPE touchscreen controllers.
926
927 To compile this driver as a module, choose M here: the
928 module will be called stmpe-ts.
929
930 config TOUCHSCREEN_SUN4I
931 tristate "Allwinner sun4i resistive touchscreen controller support"
932 depends on ARCH_SUNXI || COMPILE_TEST
933 depends on HWMON
934 help
935 This selects support for the resistive touchscreen controller
936 found on Allwinner sunxi SoCs.
937
938 To compile this driver as a module, choose M here: the
939 module will be called sun4i-ts.
940
941 config TOUCHSCREEN_SUR40
942 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
943 depends on USB
944 select INPUT_POLLDEV
945 help
946 Say Y here if you want support for the Samsung SUR40 touchscreen
947 (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
948
949 To compile this driver as a module, choose M here: the
950 module will be called sur40.
951
952 config TOUCHSCREEN_TPS6507X
953 tristate "TPS6507x based touchscreens"
954 depends on I2C
955 select INPUT_POLLDEV
956 help
957 Say Y here if you have a TPS6507x based touchscreen
958 controller.
959
960 If unsure, say N.
961
962 To compile this driver as a module, choose M here: the
963 module will be called tps6507x_ts.
964
965 config TOUCHSCREEN_ZFORCE
966 tristate "Neonode zForce infrared touchscreens"
967 depends on I2C
968 depends on GPIOLIB
969 help
970 Say Y here if you have a touchscreen using the zforce
971 infraread technology from Neonode.
972
973 If unsure, say N.
974
975 To compile this driver as a module, choose M here: the
976 module will be called zforce_ts.
977
978 endif
This page took 0.06102 seconds and 6 git commands to generate.