]> git.proxmox.com Git - mirror_ubuntu-artful-kernel.git/blob - drivers/input/touchscreen/Kconfig
Merge tag 'metag-for-v4.12' of git://git.kernel.org/pub/scm/linux/kernel/git/jhogan...
[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_MIGOR
632 tristate "Renesas MIGO-R touchscreen"
633 depends on (SH_MIGOR || COMPILE_TEST) && I2C
634 help
635 Say Y here to enable MIGO-R touchscreen support.
636
637 If unsure, say N.
638
639 To compile this driver as a module, choose M here: the
640 module will be called migor_ts.
641
642 config TOUCHSCREEN_TOUCHRIGHT
643 tristate "Touchright serial touchscreen"
644 select SERIO
645 help
646 Say Y here if you have a Touchright serial touchscreen connected to
647 your system.
648
649 If unsure, say N.
650
651 To compile this driver as a module, choose M here: the
652 module will be called touchright.
653
654 config TOUCHSCREEN_TOUCHWIN
655 tristate "Touchwin serial touchscreen"
656 select SERIO
657 help
658 Say Y here if you have a Touchwin serial touchscreen connected to
659 your system.
660
661 If unsure, say N.
662
663 To compile this driver as a module, choose M here: the
664 module will be called touchwin.
665
666 config TOUCHSCREEN_TI_AM335X_TSC
667 tristate "TI Touchscreen Interface"
668 depends on MFD_TI_AM335X_TSCADC
669 help
670 Say Y here if you have 4/5/8 wire touchscreen controller
671 to be connected to the ADC controller on your TI AM335x SoC.
672
673 If unsure, say N.
674
675 To compile this driver as a module, choose M here: the
676 module will be called ti_am335x_tsc.
677
678 config TOUCHSCREEN_UCB1400
679 tristate "Philips UCB1400 touchscreen"
680 depends on AC97_BUS
681 depends on UCB1400_CORE
682 help
683 This enables support for the Philips UCB1400 touchscreen interface.
684 The UCB1400 is an AC97 audio codec. The touchscreen interface
685 will be initialized only after the ALSA subsystem has been
686 brought up and the UCB1400 detected. You therefore have to
687 configure ALSA support as well (either built-in or modular,
688 independently of whether this driver is itself built-in or
689 modular) for this driver to work.
690
691 To compile this driver as a module, choose M here: the
692 module will be called ucb1400_ts.
693
694 config TOUCHSCREEN_PIXCIR
695 tristate "PIXCIR I2C touchscreens"
696 depends on I2C
697 help
698 Say Y here if you have a pixcir i2c touchscreen
699 controller.
700
701 If unsure, say N.
702
703 To compile this driver as a module, choose M here: the
704 module will be called pixcir_i2c_ts.
705
706 config TOUCHSCREEN_WDT87XX_I2C
707 tristate "Weida HiTech I2C touchscreen"
708 depends on I2C
709 help
710 Say Y here if you have a Weida WDT87XX I2C touchscreen
711 connected to your system.
712
713 If unsure, say N.
714
715 To compile this driver as a module, choose M here: the
716 module will be called wdt87xx_i2c.
717
718 config TOUCHSCREEN_WM831X
719 tristate "Support for WM831x touchscreen controllers"
720 depends on MFD_WM831X
721 help
722 This enables support for the touchscreen controller on the WM831x
723 series of PMICs.
724
725 To compile this driver as a module, choose M here: the
726 module will be called wm831x-ts.
727
728 config TOUCHSCREEN_WM97XX
729 tristate "Support for WM97xx AC97 touchscreen controllers"
730 depends on AC97_BUS
731 help
732 Say Y here if you have a Wolfson Microelectronics WM97xx
733 touchscreen connected to your system. Note that this option
734 only enables core driver, you will also need to select
735 support for appropriate chip below.
736
737 If unsure, say N.
738
739 To compile this driver as a module, choose M here: the
740 module will be called wm97xx-ts.
741
742 config TOUCHSCREEN_WM9705
743 bool "WM9705 Touchscreen interface support"
744 depends on TOUCHSCREEN_WM97XX
745 default y
746 help
747 Say Y here to enable support for the Wolfson Microelectronics
748 WM9705 touchscreen controller.
749
750 config TOUCHSCREEN_WM9712
751 bool "WM9712 Touchscreen interface support"
752 depends on TOUCHSCREEN_WM97XX
753 default y
754 help
755 Say Y here to enable support for the Wolfson Microelectronics
756 WM9712 touchscreen controller.
757
758 config TOUCHSCREEN_WM9713
759 bool "WM9713 Touchscreen interface support"
760 depends on TOUCHSCREEN_WM97XX
761 default y
762 help
763 Say Y here to enable support for the Wolfson Microelectronics
764 WM9713 touchscreen controller.
765
766 config TOUCHSCREEN_WM97XX_ATMEL
767 tristate "WM97xx Atmel accelerated touch"
768 depends on TOUCHSCREEN_WM97XX && AVR32
769 help
770 Say Y here for support for streaming mode with WM97xx touchscreens
771 on Atmel AT91 or AVR32 systems with an AC97C module.
772
773 Be aware that this will use channel B in the controller for
774 streaming data, this must not conflict with other AC97C drivers.
775
776 If unsure, say N.
777
778 To compile this driver as a module, choose M here: the module will
779 be called atmel-wm97xx.
780
781 config TOUCHSCREEN_WM97XX_MAINSTONE
782 tristate "WM97xx Mainstone/Palm accelerated touch"
783 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
784 help
785 Say Y here for support for streaming mode with WM97xx touchscreens
786 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
787
788 If unsure, say N.
789
790 To compile this driver as a module, choose M here: the
791 module will be called mainstone-wm97xx.
792
793 config TOUCHSCREEN_WM97XX_ZYLONITE
794 tristate "Zylonite accelerated touch"
795 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
796 select TOUCHSCREEN_WM9713
797 help
798 Say Y here for support for streaming mode with the touchscreen
799 on Zylonite systems.
800
801 If unsure, say N.
802
803 To compile this driver as a module, choose M here: the
804 module will be called zylonite-wm97xx.
805
806 config TOUCHSCREEN_USB_COMPOSITE
807 tristate "USB Touchscreen Driver"
808 depends on USB_ARCH_HAS_HCD
809 select USB
810 help
811 USB Touchscreen driver for:
812 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
813 - PanJit TouchSet USB
814 - 3M MicroTouch USB (EX II series)
815 - ITM
816 - some other eTurboTouch
817 - Gunze AHL61
818 - DMC TSC-10/25
819 - IRTOUCHSYSTEMS/UNITOP
820 - IdealTEK URTC1000
821 - GoTop Super_Q2/GogoPen/PenPower tablets
822 - JASTEC USB Touch Controller/DigiTech DTR-02U
823 - Zytronic controllers
824 - Elo TouchSystems 2700 IntelliTouch
825 - EasyTouch USB Touch Controller from Data Modul
826 - e2i (Mimo monitors)
827
828 Have a look at <http://linux.chapter7.ch/touchkit/> for
829 a usage description and the required user-space stuff.
830
831 To compile this driver as a module, choose M here: the
832 module will be called usbtouchscreen.
833
834 config TOUCHSCREEN_MXS_LRADC
835 tristate "Freescale i.MX23/i.MX28 LRADC touchscreen"
836 depends on MFD_MXS_LRADC
837 help
838 Say Y here if you have a touchscreen connected to the low-resolution
839 analog-to-digital converter (LRADC) on an i.MX23 or i.MX28 processor.
840
841 To compile this driver as a module, choose M here: the module will be
842 called mxs-lradc-ts.
843
844 config TOUCHSCREEN_MX25
845 tristate "Freescale i.MX25 touchscreen input driver"
846 depends on MFD_MX25_TSADC
847 help
848 Enable support for touchscreen connected to your i.MX25.
849
850 To compile this driver as a module, choose M here: the
851 module will be called fsl-imx25-tcq.
852
853 config TOUCHSCREEN_MC13783
854 tristate "Freescale MC13783 touchscreen input driver"
855 depends on MFD_MC13XXX
856 help
857 Say Y here if you have an Freescale MC13783 PMIC on your
858 board and want to use its touchscreen
859
860 If unsure, say N.
861
862 To compile this driver as a module, choose M here: the
863 module will be called mc13783_ts.
864
865 config TOUCHSCREEN_USB_EGALAX
866 default y
867 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
868 depends on TOUCHSCREEN_USB_COMPOSITE
869
870 config TOUCHSCREEN_USB_PANJIT
871 default y
872 bool "PanJit device support" if EXPERT
873 depends on TOUCHSCREEN_USB_COMPOSITE
874
875 config TOUCHSCREEN_USB_3M
876 default y
877 bool "3M/Microtouch EX II series device support" if EXPERT
878 depends on TOUCHSCREEN_USB_COMPOSITE
879
880 config TOUCHSCREEN_USB_ITM
881 default y
882 bool "ITM device support" if EXPERT
883 depends on TOUCHSCREEN_USB_COMPOSITE
884
885 config TOUCHSCREEN_USB_ETURBO
886 default y
887 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
888 depends on TOUCHSCREEN_USB_COMPOSITE
889
890 config TOUCHSCREEN_USB_GUNZE
891 default y
892 bool "Gunze AHL61 device support" if EXPERT
893 depends on TOUCHSCREEN_USB_COMPOSITE
894
895 config TOUCHSCREEN_USB_DMC_TSC10
896 default y
897 bool "DMC TSC-10/25 device support" if EXPERT
898 depends on TOUCHSCREEN_USB_COMPOSITE
899
900 config TOUCHSCREEN_USB_IRTOUCH
901 default y
902 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
903 depends on TOUCHSCREEN_USB_COMPOSITE
904
905 config TOUCHSCREEN_USB_IDEALTEK
906 default y
907 bool "IdealTEK URTC1000 device support" if EXPERT
908 depends on TOUCHSCREEN_USB_COMPOSITE
909
910 config TOUCHSCREEN_USB_GENERAL_TOUCH
911 default y
912 bool "GeneralTouch Touchscreen device support" if EXPERT
913 depends on TOUCHSCREEN_USB_COMPOSITE
914
915 config TOUCHSCREEN_USB_GOTOP
916 default y
917 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
918 depends on TOUCHSCREEN_USB_COMPOSITE
919
920 config TOUCHSCREEN_USB_JASTEC
921 default y
922 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
923 depends on TOUCHSCREEN_USB_COMPOSITE
924
925 config TOUCHSCREEN_USB_ELO
926 default y
927 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
928 depends on TOUCHSCREEN_USB_COMPOSITE
929
930 config TOUCHSCREEN_USB_E2I
931 default y
932 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
933 depends on TOUCHSCREEN_USB_COMPOSITE
934
935 config TOUCHSCREEN_USB_ZYTRONIC
936 default y
937 bool "Zytronic controller" if EXPERT
938 depends on TOUCHSCREEN_USB_COMPOSITE
939
940 config TOUCHSCREEN_USB_ETT_TC45USB
941 default y
942 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
943 depends on TOUCHSCREEN_USB_COMPOSITE
944
945 config TOUCHSCREEN_USB_NEXIO
946 default y
947 bool "NEXIO/iNexio device support" if EXPERT
948 depends on TOUCHSCREEN_USB_COMPOSITE
949
950 config TOUCHSCREEN_USB_EASYTOUCH
951 default y
952 bool "EasyTouch USB Touch controller device support" if EMBEDDED
953 depends on TOUCHSCREEN_USB_COMPOSITE
954 help
955 Say Y here if you have an EasyTouch USB Touch controller.
956 If unsure, say N.
957
958 config TOUCHSCREEN_TOUCHIT213
959 tristate "Sahara TouchIT-213 touchscreen"
960 select SERIO
961 help
962 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
963
964 If unsure, say N.
965
966 To compile this driver as a module, choose M here: the
967 module will be called touchit213.
968
969 config TOUCHSCREEN_TS4800
970 tristate "TS-4800 touchscreen"
971 depends on HAS_IOMEM && OF
972 depends on SOC_IMX51 || COMPILE_TEST
973 select MFD_SYSCON
974 select INPUT_POLLDEV
975 help
976 Say Y here if you have a touchscreen on a TS-4800 board.
977
978 On TS-4800, the touchscreen is not handled directly by Linux but by
979 a companion FPGA.
980
981 If unsure, say N.
982
983 To compile this driver as a module, choose M here: the
984 module will be called ts4800_ts.
985
986 config TOUCHSCREEN_TSC_SERIO
987 tristate "TSC-10/25/40 serial touchscreen support"
988 select SERIO
989 help
990 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
991 to your system.
992
993 If unsure, say N.
994
995 To compile this driver as a module, choose M here: the
996 module will be called tsc40.
997
998 config TOUCHSCREEN_TSC200X_CORE
999 tristate
1000
1001 config TOUCHSCREEN_TSC2004
1002 tristate "TSC2004 based touchscreens"
1003 depends on I2C
1004 select REGMAP_I2C
1005 select TOUCHSCREEN_TSC200X_CORE
1006 help
1007 Say Y here if you have a TSC2004 based touchscreen.
1008
1009 If unsure, say N.
1010
1011 To compile this driver as a module, choose M here: the
1012 module will be called tsc2004.
1013
1014 config TOUCHSCREEN_TSC2005
1015 tristate "TSC2005 based touchscreens"
1016 depends on SPI_MASTER
1017 select REGMAP_SPI
1018 select TOUCHSCREEN_TSC200X_CORE
1019 help
1020 Say Y here if you have a TSC2005 based touchscreen.
1021
1022 If unsure, say N.
1023
1024 To compile this driver as a module, choose M here: the
1025 module will be called tsc2005.
1026
1027 config TOUCHSCREEN_TSC2007
1028 tristate "TSC2007 based touchscreens"
1029 depends on I2C
1030 help
1031 Say Y here if you have a TSC2007 based touchscreen.
1032
1033 If unsure, say N.
1034
1035 To compile this driver as a module, choose M here: the
1036 module will be called tsc2007.
1037
1038 config TOUCHSCREEN_TSC2007_IIO
1039 bool "IIO interface for external ADC input and temperature"
1040 depends on TOUCHSCREEN_TSC2007
1041 depends on IIO=y || IIO=TOUCHSCREEN_TSC2007
1042 help
1043 Saying Y here adds an iio interface to the tsc2007 which
1044 provides values for the AUX input (used for e.g. battery
1045 or ambient light monitoring), temperature and raw input
1046 values.
1047
1048 config TOUCHSCREEN_W90X900
1049 tristate "W90P910 touchscreen driver"
1050 depends on ARCH_W90X900
1051 help
1052 Say Y here if you have a W90P910 based touchscreen.
1053
1054 To compile this driver as a module, choose M here: the
1055 module will be called w90p910_ts.
1056
1057 config TOUCHSCREEN_PCAP
1058 tristate "Motorola PCAP touchscreen"
1059 depends on EZX_PCAP
1060 help
1061 Say Y here if you have a Motorola EZX telephone and
1062 want to enable support for the built-in touchscreen.
1063
1064 To compile this driver as a module, choose M here: the
1065 module will be called pcap_ts.
1066
1067 config TOUCHSCREEN_RM_TS
1068 tristate "Raydium I2C Touchscreen"
1069 depends on I2C
1070 depends on GPIOLIB || COMPILE_TEST
1071 help
1072 Say Y here if you have Raydium series I2C touchscreen,
1073 such as RM32380, connected to your system.
1074
1075 If unsure, say N.
1076
1077 To compile this driver as a module, choose M here: the
1078 module will be called raydium_i2c_ts.
1079
1080 config TOUCHSCREEN_SILEAD
1081 tristate "Silead I2C touchscreen"
1082 depends on I2C
1083 help
1084 Say Y here if you have the Silead touchscreen connected to
1085 your system.
1086
1087 If unsure, say N.
1088
1089 To compile this driver as a module, choose M here: the
1090 module will be called silead.
1091
1092 config TOUCHSCREEN_SIS_I2C
1093 tristate "SiS 9200 family I2C touchscreen"
1094 depends on I2C
1095 select CRC_ITU_T
1096 depends on GPIOLIB || COMPILE_TEST
1097 help
1098 This enables support for SiS 9200 family over I2C based touchscreens.
1099
1100 If unsure, say N.
1101
1102 To compile this driver as a module, choose M here: the
1103 module will be called sis_i2c.
1104
1105 config TOUCHSCREEN_ST1232
1106 tristate "Sitronix ST1232 touchscreen controllers"
1107 depends on I2C
1108 help
1109 Say Y here if you want to support Sitronix ST1232
1110 touchscreen controller.
1111
1112 If unsure, say N.
1113
1114 To compile this driver as a module, choose M here: the
1115 module will be called st1232_ts.
1116
1117 config TOUCHSCREEN_STMPE
1118 tristate "STMicroelectronics STMPE touchscreens"
1119 depends on MFD_STMPE
1120 depends on (OF || COMPILE_TEST)
1121 help
1122 Say Y here if you want support for STMicroelectronics
1123 STMPE touchscreen controllers.
1124
1125 To compile this driver as a module, choose M here: the
1126 module will be called stmpe-ts.
1127
1128 config TOUCHSCREEN_SUN4I
1129 tristate "Allwinner sun4i resistive touchscreen controller support"
1130 depends on ARCH_SUNXI || COMPILE_TEST
1131 depends on HWMON
1132 depends on THERMAL || !THERMAL_OF
1133 help
1134 This selects support for the resistive touchscreen controller
1135 found on Allwinner sunxi SoCs.
1136
1137 To compile this driver as a module, choose M here: the
1138 module will be called sun4i-ts.
1139
1140 config TOUCHSCREEN_SUR40
1141 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
1142 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1143 depends on VIDEO_V4L2
1144 select INPUT_POLLDEV
1145 select VIDEOBUF2_DMA_SG
1146 help
1147 Say Y here if you want support for the Samsung SUR40 touchscreen
1148 (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
1149
1150 To compile this driver as a module, choose M here: the
1151 module will be called sur40.
1152
1153 config TOUCHSCREEN_SURFACE3_SPI
1154 tristate "Ntrig/Microsoft Surface 3 SPI touchscreen"
1155 depends on SPI
1156 depends on GPIOLIB || COMPILE_TEST
1157 help
1158 Say Y here if you have the Ntrig/Microsoft SPI touchscreen
1159 controller chip as found on the Surface 3 in your system.
1160
1161 If unsure, say N.
1162
1163 To compile this driver as a module, choose M here: the
1164 module will be called surface3_spi.
1165
1166 config TOUCHSCREEN_SX8654
1167 tristate "Semtech SX8654 touchscreen"
1168 depends on I2C
1169 help
1170 Say Y here if you have a Semtech SX8654 touchscreen controller.
1171
1172 If unsure, say N
1173
1174 To compile this driver as a module, choose M here: the
1175 module will be called sx8654.
1176
1177 config TOUCHSCREEN_TPS6507X
1178 tristate "TPS6507x based touchscreens"
1179 depends on I2C
1180 select INPUT_POLLDEV
1181 help
1182 Say Y here if you have a TPS6507x based touchscreen
1183 controller.
1184
1185 If unsure, say N.
1186
1187 To compile this driver as a module, choose M here: the
1188 module will be called tps6507x_ts.
1189
1190 config TOUCHSCREEN_ZET6223
1191 tristate "Zeitec ZET6223 touchscreen driver"
1192 depends on I2C
1193 help
1194 Say Y here if you have a touchscreen using Zeitec ZET6223
1195
1196 If unsure, say N.
1197
1198 To compile this driver as a module, choose M here: the
1199 module will be called zet6223.
1200
1201 config TOUCHSCREEN_ZFORCE
1202 tristate "Neonode zForce infrared touchscreens"
1203 depends on I2C
1204 depends on GPIOLIB || COMPILE_TEST
1205 help
1206 Say Y here if you have a touchscreen using the zforce
1207 infraread technology from Neonode.
1208
1209 If unsure, say N.
1210
1211 To compile this driver as a module, choose M here: the
1212 module will be called zforce_ts.
1213
1214 config TOUCHSCREEN_COLIBRI_VF50
1215 tristate "Toradex Colibri on board touchscreen driver"
1216 depends on IIO && VF610_ADC
1217 depends on GPIOLIB || COMPILE_TEST
1218 help
1219 Say Y here if you have a Colibri VF50 and plan to use
1220 the on-board provided 4-wire touchscreen driver.
1221
1222 If unsure, say N.
1223
1224 To compile this driver as a module, choose M here: the
1225 module will be called colibri_vf50_ts.
1226
1227 config TOUCHSCREEN_ROHM_BU21023
1228 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
1229 depends on I2C
1230 help
1231 Say Y here if you have a touchscreen using ROHM BU21023/24.
1232
1233 If unsure, say N.
1234
1235 To compile this driver as a module, choose M here: the
1236 module will be called bu21023_ts.
1237
1238 endif