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