]> git.proxmox.com Git - mirror_ubuntu-zesty-kernel.git/blob - drivers/input/touchscreen/Kconfig
rpi-ft5406: Add touchscreen driver for pi LCD display
[mirror_ubuntu-zesty-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_ATMEL_MXT_T37
119 bool "Support T37 Diagnostic Data"
120 depends on TOUCHSCREEN_ATMEL_MXT
121 depends on VIDEO_V4L2=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_V4L2=m)
122 select VIDEOBUF2_VMALLOC
123 help
124 Say Y here if you want support to output data from the T37
125 Diagnostic Data object using a V4L device.
126
127 config TOUCHSCREEN_AUO_PIXCIR
128 tristate "AUO in-cell touchscreen using Pixcir ICs"
129 depends on I2C
130 depends on GPIOLIB || COMPILE_TEST
131 help
132 Say Y here if you have a AUO display with in-cell touchscreen
133 using Pixcir ICs.
134
135 If unsure, say N.
136
137 To compile this driver as a module, choose M here: the
138 module will be called auo-pixcir-ts.
139
140 config TOUCHSCREEN_BU21013
141 tristate "BU21013 based touch panel controllers"
142 depends on I2C
143 help
144 Say Y here if you have a bu21013 touchscreen connected to
145 your system.
146
147 If unsure, say N.
148
149 To compile this driver as a module, choose M here: the
150 module will be called bu21013_ts.
151
152 config TOUCHSCREEN_CHIPONE_ICN8318
153 tristate "chipone icn8318 touchscreen controller"
154 depends on GPIOLIB || COMPILE_TEST
155 depends on I2C
156 depends on OF
157 help
158 Say Y here if you have a ChipOne icn8318 based I2C touchscreen.
159
160 If unsure, say N.
161
162 To compile this driver as a module, choose M here: the
163 module will be called chipone_icn8318.
164
165 config TOUCHSCREEN_CY8CTMG110
166 tristate "cy8ctmg110 touchscreen"
167 depends on I2C
168 depends on GPIOLIB || COMPILE_TEST
169 help
170 Say Y here if you have a cy8ctmg110 capacitive touchscreen on
171 an AAVA device.
172
173 If unsure, say N.
174
175 To compile this driver as a module, choose M here: the
176 module will be called cy8ctmg110_ts.
177
178 config TOUCHSCREEN_CYTTSP_CORE
179 tristate "Cypress TTSP touchscreen"
180 help
181 Say Y here if you have a touchscreen using controller from
182 the Cypress TrueTouch(tm) Standard Product family connected
183 to your system. You will also need to select appropriate
184 bus connection below.
185
186 If unsure, say N.
187
188 To compile this driver as a module, choose M here: the
189 module will be called cyttsp_core.
190
191 config TOUCHSCREEN_CYTTSP_I2C
192 tristate "support I2C bus connection"
193 depends on TOUCHSCREEN_CYTTSP_CORE && I2C
194 help
195 Say Y here if the touchscreen is connected via I2C bus.
196
197 To compile this driver as a module, choose M here: the
198 module will be called cyttsp_i2c.
199
200 config TOUCHSCREEN_CYTTSP_SPI
201 tristate "support SPI bus connection"
202 depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
203 help
204 Say Y here if the touchscreen is connected via SPI bus.
205
206 To compile this driver as a module, choose M here: the
207 module will be called cyttsp_spi.
208
209 config TOUCHSCREEN_CYTTSP4_CORE
210 tristate "Cypress TrueTouch Gen4 Touchscreen Driver"
211 help
212 Core driver for Cypress TrueTouch(tm) Standard Product
213 Generation4 touchscreen controllers.
214
215 Say Y here if you have a Cypress Gen4 touchscreen.
216
217 If unsure, say N.
218
219 To compile this driver as a module, choose M here.
220
221 config TOUCHSCREEN_CYTTSP4_I2C
222 tristate "support I2C bus connection"
223 depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
224 help
225 Say Y here if the touchscreen is connected via I2C bus.
226
227 To compile this driver as a module, choose M here: the
228 module will be called cyttsp4_i2c.
229
230 config TOUCHSCREEN_CYTTSP4_SPI
231 tristate "support SPI bus connection"
232 depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
233 help
234 Say Y here if the touchscreen is connected via SPI bus.
235
236 To compile this driver as a module, choose M here: the
237 module will be called cyttsp4_spi.
238
239 config TOUCHSCREEN_DA9034
240 tristate "Touchscreen support for Dialog Semiconductor DA9034"
241 depends on PMIC_DA903X
242 default y
243 help
244 Say Y here to enable the support for the touchscreen found
245 on Dialog Semiconductor DA9034 PMIC.
246
247 If unsure, say N.
248
249 To compile this driver as a module, choose M here: the
250 module will be called da9034-ts.
251
252 config TOUCHSCREEN_DA9052
253 tristate "Dialog DA9052/DA9053 TSI"
254 depends on PMIC_DA9052
255 help
256 Say Y here to support the touchscreen found on Dialog Semiconductor
257 DA9052-BC and DA9053-AA/Bx PMICs.
258
259 If unsure, say N.
260
261 To compile this driver as a module, choose M here: the
262 module will be called da9052_tsi.
263
264 config TOUCHSCREEN_DYNAPRO
265 tristate "Dynapro serial touchscreen"
266 select SERIO
267 help
268 Say Y here if you have a Dynapro serial touchscreen connected to
269 your system.
270
271 If unsure, say N.
272
273 To compile this driver as a module, choose M here: the
274 module will be called dynapro.
275
276 config TOUCHSCREEN_HAMPSHIRE
277 tristate "Hampshire serial touchscreen"
278 select SERIO
279 help
280 Say Y here if you have a Hampshire serial touchscreen connected to
281 your system.
282
283 If unsure, say N.
284
285 To compile this driver as a module, choose M here: the
286 module will be called hampshire.
287
288 config TOUCHSCREEN_EETI
289 tristate "EETI touchscreen panel support"
290 depends on I2C
291 help
292 Say Y here to enable support for I2C connected EETI touch panels.
293
294 To compile this driver as a module, choose M here: the
295 module will be called eeti_ts.
296
297 config TOUCHSCREEN_EGALAX
298 tristate "EETI eGalax multi-touch panel support"
299 depends on I2C && OF
300 help
301 Say Y here to enable support for I2C connected EETI
302 eGalax multi-touch panels.
303
304 To compile this driver as a module, choose M here: the
305 module will be called egalax_ts.
306
307 config TOUCHSCREEN_EGALAX_SERIAL
308 tristate "EETI eGalax serial touchscreen"
309 select SERIO
310 help
311 Say Y here to enable support for serial connected EETI
312 eGalax touch panels.
313
314 To compile this driver as a module, choose M here: the
315 module will be called egalax_ts_serial.
316
317 config TOUCHSCREEN_FUJITSU
318 tristate "Fujitsu serial touchscreen"
319 select SERIO
320 help
321 Say Y here if you have the Fujitsu touchscreen (such as one
322 installed in Lifebook P series laptop) connected to your
323 system.
324
325 If unsure, say N.
326
327 To compile this driver as a module, choose M here: the
328 module will be called fujitsu-ts.
329
330 config TOUCHSCREEN_GOODIX
331 tristate "Goodix I2C touchscreen"
332 depends on I2C
333 depends on GPIOLIB || COMPILE_TEST
334 help
335 Say Y here if you have the Goodix touchscreen (such as one
336 installed in Onda v975w tablets) connected to your
337 system. It also supports 5-finger chip models, which can be
338 found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
339
340 If unsure, say N.
341
342 To compile this driver as a module, choose M here: the
343 module will be called goodix.
344
345 config TOUCHSCREEN_ILI210X
346 tristate "Ilitek ILI210X based touchscreen"
347 depends on I2C
348 help
349 Say Y here if you have a ILI210X based touchscreen
350 controller. This driver supports models ILI2102,
351 ILI2102s, ILI2103, ILI2103s and ILI2105.
352 Such kind of chipsets can be found in Amazon Kindle Fire
353 touchscreens.
354
355 If unsure, say N.
356
357 To compile this driver as a module, choose M here: the
358 module will be called ili210x.
359
360 config TOUCHSCREEN_IPROC
361 tristate "IPROC touch panel driver support"
362 depends on ARCH_BCM_IPROC || COMPILE_TEST
363 help
364 Say Y here if you want to add support for the IPROC touch
365 controller to your system.
366
367 If unsure, say N.
368
369 To compile this driver as a module, choose M here: the
370 module will be called bcm_iproc_tsc.
371
372 config TOUCHSCREEN_S3C2410
373 tristate "Samsung S3C2410/generic touchscreen input driver"
374 depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
375 depends on S3C_ADC
376 help
377 Say Y here if you have the s3c2410 touchscreen.
378
379 If unsure, say N.
380
381 To compile this driver as a module, choose M here: the
382 module will be called s3c2410_ts.
383
384 config TOUCHSCREEN_GUNZE
385 tristate "Gunze AHL-51S touchscreen"
386 select SERIO
387 help
388 Say Y here if you have the Gunze AHL-51 touchscreen connected to
389 your system.
390
391 If unsure, say N.
392
393 To compile this driver as a module, choose M here: the
394 module will be called gunze.
395
396 config TOUCHSCREEN_EKTF2127
397 tristate "Elan eKTF2127 I2C touchscreen"
398 depends on I2C
399 help
400 Say Y here if you have an Elan eKTF2127 touchscreen
401 connected to your system.
402
403 If unsure, say N.
404
405 To compile this driver as a module, choose M here: the
406 module will be called ektf2127.
407
408 config TOUCHSCREEN_ELAN
409 tristate "Elan eKTH I2C touchscreen"
410 depends on I2C
411 help
412 Say Y here if you have an Elan eKTH I2C touchscreen
413 connected to 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 elants_i2c.
419
420 config TOUCHSCREEN_ELO
421 tristate "Elo serial touchscreens"
422 select SERIO
423 help
424 Say Y here if you have an Elo serial touchscreen connected to
425 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 elo.
431
432 config TOUCHSCREEN_WACOM_W8001
433 tristate "Wacom W8001 penabled serial touchscreen"
434 select SERIO
435 help
436 Say Y here if you have an Wacom W8001 penabled serial touchscreen
437 connected to 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 wacom_w8001.
443
444 config TOUCHSCREEN_WACOM_I2C
445 tristate "Wacom Tablet support (I2C)"
446 depends on I2C
447 help
448 Say Y here if you want to use the I2C version of the Wacom
449 Pen Tablet.
450
451 If unsure, say N.
452
453 To compile this driver as a module, choose M here: the module
454 will be called wacom_i2c.
455
456 config TOUCHSCREEN_LPC32XX
457 tristate "LPC32XX touchscreen controller"
458 depends on ARCH_LPC32XX
459 help
460 Say Y here if you have a LPC32XX device and want
461 to support the built-in touchscreen.
462
463 To compile this driver as a module, choose M here: the
464 module will be called lpc32xx_ts.
465
466 config TOUCHSCREEN_MAX11801
467 tristate "MAX11801 based touchscreens"
468 depends on I2C
469 help
470 Say Y here if you have a MAX11801 based touchscreen
471 controller.
472
473 If unsure, say N.
474
475 To compile this driver as a module, choose M here: the
476 module will be called max11801_ts.
477
478 config TOUCHSCREEN_MCS5000
479 tristate "MELFAS MCS-5000 touchscreen"
480 depends on I2C
481 help
482 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
483 chip in your system.
484
485 If unsure, say N.
486
487 To compile this driver as a module, choose M here: the
488 module will be called mcs5000_ts.
489
490 config TOUCHSCREEN_MMS114
491 tristate "MELFAS MMS114 touchscreen"
492 depends on I2C
493 help
494 Say Y here if you have the MELFAS MMS114 touchscreen controller
495 chip in your system.
496
497 If unsure, say N.
498
499 To compile this driver as a module, choose M here: the
500 module will be called mms114.
501
502 config TOUCHSCREEN_MELFAS_MIP4
503 tristate "MELFAS MIP4 Touchscreen"
504 depends on I2C
505 help
506 Say Y here if you have a MELFAS MIP4 Touchscreen device.
507
508 If unsure, say N.
509
510 To compile this driver as a module, choose M here:
511 the module will be called melfas_mip4.
512
513 config TOUCHSCREEN_MTOUCH
514 tristate "MicroTouch serial touchscreens"
515 select SERIO
516 help
517 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
518 your system.
519
520 If unsure, say N.
521
522 To compile this driver as a module, choose M here: the
523 module will be called mtouch.
524
525 config TOUCHSCREEN_IMX6UL_TSC
526 tristate "Freescale i.MX6UL touchscreen controller"
527 depends on (OF && GPIOLIB) || COMPILE_TEST
528 help
529 Say Y here if you have a Freescale i.MX6UL, and want to
530 use the internal touchscreen controller.
531
532 If unsure, say N.
533
534 To compile this driver as a module, choose M here: the
535 module will be called imx6ul_tsc.
536
537 config TOUCHSCREEN_INEXIO
538 tristate "iNexio serial touchscreens"
539 select SERIO
540 help
541 Say Y here if you have an iNexio serial touchscreen connected to
542 your system.
543
544 If unsure, say N.
545
546 To compile this driver as a module, choose M here: the
547 module will be called inexio.
548
549 config TOUCHSCREEN_INTEL_MID
550 tristate "Intel MID platform resistive touchscreen"
551 depends on INTEL_SCU_IPC
552 help
553 Say Y here if you have a Intel MID based touchscreen in
554 your system.
555
556 If unsure, say N.
557
558 To compile this driver as a module, choose M here: the
559 module will be called intel_mid_touch.
560
561 config TOUCHSCREEN_MK712
562 tristate "ICS MicroClock MK712 touchscreen"
563 help
564 Say Y here if you have the ICS MicroClock MK712 touchscreen
565 controller chip in your system.
566
567 If unsure, say N.
568
569 To compile this driver as a module, choose M here: the
570 module will be called mk712.
571
572 config TOUCHSCREEN_HP600
573 tristate "HP Jornada 6xx touchscreen"
574 depends on SH_HP6XX && SH_ADC
575 help
576 Say Y here if you have a HP Jornada 620/660/680/690 and want to
577 support the built-in touchscreen.
578
579 To compile this driver as a module, choose M here: the
580 module will be called hp680_ts_input.
581
582 config TOUCHSCREEN_HP7XX
583 tristate "HP Jornada 7xx touchscreen"
584 depends on SA1100_JORNADA720_SSP
585 help
586 Say Y here if you have a HP Jornada 710/720/728 and want
587 to support the built-in touchscreen.
588
589 To compile this driver as a module, choose M here: the
590 module will be called jornada720_ts.
591
592 config TOUCHSCREEN_IPAQ_MICRO
593 tristate "HP iPAQ Atmel Micro ASIC touchscreen"
594 depends on MFD_IPAQ_MICRO
595 help
596 Say Y here to enable support for the touchscreen attached to
597 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
598
599 If unsure, say N.
600
601 To compile this driver as a module, choose M here: the
602 module will be called ipaq-micro-ts.
603
604 config TOUCHSCREEN_HTCPEN
605 tristate "HTC Shift X9500 touchscreen"
606 depends on ISA
607 help
608 Say Y here if you have an HTC Shift UMPC also known as HTC X9500
609 Clio / Shangrila and want to support the built-in touchscreen.
610
611 If unsure, say N.
612
613 To compile this driver as a module, choose M here: the
614 module will be called htcpen.
615
616 config TOUCHSCREEN_PENMOUNT
617 tristate "Penmount serial touchscreen"
618 select SERIO
619 help
620 Say Y here if you have a Penmount serial touchscreen connected to
621 your system.
622
623 If unsure, say N.
624
625 To compile this driver as a module, choose M here: the
626 module will be called penmount.
627
628 config TOUCHSCREEN_EDT_FT5X06
629 tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
630 depends on I2C
631 help
632 Say Y here if you have an EDT "Polytouch" touchscreen based
633 on the FocalTech FT5x06 family of controllers connected to
634 your system.
635
636 If unsure, say N.
637
638 To compile this driver as a module, choose M here: the
639 module will be called edt-ft5x06.
640
641 config TOUCHSCREEN_RPI_FT5406
642 tristate "Raspberry Pi FT5406 driver"
643 depends on RASPBERRYPI_FIRMWARE
644 help
645 Say Y here to enable the Raspberry Pi memory based FT5406 device
646
647
648 config TOUCHSCREEN_MIGOR
649 tristate "Renesas MIGO-R touchscreen"
650 depends on (SH_MIGOR || COMPILE_TEST) && I2C
651 help
652 Say Y here to enable MIGO-R touchscreen support.
653
654 If unsure, say N.
655
656 To compile this driver as a module, choose M here: the
657 module will be called migor_ts.
658
659 config TOUCHSCREEN_TOUCHRIGHT
660 tristate "Touchright serial touchscreen"
661 select SERIO
662 help
663 Say Y here if you have a Touchright serial touchscreen connected to
664 your system.
665
666 If unsure, say N.
667
668 To compile this driver as a module, choose M here: the
669 module will be called touchright.
670
671 config TOUCHSCREEN_TOUCHWIN
672 tristate "Touchwin serial touchscreen"
673 select SERIO
674 help
675 Say Y here if you have a Touchwin serial touchscreen connected to
676 your system.
677
678 If unsure, say N.
679
680 To compile this driver as a module, choose M here: the
681 module will be called touchwin.
682
683 config TOUCHSCREEN_TI_AM335X_TSC
684 tristate "TI Touchscreen Interface"
685 depends on MFD_TI_AM335X_TSCADC
686 help
687 Say Y here if you have 4/5/8 wire touchscreen controller
688 to be connected to the ADC controller on your TI AM335x SoC.
689
690 If unsure, say N.
691
692 To compile this driver as a module, choose M here: the
693 module will be called ti_am335x_tsc.
694
695 config TOUCHSCREEN_UCB1400
696 tristate "Philips UCB1400 touchscreen"
697 depends on AC97_BUS
698 depends on UCB1400_CORE
699 help
700 This enables support for the Philips UCB1400 touchscreen interface.
701 The UCB1400 is an AC97 audio codec. The touchscreen interface
702 will be initialized only after the ALSA subsystem has been
703 brought up and the UCB1400 detected. You therefore have to
704 configure ALSA support as well (either built-in or modular,
705 independently of whether this driver is itself built-in or
706 modular) for this driver to work.
707
708 To compile this driver as a module, choose M here: the
709 module will be called ucb1400_ts.
710
711 config TOUCHSCREEN_PIXCIR
712 tristate "PIXCIR I2C touchscreens"
713 depends on I2C
714 help
715 Say Y here if you have a pixcir i2c touchscreen
716 controller.
717
718 If unsure, say N.
719
720 To compile this driver as a module, choose M here: the
721 module will be called pixcir_i2c_ts.
722
723 config TOUCHSCREEN_WDT87XX_I2C
724 tristate "Weida HiTech I2C touchscreen"
725 depends on I2C
726 help
727 Say Y here if you have a Weida WDT87XX I2C touchscreen
728 connected to your system.
729
730 If unsure, say N.
731
732 To compile this driver as a module, choose M here: the
733 module will be called wdt87xx_i2c.
734
735 config TOUCHSCREEN_WM831X
736 tristate "Support for WM831x touchscreen controllers"
737 depends on MFD_WM831X
738 help
739 This enables support for the touchscreen controller on the WM831x
740 series of PMICs.
741
742 To compile this driver as a module, choose M here: the
743 module will be called wm831x-ts.
744
745 config TOUCHSCREEN_WM97XX
746 tristate "Support for WM97xx AC97 touchscreen controllers"
747 depends on AC97_BUS
748 help
749 Say Y here if you have a Wolfson Microelectronics WM97xx
750 touchscreen connected to your system. Note that this option
751 only enables core driver, you will also need to select
752 support for appropriate chip below.
753
754 If unsure, say N.
755
756 To compile this driver as a module, choose M here: the
757 module will be called wm97xx-ts.
758
759 config TOUCHSCREEN_WM9705
760 bool "WM9705 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 WM9705 touchscreen controller.
766
767 config TOUCHSCREEN_WM9712
768 bool "WM9712 Touchscreen interface support"
769 depends on TOUCHSCREEN_WM97XX
770 default y
771 help
772 Say Y here to enable support for the Wolfson Microelectronics
773 WM9712 touchscreen controller.
774
775 config TOUCHSCREEN_WM9713
776 bool "WM9713 Touchscreen interface support"
777 depends on TOUCHSCREEN_WM97XX
778 default y
779 help
780 Say Y here to enable support for the Wolfson Microelectronics
781 WM9713 touchscreen controller.
782
783 config TOUCHSCREEN_WM97XX_ATMEL
784 tristate "WM97xx Atmel accelerated touch"
785 depends on TOUCHSCREEN_WM97XX && AVR32
786 help
787 Say Y here for support for streaming mode with WM97xx touchscreens
788 on Atmel AT91 or AVR32 systems with an AC97C module.
789
790 Be aware that this will use channel B in the controller for
791 streaming data, this must not conflict with other AC97C drivers.
792
793 If unsure, say N.
794
795 To compile this driver as a module, choose M here: the module will
796 be called atmel-wm97xx.
797
798 config TOUCHSCREEN_WM97XX_MAINSTONE
799 tristate "WM97xx Mainstone/Palm accelerated touch"
800 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
801 help
802 Say Y here for support for streaming mode with WM97xx touchscreens
803 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
804
805 If unsure, say N.
806
807 To compile this driver as a module, choose M here: the
808 module will be called mainstone-wm97xx.
809
810 config TOUCHSCREEN_WM97XX_ZYLONITE
811 tristate "Zylonite accelerated touch"
812 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
813 select TOUCHSCREEN_WM9713
814 help
815 Say Y here for support for streaming mode with the touchscreen
816 on Zylonite systems.
817
818 If unsure, say N.
819
820 To compile this driver as a module, choose M here: the
821 module will be called zylonite-wm97xx.
822
823 config TOUCHSCREEN_USB_COMPOSITE
824 tristate "USB Touchscreen Driver"
825 depends on USB_ARCH_HAS_HCD
826 select USB
827 help
828 USB Touchscreen driver for:
829 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
830 - PanJit TouchSet USB
831 - 3M MicroTouch USB (EX II series)
832 - ITM
833 - some other eTurboTouch
834 - Gunze AHL61
835 - DMC TSC-10/25
836 - IRTOUCHSYSTEMS/UNITOP
837 - IdealTEK URTC1000
838 - GoTop Super_Q2/GogoPen/PenPower tablets
839 - JASTEC USB Touch Controller/DigiTech DTR-02U
840 - Zytronic controllers
841 - Elo TouchSystems 2700 IntelliTouch
842 - EasyTouch USB Touch Controller from Data Modul
843 - e2i (Mimo monitors)
844
845 Have a look at <http://linux.chapter7.ch/touchkit/> for
846 a usage description and the required user-space stuff.
847
848 To compile this driver as a module, choose M here: the
849 module will be called usbtouchscreen.
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_W90X900
1046 tristate "W90P910 touchscreen driver"
1047 depends on ARCH_W90X900
1048 help
1049 Say Y here if you have a W90P910 based touchscreen.
1050
1051 To compile this driver as a module, choose M here: the
1052 module will be called w90p910_ts.
1053
1054 config TOUCHSCREEN_PCAP
1055 tristate "Motorola PCAP touchscreen"
1056 depends on EZX_PCAP
1057 help
1058 Say Y here if you have a Motorola EZX telephone and
1059 want to enable support for the built-in touchscreen.
1060
1061 To compile this driver as a module, choose M here: the
1062 module will be called pcap_ts.
1063
1064 config TOUCHSCREEN_RM_TS
1065 tristate "Raydium I2C Touchscreen"
1066 depends on I2C
1067 depends on GPIOLIB || COMPILE_TEST
1068 help
1069 Say Y here if you have Raydium series I2C touchscreen,
1070 such as RM32380, connected to your system.
1071
1072 If unsure, say N.
1073
1074 To compile this driver as a module, choose M here: the
1075 module will be called raydium_i2c_ts.
1076
1077 config TOUCHSCREEN_SILEAD
1078 tristate "Silead I2C touchscreen"
1079 depends on I2C
1080 help
1081 Say Y here if you have the Silead touchscreen connected to
1082 your system.
1083
1084 If unsure, say N.
1085
1086 To compile this driver as a module, choose M here: the
1087 module will be called silead.
1088
1089 config TOUCHSCREEN_SIS_I2C
1090 tristate "SiS 9200 family I2C touchscreen"
1091 depends on I2C
1092 select CRC_ITU_T
1093 depends on GPIOLIB || COMPILE_TEST
1094 help
1095 This enables support for SiS 9200 family over I2C based touchscreens.
1096
1097 If unsure, say N.
1098
1099 To compile this driver as a module, choose M here: the
1100 module will be called sis_i2c.
1101
1102 config TOUCHSCREEN_ST1232
1103 tristate "Sitronix ST1232 touchscreen controllers"
1104 depends on I2C
1105 help
1106 Say Y here if you want to support Sitronix ST1232
1107 touchscreen controller.
1108
1109 If unsure, say N.
1110
1111 To compile this driver as a module, choose M here: the
1112 module will be called st1232_ts.
1113
1114 config TOUCHSCREEN_STMPE
1115 tristate "STMicroelectronics STMPE touchscreens"
1116 depends on MFD_STMPE
1117 depends on (OF || COMPILE_TEST)
1118 help
1119 Say Y here if you want support for STMicroelectronics
1120 STMPE touchscreen controllers.
1121
1122 To compile this driver as a module, choose M here: the
1123 module will be called stmpe-ts.
1124
1125 config TOUCHSCREEN_SUN4I
1126 tristate "Allwinner sun4i resistive touchscreen controller support"
1127 depends on ARCH_SUNXI || COMPILE_TEST
1128 depends on HWMON
1129 depends on THERMAL || !THERMAL_OF
1130 help
1131 This selects support for the resistive touchscreen controller
1132 found on Allwinner sunxi SoCs.
1133
1134 To compile this driver as a module, choose M here: the
1135 module will be called sun4i-ts.
1136
1137 config TOUCHSCREEN_SUR40
1138 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
1139 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1140 depends on VIDEO_V4L2
1141 select INPUT_POLLDEV
1142 select VIDEOBUF2_DMA_SG
1143 help
1144 Say Y here if you want support for the Samsung SUR40 touchscreen
1145 (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
1146
1147 To compile this driver as a module, choose M here: the
1148 module will be called sur40.
1149
1150 config TOUCHSCREEN_SURFACE3_SPI
1151 tristate "Ntrig/Microsoft Surface 3 SPI touchscreen"
1152 depends on SPI
1153 depends on GPIOLIB || COMPILE_TEST
1154 help
1155 Say Y here if you have the Ntrig/Microsoft SPI touchscreen
1156 controller chip as found on the Surface 3 in your system.
1157
1158 If unsure, say N.
1159
1160 To compile this driver as a module, choose M here: the
1161 module will be called surface3_spi.
1162
1163 config TOUCHSCREEN_SX8654
1164 tristate "Semtech SX8654 touchscreen"
1165 depends on I2C
1166 help
1167 Say Y here if you have a Semtech SX8654 touchscreen controller.
1168
1169 If unsure, say N
1170
1171 To compile this driver as a module, choose M here: the
1172 module will be called sx8654.
1173
1174 config TOUCHSCREEN_TPS6507X
1175 tristate "TPS6507x based touchscreens"
1176 depends on I2C
1177 select INPUT_POLLDEV
1178 help
1179 Say Y here if you have a TPS6507x based touchscreen
1180 controller.
1181
1182 If unsure, say N.
1183
1184 To compile this driver as a module, choose M here: the
1185 module will be called tps6507x_ts.
1186
1187 config TOUCHSCREEN_ZFORCE
1188 tristate "Neonode zForce infrared touchscreens"
1189 depends on I2C
1190 depends on GPIOLIB || COMPILE_TEST
1191 help
1192 Say Y here if you have a touchscreen using the zforce
1193 infraread technology from Neonode.
1194
1195 If unsure, say N.
1196
1197 To compile this driver as a module, choose M here: the
1198 module will be called zforce_ts.
1199
1200 config TOUCHSCREEN_COLIBRI_VF50
1201 tristate "Toradex Colibri on board touchscreen driver"
1202 depends on IIO && VF610_ADC
1203 depends on GPIOLIB || COMPILE_TEST
1204 help
1205 Say Y here if you have a Colibri VF50 and plan to use
1206 the on-board provided 4-wire touchscreen driver.
1207
1208 If unsure, say N.
1209
1210 To compile this driver as a module, choose M here: the
1211 module will be called colibri_vf50_ts.
1212
1213 config TOUCHSCREEN_ROHM_BU21023
1214 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
1215 depends on I2C
1216 help
1217 Say Y here if you have a touchscreen using ROHM BU21023/24.
1218
1219 If unsure, say N.
1220
1221 To compile this driver as a module, choose M here: the
1222 module will be called bu21023_ts.
1223
1224 endif