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