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