xref: /openbmc/linux/drivers/input/touchscreen/Kconfig (revision df2634f43f5106947f3735a0b61a6527a4b278cd)
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_BITSY
90	tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
91	depends on SA1100_BITSY
92	select SERIO
93	help
94	  Say Y here if you have the h3600 (Bitsy) touchscreen.
95
96	  If unsure, say N.
97
98	  To compile this driver as a module, choose M here: the
99	  module will be called h3600_ts_input.
100
101config TOUCHSCREEN_BU21013
102	tristate "BU21013 based touch panel controllers"
103	depends on I2C
104	help
105	  Say Y here if you have a bu21013 touchscreen connected to
106	  your system.
107
108	  If unsure, say N.
109
110	  To compile this driver as a module, choose M here: the
111	  module will be called bu21013_ts.
112
113config TOUCHSCREEN_CY8CTMG110
114	tristate "cy8ctmg110 touchscreen"
115	depends on I2C
116	depends on GPIOLIB
117
118	help
119	  Say Y here if you have a cy8ctmg110 capacitive touchscreen on
120	  an AAVA device.
121
122	  If unsure, say N.
123
124	  To compile this driver as a module, choose M here: the
125	  module will be called cy8ctmg110_ts.
126
127config TOUCHSCREEN_DA9034
128	tristate "Touchscreen support for Dialog Semiconductor DA9034"
129	depends on PMIC_DA903X
130	default y
131	help
132	  Say Y here to enable the support for the touchscreen found
133	  on Dialog Semiconductor DA9034 PMIC.
134
135config TOUCHSCREEN_DYNAPRO
136	tristate "Dynapro serial touchscreen"
137	select SERIO
138	help
139	  Say Y here if you have a Dynapro serial touchscreen connected to
140	  your system.
141
142	  If unsure, say N.
143
144	  To compile this driver as a module, choose M here: the
145	  module will be called dynapro.
146
147config TOUCHSCREEN_HAMPSHIRE
148	tristate "Hampshire serial touchscreen"
149	select SERIO
150	help
151	  Say Y here if you have a Hampshire serial touchscreen connected to
152	  your system.
153
154	  If unsure, say N.
155
156	  To compile this driver as a module, choose M here: the
157	  module will be called hampshire.
158
159config TOUCHSCREEN_EETI
160	tristate "EETI touchscreen panel support"
161	depends on I2C
162	help
163	  Say Y here to enable support for I2C connected EETI touch panels.
164
165	  To compile this driver as a module, choose M here: the
166	  module will be called eeti_ts.
167
168config TOUCHSCREEN_FUJITSU
169	tristate "Fujitsu serial touchscreen"
170	select SERIO
171	help
172	  Say Y here if you have the Fujitsu touchscreen (such as one
173	  installed in Lifebook P series laptop) connected to your
174	  system.
175
176	  If unsure, say N.
177
178	  To compile this driver as a module, choose M here: the
179	  module will be called fujitsu-ts.
180
181config TOUCHSCREEN_S3C2410
182	tristate "Samsung S3C2410/generic touchscreen input driver"
183	depends on ARCH_S3C2410 || SAMSUNG_DEV_TS
184	select S3C_ADC
185	help
186	  Say Y here if you have the s3c2410 touchscreen.
187
188	  If unsure, say N.
189
190	  To compile this driver as a module, choose M here: the
191	  module will be called s3c2410_ts.
192
193config TOUCHSCREEN_GUNZE
194	tristate "Gunze AHL-51S touchscreen"
195	select SERIO
196	help
197	  Say Y here if you have the Gunze AHL-51 touchscreen connected to
198	  your system.
199
200	  If unsure, say N.
201
202	  To compile this driver as a module, choose M here: the
203	  module will be called gunze.
204
205config TOUCHSCREEN_ELO
206	tristate "Elo serial touchscreens"
207	select SERIO
208	help
209	  Say Y here if you have an Elo serial touchscreen connected to
210	  your system.
211
212	  If unsure, say N.
213
214	  To compile this driver as a module, choose M here: the
215	  module will be called elo.
216
217config TOUCHSCREEN_WACOM_W8001
218	tristate "Wacom W8001 penabled serial touchscreen"
219	select SERIO
220	help
221	  Say Y here if you have an Wacom W8001 penabled serial touchscreen
222	  connected to your system.
223
224	  If unsure, say N.
225
226	  To compile this driver as a module, choose M here: the
227	  module will be called wacom_w8001.
228
229config TOUCHSCREEN_LPC32XX
230	tristate "LPC32XX touchscreen controller"
231	depends on ARCH_LPC32XX
232	help
233	  Say Y here if you have a LPC32XX device and want
234	  to support the built-in touchscreen.
235
236	  To compile this driver as a module, choose M here: the
237	  module will be called lpc32xx_ts.
238
239config TOUCHSCREEN_MCS5000
240	tristate "MELFAS MCS-5000 touchscreen"
241	depends on I2C
242	help
243	  Say Y here if you have the MELFAS MCS-5000 touchscreen controller
244	  chip in your system.
245
246	  If unsure, say N.
247
248	  To compile this driver as a module, choose M here: the
249	  module will be called mcs5000_ts.
250
251config TOUCHSCREEN_MTOUCH
252	tristate "MicroTouch serial touchscreens"
253	select SERIO
254	help
255	  Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
256	  your system.
257
258	  If unsure, say N.
259
260	  To compile this driver as a module, choose M here: the
261	  module will be called mtouch.
262
263config TOUCHSCREEN_INEXIO
264	tristate "iNexio serial touchscreens"
265	select SERIO
266	help
267	  Say Y here if you have an iNexio serial touchscreen connected to
268	  your system.
269
270	  If unsure, say N.
271
272	  To compile this driver as a module, choose M here: the
273	  module will be called inexio.
274
275config TOUCHSCREEN_INTEL_MID
276	tristate "Intel MID platform resistive touchscreen"
277	depends on INTEL_SCU_IPC
278	help
279	  Say Y here if you have a Intel MID based touchscreen in
280	  your system.
281
282	  If unsure, say N.
283
284	  To compile this driver as a module, choose M here: the
285	  module will be called intel_mid_touch.
286
287config TOUCHSCREEN_MK712
288	tristate "ICS MicroClock MK712 touchscreen"
289	help
290	  Say Y here if you have the ICS MicroClock MK712 touchscreen
291	  controller chip in your system.
292
293	  If unsure, say N.
294
295	  To compile this driver as a module, choose M here: the
296	  module will be called mk712.
297
298config TOUCHSCREEN_HP600
299	tristate "HP Jornada 6xx touchscreen"
300	depends on SH_HP6XX && SH_ADC
301	help
302	  Say Y here if you have a HP Jornada 620/660/680/690 and want to
303          support the built-in touchscreen.
304
305	  To compile this driver as a module, choose M here: the
306	  module will be called hp680_ts_input.
307
308config TOUCHSCREEN_HP7XX
309	tristate "HP Jornada 7xx touchscreen"
310	depends on SA1100_JORNADA720_SSP
311	help
312	  Say Y here if you have a HP Jornada 710/720/728 and want
313	  to support the built-in touchscreen.
314
315	  To compile this driver as a module, choose M here: the
316	  module will be called jornada720_ts.
317
318config TOUCHSCREEN_HTCPEN
319	tristate "HTC Shift X9500 touchscreen"
320	depends on ISA
321	help
322	  Say Y here if you have an HTC Shift UMPC also known as HTC X9500
323	  Clio / Shangrila and want to support the built-in touchscreen.
324
325	  If unsure, say N.
326
327	  To compile this driver as a module, choose M here: the
328	  module will be called htcpen.
329
330config TOUCHSCREEN_PENMOUNT
331	tristate "Penmount serial touchscreen"
332	select SERIO
333	help
334	  Say Y here if you have a Penmount serial touchscreen connected to
335	  your system.
336
337	  If unsure, say N.
338
339	  To compile this driver as a module, choose M here: the
340	  module will be called penmount.
341
342config TOUCHSCREEN_QT602240
343	tristate "QT602240 I2C Touchscreen"
344	depends on I2C
345	help
346	  Say Y here if you have the AT42QT602240/ATMXT224 I2C touchscreen
347	  connected to your system.
348
349	  If unsure, say N.
350
351	  To compile this driver as a module, choose M here: the
352	  module will be called qt602240_ts.
353
354config TOUCHSCREEN_MIGOR
355	tristate "Renesas MIGO-R touchscreen"
356	depends on SH_MIGOR && I2C
357	help
358	  Say Y here to enable MIGO-R touchscreen support.
359
360	  If unsure, say N.
361
362	  To compile this driver as a module, choose M here: the
363	  module will be called migor_ts.
364
365config TOUCHSCREEN_TNETV107X
366	tristate "TI TNETV107X touchscreen support"
367	depends on ARCH_DAVINCI_TNETV107X
368	help
369	  Say Y here if you want to use the TNETV107X touchscreen.
370
371	  To compile this driver as a module, choose M here: the
372	  module will be called tnetv107x-ts.
373
374config TOUCHSCREEN_TOUCHRIGHT
375	tristate "Touchright serial touchscreen"
376	select SERIO
377	help
378	  Say Y here if you have a Touchright serial touchscreen connected to
379	  your system.
380
381	  If unsure, say N.
382
383	  To compile this driver as a module, choose M here: the
384	  module will be called touchright.
385
386config TOUCHSCREEN_TOUCHWIN
387	tristate "Touchwin serial touchscreen"
388	select SERIO
389	help
390	  Say Y here if you have a Touchwin serial touchscreen connected to
391	  your system.
392
393	  If unsure, say N.
394
395	  To compile this driver as a module, choose M here: the
396	  module will be called touchwin.
397
398config TOUCHSCREEN_ATMEL_TSADCC
399	tristate "Atmel Touchscreen Interface"
400	depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
401	help
402	  Say Y here if you have a 4-wire touchscreen connected to the
403          ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
404
405	  If unsure, say N.
406
407	  To compile this driver as a module, choose M here: the
408	  module will be called atmel_tsadcc.
409
410config TOUCHSCREEN_UCB1400
411	tristate "Philips UCB1400 touchscreen"
412	depends on AC97_BUS
413	depends on UCB1400_CORE
414	help
415	  This enables support for the Philips UCB1400 touchscreen interface.
416	  The UCB1400 is an AC97 audio codec.  The touchscreen interface
417	  will be initialized only after the ALSA subsystem has been
418	  brought up and the UCB1400 detected.  You therefore have to
419	  configure ALSA support as well (either built-in or modular,
420	  independently of whether this driver is itself built-in or
421	  modular) for this driver to work.
422
423	  To compile this driver as a module, choose M here: the
424	  module will be called ucb1400_ts.
425
426config TOUCHSCREEN_WM97XX
427	tristate "Support for WM97xx AC97 touchscreen controllers"
428	depends on AC97_BUS
429	help
430	  Say Y here if you have a Wolfson Microelectronics WM97xx
431	  touchscreen connected to your system. Note that this option
432	  only enables core driver, you will also need to select
433	  support for appropriate chip below.
434
435	  If unsure, say N.
436
437	  To compile this driver as a module, choose M here: the
438	  module will be called wm97xx-ts.
439
440config TOUCHSCREEN_WM9705
441	bool "WM9705 Touchscreen interface support"
442	depends on TOUCHSCREEN_WM97XX
443	default y
444	help
445	  Say Y here to enable support for the Wolfson Microelectronics
446	  WM9705 touchscreen controller.
447
448config TOUCHSCREEN_WM9712
449	bool "WM9712 Touchscreen interface support"
450	depends on TOUCHSCREEN_WM97XX
451	default y
452	help
453	  Say Y here to enable support for the Wolfson Microelectronics
454	  WM9712 touchscreen controller.
455
456config TOUCHSCREEN_WM9713
457	bool "WM9713 Touchscreen interface support"
458	depends on TOUCHSCREEN_WM97XX
459	default y
460	help
461	  Say Y here to enable support for the Wolfson Microelectronics
462	  WM9713 touchscreen controller.
463
464config TOUCHSCREEN_WM97XX_ATMEL
465	tristate "WM97xx Atmel accelerated touch"
466	depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
467	help
468	  Say Y here for support for streaming mode with WM97xx touchscreens
469	  on Atmel AT91 or AVR32 systems with an AC97C module.
470
471	  Be aware that this will use channel B in the controller for
472	  streaming data, this must not conflict with other AC97C drivers.
473
474	  If unsure, say N.
475
476	  To compile this driver as a module, choose M here: the module will
477	  be called atmel-wm97xx.
478
479config TOUCHSCREEN_WM97XX_MAINSTONE
480	tristate "WM97xx Mainstone/Palm accelerated touch"
481	depends on TOUCHSCREEN_WM97XX && ARCH_PXA
482	help
483	  Say Y here for support for streaming mode with WM97xx touchscreens
484	  on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
485
486	  If unsure, say N.
487
488	  To compile this driver as a module, choose M here: the
489	  module will be called mainstone-wm97xx.
490
491config TOUCHSCREEN_WM97XX_ZYLONITE
492	tristate "Zylonite accelerated touch"
493	depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
494	select TOUCHSCREEN_WM9713
495	help
496	  Say Y here for support for streaming mode with the touchscreen
497	  on Zylonite systems.
498
499	  If unsure, say N.
500
501	  To compile this driver as a module, choose M here: the
502	  module will be called zylonite-wm97xx.
503
504config TOUCHSCREEN_USB_COMPOSITE
505	tristate "USB Touchscreen Driver"
506	depends on USB_ARCH_HAS_HCD
507	select USB
508	help
509	  USB Touchscreen driver for:
510	  - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
511	  - PanJit TouchSet USB
512	  - 3M MicroTouch USB (EX II series)
513	  - ITM
514	  - some other eTurboTouch
515	  - Gunze AHL61
516	  - DMC TSC-10/25
517	  - IRTOUCHSYSTEMS/UNITOP
518	  - IdealTEK URTC1000
519	  - GoTop Super_Q2/GogoPen/PenPower tablets
520	  - JASTEC USB Touch Controller/DigiTech DTR-02U
521	  - Zytronic controllers
522
523	  Have a look at <http://linux.chapter7.ch/touchkit/> for
524	  a usage description and the required user-space stuff.
525
526	  To compile this driver as a module, choose M here: the
527	  module will be called usbtouchscreen.
528
529config TOUCHSCREEN_MC13783
530	tristate "Freescale MC13783 touchscreen input driver"
531	depends on MFD_MC13783
532	help
533	  Say Y here if you have an Freescale MC13783 PMIC on your
534	  board and want to use its touchscreen
535
536	  If unsure, say N.
537
538	  To compile this driver as a module, choose M here: the
539	  module will be called mc13783_ts.
540
541config TOUCHSCREEN_USB_EGALAX
542	default y
543	bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
544	depends on TOUCHSCREEN_USB_COMPOSITE
545
546config TOUCHSCREEN_USB_PANJIT
547	default y
548	bool "PanJit device support" if EXPERT
549	depends on TOUCHSCREEN_USB_COMPOSITE
550
551config TOUCHSCREEN_USB_3M
552	default y
553	bool "3M/Microtouch EX II series device support" if EXPERT
554	depends on TOUCHSCREEN_USB_COMPOSITE
555
556config TOUCHSCREEN_USB_ITM
557	default y
558	bool "ITM device support" if EXPERT
559	depends on TOUCHSCREEN_USB_COMPOSITE
560
561config TOUCHSCREEN_USB_ETURBO
562	default y
563	bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
564	depends on TOUCHSCREEN_USB_COMPOSITE
565
566config TOUCHSCREEN_USB_GUNZE
567	default y
568	bool "Gunze AHL61 device support" if EXPERT
569	depends on TOUCHSCREEN_USB_COMPOSITE
570
571config TOUCHSCREEN_USB_DMC_TSC10
572	default y
573	bool "DMC TSC-10/25 device support" if EXPERT
574	depends on TOUCHSCREEN_USB_COMPOSITE
575
576config TOUCHSCREEN_USB_IRTOUCH
577	default y
578	bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
579	depends on TOUCHSCREEN_USB_COMPOSITE
580
581config TOUCHSCREEN_USB_IDEALTEK
582	default y
583	bool "IdealTEK URTC1000 device support" if EXPERT
584	depends on TOUCHSCREEN_USB_COMPOSITE
585
586config TOUCHSCREEN_USB_GENERAL_TOUCH
587	default y
588	bool "GeneralTouch Touchscreen device support" if EXPERT
589	depends on TOUCHSCREEN_USB_COMPOSITE
590
591config TOUCHSCREEN_USB_GOTOP
592	default y
593	bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
594	depends on TOUCHSCREEN_USB_COMPOSITE
595
596config TOUCHSCREEN_USB_JASTEC
597	default y
598	bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
599	depends on TOUCHSCREEN_USB_COMPOSITE
600
601config TOUCHSCREEN_USB_E2I
602	default y
603	bool "e2i Touchscreen controller (e.g. from Mimo 740)"
604	depends on TOUCHSCREEN_USB_COMPOSITE
605
606config TOUCHSCREEN_USB_ZYTRONIC
607	default y
608	bool "Zytronic controller" if EXPERT
609	depends on TOUCHSCREEN_USB_COMPOSITE
610
611config TOUCHSCREEN_USB_ETT_TC45USB
612	default y
613	bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
614	depends on TOUCHSCREEN_USB_COMPOSITE
615
616config TOUCHSCREEN_USB_NEXIO
617	default y
618	bool "NEXIO/iNexio device support" if EXPERT
619	depends on TOUCHSCREEN_USB_COMPOSITE
620
621config TOUCHSCREEN_TOUCHIT213
622	tristate "Sahara TouchIT-213 touchscreen"
623	select SERIO
624	help
625	  Say Y here if you have a Sahara TouchIT-213 Tablet PC.
626
627	  If unsure, say N.
628
629	  To compile this driver as a module, choose M here: the
630	  module will be called touchit213.
631
632config TOUCHSCREEN_TSC2007
633	tristate "TSC2007 based touchscreens"
634	depends on I2C
635	help
636	  Say Y here if you have a TSC2007 based touchscreen.
637
638	  If unsure, say N.
639
640	  To compile this driver as a module, choose M here: the
641	  module will be called tsc2007.
642
643config TOUCHSCREEN_W90X900
644	tristate "W90P910 touchscreen driver"
645	depends on HAVE_CLK
646	help
647	  Say Y here if you have a W90P910 based touchscreen.
648
649	  To compile this driver as a module, choose M here: the
650	  module will be called w90p910_ts.
651
652config TOUCHSCREEN_PCAP
653	tristate "Motorola PCAP touchscreen"
654	depends on EZX_PCAP
655	help
656	  Say Y here if you have a Motorola EZX telephone and
657	  want to enable support for the built-in touchscreen.
658
659	  To compile this driver as a module, choose M here: the
660	  module will be called pcap_ts.
661
662config TOUCHSCREEN_ST1232
663	tristate "Sitronix ST1232 touchscreen controllers"
664	depends on I2C
665	help
666	  Say Y here if you want to support Sitronix ST1232
667	  touchscreen controller.
668
669	  If unsure, say N.
670
671	  To compile this driver as a module, choose M here: the
672	  module will be called st1232_ts.
673
674config TOUCHSCREEN_STMPE
675	tristate "STMicroelectronics STMPE touchscreens"
676	depends on MFD_STMPE
677	help
678	  Say Y here if you want support for STMicroelectronics
679	  STMPE touchscreen controllers.
680
681	  To compile this driver as a module, choose M here: the
682	  module will be called stmpe-ts.
683
684config TOUCHSCREEN_TPS6507X
685	tristate "TPS6507x based touchscreens"
686	depends on I2C
687	help
688	  Say Y here if you have a TPS6507x based touchscreen
689	  controller.
690
691	  If unsure, say N.
692
693	  To compile this driver as a module, choose M here: the
694	  module will be called tps6507x_ts.
695
696endif
697