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