]> git.proxmox.com Git - mirror_ubuntu-artful-kernel.git/blob - drivers/input/touchscreen/Kconfig
Merge tag 'v4.8' into next
[mirror_ubuntu-artful-kernel.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 TOUCHSCREEN_PROPERTIES
15 def_tristate INPUT
16 depends on INPUT
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 || COMPILE_TEST
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_CHIPONE_ICN8318
144 tristate "chipone icn8318 touchscreen controller"
145 depends on GPIOLIB || COMPILE_TEST
146 depends on I2C
147 depends on OF
148 help
149 Say Y here if you have a ChipOne icn8318 based I2C touchscreen.
150
151 If unsure, say N.
152
153 To compile this driver as a module, choose M here: the
154 module will be called chipone_icn8318.
155
156 config TOUCHSCREEN_CY8CTMG110
157 tristate "cy8ctmg110 touchscreen"
158 depends on I2C
159 depends on GPIOLIB || COMPILE_TEST
160 help
161 Say Y here if you have a cy8ctmg110 capacitive touchscreen on
162 an AAVA device.
163
164 If unsure, say N.
165
166 To compile this driver as a module, choose M here: the
167 module will be called cy8ctmg110_ts.
168
169 config TOUCHSCREEN_CYTTSP_CORE
170 tristate "Cypress TTSP touchscreen"
171 help
172 Say Y here if you have a touchscreen using controller from
173 the Cypress TrueTouch(tm) Standard Product family connected
174 to your system. You will also need to select appropriate
175 bus connection below.
176
177 If unsure, say N.
178
179 To compile this driver as a module, choose M here: the
180 module will be called cyttsp_core.
181
182 config TOUCHSCREEN_CYTTSP_I2C
183 tristate "support I2C bus connection"
184 depends on TOUCHSCREEN_CYTTSP_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 cyttsp_i2c.
190
191 config TOUCHSCREEN_CYTTSP_SPI
192 tristate "support SPI bus connection"
193 depends on TOUCHSCREEN_CYTTSP_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 cyttsp_spi.
199
200 config TOUCHSCREEN_CYTTSP4_CORE
201 tristate "Cypress TrueTouch Gen4 Touchscreen Driver"
202 help
203 Core driver for Cypress TrueTouch(tm) Standard Product
204 Generation4 touchscreen controllers.
205
206 Say Y here if you have a Cypress Gen4 touchscreen.
207
208 If unsure, say N.
209
210 To compile this driver as a module, choose M here.
211
212 config TOUCHSCREEN_CYTTSP4_I2C
213 tristate "support I2C bus connection"
214 depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
215 help
216 Say Y here if the touchscreen is connected via I2C bus.
217
218 To compile this driver as a module, choose M here: the
219 module will be called cyttsp4_i2c.
220
221 config TOUCHSCREEN_CYTTSP4_SPI
222 tristate "support SPI bus connection"
223 depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
224 help
225 Say Y here if the touchscreen is connected via SPI bus.
226
227 To compile this driver as a module, choose M here: the
228 module will be called cyttsp4_spi.
229
230 config TOUCHSCREEN_DA9034
231 tristate "Touchscreen support for Dialog Semiconductor DA9034"
232 depends on PMIC_DA903X
233 default y
234 help
235 Say Y here to enable the support for the touchscreen found
236 on Dialog Semiconductor DA9034 PMIC.
237
238 If unsure, say N.
239
240 To compile this driver as a module, choose M here: the
241 module will be called da9034-ts.
242
243 config TOUCHSCREEN_DA9052
244 tristate "Dialog DA9052/DA9053 TSI"
245 depends on PMIC_DA9052
246 help
247 Say Y here to support the touchscreen found on Dialog Semiconductor
248 DA9052-BC and DA9053-AA/Bx PMICs.
249
250 If unsure, say N.
251
252 To compile this driver as a module, choose M here: the
253 module will be called da9052_tsi.
254
255 config TOUCHSCREEN_DYNAPRO
256 tristate "Dynapro serial touchscreen"
257 select SERIO
258 help
259 Say Y here if you have a Dynapro serial touchscreen connected to
260 your system.
261
262 If unsure, say N.
263
264 To compile this driver as a module, choose M here: the
265 module will be called dynapro.
266
267 config TOUCHSCREEN_HAMPSHIRE
268 tristate "Hampshire serial touchscreen"
269 select SERIO
270 help
271 Say Y here if you have a Hampshire serial touchscreen connected to
272 your system.
273
274 If unsure, say N.
275
276 To compile this driver as a module, choose M here: the
277 module will be called hampshire.
278
279 config TOUCHSCREEN_EETI
280 tristate "EETI touchscreen panel support"
281 depends on I2C
282 help
283 Say Y here to enable support for I2C connected EETI touch panels.
284
285 To compile this driver as a module, choose M here: the
286 module will be called eeti_ts.
287
288 config TOUCHSCREEN_EGALAX
289 tristate "EETI eGalax multi-touch panel support"
290 depends on I2C && OF
291 help
292 Say Y here to enable support for I2C connected EETI
293 eGalax multi-touch panels.
294
295 To compile this driver as a module, choose M here: the
296 module will be called egalax_ts.
297
298 config TOUCHSCREEN_EGALAX_SERIAL
299 tristate "EETI eGalax serial touchscreen"
300 select SERIO
301 help
302 Say Y here to enable support for serial connected EETI
303 eGalax touch panels.
304
305 To compile this driver as a module, choose M here: the
306 module will be called egalax_ts_serial.
307
308 config TOUCHSCREEN_FUJITSU
309 tristate "Fujitsu serial touchscreen"
310 select SERIO
311 help
312 Say Y here if you have the Fujitsu touchscreen (such as one
313 installed in Lifebook P series laptop) connected to your
314 system.
315
316 If unsure, say N.
317
318 To compile this driver as a module, choose M here: the
319 module will be called fujitsu-ts.
320
321 config TOUCHSCREEN_GOODIX
322 tristate "Goodix I2C touchscreen"
323 depends on I2C
324 depends on GPIOLIB || COMPILE_TEST
325 help
326 Say Y here if you have the Goodix touchscreen (such as one
327 installed in Onda v975w tablets) connected to your
328 system. It also supports 5-finger chip models, which can be
329 found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
330
331 If unsure, say N.
332
333 To compile this driver as a module, choose M here: the
334 module will be called goodix.
335
336 config TOUCHSCREEN_ILI210X
337 tristate "Ilitek ILI210X based touchscreen"
338 depends on I2C
339 help
340 Say Y here if you have a ILI210X based touchscreen
341 controller. This driver supports models ILI2102,
342 ILI2102s, ILI2103, ILI2103s and ILI2105.
343 Such kind of chipsets can be found in Amazon Kindle Fire
344 touchscreens.
345
346 If unsure, say N.
347
348 To compile this driver as a module, choose M here: the
349 module will be called ili210x.
350
351 config TOUCHSCREEN_IPROC
352 tristate "IPROC touch panel driver support"
353 depends on ARCH_BCM_IPROC || COMPILE_TEST
354 help
355 Say Y here if you want to add support for the IPROC touch
356 controller to your system.
357
358 If unsure, say N.
359
360 To compile this driver as a module, choose M here: the
361 module will be called bcm_iproc_tsc.
362
363 config TOUCHSCREEN_S3C2410
364 tristate "Samsung S3C2410/generic touchscreen input driver"
365 depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
366 depends on S3C_ADC
367 help
368 Say Y here if you have the s3c2410 touchscreen.
369
370 If unsure, say N.
371
372 To compile this driver as a module, choose M here: the
373 module will be called s3c2410_ts.
374
375 config TOUCHSCREEN_GUNZE
376 tristate "Gunze AHL-51S touchscreen"
377 select SERIO
378 help
379 Say Y here if you have the Gunze AHL-51 touchscreen connected to
380 your system.
381
382 If unsure, say N.
383
384 To compile this driver as a module, choose M here: the
385 module will be called gunze.
386
387 config TOUCHSCREEN_EKTF2127
388 tristate "Elan eKTF2127 I2C touchscreen"
389 depends on I2C
390 help
391 Say Y here if you have an Elan eKTF2127 touchscreen
392 connected to your system.
393
394 If unsure, say N.
395
396 To compile this driver as a module, choose M here: the
397 module will be called ektf2127.
398
399 config TOUCHSCREEN_ELAN
400 tristate "Elan eKTH I2C touchscreen"
401 depends on I2C
402 help
403 Say Y here if you have an Elan eKTH I2C touchscreen
404 connected to your system.
405
406 If unsure, say N.
407
408 To compile this driver as a module, choose M here: the
409 module will be called elants_i2c.
410
411 config TOUCHSCREEN_ELO
412 tristate "Elo serial touchscreens"
413 select SERIO
414 help
415 Say Y here if you have an Elo serial touchscreen connected to
416 your system.
417
418 If unsure, say N.
419
420 To compile this driver as a module, choose M here: the
421 module will be called elo.
422
423 config TOUCHSCREEN_WACOM_W8001
424 tristate "Wacom W8001 penabled serial touchscreen"
425 select SERIO
426 help
427 Say Y here if you have an Wacom W8001 penabled serial touchscreen
428 connected to your system.
429
430 If unsure, say N.
431
432 To compile this driver as a module, choose M here: the
433 module will be called wacom_w8001.
434
435 config TOUCHSCREEN_WACOM_I2C
436 tristate "Wacom Tablet support (I2C)"
437 depends on I2C
438 help
439 Say Y here if you want to use the I2C version of the Wacom
440 Pen Tablet.
441
442 If unsure, say N.
443
444 To compile this driver as a module, choose M here: the module
445 will be called wacom_i2c.
446
447 config TOUCHSCREEN_LPC32XX
448 tristate "LPC32XX touchscreen controller"
449 depends on ARCH_LPC32XX
450 help
451 Say Y here if you have a LPC32XX device and want
452 to support the built-in touchscreen.
453
454 To compile this driver as a module, choose M here: the
455 module will be called lpc32xx_ts.
456
457 config TOUCHSCREEN_MAX11801
458 tristate "MAX11801 based touchscreens"
459 depends on I2C
460 help
461 Say Y here if you have a MAX11801 based touchscreen
462 controller.
463
464 If unsure, say N.
465
466 To compile this driver as a module, choose M here: the
467 module will be called max11801_ts.
468
469 config TOUCHSCREEN_MCS5000
470 tristate "MELFAS MCS-5000 touchscreen"
471 depends on I2C
472 help
473 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
474 chip in your system.
475
476 If unsure, say N.
477
478 To compile this driver as a module, choose M here: the
479 module will be called mcs5000_ts.
480
481 config TOUCHSCREEN_MMS114
482 tristate "MELFAS MMS114 touchscreen"
483 depends on I2C
484 help
485 Say Y here if you have the MELFAS MMS114 touchscreen controller
486 chip in 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 mms114.
492
493 config TOUCHSCREEN_MELFAS_MIP4
494 tristate "MELFAS MIP4 Touchscreen"
495 depends on I2C
496 help
497 Say Y here if you have a MELFAS MIP4 Touchscreen device.
498
499 If unsure, say N.
500
501 To compile this driver as a module, choose M here:
502 the module will be called melfas_mip4.
503
504 config TOUCHSCREEN_MTOUCH
505 tristate "MicroTouch serial touchscreens"
506 select SERIO
507 help
508 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
509 your system.
510
511 If unsure, say N.
512
513 To compile this driver as a module, choose M here: the
514 module will be called mtouch.
515
516 config TOUCHSCREEN_IMX6UL_TSC
517 tristate "Freescale i.MX6UL touchscreen controller"
518 depends on (OF && GPIOLIB) || COMPILE_TEST
519 help
520 Say Y here if you have a Freescale i.MX6UL, and want to
521 use the internal touchscreen controller.
522
523 If unsure, say N.
524
525 To compile this driver as a module, choose M here: the
526 module will be called imx6ul_tsc.
527
528 config TOUCHSCREEN_INEXIO
529 tristate "iNexio serial touchscreens"
530 select SERIO
531 help
532 Say Y here if you have an iNexio serial touchscreen connected to
533 your system.
534
535 If unsure, say N.
536
537 To compile this driver as a module, choose M here: the
538 module will be called inexio.
539
540 config TOUCHSCREEN_INTEL_MID
541 tristate "Intel MID platform resistive touchscreen"
542 depends on INTEL_SCU_IPC
543 help
544 Say Y here if you have a Intel MID based touchscreen in
545 your system.
546
547 If unsure, say N.
548
549 To compile this driver as a module, choose M here: the
550 module will be called intel_mid_touch.
551
552 config TOUCHSCREEN_MK712
553 tristate "ICS MicroClock MK712 touchscreen"
554 help
555 Say Y here if you have the ICS MicroClock MK712 touchscreen
556 controller chip in your system.
557
558 If unsure, say N.
559
560 To compile this driver as a module, choose M here: the
561 module will be called mk712.
562
563 config TOUCHSCREEN_HP600
564 tristate "HP Jornada 6xx touchscreen"
565 depends on SH_HP6XX && SH_ADC
566 help
567 Say Y here if you have a HP Jornada 620/660/680/690 and want to
568 support the built-in touchscreen.
569
570 To compile this driver as a module, choose M here: the
571 module will be called hp680_ts_input.
572
573 config TOUCHSCREEN_HP7XX
574 tristate "HP Jornada 7xx touchscreen"
575 depends on SA1100_JORNADA720_SSP
576 help
577 Say Y here if you have a HP Jornada 710/720/728 and want
578 to support the built-in touchscreen.
579
580 To compile this driver as a module, choose M here: the
581 module will be called jornada720_ts.
582
583 config TOUCHSCREEN_IPAQ_MICRO
584 tristate "HP iPAQ Atmel Micro ASIC touchscreen"
585 depends on MFD_IPAQ_MICRO
586 help
587 Say Y here to enable support for the touchscreen attached to
588 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
589
590 If unsure, say N.
591
592 To compile this driver as a module, choose M here: the
593 module will be called ipaq-micro-ts.
594
595 config TOUCHSCREEN_HTCPEN
596 tristate "HTC Shift X9500 touchscreen"
597 depends on ISA
598 help
599 Say Y here if you have an HTC Shift UMPC also known as HTC X9500
600 Clio / Shangrila and want to support the built-in touchscreen.
601
602 If unsure, say N.
603
604 To compile this driver as a module, choose M here: the
605 module will be called htcpen.
606
607 config TOUCHSCREEN_PENMOUNT
608 tristate "Penmount serial touchscreen"
609 select SERIO
610 help
611 Say Y here if you have a Penmount serial touchscreen connected to
612 your system.
613
614 If unsure, say N.
615
616 To compile this driver as a module, choose M here: the
617 module will be called penmount.
618
619 config TOUCHSCREEN_EDT_FT5X06
620 tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
621 depends on I2C
622 help
623 Say Y here if you have an EDT "Polytouch" touchscreen based
624 on the FocalTech FT5x06 family of controllers connected to
625 your system.
626
627 If unsure, say N.
628
629 To compile this driver as a module, choose M here: the
630 module will be called edt-ft5x06.
631
632 config TOUCHSCREEN_MIGOR
633 tristate "Renesas MIGO-R touchscreen"
634 depends on (SH_MIGOR || COMPILE_TEST) && I2C
635 help
636 Say Y here to enable MIGO-R touchscreen support.
637
638 If unsure, say N.
639
640 To compile this driver as a module, choose M here: the
641 module will be called migor_ts.
642
643 config TOUCHSCREEN_TOUCHRIGHT
644 tristate "Touchright serial touchscreen"
645 select SERIO
646 help
647 Say Y here if you have a Touchright serial touchscreen connected to
648 your system.
649
650 If unsure, say N.
651
652 To compile this driver as a module, choose M here: the
653 module will be called touchright.
654
655 config TOUCHSCREEN_TOUCHWIN
656 tristate "Touchwin serial touchscreen"
657 select SERIO
658 help
659 Say Y here if you have a Touchwin serial touchscreen connected to
660 your system.
661
662 If unsure, say N.
663
664 To compile this driver as a module, choose M here: the
665 module will be called touchwin.
666
667 config TOUCHSCREEN_TI_AM335X_TSC
668 tristate "TI Touchscreen Interface"
669 depends on MFD_TI_AM335X_TSCADC
670 help
671 Say Y here if you have 4/5/8 wire touchscreen controller
672 to be connected to the ADC controller on your TI AM335x SoC.
673
674 If unsure, say N.
675
676 To compile this driver as a module, choose M here: the
677 module will be called ti_am335x_tsc.
678
679 config TOUCHSCREEN_UCB1400
680 tristate "Philips UCB1400 touchscreen"
681 depends on AC97_BUS
682 depends on UCB1400_CORE
683 help
684 This enables support for the Philips UCB1400 touchscreen interface.
685 The UCB1400 is an AC97 audio codec. The touchscreen interface
686 will be initialized only after the ALSA subsystem has been
687 brought up and the UCB1400 detected. You therefore have to
688 configure ALSA support as well (either built-in or modular,
689 independently of whether this driver is itself built-in or
690 modular) for this driver to work.
691
692 To compile this driver as a module, choose M here: the
693 module will be called ucb1400_ts.
694
695 config TOUCHSCREEN_PIXCIR
696 tristate "PIXCIR I2C touchscreens"
697 depends on I2C
698 help
699 Say Y here if you have a pixcir i2c touchscreen
700 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 pixcir_i2c_ts.
706
707 config TOUCHSCREEN_WDT87XX_I2C
708 tristate "Weida HiTech I2C touchscreen"
709 depends on I2C
710 help
711 Say Y here if you have a Weida WDT87XX I2C touchscreen
712 connected to your system.
713
714 If unsure, say N.
715
716 To compile this driver as a module, choose M here: the
717 module will be called wdt87xx_i2c.
718
719 config TOUCHSCREEN_WM831X
720 tristate "Support for WM831x touchscreen controllers"
721 depends on MFD_WM831X
722 help
723 This enables support for the touchscreen controller on the WM831x
724 series of PMICs.
725
726 To compile this driver as a module, choose M here: the
727 module will be called wm831x-ts.
728
729 config TOUCHSCREEN_WM97XX
730 tristate "Support for WM97xx AC97 touchscreen controllers"
731 depends on AC97_BUS
732 help
733 Say Y here if you have a Wolfson Microelectronics WM97xx
734 touchscreen connected to your system. Note that this option
735 only enables core driver, you will also need to select
736 support for appropriate chip below.
737
738 If unsure, say N.
739
740 To compile this driver as a module, choose M here: the
741 module will be called wm97xx-ts.
742
743 config TOUCHSCREEN_WM9705
744 bool "WM9705 Touchscreen interface support"
745 depends on TOUCHSCREEN_WM97XX
746 default y
747 help
748 Say Y here to enable support for the Wolfson Microelectronics
749 WM9705 touchscreen controller.
750
751 config TOUCHSCREEN_WM9712
752 bool "WM9712 Touchscreen interface support"
753 depends on TOUCHSCREEN_WM97XX
754 default y
755 help
756 Say Y here to enable support for the Wolfson Microelectronics
757 WM9712 touchscreen controller.
758
759 config TOUCHSCREEN_WM9713
760 bool "WM9713 Touchscreen interface support"
761 depends on TOUCHSCREEN_WM97XX
762 default y
763 help
764 Say Y here to enable support for the Wolfson Microelectronics
765 WM9713 touchscreen controller.
766
767 config TOUCHSCREEN_WM97XX_ATMEL
768 tristate "WM97xx Atmel accelerated touch"
769 depends on TOUCHSCREEN_WM97XX && AVR32
770 help
771 Say Y here for support for streaming mode with WM97xx touchscreens
772 on Atmel AT91 or AVR32 systems with an AC97C module.
773
774 Be aware that this will use channel B in the controller for
775 streaming data, this must not conflict with other AC97C drivers.
776
777 If unsure, say N.
778
779 To compile this driver as a module, choose M here: the module will
780 be called atmel-wm97xx.
781
782 config TOUCHSCREEN_WM97XX_MAINSTONE
783 tristate "WM97xx Mainstone/Palm accelerated touch"
784 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
785 help
786 Say Y here for support for streaming mode with WM97xx touchscreens
787 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
788
789 If unsure, say N.
790
791 To compile this driver as a module, choose M here: the
792 module will be called mainstone-wm97xx.
793
794 config TOUCHSCREEN_WM97XX_ZYLONITE
795 tristate "Zylonite accelerated touch"
796 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
797 select TOUCHSCREEN_WM9713
798 help
799 Say Y here for support for streaming mode with the touchscreen
800 on Zylonite systems.
801
802 If unsure, say N.
803
804 To compile this driver as a module, choose M here: the
805 module will be called zylonite-wm97xx.
806
807 config TOUCHSCREEN_USB_COMPOSITE
808 tristate "USB Touchscreen Driver"
809 depends on USB_ARCH_HAS_HCD
810 select USB
811 help
812 USB Touchscreen driver for:
813 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
814 - PanJit TouchSet USB
815 - 3M MicroTouch USB (EX II series)
816 - ITM
817 - some other eTurboTouch
818 - Gunze AHL61
819 - DMC TSC-10/25
820 - IRTOUCHSYSTEMS/UNITOP
821 - IdealTEK URTC1000
822 - GoTop Super_Q2/GogoPen/PenPower tablets
823 - JASTEC USB Touch Controller/DigiTech DTR-02U
824 - Zytronic controllers
825 - Elo TouchSystems 2700 IntelliTouch
826 - EasyTouch USB Touch Controller from Data Modul
827 - e2i (Mimo monitors)
828
829 Have a look at <http://linux.chapter7.ch/touchkit/> for
830 a usage description and the required user-space stuff.
831
832 To compile this driver as a module, choose M here: the
833 module will be called usbtouchscreen.
834
835 config TOUCHSCREEN_MX25
836 tristate "Freescale i.MX25 touchscreen input driver"
837 depends on MFD_MX25_TSADC
838 help
839 Enable support for touchscreen connected to your i.MX25.
840
841 To compile this driver as a module, choose M here: the
842 module will be called fsl-imx25-tcq.
843
844 config TOUCHSCREEN_MC13783
845 tristate "Freescale MC13783 touchscreen input driver"
846 depends on MFD_MC13XXX
847 help
848 Say Y here if you have an Freescale MC13783 PMIC on your
849 board and want to use its touchscreen
850
851 If unsure, say N.
852
853 To compile this driver as a module, choose M here: the
854 module will be called mc13783_ts.
855
856 config TOUCHSCREEN_USB_EGALAX
857 default y
858 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
859 depends on TOUCHSCREEN_USB_COMPOSITE
860
861 config TOUCHSCREEN_USB_PANJIT
862 default y
863 bool "PanJit device support" if EXPERT
864 depends on TOUCHSCREEN_USB_COMPOSITE
865
866 config TOUCHSCREEN_USB_3M
867 default y
868 bool "3M/Microtouch EX II series device support" if EXPERT
869 depends on TOUCHSCREEN_USB_COMPOSITE
870
871 config TOUCHSCREEN_USB_ITM
872 default y
873 bool "ITM device support" if EXPERT
874 depends on TOUCHSCREEN_USB_COMPOSITE
875
876 config TOUCHSCREEN_USB_ETURBO
877 default y
878 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
879 depends on TOUCHSCREEN_USB_COMPOSITE
880
881 config TOUCHSCREEN_USB_GUNZE
882 default y
883 bool "Gunze AHL61 device support" if EXPERT
884 depends on TOUCHSCREEN_USB_COMPOSITE
885
886 config TOUCHSCREEN_USB_DMC_TSC10
887 default y
888 bool "DMC TSC-10/25 device support" if EXPERT
889 depends on TOUCHSCREEN_USB_COMPOSITE
890
891 config TOUCHSCREEN_USB_IRTOUCH
892 default y
893 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
894 depends on TOUCHSCREEN_USB_COMPOSITE
895
896 config TOUCHSCREEN_USB_IDEALTEK
897 default y
898 bool "IdealTEK URTC1000 device support" if EXPERT
899 depends on TOUCHSCREEN_USB_COMPOSITE
900
901 config TOUCHSCREEN_USB_GENERAL_TOUCH
902 default y
903 bool "GeneralTouch Touchscreen device support" if EXPERT
904 depends on TOUCHSCREEN_USB_COMPOSITE
905
906 config TOUCHSCREEN_USB_GOTOP
907 default y
908 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
909 depends on TOUCHSCREEN_USB_COMPOSITE
910
911 config TOUCHSCREEN_USB_JASTEC
912 default y
913 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
914 depends on TOUCHSCREEN_USB_COMPOSITE
915
916 config TOUCHSCREEN_USB_ELO
917 default y
918 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
919 depends on TOUCHSCREEN_USB_COMPOSITE
920
921 config TOUCHSCREEN_USB_E2I
922 default y
923 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
924 depends on TOUCHSCREEN_USB_COMPOSITE
925
926 config TOUCHSCREEN_USB_ZYTRONIC
927 default y
928 bool "Zytronic controller" if EXPERT
929 depends on TOUCHSCREEN_USB_COMPOSITE
930
931 config TOUCHSCREEN_USB_ETT_TC45USB
932 default y
933 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
934 depends on TOUCHSCREEN_USB_COMPOSITE
935
936 config TOUCHSCREEN_USB_NEXIO
937 default y
938 bool "NEXIO/iNexio device support" if EXPERT
939 depends on TOUCHSCREEN_USB_COMPOSITE
940
941 config TOUCHSCREEN_USB_EASYTOUCH
942 default y
943 bool "EasyTouch USB Touch controller device support" if EMBEDDED
944 depends on TOUCHSCREEN_USB_COMPOSITE
945 help
946 Say Y here if you have an EasyTouch USB Touch controller.
947 If unsure, say N.
948
949 config TOUCHSCREEN_TOUCHIT213
950 tristate "Sahara TouchIT-213 touchscreen"
951 select SERIO
952 help
953 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
954
955 If unsure, say N.
956
957 To compile this driver as a module, choose M here: the
958 module will be called touchit213.
959
960 config TOUCHSCREEN_TS4800
961 tristate "TS-4800 touchscreen"
962 depends on HAS_IOMEM && OF
963 depends on SOC_IMX51 || COMPILE_TEST
964 select MFD_SYSCON
965 select INPUT_POLLDEV
966 help
967 Say Y here if you have a touchscreen on a TS-4800 board.
968
969 On TS-4800, the touchscreen is not handled directly by Linux but by
970 a companion FPGA.
971
972 If unsure, say N.
973
974 To compile this driver as a module, choose M here: the
975 module will be called ts4800_ts.
976
977 config TOUCHSCREEN_TSC_SERIO
978 tristate "TSC-10/25/40 serial touchscreen support"
979 select SERIO
980 help
981 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
982 to your system.
983
984 If unsure, say N.
985
986 To compile this driver as a module, choose M here: the
987 module will be called tsc40.
988
989 config TOUCHSCREEN_TSC200X_CORE
990 tristate
991
992 config TOUCHSCREEN_TSC2004
993 tristate "TSC2004 based touchscreens"
994 depends on I2C
995 select REGMAP_I2C
996 select TOUCHSCREEN_TSC200X_CORE
997 help
998 Say Y here if you have a TSC2004 based touchscreen.
999
1000 If unsure, say N.
1001
1002 To compile this driver as a module, choose M here: the
1003 module will be called tsc2004.
1004
1005 config TOUCHSCREEN_TSC2005
1006 tristate "TSC2005 based touchscreens"
1007 depends on SPI_MASTER
1008 select REGMAP_SPI
1009 select TOUCHSCREEN_TSC200X_CORE
1010 help
1011 Say Y here if you have a TSC2005 based touchscreen.
1012
1013 If unsure, say N.
1014
1015 To compile this driver as a module, choose M here: the
1016 module will be called tsc2005.
1017
1018 config TOUCHSCREEN_TSC2007
1019 tristate "TSC2007 based touchscreens"
1020 depends on I2C
1021 help
1022 Say Y here if you have a TSC2007 based touchscreen.
1023
1024 If unsure, say N.
1025
1026 To compile this driver as a module, choose M here: the
1027 module will be called tsc2007.
1028
1029 config TOUCHSCREEN_W90X900
1030 tristate "W90P910 touchscreen driver"
1031 depends on ARCH_W90X900
1032 help
1033 Say Y here if you have a W90P910 based touchscreen.
1034
1035 To compile this driver as a module, choose M here: the
1036 module will be called w90p910_ts.
1037
1038 config TOUCHSCREEN_PCAP
1039 tristate "Motorola PCAP touchscreen"
1040 depends on EZX_PCAP
1041 help
1042 Say Y here if you have a Motorola EZX telephone and
1043 want to enable support for the built-in touchscreen.
1044
1045 To compile this driver as a module, choose M here: the
1046 module will be called pcap_ts.
1047
1048 config TOUCHSCREEN_RM_TS
1049 tristate "Raydium I2C Touchscreen"
1050 depends on I2C
1051 depends on GPIOLIB || COMPILE_TEST
1052 help
1053 Say Y here if you have Raydium series I2C touchscreen,
1054 such as RM32380, connected to your system.
1055
1056 If unsure, say N.
1057
1058 To compile this driver as a module, choose M here: the
1059 module will be called raydium_i2c_ts.
1060
1061 config TOUCHSCREEN_SILEAD
1062 tristate "Silead I2C touchscreen"
1063 depends on I2C
1064 help
1065 Say Y here if you have the Silead touchscreen connected to
1066 your system.
1067
1068 If unsure, say N.
1069
1070 To compile this driver as a module, choose M here: the
1071 module will be called silead.
1072
1073 config TOUCHSCREEN_SIS_I2C
1074 tristate "SiS 9200 family I2C touchscreen"
1075 depends on I2C
1076 select CRC_ITU_T
1077 depends on GPIOLIB || COMPILE_TEST
1078 help
1079 This enables support for SiS 9200 family over I2C based touchscreens.
1080
1081 If unsure, say N.
1082
1083 To compile this driver as a module, choose M here: the
1084 module will be called sis_i2c.
1085
1086 config TOUCHSCREEN_ST1232
1087 tristate "Sitronix ST1232 touchscreen controllers"
1088 depends on I2C
1089 help
1090 Say Y here if you want to support Sitronix ST1232
1091 touchscreen controller.
1092
1093 If unsure, say N.
1094
1095 To compile this driver as a module, choose M here: the
1096 module will be called st1232_ts.
1097
1098 config TOUCHSCREEN_STMPE
1099 tristate "STMicroelectronics STMPE touchscreens"
1100 depends on MFD_STMPE
1101 depends on (OF || COMPILE_TEST)
1102 help
1103 Say Y here if you want support for STMicroelectronics
1104 STMPE touchscreen controllers.
1105
1106 To compile this driver as a module, choose M here: the
1107 module will be called stmpe-ts.
1108
1109 config TOUCHSCREEN_SUN4I
1110 tristate "Allwinner sun4i resistive touchscreen controller support"
1111 depends on ARCH_SUNXI || COMPILE_TEST
1112 depends on HWMON
1113 depends on THERMAL || !THERMAL_OF
1114 help
1115 This selects support for the resistive touchscreen controller
1116 found on Allwinner sunxi SoCs.
1117
1118 To compile this driver as a module, choose M here: the
1119 module will be called sun4i-ts.
1120
1121 config TOUCHSCREEN_SUR40
1122 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
1123 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1124 depends on VIDEO_V4L2
1125 select INPUT_POLLDEV
1126 select VIDEOBUF2_DMA_SG
1127 help
1128 Say Y here if you want support for the Samsung SUR40 touchscreen
1129 (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
1130
1131 To compile this driver as a module, choose M here: the
1132 module will be called sur40.
1133
1134 config TOUCHSCREEN_SURFACE3_SPI
1135 tristate "Ntrig/Microsoft Surface 3 SPI touchscreen"
1136 depends on SPI
1137 depends on GPIOLIB || COMPILE_TEST
1138 help
1139 Say Y here if you have the Ntrig/Microsoft SPI touchscreen
1140 controller chip as found on the Surface 3 in your system.
1141
1142 If unsure, say N.
1143
1144 To compile this driver as a module, choose M here: the
1145 module will be called surface3_spi.
1146
1147 config TOUCHSCREEN_SX8654
1148 tristate "Semtech SX8654 touchscreen"
1149 depends on I2C
1150 help
1151 Say Y here if you have a Semtech SX8654 touchscreen controller.
1152
1153 If unsure, say N
1154
1155 To compile this driver as a module, choose M here: the
1156 module will be called sx8654.
1157
1158 config TOUCHSCREEN_TPS6507X
1159 tristate "TPS6507x based touchscreens"
1160 depends on I2C
1161 select INPUT_POLLDEV
1162 help
1163 Say Y here if you have a TPS6507x based touchscreen
1164 controller.
1165
1166 If unsure, say N.
1167
1168 To compile this driver as a module, choose M here: the
1169 module will be called tps6507x_ts.
1170
1171 config TOUCHSCREEN_ZFORCE
1172 tristate "Neonode zForce infrared touchscreens"
1173 depends on I2C
1174 depends on GPIOLIB || COMPILE_TEST
1175 help
1176 Say Y here if you have a touchscreen using the zforce
1177 infraread technology from Neonode.
1178
1179 If unsure, say N.
1180
1181 To compile this driver as a module, choose M here: the
1182 module will be called zforce_ts.
1183
1184 config TOUCHSCREEN_COLIBRI_VF50
1185 tristate "Toradex Colibri on board touchscreen driver"
1186 depends on IIO && VF610_ADC
1187 depends on GPIOLIB || COMPILE_TEST
1188 help
1189 Say Y here if you have a Colibri VF50 and plan to use
1190 the on-board provided 4-wire touchscreen driver.
1191
1192 If unsure, say N.
1193
1194 To compile this driver as a module, choose M here: the
1195 module will be called colibri_vf50_ts.
1196
1197 config TOUCHSCREEN_ROHM_BU21023
1198 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
1199 depends on I2C
1200 help
1201 Say Y here if you have a touchscreen using ROHM BU21023/24.
1202
1203 If unsure, say N.
1204
1205 To compile this driver as a module, choose M here: the
1206 module will be called bu21023_ts.
1207
1208 endif