1cd9e8c8efb32883d65c741735a6acac295f7d73
[deliverable/linux.git] / drivers / input / touchscreen / Kconfig
1 #
2 # Touchscreen driver configuration
3 #
4 menuconfig INPUT_TOUCHSCREEN
5 bool "Touchscreens"
6 help
7 Say Y here, and a list of supported touchscreens will be displayed.
8 This option doesn't affect the kernel.
9
10 If unsure, say Y.
11
12 if INPUT_TOUCHSCREEN
13
14 config TOUCHSCREEN_ADS7846
15 tristate "ADS7846/TSC2046 and ADS7843 based touchscreens"
16 depends on SPI_MASTER
17 depends on HWMON = n || HWMON
18 help
19 Say Y here if you have a touchscreen interface using the
20 ADS7846/TSC2046 or ADS7843 controller, and your board-specific
21 setup code includes that in its table of SPI devices.
22
23 If HWMON is selected, and the driver is told the reference voltage
24 on your board, you will also get hwmon interfaces for the voltage
25 (and on ads7846/tsc2046, temperature) sensors of this chip.
26
27 If unsure, say N (but it's safe to say "Y").
28
29 To compile this driver as a module, choose M here: the
30 module will be called ads7846.
31
32 config TOUCHSCREEN_AD7877
33 tristate "AD7877 based touchscreens"
34 depends on SPI_MASTER
35 help
36 Say Y here if you have a touchscreen interface using the
37 AD7877 controller, and your board-specific initialization
38 code includes that in its table of SPI devices.
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 ad7877.
44
45 config TOUCHSCREEN_AD7879_I2C
46 tristate "AD7879 based touchscreens: AD7879-1 I2C Interface"
47 depends on I2C
48 select TOUCHSCREEN_AD7879
49 help
50 Say Y here if you have a touchscreen interface using the
51 AD7879-1/AD7889-1 controller, and your board-specific
52 initialization code includes that in its table of I2C devices.
53
54 If unsure, say N (but it's safe to say "Y").
55
56 To compile this driver as a module, choose M here: the
57 module will be called ad7879.
58
59 config TOUCHSCREEN_AD7879_SPI
60 tristate "AD7879 based touchscreens: AD7879 SPI Interface"
61 depends on SPI_MASTER && TOUCHSCREEN_AD7879_I2C = n
62 select TOUCHSCREEN_AD7879
63 help
64 Say Y here if you have a touchscreen interface using the
65 AD7879/AD7889 controller, and your board-specific initialization
66 code includes that in its table of SPI devices.
67
68 If unsure, say N (but it's safe to say "Y").
69
70 To compile this driver as a module, choose M here: the
71 module will be called ad7879.
72
73 config TOUCHSCREEN_AD7879
74 tristate
75 default n
76
77 config TOUCHSCREEN_BITSY
78 tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
79 depends on SA1100_BITSY
80 select SERIO
81 help
82 Say Y here if you have the h3600 (Bitsy) touchscreen.
83
84 If unsure, say N.
85
86 To compile this driver as a module, choose M here: the
87 module will be called h3600_ts_input.
88
89 config TOUCHSCREEN_CORGI
90 tristate "SharpSL (Corgi and Spitz series) touchscreen driver (DEPRECATED)"
91 depends on PXA_SHARPSL
92 select CORGI_SSP_DEPRECATED
93 default y
94 help
95 Say Y here to enable the driver for the touchscreen on the
96 Sharp SL-C7xx and SL-Cxx00 series of PDAs.
97
98 If unsure, say N.
99
100 To compile this driver as a module, choose M here: the
101 module will be called corgi_ts.
102
103 NOTE: this driver is deprecated, try enable SPI and generic
104 ADS7846-based touchscreen driver.
105
106 config TOUCHSCREEN_DA9034
107 tristate "Touchscreen support for Dialog Semiconductor DA9034"
108 depends on PMIC_DA903X
109 default y
110 help
111 Say Y here to enable the support for the touchscreen found
112 on Dialog Semiconductor DA9034 PMIC.
113
114 config TOUCHSCREEN_DYNAPRO
115 tristate "Dynapro serial touchscreen"
116 select SERIO
117 help
118 Say Y here if you have a Dynapro serial 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 dynapro.
125
126 config TOUCHSCREEN_EETI
127 tristate "EETI touchscreen panel support"
128 depends on I2C
129 help
130 Say Y here to enable support for I2C connected EETI touch panels.
131
132 To compile this driver as a module, choose M here: the
133 module will be called eeti_ts.
134
135 config TOUCHSCREEN_FUJITSU
136 tristate "Fujitsu serial touchscreen"
137 select SERIO
138 help
139 Say Y here if you have the Fujitsu touchscreen (such as one
140 installed in Lifebook P series laptop) connected to your
141 system.
142
143 If unsure, say N.
144
145 To compile this driver as a module, choose M here: the
146 module will be called fujitsu-ts.
147
148 config TOUCHSCREEN_GUNZE
149 tristate "Gunze AHL-51S touchscreen"
150 select SERIO
151 help
152 Say Y here if you have the Gunze AHL-51 touchscreen connected to
153 your system.
154
155 If unsure, say N.
156
157 To compile this driver as a module, choose M here: the
158 module will be called gunze.
159
160 config TOUCHSCREEN_ELO
161 tristate "Elo serial touchscreens"
162 select SERIO
163 help
164 Say Y here if you have an Elo serial touchscreen connected to
165 your system.
166
167 If unsure, say N.
168
169 To compile this driver as a module, choose M here: the
170 module will be called elo.
171
172 config TOUCHSCREEN_WACOM_W8001
173 tristate "Wacom W8001 penabled serial touchscreen"
174 select SERIO
175 help
176 Say Y here if you have an Wacom W8001 penabled serial touchscreen
177 connected to your system.
178
179 If unsure, say N.
180
181 To compile this driver as a module, choose M here: the
182 module will be called wacom_w8001.
183
184 config TOUCHSCREEN_MCS5000
185 tristate "MELFAS MCS-5000 touchscreen"
186 depends on I2C
187 help
188 Say Y here if you have the MELFAS MCS-5000 touchscreen controller
189 chip in your system.
190
191 If unsure, say N.
192
193 To compile this driver as a module, choose M here: the
194 module will be called mcs5000_ts.
195
196 config TOUCHSCREEN_MTOUCH
197 tristate "MicroTouch serial touchscreens"
198 select SERIO
199 help
200 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
201 your system.
202
203 If unsure, say N.
204
205 To compile this driver as a module, choose M here: the
206 module will be called mtouch.
207
208 config TOUCHSCREEN_INEXIO
209 tristate "iNexio serial touchscreens"
210 select SERIO
211 help
212 Say Y here if you have an iNexio serial touchscreen connected to
213 your system.
214
215 If unsure, say N.
216
217 To compile this driver as a module, choose M here: the
218 module will be called inexio.
219
220 config TOUCHSCREEN_MK712
221 tristate "ICS MicroClock MK712 touchscreen"
222 help
223 Say Y here if you have the ICS MicroClock MK712 touchscreen
224 controller chip in your system.
225
226 If unsure, say N.
227
228 To compile this driver as a module, choose M here: the
229 module will be called mk712.
230
231 config TOUCHSCREEN_HP600
232 tristate "HP Jornada 6xx touchscreen"
233 depends on SH_HP6XX && SH_ADC
234 help
235 Say Y here if you have a HP Jornada 620/660/680/690 and want to
236 support the built-in touchscreen.
237
238 To compile this driver as a module, choose M here: the
239 module will be called hp680_ts_input.
240
241 config TOUCHSCREEN_HP7XX
242 tristate "HP Jornada 7xx touchscreen"
243 depends on SA1100_JORNADA720_SSP
244 help
245 Say Y here if you have a HP Jornada 710/720/728 and want
246 to support the built-in touchscreen.
247
248 To compile this driver as a module, choose M here: the
249 module will be called jornada720_ts.
250
251 config TOUCHSCREEN_HTCPEN
252 tristate "HTC Shift X9500 touchscreen"
253 depends on ISA
254 help
255 Say Y here if you have an HTC Shift UMPC also known as HTC X9500
256 Clio / Shangrila and want to support the built-in touchscreen.
257
258 If unsure, say N.
259
260 To compile this driver as a module, choose M here: the
261 module will be called htcpen.
262
263 config TOUCHSCREEN_PENMOUNT
264 tristate "Penmount serial touchscreen"
265 select SERIO
266 help
267 Say Y here if you have a Penmount 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 penmount.
274
275 config TOUCHSCREEN_MIGOR
276 tristate "Renesas MIGO-R touchscreen"
277 depends on SH_MIGOR && I2C
278 help
279 Say Y here to enable MIGO-R touchscreen support.
280
281 If unsure, say N.
282
283 To compile this driver as a module, choose M here: the
284 module will be called migor_ts.
285
286 config TOUCHSCREEN_TOUCHRIGHT
287 tristate "Touchright serial touchscreen"
288 select SERIO
289 help
290 Say Y here if you have a Touchright serial touchscreen connected to
291 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 touchright.
297
298 config TOUCHSCREEN_TOUCHWIN
299 tristate "Touchwin serial touchscreen"
300 select SERIO
301 help
302 Say Y here if you have a Touchwin serial touchscreen connected to
303 your system.
304
305 If unsure, say N.
306
307 To compile this driver as a module, choose M here: the
308 module will be called touchwin.
309
310 config TOUCHSCREEN_ATMEL_TSADCC
311 tristate "Atmel Touchscreen Interface"
312 depends on ARCH_AT91SAM9RL
313 help
314 Say Y here if you have a 4-wire touchscreen connected to the
315 ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
316
317 If unsure, say N.
318
319 To compile this driver as a module, choose M here: the
320 module will be called atmel_tsadcc.
321
322 config TOUCHSCREEN_UCB1400
323 tristate "Philips UCB1400 touchscreen"
324 depends on AC97_BUS
325 depends on UCB1400_CORE
326 help
327 This enables support for the Philips UCB1400 touchscreen interface.
328 The UCB1400 is an AC97 audio codec. The touchscreen interface
329 will be initialized only after the ALSA subsystem has been
330 brought up and the UCB1400 detected. You therefore have to
331 configure ALSA support as well (either built-in or modular,
332 independently of whether this driver is itself built-in or
333 modular) for this driver to work.
334
335 To compile this driver as a module, choose M here: the
336 module will be called ucb1400_ts.
337
338 config TOUCHSCREEN_WM97XX
339 tristate "Support for WM97xx AC97 touchscreen controllers"
340 depends on AC97_BUS
341 help
342 Say Y here if you have a Wolfson Microelectronics WM97xx
343 touchscreen connected to your system. Note that this option
344 only enables core driver, you will also need to select
345 support for appropriate chip below.
346
347 If unsure, say N.
348
349 To compile this driver as a module, choose M here: the
350 module will be called wm97xx-ts.
351
352 config TOUCHSCREEN_WM9705
353 bool "WM9705 Touchscreen interface support"
354 depends on TOUCHSCREEN_WM97XX
355 default y
356 help
357 Say Y here to enable support for the Wolfson Microelectronics
358 WM9705 touchscreen controller.
359
360 config TOUCHSCREEN_WM9712
361 bool "WM9712 Touchscreen interface support"
362 depends on TOUCHSCREEN_WM97XX
363 default y
364 help
365 Say Y here to enable support for the Wolfson Microelectronics
366 WM9712 touchscreen controller.
367
368 config TOUCHSCREEN_WM9713
369 bool "WM9713 Touchscreen interface support"
370 depends on TOUCHSCREEN_WM97XX
371 default y
372 help
373 Say Y here to enable support for the Wolfson Microelectronics
374 WM9713 touchscreen controller.
375
376 config TOUCHSCREEN_WM97XX_ATMEL
377 tristate "WM97xx Atmel accelerated touch"
378 depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
379 help
380 Say Y here for support for streaming mode with WM97xx touchscreens
381 on Atmel AT91 or AVR32 systems with an AC97C module.
382
383 Be aware that this will use channel B in the controller for
384 streaming data, this must not conflict with other AC97C drivers.
385
386 If unsure, say N.
387
388 To compile this driver as a module, choose M here: the module will
389 be called atmel-wm97xx.
390
391 config TOUCHSCREEN_WM97XX_MAINSTONE
392 tristate "WM97xx Mainstone/Palm accelerated touch"
393 depends on TOUCHSCREEN_WM97XX && ARCH_PXA
394 help
395 Say Y here for support for streaming mode with WM97xx touchscreens
396 on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
397
398 If unsure, say N.
399
400 To compile this driver as a module, choose M here: the
401 module will be called mainstone-wm97xx.
402
403 config TOUCHSCREEN_WM97XX_ZYLONITE
404 tristate "Zylonite accelerated touch"
405 depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
406 select TOUCHSCREEN_WM9713
407 help
408 Say Y here for support for streaming mode with the touchscreen
409 on Zylonite systems.
410
411 If unsure, say N.
412
413 To compile this driver as a module, choose M here: the
414 module will be called zylonite-wm97xx.
415
416 config TOUCHSCREEN_USB_COMPOSITE
417 tristate "USB Touchscreen Driver"
418 depends on USB_ARCH_HAS_HCD
419 select USB
420 help
421 USB Touchscreen driver for:
422 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
423 - PanJit TouchSet USB
424 - 3M MicroTouch USB (EX II series)
425 - ITM
426 - some other eTurboTouch
427 - Gunze AHL61
428 - DMC TSC-10/25
429 - IRTOUCHSYSTEMS/UNITOP
430 - IdealTEK URTC1000
431 - GoTop Super_Q2/GogoPen/PenPower tablets
432 - JASTEC USB Touch Controller/DigiTech DTR-02U
433
434 Have a look at <http://linux.chapter7.ch/touchkit/> for
435 a usage description and the required user-space stuff.
436
437 To compile this driver as a module, choose M here: the
438 module will be called usbtouchscreen.
439
440 config TOUCHSCREEN_USB_EGALAX
441 default y
442 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
443 depends on TOUCHSCREEN_USB_COMPOSITE
444
445 config TOUCHSCREEN_USB_PANJIT
446 default y
447 bool "PanJit device support" if EMBEDDED
448 depends on TOUCHSCREEN_USB_COMPOSITE
449
450 config TOUCHSCREEN_USB_3M
451 default y
452 bool "3M/Microtouch EX II series device support" if EMBEDDED
453 depends on TOUCHSCREEN_USB_COMPOSITE
454
455 config TOUCHSCREEN_USB_ITM
456 default y
457 bool "ITM device support" if EMBEDDED
458 depends on TOUCHSCREEN_USB_COMPOSITE
459
460 config TOUCHSCREEN_USB_ETURBO
461 default y
462 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
463 depends on TOUCHSCREEN_USB_COMPOSITE
464
465 config TOUCHSCREEN_USB_GUNZE
466 default y
467 bool "Gunze AHL61 device support" if EMBEDDED
468 depends on TOUCHSCREEN_USB_COMPOSITE
469
470 config TOUCHSCREEN_USB_DMC_TSC10
471 default y
472 bool "DMC TSC-10/25 device support" if EMBEDDED
473 depends on TOUCHSCREEN_USB_COMPOSITE
474
475 config TOUCHSCREEN_USB_IRTOUCH
476 default y
477 bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED
478 depends on TOUCHSCREEN_USB_COMPOSITE
479
480 config TOUCHSCREEN_USB_IDEALTEK
481 default y
482 bool "IdealTEK URTC1000 device support" if EMBEDDED
483 depends on TOUCHSCREEN_USB_COMPOSITE
484
485 config TOUCHSCREEN_USB_GENERAL_TOUCH
486 default y
487 bool "GeneralTouch Touchscreen device support" if EMBEDDED
488 depends on TOUCHSCREEN_USB_COMPOSITE
489
490 config TOUCHSCREEN_USB_GOTOP
491 default y
492 bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED
493 depends on TOUCHSCREEN_USB_COMPOSITE
494
495 config TOUCHSCREEN_USB_JASTEC
496 default y
497 bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EMBEDDED
498 depends on TOUCHSCREEN_USB_COMPOSITE
499
500 config TOUCHSCREEN_USB_E2I
501 default y
502 bool "e2i Touchscreen controller (e.g. from Mimo 740)"
503 depends on TOUCHSCREEN_USB_COMPOSITE
504
505 config TOUCHSCREEN_TOUCHIT213
506 tristate "Sahara TouchIT-213 touchscreen"
507 select SERIO
508 help
509 Say Y here if you have a Sahara TouchIT-213 Tablet PC.
510
511 If unsure, say N.
512
513 To compile this driver as a module, choose M here: the
514 module will be called touchit213.
515
516 config TOUCHSCREEN_TSC2007
517 tristate "TSC2007 based touchscreens"
518 depends on I2C
519 help
520 Say Y here if you have a TSC2007 based touchscreen.
521
522 If unsure, say N.
523
524 To compile this driver as a module, choose M here: the
525 module will be called tsc2007.
526
527 config TOUCHSCREEN_W90X900
528 tristate "W90P910 touchscreen driver"
529 depends on HAVE_CLK
530 help
531 Say Y here if you have a W90P910 based touchscreen.
532
533 To compile this driver as a module, choose M here: the
534 module will be called w90p910_ts.
535
536 config TOUCHSCREEN_PCAP
537 tristate "Motorola PCAP touchscreen"
538 depends on EZX_PCAP
539 help
540 Say Y here if you have a Motorola EZX telephone and
541 want to enable support for the built-in touchscreen.
542
543 To compile this driver as a module, choose M here: the
544 module will be called pcap_ts.
545 endif
This page took 0.041386 seconds and 4 git commands to generate.