Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
1#
2# Touchscreen driver configuration
3#
4menuconfig 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
12if INPUT_TOUCHSCREEN
13
14config TOUCHSCREEN_PROPERTIES
15 def_tristate INPUT
16 depends on INPUT
17
18config 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
30config 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
49config 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
62config 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
73config 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
82config 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
93config 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
105config 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
118config 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
127config 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
140config 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
152config 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
165config 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
178config 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
191config 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
200config 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
209config 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
221config 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
230config 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
239config 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
252config 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
264config 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
276config 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
288config 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
297config 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
307config 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
317config 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
330config 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
345config 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
360config 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
372config 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
384config 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
396config 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
408config 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
420config 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
432config 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
444config 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
456config 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
466config 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
478config 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
490config 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
502config 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
513config 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
525config 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
537config 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
549config TOUCHSCREEN_MK712
550 tristate "ICS MicroClock MK712 touchscreen"
551 help
552 Say Y here if you have the ICS MicroClock MK712 touchscreen
553 controller chip in your system.
554
555 If unsure, say N.
556
557 To compile this driver as a module, choose M here: the
558 module will be called mk712.
559
560config TOUCHSCREEN_HP600
561 tristate "HP Jornada 6xx touchscreen"
562 depends on SH_HP6XX && SH_ADC
563 help
564 Say Y here if you have a HP Jornada 620/660/680/690 and want to
565 support the built-in touchscreen.
566
567 To compile this driver as a module, choose M here: the
568 module will be called hp680_ts_input.
569
570config TOUCHSCREEN_HP7XX
571 tristate "HP Jornada 7xx touchscreen"
572 depends on SA1100_JORNADA720_SSP
573 help
574 Say Y here if you have a HP Jornada 710/720/728 and want
575 to support the built-in touchscreen.
576
577 To compile this driver as a module, choose M here: the
578 module will be called jornada720_ts.
579
580config TOUCHSCREEN_IPAQ_MICRO
581 tristate "HP iPAQ Atmel Micro ASIC touchscreen"
582 depends on MFD_IPAQ_MICRO
583 help
584 Say Y here to enable support for the touchscreen attached to
585 the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
586
587 If unsure, say N.
588
589 To compile this driver as a module, choose M here: the
590 module will be called ipaq-micro-ts.
591
592config TOUCHSCREEN_HTCPEN
593 tristate "HTC Shift X9500 touchscreen"
594 depends on ISA
595 help
596 Say Y here if you have an HTC Shift UMPC also known as HTC X9500
597 Clio / Shangrila and want to support the built-in touchscreen.
598
599 If unsure, say N.
600
601 To compile this driver as a module, choose M here: the
602 module will be called htcpen.
603
604config TOUCHSCREEN_PENMOUNT
605 tristate "Penmount serial touchscreen"
606 select SERIO
607 help
608 Say Y here if you have a Penmount serial touchscreen connected to
609 your system.
610
611 If unsure, say N.
612
613 To compile this driver as a module, choose M here: the
614 module will be called penmount.
615
616config TOUCHSCREEN_EDT_FT5X06
617 tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
618 depends on I2C
619 help
620 Say Y here if you have an EDT "Polytouch" touchscreen based
621 on the FocalTech FT5x06 family of controllers connected to
622 your system.
623
624 If unsure, say N.
625
626 To compile this driver as a module, choose M here: the
627 module will be called edt-ft5x06.
628
629config TOUCHSCREEN_MIGOR
630 tristate "Renesas MIGO-R touchscreen"
631 depends on (SH_MIGOR || COMPILE_TEST) && I2C
632 help
633 Say Y here to enable MIGO-R touchscreen support.
634
635 If unsure, say N.
636
637 To compile this driver as a module, choose M here: the
638 module will be called migor_ts.
639
640config TOUCHSCREEN_TOUCHRIGHT
641 tristate "Touchright serial touchscreen"
642 select SERIO
643 help
644 Say Y here if you have a Touchright serial touchscreen connected to
645 your system.
646
647 If unsure, say N.
648
649 To compile this driver as a module, choose M here: the
650 module will be called touchright.
651
652config TOUCHSCREEN_TOUCHWIN
653 tristate "Touchwin serial touchscreen"
654 select SERIO
655 help
656 Say Y here if you have a Touchwin serial touchscreen connected to
657 your system.
658
659 If unsure, say N.
660
661 To compile this driver as a module, choose M here: the
662 module will be called touchwin.
663
664config TOUCHSCREEN_TI_AM335X_TSC
665 tristate "TI Touchscreen Interface"
666 depends on MFD_TI_AM335X_TSCADC
667 help
668 Say Y here if you have 4/5/8 wire touchscreen controller
669 to be connected to the ADC controller on your TI AM335x SoC.
670
671 If unsure, say N.
672
673 To compile this driver as a module, choose M here: the
674 module will be called ti_am335x_tsc.
675
676config TOUCHSCREEN_UCB1400
677 tristate "Philips UCB1400 touchscreen"
678 depends on AC97_BUS
679 depends on UCB1400_CORE
680 help
681 This enables support for the Philips UCB1400 touchscreen interface.
682 The UCB1400 is an AC97 audio codec. The touchscreen interface
683 will be initialized only after the ALSA subsystem has been
684 brought up and the UCB1400 detected. You therefore have to
685 configure ALSA support as well (either built-in or modular,
686 independently of whether this driver is itself built-in or
687 modular) for this driver to work.
688
689 To compile this driver as a module, choose M here: the
690 module will be called ucb1400_ts.
691
692config TOUCHSCREEN_PIXCIR
693 tristate "PIXCIR I2C touchscreens"
694 depends on I2C
695 help
696 Say Y here if you have a pixcir i2c touchscreen
697 controller.
698
699 If unsure, say N.
700
701 To compile this driver as a module, choose M here: the
702 module will be called pixcir_i2c_ts.
703
704config TOUCHSCREEN_WDT87XX_I2C
705 tristate "Weida HiTech I2C touchscreen"
706 depends on I2C
707 help
708 Say Y here if you have a Weida WDT87XX I2C touchscreen
709 connected to your system.
710
711 If unsure, say N.
712
713 To compile this driver as a module, choose M here: the
714 module will be called wdt87xx_i2c.
715
716config TOUCHSCREEN_WM831X
717 tristate "Support for WM831x touchscreen controllers"
718 depends on MFD_WM831X
719 help
720 This enables support for the touchscreen controller on the WM831x
721 series of PMICs.
722
723 To compile this driver as a module, choose M here: the
724 module will be called wm831x-ts.
725
726config TOUCHSCREEN_WM97XX
727 tristate "Support for WM97xx AC97 touchscreen controllers"
728 depends on AC97_BUS
729 help
730 Say Y here if you have a Wolfson Microelectronics WM97xx
731 touchscreen connected to your system. Note that this option
732 only enables core driver, you will also need to select
733 support for appropriate chip below.
734
735 If unsure, say N.
736
737 To compile this driver as a module, choose M here: the
738 module will be called wm97xx-ts.
739
740config TOUCHSCREEN_WM9705
741 bool "WM9705 Touchscreen interface support"
742 depends on TOUCHSCREEN_WM97XX
743 default y
744 help
745 Say Y here to enable support for the Wolfson Microelectronics
746 WM9705 touchscreen controller.
747
748config TOUCHSCREEN_WM9712
749 bool "WM9712 Touchscreen interface support"
750 depends on TOUCHSCREEN_WM97XX
751 default y
752 help
753 Say Y here to enable support for the Wolfson Microelectronics
754 WM9712 touchscreen controller.
755
756config TOUCHSCREEN_WM9713
757 bool "WM9713 Touchscreen interface support"
758 depends on TOUCHSCREEN_WM97XX
759 default y
760 help
761 Say Y here to enable support for the Wolfson Microelectronics
762 WM9713 touchscreen controller.
763
764config TOUCHSCREEN_WM97XX_ATMEL
765 tristate "WM97xx Atmel accelerated touch"
766 depends on TOUCHSCREEN_WM97XX && AVR32
767 help
768 Say Y here for support for streaming mode with WM97xx touchscreens
769 on Atmel AT91 or AVR32 systems with an AC97C module.
770
771 Be aware that this will use channel B in the controller for
772 streaming data, this must not conflict with other AC97C drivers.
773
774 If unsure, say N.
775
776 To compile this driver as a module, choose M here: the module will
777 be called atmel-wm97xx.
778
779config TOUCHSCREEN_WM97XX_MAINSTONE
780 tristate "WM97xx Mainstone/Palm accelerated touch"
781 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
782 help
783 Say Y here for support for streaming mode with WM97xx touchscreens
784 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
785
786 If unsure, say N.
787
788 To compile this driver as a module, choose M here: the
789 module will be called mainstone-wm97xx.
790
791config TOUCHSCREEN_WM97XX_ZYLONITE
792 tristate "Zylonite accelerated touch"
793 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
794 select TOUCHSCREEN_WM9713
795 help
796 Say Y here for support for streaming mode with the touchscreen
797 on Zylonite systems.
798
799 If unsure, say N.
800
801 To compile this driver as a module, choose M here: the
802 module will be called zylonite-wm97xx.
803
804config TOUCHSCREEN_USB_COMPOSITE
805 tristate "USB Touchscreen Driver"
806 depends on USB_ARCH_HAS_HCD
807 select USB
808 help
809 USB Touchscreen driver for:
810 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
811 - PanJit TouchSet USB
812 - 3M MicroTouch USB (EX II series)
813 - ITM
814 - some other eTurboTouch
815 - Gunze AHL61
816 - DMC TSC-10/25
817 - IRTOUCHSYSTEMS/UNITOP
818 - IdealTEK URTC1000
819 - GoTop Super_Q2/GogoPen/PenPower tablets
820 - JASTEC USB Touch Controller/DigiTech DTR-02U
821 - Zytronic controllers
822 - Elo TouchSystems 2700 IntelliTouch
823 - EasyTouch USB Touch Controller from Data Modul
824 - e2i (Mimo monitors)
825
826 Have a look at <http://linux.chapter7.ch/touchkit/> for
827 a usage description and the required user-space stuff.
828
829 To compile this driver as a module, choose M here: the
830 module will be called usbtouchscreen.
831
832config TOUCHSCREEN_MX25
833 tristate "Freescale i.MX25 touchscreen input driver"
834 depends on MFD_MX25_TSADC
835 help
836 Enable support for touchscreen connected to your i.MX25.
837
838 To compile this driver as a module, choose M here: the
839 module will be called fsl-imx25-tcq.
840
841config TOUCHSCREEN_MC13783
842 tristate "Freescale MC13783 touchscreen input driver"
843 depends on MFD_MC13XXX
844 help
845 Say Y here if you have an Freescale MC13783 PMIC on your
846 board and want to use its touchscreen
847
848 If unsure, say N.
849
850 To compile this driver as a module, choose M here: the
851 module will be called mc13783_ts.
852
853config TOUCHSCREEN_USB_EGALAX
854 default y
855 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
856 depends on TOUCHSCREEN_USB_COMPOSITE
857
858config TOUCHSCREEN_USB_PANJIT
859 default y
860 bool "PanJit device support" if EXPERT
861 depends on TOUCHSCREEN_USB_COMPOSITE
862
863config TOUCHSCREEN_USB_3M
864 default y
865 bool "3M/Microtouch EX II series device support" if EXPERT
866 depends on TOUCHSCREEN_USB_COMPOSITE
867
868config TOUCHSCREEN_USB_ITM
869 default y
870 bool "ITM device support" if EXPERT
871 depends on TOUCHSCREEN_USB_COMPOSITE
872
873config TOUCHSCREEN_USB_ETURBO
874 default y
875 bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
876 depends on TOUCHSCREEN_USB_COMPOSITE
877
878config TOUCHSCREEN_USB_GUNZE
879 default y
880 bool "Gunze AHL61 device support" if EXPERT
881 depends on TOUCHSCREEN_USB_COMPOSITE
882
883config TOUCHSCREEN_USB_DMC_TSC10
884 default y
885 bool "DMC TSC-10/25 device support" if EXPERT
886 depends on TOUCHSCREEN_USB_COMPOSITE
887
888config TOUCHSCREEN_USB_IRTOUCH
889 default y
890 bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
891 depends on TOUCHSCREEN_USB_COMPOSITE
892
893config TOUCHSCREEN_USB_IDEALTEK
894 default y
895 bool "IdealTEK URTC1000 device support" if EXPERT
896 depends on TOUCHSCREEN_USB_COMPOSITE
897
898config TOUCHSCREEN_USB_GENERAL_TOUCH
899 default y
900 bool "GeneralTouch Touchscreen device support" if EXPERT
901 depends on TOUCHSCREEN_USB_COMPOSITE
902
903config TOUCHSCREEN_USB_GOTOP
904 default y
905 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
906 depends on TOUCHSCREEN_USB_COMPOSITE
907
908config TOUCHSCREEN_USB_JASTEC
909 default y
910 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
911 depends on TOUCHSCREEN_USB_COMPOSITE
912
913config TOUCHSCREEN_USB_ELO
914 default y
915 bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
916 depends on TOUCHSCREEN_USB_COMPOSITE
917
918config TOUCHSCREEN_USB_E2I
919 default y
920 bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
921 depends on TOUCHSCREEN_USB_COMPOSITE
922
923config TOUCHSCREEN_USB_ZYTRONIC
924 default y
925 bool "Zytronic controller" if EXPERT
926 depends on TOUCHSCREEN_USB_COMPOSITE
927
928config TOUCHSCREEN_USB_ETT_TC45USB
929 default y
930 bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
931 depends on TOUCHSCREEN_USB_COMPOSITE
932
933config TOUCHSCREEN_USB_NEXIO
934 default y
935 bool "NEXIO/iNexio device support" if EXPERT
936 depends on TOUCHSCREEN_USB_COMPOSITE
937
938config TOUCHSCREEN_USB_EASYTOUCH
939 default y
940 bool "EasyTouch USB Touch controller device support" if EMBEDDED
941 depends on TOUCHSCREEN_USB_COMPOSITE
942 help
943 Say Y here if you have an EasyTouch USB Touch controller.
944 If unsure, say N.
945
946config TOUCHSCREEN_TOUCHIT213
947 tristate "Sahara TouchIT-213 touchscreen"
948 select SERIO
949 help
950 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
951
952 If unsure, say N.
953
954 To compile this driver as a module, choose M here: the
955 module will be called touchit213.
956
957config TOUCHSCREEN_TS4800
958 tristate "TS-4800 touchscreen"
959 depends on HAS_IOMEM && OF
960 depends on SOC_IMX51 || COMPILE_TEST
961 select MFD_SYSCON
962 select INPUT_POLLDEV
963 help
964 Say Y here if you have a touchscreen on a TS-4800 board.
965
966 On TS-4800, the touchscreen is not handled directly by Linux but by
967 a companion FPGA.
968
969 If unsure, say N.
970
971 To compile this driver as a module, choose M here: the
972 module will be called ts4800_ts.
973
974config TOUCHSCREEN_TSC_SERIO
975 tristate "TSC-10/25/40 serial touchscreen support"
976 select SERIO
977 help
978 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
979 to your system.
980
981 If unsure, say N.
982
983 To compile this driver as a module, choose M here: the
984 module will be called tsc40.
985
986config TOUCHSCREEN_TSC200X_CORE
987 tristate
988
989config TOUCHSCREEN_TSC2004
990 tristate "TSC2004 based touchscreens"
991 depends on I2C
992 select REGMAP_I2C
993 select TOUCHSCREEN_TSC200X_CORE
994 help
995 Say Y here if you have a TSC2004 based touchscreen.
996
997 If unsure, say N.
998
999 To compile this driver as a module, choose M here: the
1000 module will be called tsc2004.
1001
1002config TOUCHSCREEN_TSC2005
1003 tristate "TSC2005 based touchscreens"
1004 depends on SPI_MASTER
1005 select REGMAP_SPI
1006 select TOUCHSCREEN_TSC200X_CORE
1007 help
1008 Say Y here if you have a TSC2005 based touchscreen.
1009
1010 If unsure, say N.
1011
1012 To compile this driver as a module, choose M here: the
1013 module will be called tsc2005.
1014
1015config TOUCHSCREEN_TSC2007
1016 tristate "TSC2007 based touchscreens"
1017 depends on I2C
1018 help
1019 Say Y here if you have a TSC2007 based touchscreen.
1020
1021 If unsure, say N.
1022
1023 To compile this driver as a module, choose M here: the
1024 module will be called tsc2007.
1025
1026config TOUCHSCREEN_W90X900
1027 tristate "W90P910 touchscreen driver"
1028 depends on ARCH_W90X900
1029 help
1030 Say Y here if you have a W90P910 based touchscreen.
1031
1032 To compile this driver as a module, choose M here: the
1033 module will be called w90p910_ts.
1034
1035config TOUCHSCREEN_PCAP
1036 tristate "Motorola PCAP touchscreen"
1037 depends on EZX_PCAP
1038 help
1039 Say Y here if you have a Motorola EZX telephone and
1040 want to enable support for the built-in touchscreen.
1041
1042 To compile this driver as a module, choose M here: the
1043 module will be called pcap_ts.
1044
1045config TOUCHSCREEN_RM_TS
1046 tristate "Raydium I2C Touchscreen"
1047 depends on I2C
1048 depends on GPIOLIB || COMPILE_TEST
1049 help
1050 Say Y here if you have Raydium series I2C touchscreen,
1051 such as RM32380, connected to your system.
1052
1053 If unsure, say N.
1054
1055 To compile this driver as a module, choose M here: the
1056 module will be called raydium_i2c_ts.
1057
1058config TOUCHSCREEN_SILEAD
1059 tristate "Silead I2C touchscreen"
1060 depends on I2C
1061 help
1062 Say Y here if you have the Silead touchscreen connected to
1063 your system.
1064
1065 If unsure, say N.
1066
1067 To compile this driver as a module, choose M here: the
1068 module will be called silead.
1069
1070config TOUCHSCREEN_SIS_I2C
1071 tristate "SiS 9200 family I2C touchscreen"
1072 depends on I2C
1073 select CRC_ITU_T
1074 depends on GPIOLIB || COMPILE_TEST
1075 help
1076 This enables support for SiS 9200 family over I2C based touchscreens.
1077
1078 If unsure, say N.
1079
1080 To compile this driver as a module, choose M here: the
1081 module will be called sis_i2c.
1082
1083config TOUCHSCREEN_ST1232
1084 tristate "Sitronix ST1232 touchscreen controllers"
1085 depends on I2C
1086 help
1087 Say Y here if you want to support Sitronix ST1232
1088 touchscreen controller.
1089
1090 If unsure, say N.
1091
1092 To compile this driver as a module, choose M here: the
1093 module will be called st1232_ts.
1094
1095config TOUCHSCREEN_STMPE
1096 tristate "STMicroelectronics STMPE touchscreens"
1097 depends on MFD_STMPE
1098 depends on (OF || COMPILE_TEST)
1099 help
1100 Say Y here if you want support for STMicroelectronics
1101 STMPE touchscreen controllers.
1102
1103 To compile this driver as a module, choose M here: the
1104 module will be called stmpe-ts.
1105
1106config TOUCHSCREEN_SUN4I
1107 tristate "Allwinner sun4i resistive touchscreen controller support"
1108 depends on ARCH_SUNXI || COMPILE_TEST
1109 depends on HWMON
1110 depends on THERMAL || !THERMAL_OF
1111 help
1112 This selects support for the resistive touchscreen controller
1113 found on Allwinner sunxi SoCs.
1114
1115 To compile this driver as a module, choose M here: the
1116 module will be called sun4i-ts.
1117
1118config TOUCHSCREEN_SUR40
1119 tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
1120 depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
1121 depends on VIDEO_V4L2
1122 select INPUT_POLLDEV
1123 select VIDEOBUF2_DMA_SG
1124 help
1125 Say Y here if you want support for the Samsung SUR40 touchscreen
1126 (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
1127
1128 To compile this driver as a module, choose M here: the
1129 module will be called sur40.
1130
1131config TOUCHSCREEN_SURFACE3_SPI
1132 tristate "Ntrig/Microsoft Surface 3 SPI touchscreen"
1133 depends on SPI
1134 depends on GPIOLIB || COMPILE_TEST
1135 help
1136 Say Y here if you have the Ntrig/Microsoft SPI touchscreen
1137 controller chip as found on the Surface 3 in your system.
1138
1139 If unsure, say N.
1140
1141 To compile this driver as a module, choose M here: the
1142 module will be called surface3_spi.
1143
1144config TOUCHSCREEN_SX8654
1145 tristate "Semtech SX8654 touchscreen"
1146 depends on I2C
1147 help
1148 Say Y here if you have a Semtech SX8654 touchscreen controller.
1149
1150 If unsure, say N
1151
1152 To compile this driver as a module, choose M here: the
1153 module will be called sx8654.
1154
1155config TOUCHSCREEN_TPS6507X
1156 tristate "TPS6507x based touchscreens"
1157 depends on I2C
1158 select INPUT_POLLDEV
1159 help
1160 Say Y here if you have a TPS6507x based touchscreen
1161 controller.
1162
1163 If unsure, say N.
1164
1165 To compile this driver as a module, choose M here: the
1166 module will be called tps6507x_ts.
1167
1168config TOUCHSCREEN_ZET6223
1169 tristate "Zeitec ZET6223 touchscreen driver"
1170 depends on I2C
1171 help
1172 Say Y here if you have a touchscreen using Zeitec ZET6223
1173
1174 If unsure, say N.
1175
1176 To compile this driver as a module, choose M here: the
1177 module will be called zet6223.
1178
1179config TOUCHSCREEN_ZFORCE
1180 tristate "Neonode zForce infrared touchscreens"
1181 depends on I2C
1182 depends on GPIOLIB || COMPILE_TEST
1183 help
1184 Say Y here if you have a touchscreen using the zforce
1185 infraread technology from Neonode.
1186
1187 If unsure, say N.
1188
1189 To compile this driver as a module, choose M here: the
1190 module will be called zforce_ts.
1191
1192config TOUCHSCREEN_COLIBRI_VF50
1193 tristate "Toradex Colibri on board touchscreen driver"
1194 depends on IIO && VF610_ADC
1195 depends on GPIOLIB || COMPILE_TEST
1196 help
1197 Say Y here if you have a Colibri VF50 and plan to use
1198 the on-board provided 4-wire touchscreen driver.
1199
1200 If unsure, say N.
1201
1202 To compile this driver as a module, choose M here: the
1203 module will be called colibri_vf50_ts.
1204
1205config TOUCHSCREEN_ROHM_BU21023
1206 tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
1207 depends on I2C
1208 help
1209 Say Y here if you have a touchscreen using ROHM BU21023/24.
1210
1211 If unsure, say N.
1212
1213 To compile this driver as a module, choose M here: the
1214 module will be called bu21023_ts.
1215
1216endif