]>
Commit | Line | Data |
---|---|---|
1da177e4 | 1 | # |
d05e84e6 | 2 | # Touchscreen driver configuration |
1da177e4 LT |
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 | ||
4200e831 | 14 | config TOUCHSCREEN_PROPERTIES |
b98abe52 | 15 | def_tristate INPUT |
4200e831 | 16 | depends on INPUT |
b98abe52 | 17 | |
866a98ae HZ |
18 | config TOUCHSCREEN_88PM860X |
19 | tristate "Marvell 88PM860x touchscreen" | |
20 | depends on MFD_88PM860X | |
21 | help | |
22 | Say Y here if you have a 88PM860x PMIC and want to enable | |
23 | support for the built-in touchscreen. | |
24 | ||
25 | If unsure, say N. | |
26 | ||
27 | To compile this driver as a module, choose M here: the | |
28 | module will be called 88pm860x-ts. | |
29 | ||
ffa458c1 | 30 | config TOUCHSCREEN_ADS7846 |
06a09124 | 31 | tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens" |
ffa458c1 | 32 | depends on SPI_MASTER |
2c8dc071 | 33 | depends on HWMON = n || HWMON |
ffa458c1 DB |
34 | help |
35 | Say Y here if you have a touchscreen interface using the | |
06a09124 MH |
36 | ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller, |
37 | and your board-specific setup code includes that in its | |
38 | table of SPI devices. | |
ffa458c1 | 39 | |
2c8dc071 DB |
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 | |
06a09124 | 42 | (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip. |
2c8dc071 | 43 | |
ffa458c1 DB |
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 | ||
331b78ed MH |
49 | config TOUCHSCREEN_AD7877 |
50 | tristate "AD7877 based touchscreens" | |
51 | depends on SPI_MASTER | |
52 | help | |
53 | Say Y here if you have a touchscreen interface using the | |
54 | AD7877 controller, and your board-specific initialization | |
55 | code includes that in its table of SPI devices. | |
56 | ||
57 | If unsure, say N (but it's safe to say "Y"). | |
58 | ||
59 | To compile this driver as a module, choose M here: the | |
60 | module will be called ad7877. | |
61 | ||
4397c98a MF |
62 | config TOUCHSCREEN_AD7879 |
63 | tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface" | |
b4be468c | 64 | help |
4397c98a MF |
65 | Say Y here if you want to support a touchscreen interface using |
66 | the AD7879-1/AD7889-1 controller. | |
b4be468c | 67 | |
4397c98a | 68 | You should select a bus connection too. |
b4be468c MH |
69 | |
70 | To compile this driver as a module, choose M here: the | |
71 | module will be called ad7879. | |
72 | ||
4397c98a MF |
73 | config TOUCHSCREEN_AD7879_I2C |
74 | tristate "support I2C bus connection" | |
75 | depends on TOUCHSCREEN_AD7879 && I2C | |
76 | help | |
77 | Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus. | |
78 | ||
79 | To compile this driver as a module, choose M here: the | |
80 | module will be called ad7879-i2c. | |
81 | ||
b4be468c | 82 | config TOUCHSCREEN_AD7879_SPI |
4397c98a MF |
83 | tristate "support SPI bus connection" |
84 | depends on TOUCHSCREEN_AD7879 && SPI_MASTER | |
b4be468c | 85 | help |
4397c98a | 86 | Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus. |
b4be468c MH |
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 | |
4397c98a | 91 | module will be called ad7879-spi. |
b4be468c | 92 | |
dd4cae8b CG |
93 | config TOUCHSCREEN_AR1021_I2C |
94 | tristate "Microchip AR1021 i2c touchscreen" | |
95 | depends on I2C && OF | |
96 | help | |
97 | Say Y here if you have the Microchip AR1021 touchscreen controller | |
98 | chip in your system. | |
99 | ||
100 | If unsure, say N. | |
101 | ||
102 | To compile this driver as a module, choose M here: the | |
103 | module will be called ar1021_i2c. | |
104 | ||
964de521 DT |
105 | config TOUCHSCREEN_ATMEL_MXT |
106 | tristate "Atmel mXT I2C Touchscreen" | |
107 | depends on I2C | |
82c2c0d6 | 108 | select FW_LOADER |
964de521 DT |
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 | ||
5245db49 HS |
118 | config TOUCHSCREEN_AUO_PIXCIR |
119 | tristate "AUO in-cell touchscreen using Pixcir ICs" | |
120 | depends on I2C | |
7d6548ab | 121 | depends on GPIOLIB || COMPILE_TEST |
5245db49 HS |
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 | ||
4780c8df NKG |
131 | config TOUCHSCREEN_BU21013 |
132 | tristate "BU21013 based touch panel controllers" | |
133 | depends on I2C | |
134 | help | |
135 | Say Y here if you have a bu21013 touchscreen connected to | |
136 | your system. | |
137 | ||
138 | If unsure, say N. | |
139 | ||
140 | To compile this driver as a module, choose M here: the | |
141 | module will be called bu21013_ts. | |
142 | ||
a93ad65d HG |
143 | config TOUCHSCREEN_CHIPONE_ICN8318 |
144 | tristate "chipone icn8318 touchscreen controller" | |
7d6548ab | 145 | depends on GPIOLIB || COMPILE_TEST |
a93ad65d HG |
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 | ||
60347c19 SK |
156 | config TOUCHSCREEN_CY8CTMG110 |
157 | tristate "cy8ctmg110 touchscreen" | |
158 | depends on I2C | |
7d6548ab | 159 | depends on GPIOLIB || COMPILE_TEST |
60347c19 SK |
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 | ||
4065d1e7 JMC |
169 | config TOUCHSCREEN_CYTTSP_CORE |
170 | tristate "Cypress TTSP touchscreen" | |
171 | help | |
172 | Say Y here if you have a touchscreen using controller from | |
173 | the Cypress TrueTouch(tm) Standard Product family connected | |
174 | to your system. You will also need to select appropriate | |
175 | bus connection below. | |
176 | ||
177 | If unsure, say N. | |
178 | ||
179 | To compile this driver as a module, choose M here: the | |
180 | module will be called cyttsp_core. | |
181 | ||
182 | config TOUCHSCREEN_CYTTSP_I2C | |
183 | tristate "support I2C bus connection" | |
184 | depends on TOUCHSCREEN_CYTTSP_CORE && I2C | |
185 | help | |
186 | Say Y here if the touchscreen is connected via I2C bus. | |
187 | ||
188 | To compile this driver as a module, choose M here: the | |
189 | module will be called cyttsp_i2c. | |
190 | ||
191 | config TOUCHSCREEN_CYTTSP_SPI | |
192 | tristate "support SPI bus connection" | |
193 | depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER | |
194 | help | |
195 | Say Y here if the touchscreen is connected via SPI bus. | |
196 | ||
197 | To compile this driver as a module, choose M here: the | |
198 | module will be called cyttsp_spi. | |
199 | ||
17fb1563 FY |
200 | config TOUCHSCREEN_CYTTSP4_CORE |
201 | tristate "Cypress TrueTouch Gen4 Touchscreen Driver" | |
202 | help | |
203 | Core driver for Cypress TrueTouch(tm) Standard Product | |
204 | Generation4 touchscreen controllers. | |
205 | ||
206 | Say Y here if you have a Cypress Gen4 touchscreen. | |
207 | ||
208 | If unsure, say N. | |
209 | ||
210 | To compile this driver as a module, choose M here. | |
211 | ||
4f9e8680 FY |
212 | config TOUCHSCREEN_CYTTSP4_I2C |
213 | tristate "support I2C bus connection" | |
214 | depends on TOUCHSCREEN_CYTTSP4_CORE && I2C | |
215 | help | |
216 | Say Y here if the touchscreen is connected via I2C bus. | |
217 | ||
218 | To compile this driver as a module, choose M here: the | |
219 | module will be called cyttsp4_i2c. | |
220 | ||
67bf12ca FY |
221 | config TOUCHSCREEN_CYTTSP4_SPI |
222 | tristate "support SPI bus connection" | |
223 | depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER | |
224 | help | |
225 | Say Y here if the touchscreen is connected via SPI bus. | |
226 | ||
227 | To compile this driver as a module, choose M here: the | |
228 | module will be called cyttsp4_spi. | |
229 | ||
9bcc00b9 EM |
230 | config TOUCHSCREEN_DA9034 |
231 | tristate "Touchscreen support for Dialog Semiconductor DA9034" | |
232 | depends on PMIC_DA903X | |
233 | default y | |
234 | help | |
235 | Say Y here to enable the support for the touchscreen found | |
236 | on Dialog Semiconductor DA9034 PMIC. | |
237 | ||
eead75a2 AJ |
238 | If unsure, say N. |
239 | ||
240 | To compile this driver as a module, choose M here: the | |
241 | module will be called da9034-ts. | |
242 | ||
243 | config TOUCHSCREEN_DA9052 | |
244 | tristate "Dialog DA9052/DA9053 TSI" | |
245 | depends on PMIC_DA9052 | |
246 | help | |
247 | Say Y here to support the touchscreen found on Dialog Semiconductor | |
248 | DA9052-BC and DA9053-AA/Bx PMICs. | |
249 | ||
250 | If unsure, say N. | |
251 | ||
252 | To compile this driver as a module, choose M here: the | |
253 | module will be called da9052_tsi. | |
254 | ||
a5f523bc TG |
255 | config TOUCHSCREEN_DYNAPRO |
256 | tristate "Dynapro serial touchscreen" | |
257 | select SERIO | |
258 | help | |
259 | Say Y here if you have a Dynapro serial touchscreen connected to | |
260 | your system. | |
261 | ||
262 | If unsure, say N. | |
263 | ||
264 | To compile this driver as a module, choose M here: the | |
265 | module will be called dynapro. | |
266 | ||
422dee56 AB |
267 | config TOUCHSCREEN_HAMPSHIRE |
268 | tristate "Hampshire serial touchscreen" | |
269 | select SERIO | |
270 | help | |
271 | Say Y here if you have a Hampshire serial touchscreen connected to | |
272 | your system. | |
273 | ||
274 | If unsure, say N. | |
275 | ||
276 | To compile this driver as a module, choose M here: the | |
277 | module will be called hampshire. | |
278 | ||
10494dce DM |
279 | config TOUCHSCREEN_EETI |
280 | tristate "EETI touchscreen panel support" | |
281 | depends on I2C | |
282 | help | |
283 | Say Y here to enable support for I2C connected EETI touch panels. | |
284 | ||
285 | To compile this driver as a module, choose M here: the | |
286 | module will be called eeti_ts. | |
287 | ||
59bae1db ZJ |
288 | config TOUCHSCREEN_EGALAX |
289 | tristate "EETI eGalax multi-touch panel support" | |
ae495e84 | 290 | depends on I2C && OF |
59bae1db ZJ |
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 | ||
6b0f8f9c BZ |
298 | config 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 | ||
92deea13 NT |
308 | config 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 | ||
85f202d5 DT |
321 | config 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 | ||
ca96ea86 BN |
334 | config TOUCHSCREEN_GOODIX |
335 | tristate "Goodix I2C touchscreen" | |
771d8f1b | 336 | depends on I2C |
ca96ea86 BN |
337 | help |
338 | Say Y here if you have the Goodix touchscreen (such as one | |
339 | installed in Onda v975w tablets) connected to your | |
771d8f1b AM |
340 | system. It also supports 5-finger chip models, which can be |
341 | found on ARM tablets, like Wexler TAB7200 and MSI Primo73. | |
ca96ea86 BN |
342 | |
343 | If unsure, say N. | |
344 | ||
345 | To compile this driver as a module, choose M here: the | |
346 | module will be called goodix. | |
347 | ||
5c6a7a62 OS |
348 | config TOUCHSCREEN_ILI210X |
349 | tristate "Ilitek ILI210X based touchscreen" | |
350 | depends on I2C | |
351 | help | |
352 | Say Y here if you have a ILI210X based touchscreen | |
353 | controller. This driver supports models ILI2102, | |
354 | ILI2102s, ILI2103, ILI2103s and ILI2105. | |
355 | Such kind of chipsets can be found in Amazon Kindle Fire | |
356 | touchscreens. | |
357 | ||
358 | If unsure, say N. | |
359 | ||
360 | To compile this driver as a module, choose M here: the | |
361 | module will be called ili210x. | |
362 | ||
d5ae685f JR |
363 | config TOUCHSCREEN_IPROC |
364 | tristate "IPROC touch panel driver support" | |
365 | depends on ARCH_BCM_IPROC || COMPILE_TEST | |
366 | help | |
367 | Say Y here if you want to add support for the IPROC touch | |
368 | controller to your system. | |
369 | ||
370 | If unsure, say N. | |
371 | ||
372 | To compile this driver as a module, choose M here: the | |
373 | module will be called bcm_iproc_tsc. | |
374 | ||
f5f96b93 | 375 | config TOUCHSCREEN_S3C2410 |
504d36e9 | 376 | tristate "Samsung S3C2410/generic touchscreen input driver" |
b130d5c2 | 377 | depends on ARCH_S3C24XX || SAMSUNG_DEV_TS |
829ab5b5 | 378 | select S3C_ADC |
f5f96b93 AP |
379 | help |
380 | Say Y here if you have the s3c2410 touchscreen. | |
381 | ||
382 | If unsure, say N. | |
383 | ||
384 | To compile this driver as a module, choose M here: the | |
385 | module will be called s3c2410_ts. | |
386 | ||
1da177e4 LT |
387 | config TOUCHSCREEN_GUNZE |
388 | tristate "Gunze AHL-51S touchscreen" | |
389 | select SERIO | |
390 | help | |
391 | Say Y here if you have the Gunze AHL-51 touchscreen connected to | |
392 | your system. | |
393 | ||
394 | If unsure, say N. | |
395 | ||
396 | To compile this driver as a module, choose M here: the | |
397 | module will be called gunze. | |
398 | ||
66aee900 SL |
399 | config TOUCHSCREEN_ELAN |
400 | tristate "Elan eKTH I2C touchscreen" | |
401 | depends on I2C | |
402 | help | |
403 | Say Y here if you have an Elan eKTH I2C touchscreen | |
404 | connected to your system. | |
405 | ||
406 | If unsure, say N. | |
407 | ||
408 | To compile this driver as a module, choose M here: the | |
409 | module will be called elants_i2c. | |
410 | ||
1da177e4 LT |
411 | config TOUCHSCREEN_ELO |
412 | tristate "Elo serial touchscreens" | |
413 | select SERIO | |
414 | help | |
415 | Say Y here if you have an Elo serial touchscreen connected to | |
416 | your system. | |
417 | ||
418 | If unsure, say N. | |
419 | ||
420 | To compile this driver as a module, choose M here: the | |
153ab429 | 421 | module will be called elo. |
1da177e4 | 422 | |
3eb1aa43 JK |
423 | config TOUCHSCREEN_WACOM_W8001 |
424 | tristate "Wacom W8001 penabled serial touchscreen" | |
425 | select SERIO | |
426 | help | |
427 | Say Y here if you have an Wacom W8001 penabled serial touchscreen | |
428 | connected to your system. | |
429 | ||
430 | If unsure, say N. | |
431 | ||
432 | To compile this driver as a module, choose M here: the | |
433 | module will be called wacom_w8001. | |
434 | ||
5a966261 TT |
435 | config TOUCHSCREEN_WACOM_I2C |
436 | tristate "Wacom Tablet support (I2C)" | |
437 | depends on I2C | |
438 | help | |
439 | Say Y here if you want to use the I2C version of the Wacom | |
440 | Pen Tablet. | |
441 | ||
442 | If unsure, say N. | |
443 | ||
444 | To compile this driver as a module, choose M here: the module | |
445 | will be called wacom_i2c. | |
446 | ||
3045a5f5 KW |
447 | config TOUCHSCREEN_LPC32XX |
448 | tristate "LPC32XX touchscreen controller" | |
449 | depends on ARCH_LPC32XX | |
450 | help | |
451 | Say Y here if you have a LPC32XX device and want | |
452 | to support the built-in touchscreen. | |
453 | ||
454 | To compile this driver as a module, choose M here: the | |
455 | module will be called lpc32xx_ts. | |
456 | ||
42033065 ZJ |
457 | config TOUCHSCREEN_MAX11801 |
458 | tristate "MAX11801 based touchscreens" | |
459 | depends on I2C | |
460 | help | |
461 | Say Y here if you have a MAX11801 based touchscreen | |
462 | controller. | |
463 | ||
464 | If unsure, say N. | |
465 | ||
466 | To compile this driver as a module, choose M here: the | |
467 | module will be called max11801_ts. | |
468 | ||
38e783b3 JS |
469 | config TOUCHSCREEN_MCS5000 |
470 | tristate "MELFAS MCS-5000 touchscreen" | |
471 | depends on I2C | |
472 | help | |
473 | Say Y here if you have the MELFAS MCS-5000 touchscreen controller | |
474 | chip in your system. | |
475 | ||
476 | If unsure, say N. | |
477 | ||
478 | To compile this driver as a module, choose M here: the | |
479 | module will be called mcs5000_ts. | |
3eb1aa43 | 480 | |
07b8481d JS |
481 | config TOUCHSCREEN_MMS114 |
482 | tristate "MELFAS MMS114 touchscreen" | |
0244ad00 | 483 | depends on I2C |
07b8481d JS |
484 | help |
485 | Say Y here if you have the MELFAS MMS114 touchscreen controller | |
486 | chip in 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 mms114. | |
492 | ||
1da177e4 LT |
493 | config TOUCHSCREEN_MTOUCH |
494 | tristate "MicroTouch serial touchscreens" | |
495 | select SERIO | |
496 | help | |
497 | Say Y here if you have a MicroTouch (3M) serial touchscreen connected to | |
498 | your system. | |
499 | ||
500 | If unsure, say N. | |
501 | ||
502 | To compile this driver as a module, choose M here: the | |
503 | module will be called mtouch. | |
504 | ||
9a436d52 HC |
505 | config TOUCHSCREEN_IMX6UL_TSC |
506 | tristate "Freescale i.MX6UL touchscreen controller" | |
507 | depends on (OF && GPIOLIB) || COMPILE_TEST | |
508 | help | |
509 | Say Y here if you have a Freescale i.MX6UL, and want to | |
510 | use the internal touchscreen controller. | |
511 | ||
512 | If unsure, say N. | |
513 | ||
514 | To compile this driver as a module, choose M here: the | |
515 | module will be called imx6ul_tsc. | |
516 | ||
3cadd2d9 RL |
517 | config TOUCHSCREEN_INEXIO |
518 | tristate "iNexio serial touchscreens" | |
519 | select SERIO | |
520 | help | |
521 | Say Y here if you have an iNexio 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 inexio. | |
528 | ||
d4f5f937 DT |
529 | config TOUCHSCREEN_INTEL_MID |
530 | tristate "Intel MID platform resistive touchscreen" | |
531 | depends on INTEL_SCU_IPC | |
532 | help | |
533 | Say Y here if you have a Intel MID based touchscreen in | |
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 intel_mid_touch. | |
540 | ||
1da177e4 LT |
541 | config TOUCHSCREEN_MK712 |
542 | tristate "ICS MicroClock MK712 touchscreen" | |
543 | help | |
544 | Say Y here if you have the ICS MicroClock MK712 touchscreen | |
545 | controller chip in your system. | |
546 | ||
547 | If unsure, say N. | |
548 | ||
549 | To compile this driver as a module, choose M here: the | |
550 | module will be called mk712. | |
551 | ||
552 | config TOUCHSCREEN_HP600 | |
4ff891eb | 553 | tristate "HP Jornada 6xx touchscreen" |
0025835c | 554 | depends on SH_HP6XX && SH_ADC |
1da177e4 | 555 | help |
4ff891eb | 556 | Say Y here if you have a HP Jornada 620/660/680/690 and want to |
1da177e4 LT |
557 | support the built-in touchscreen. |
558 | ||
1da177e4 LT |
559 | To compile this driver as a module, choose M here: the |
560 | module will be called hp680_ts_input. | |
561 | ||
5637f02a | 562 | config TOUCHSCREEN_HP7XX |
4ff891eb | 563 | tristate "HP Jornada 7xx touchscreen" |
5637f02a KE |
564 | depends on SA1100_JORNADA720_SSP |
565 | help | |
566 | Say Y here if you have a HP Jornada 710/720/728 and want | |
567 | to support the built-in touchscreen. | |
568 | ||
569 | To compile this driver as a module, choose M here: the | |
570 | module will be called jornada720_ts. | |
571 | ||
3ea7e551 DA |
572 | config TOUCHSCREEN_IPAQ_MICRO |
573 | tristate "HP iPAQ Atmel Micro ASIC touchscreen" | |
574 | depends on MFD_IPAQ_MICRO | |
575 | help | |
576 | Say Y here to enable support for the touchscreen attached to | |
577 | the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700 | |
578 | ||
579 | If unsure, say N. | |
580 | ||
581 | To compile this driver as a module, choose M here: the | |
582 | module will be called ipaq-micro-ts. | |
583 | ||
5a18c343 POF |
584 | config TOUCHSCREEN_HTCPEN |
585 | tristate "HTC Shift X9500 touchscreen" | |
586 | depends on ISA | |
587 | help | |
588 | Say Y here if you have an HTC Shift UMPC also known as HTC X9500 | |
589 | Clio / Shangrila and want to support the built-in touchscreen. | |
590 | ||
591 | If unsure, say N. | |
592 | ||
593 | To compile this driver as a module, choose M here: the | |
594 | module will be called htcpen. | |
595 | ||
ee479999 RK |
596 | config TOUCHSCREEN_PENMOUNT |
597 | tristate "Penmount serial touchscreen" | |
598 | select SERIO | |
599 | help | |
600 | Say Y here if you have a Penmount serial touchscreen connected to | |
601 | your system. | |
602 | ||
603 | If unsure, say N. | |
604 | ||
605 | To compile this driver as a module, choose M here: the | |
606 | module will be called penmount. | |
607 | ||
43c4d13e SB |
608 | config TOUCHSCREEN_EDT_FT5X06 |
609 | tristate "EDT FocalTech FT5x06 I2C Touchscreen support" | |
610 | depends on I2C | |
611 | help | |
612 | Say Y here if you have an EDT "Polytouch" touchscreen based | |
613 | on the FocalTech FT5x06 family of controllers connected to | |
614 | your system. | |
615 | ||
616 | If unsure, say N. | |
617 | ||
618 | To compile this driver as a module, choose M here: the | |
619 | module will be called edt-ft5x06. | |
620 | ||
885c316d MD |
621 | config TOUCHSCREEN_MIGOR |
622 | tristate "Renesas MIGO-R touchscreen" | |
623 | depends on SH_MIGOR && I2C | |
624 | help | |
625 | Say Y here to enable MIGO-R touchscreen support. | |
626 | ||
627 | If unsure, say N. | |
628 | ||
629 | To compile this driver as a module, choose M here: the | |
630 | module will be called migor_ts. | |
631 | ||
4003dff4 RK |
632 | config TOUCHSCREEN_TOUCHRIGHT |
633 | tristate "Touchright serial touchscreen" | |
634 | select SERIO | |
635 | help | |
636 | Say Y here if you have a Touchright serial touchscreen connected to | |
637 | your system. | |
638 | ||
639 | If unsure, say N. | |
640 | ||
641 | To compile this driver as a module, choose M here: the | |
642 | module will be called touchright. | |
643 | ||
11ea3173 RK |
644 | config TOUCHSCREEN_TOUCHWIN |
645 | tristate "Touchwin serial touchscreen" | |
646 | select SERIO | |
647 | help | |
648 | Say Y here if you have a Touchwin 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 touchwin. | |
655 | ||
55c04de5 | 656 | config TOUCHSCREEN_TI_AM335X_TSC |
1b8be32e | 657 | tristate "TI Touchscreen Interface" |
2b99bafa | 658 | depends on MFD_TI_AM335X_TSCADC |
1b8be32e RP |
659 | help |
660 | Say Y here if you have 4/5/8 wire touchscreen controller | |
661 | to be connected to the ADC controller on your TI AM335x SoC. | |
662 | ||
663 | If unsure, say N. | |
664 | ||
665 | To compile this driver as a module, choose M here: the | |
55c04de5 | 666 | module will be called ti_am335x_tsc. |
1b8be32e | 667 | |
f40219bf NP |
668 | config TOUCHSCREEN_UCB1400 |
669 | tristate "Philips UCB1400 touchscreen" | |
64c12e9b | 670 | depends on AC97_BUS |
d9105c2b | 671 | depends on UCB1400_CORE |
f40219bf NP |
672 | help |
673 | This enables support for the Philips UCB1400 touchscreen interface. | |
674 | The UCB1400 is an AC97 audio codec. The touchscreen interface | |
675 | will be initialized only after the ALSA subsystem has been | |
676 | brought up and the UCB1400 detected. You therefore have to | |
677 | configure ALSA support as well (either built-in or modular, | |
678 | independently of whether this driver is itself built-in or | |
679 | modular) for this driver to work. | |
680 | ||
681 | To compile this driver as a module, choose M here: the | |
682 | module will be called ucb1400_ts. | |
683 | ||
36a281e2 JB |
684 | config TOUCHSCREEN_PIXCIR |
685 | tristate "PIXCIR I2C touchscreens" | |
686 | depends on I2C | |
687 | help | |
688 | Say Y here if you have a pixcir i2c 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 pixcir_i2c_ts. | |
695 | ||
3e30c11c HC |
696 | config TOUCHSCREEN_WDT87XX_I2C |
697 | tristate "Weida HiTech I2C touchscreen" | |
698 | depends on I2C | |
699 | help | |
700 | Say Y here if you have a Weida WDT87XX I2C touchscreen | |
701 | connected to your system. | |
702 | ||
703 | If unsure, say N. | |
704 | ||
705 | To compile this driver as a module, choose M here: the | |
706 | module will be called wdt87xx_i2c. | |
707 | ||
00cfa730 MB |
708 | config TOUCHSCREEN_WM831X |
709 | tristate "Support for WM831x touchscreen controllers" | |
710 | depends on MFD_WM831X | |
711 | help | |
712 | This enables support for the touchscreen controller on the WM831x | |
713 | series of PMICs. | |
714 | ||
715 | To compile this driver as a module, choose M here: the | |
716 | module will be called wm831x-ts. | |
717 | ||
febf1dff MB |
718 | config TOUCHSCREEN_WM97XX |
719 | tristate "Support for WM97xx AC97 touchscreen controllers" | |
720 | depends on AC97_BUS | |
721 | help | |
722 | Say Y here if you have a Wolfson Microelectronics WM97xx | |
723 | touchscreen connected to your system. Note that this option | |
724 | only enables core driver, you will also need to select | |
725 | support for appropriate chip below. | |
726 | ||
727 | If unsure, say N. | |
728 | ||
729 | To compile this driver as a module, choose M here: the | |
730 | module will be called wm97xx-ts. | |
731 | ||
9448cefc MB |
732 | config TOUCHSCREEN_WM9705 |
733 | bool "WM9705 Touchscreen interface support" | |
734 | depends on TOUCHSCREEN_WM97XX | |
558a171d | 735 | default y |
9448cefc | 736 | help |
558a171d MB |
737 | Say Y here to enable support for the Wolfson Microelectronics |
738 | WM9705 touchscreen controller. | |
9448cefc | 739 | |
de22b9ef MB |
740 | config TOUCHSCREEN_WM9712 |
741 | bool "WM9712 Touchscreen interface support" | |
742 | depends on TOUCHSCREEN_WM97XX | |
558a171d | 743 | default y |
de22b9ef | 744 | help |
558a171d MB |
745 | Say Y here to enable support for the Wolfson Microelectronics |
746 | WM9712 touchscreen controller. | |
de22b9ef | 747 | |
dca98e91 MB |
748 | config TOUCHSCREEN_WM9713 |
749 | bool "WM9713 Touchscreen interface support" | |
750 | depends on TOUCHSCREEN_WM97XX | |
558a171d | 751 | default y |
dca98e91 | 752 | help |
558a171d MB |
753 | Say Y here to enable support for the Wolfson Microelectronics |
754 | WM9713 touchscreen controller. | |
dca98e91 | 755 | |
864fe73c HCE |
756 | config TOUCHSCREEN_WM97XX_ATMEL |
757 | tristate "WM97xx Atmel accelerated touch" | |
ba77341c | 758 | depends on TOUCHSCREEN_WM97XX && AVR32 |
864fe73c HCE |
759 | help |
760 | Say Y here for support for streaming mode with WM97xx touchscreens | |
761 | on Atmel AT91 or AVR32 systems with an AC97C module. | |
762 | ||
763 | Be aware that this will use channel B in the controller for | |
764 | streaming data, this must not conflict with other AC97C drivers. | |
765 | ||
766 | If unsure, say N. | |
767 | ||
768 | To compile this driver as a module, choose M here: the module will | |
769 | be called atmel-wm97xx. | |
770 | ||
4db8a5f2 | 771 | config TOUCHSCREEN_WM97XX_MAINSTONE |
b833306f | 772 | tristate "WM97xx Mainstone/Palm accelerated touch" |
4db8a5f2 MB |
773 | depends on TOUCHSCREEN_WM97XX && ARCH_PXA |
774 | help | |
775 | Say Y here for support for streaming mode with WM97xx touchscreens | |
b833306f | 776 | on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. |
4db8a5f2 MB |
777 | |
778 | If unsure, say N. | |
779 | ||
780 | To compile this driver as a module, choose M here: the | |
781 | module will be called mainstone-wm97xx. | |
782 | ||
22e39d34 MB |
783 | config TOUCHSCREEN_WM97XX_ZYLONITE |
784 | tristate "Zylonite accelerated touch" | |
785 | depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE | |
786 | select TOUCHSCREEN_WM9713 | |
787 | help | |
788 | Say Y here for support for streaming mode with the touchscreen | |
789 | on Zylonite systems. | |
790 | ||
791 | If unsure, say N. | |
792 | ||
793 | To compile this driver as a module, choose M here: the | |
794 | module will be called zylonite-wm97xx. | |
795 | ||
d05e84e6 DT |
796 | config TOUCHSCREEN_USB_COMPOSITE |
797 | tristate "USB Touchscreen Driver" | |
7a86edef | 798 | depends on USB_ARCH_HAS_HCD |
d05e84e6 DT |
799 | select USB |
800 | help | |
801 | USB Touchscreen driver for: | |
802 | - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) | |
803 | - PanJit TouchSet USB | |
804 | - 3M MicroTouch USB (EX II series) | |
805 | - ITM | |
806 | - some other eTurboTouch | |
807 | - Gunze AHL61 | |
808 | - DMC TSC-10/25 | |
df561fcd | 809 | - IRTOUCHSYSTEMS/UNITOP |
a14a8401 | 810 | - IdealTEK URTC1000 |
14e40206 | 811 | - GoTop Super_Q2/GogoPen/PenPower tablets |
f7370699 | 812 | - JASTEC USB Touch Controller/DigiTech DTR-02U |
2330ed18 | 813 | - Zytronic controllers |
d2cc817a | 814 | - Elo TouchSystems 2700 IntelliTouch |
aa87512f | 815 | - EasyTouch USB Touch Controller from Data Modul |
df052676 | 816 | - e2i (Mimo monitors) |
d05e84e6 DT |
817 | |
818 | Have a look at <http://linux.chapter7.ch/touchkit/> for | |
819 | a usage description and the required user-space stuff. | |
820 | ||
821 | To compile this driver as a module, choose M here: the | |
822 | module will be called usbtouchscreen. | |
823 | ||
d201fd5d SH |
824 | config TOUCHSCREEN_MC13783 |
825 | tristate "Freescale MC13783 touchscreen input driver" | |
e5a3da21 | 826 | depends on MFD_MC13XXX |
d201fd5d SH |
827 | help |
828 | Say Y here if you have an Freescale MC13783 PMIC on your | |
829 | board and want to use its touchscreen | |
830 | ||
831 | If unsure, say N. | |
832 | ||
833 | To compile this driver as a module, choose M here: the | |
834 | module will be called mc13783_ts. | |
835 | ||
d05e84e6 DT |
836 | config TOUCHSCREEN_USB_EGALAX |
837 | default y | |
6a108a14 | 838 | bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT |
d05e84e6 DT |
839 | depends on TOUCHSCREEN_USB_COMPOSITE |
840 | ||
841 | config TOUCHSCREEN_USB_PANJIT | |
842 | default y | |
6a108a14 | 843 | bool "PanJit device support" if EXPERT |
d05e84e6 DT |
844 | depends on TOUCHSCREEN_USB_COMPOSITE |
845 | ||
846 | config TOUCHSCREEN_USB_3M | |
847 | default y | |
6a108a14 | 848 | bool "3M/Microtouch EX II series device support" if EXPERT |
d05e84e6 DT |
849 | depends on TOUCHSCREEN_USB_COMPOSITE |
850 | ||
851 | config TOUCHSCREEN_USB_ITM | |
852 | default y | |
6a108a14 | 853 | bool "ITM device support" if EXPERT |
d05e84e6 DT |
854 | depends on TOUCHSCREEN_USB_COMPOSITE |
855 | ||
856 | config TOUCHSCREEN_USB_ETURBO | |
857 | default y | |
6a108a14 | 858 | bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT |
d05e84e6 DT |
859 | depends on TOUCHSCREEN_USB_COMPOSITE |
860 | ||
861 | config TOUCHSCREEN_USB_GUNZE | |
862 | default y | |
6a108a14 | 863 | bool "Gunze AHL61 device support" if EXPERT |
d05e84e6 DT |
864 | depends on TOUCHSCREEN_USB_COMPOSITE |
865 | ||
866 | config TOUCHSCREEN_USB_DMC_TSC10 | |
867 | default y | |
6a108a14 | 868 | bool "DMC TSC-10/25 device support" if EXPERT |
d05e84e6 DT |
869 | depends on TOUCHSCREEN_USB_COMPOSITE |
870 | ||
df561fcd OZ |
871 | config TOUCHSCREEN_USB_IRTOUCH |
872 | default y | |
6a108a14 | 873 | bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT |
df561fcd OZ |
874 | depends on TOUCHSCREEN_USB_COMPOSITE |
875 | ||
a14a8401 OZ |
876 | config TOUCHSCREEN_USB_IDEALTEK |
877 | default y | |
6a108a14 | 878 | bool "IdealTEK URTC1000 device support" if EXPERT |
a14a8401 OZ |
879 | depends on TOUCHSCREEN_USB_COMPOSITE |
880 | ||
9d5657db IF |
881 | config TOUCHSCREEN_USB_GENERAL_TOUCH |
882 | default y | |
6a108a14 | 883 | bool "GeneralTouch Touchscreen device support" if EXPERT |
9d5657db IF |
884 | depends on TOUCHSCREEN_USB_COMPOSITE |
885 | ||
14e40206 JJ |
886 | config TOUCHSCREEN_USB_GOTOP |
887 | default y | |
6a108a14 | 888 | bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT |
14e40206 JJ |
889 | depends on TOUCHSCREEN_USB_COMPOSITE |
890 | ||
f7370699 JP |
891 | config TOUCHSCREEN_USB_JASTEC |
892 | default y | |
6a108a14 | 893 | bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT |
f7370699 JP |
894 | depends on TOUCHSCREEN_USB_COMPOSITE |
895 | ||
d2cc817a MG |
896 | config TOUCHSCREEN_USB_ELO |
897 | default y | |
898 | bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT | |
899 | depends on TOUCHSCREEN_USB_COMPOSITE | |
900 | ||
9e3b2583 FE |
901 | config TOUCHSCREEN_USB_E2I |
902 | default y | |
df052676 | 903 | bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT |
9e3b2583 FE |
904 | depends on TOUCHSCREEN_USB_COMPOSITE |
905 | ||
2330ed18 DS |
906 | config TOUCHSCREEN_USB_ZYTRONIC |
907 | default y | |
6a108a14 | 908 | bool "Zytronic controller" if EXPERT |
2330ed18 DS |
909 | depends on TOUCHSCREEN_USB_COMPOSITE |
910 | ||
38771bb4 | 911 | config TOUCHSCREEN_USB_ETT_TC45USB |
dbe1420b | 912 | default y |
6a108a14 | 913 | bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT |
dbe1420b PŠ |
914 | depends on TOUCHSCREEN_USB_COMPOSITE |
915 | ||
5197424c OZ |
916 | config TOUCHSCREEN_USB_NEXIO |
917 | default y | |
6a108a14 | 918 | bool "NEXIO/iNexio device support" if EXPERT |
5197424c OZ |
919 | depends on TOUCHSCREEN_USB_COMPOSITE |
920 | ||
aa87512f AV |
921 | config TOUCHSCREEN_USB_EASYTOUCH |
922 | default y | |
923 | bool "EasyTouch USB Touch controller device support" if EMBEDDED | |
924 | depends on TOUCHSCREEN_USB_COMPOSITE | |
925 | help | |
41baf636 | 926 | Say Y here if you have an EasyTouch USB Touch controller. |
aa87512f AV |
927 | If unsure, say N. |
928 | ||
73422392 CN |
929 | config TOUCHSCREEN_TOUCHIT213 |
930 | tristate "Sahara TouchIT-213 touchscreen" | |
931 | select SERIO | |
932 | help | |
933 | Say Y here if you have a Sahara TouchIT-213 Tablet PC. | |
934 | ||
935 | If unsure, say N. | |
936 | ||
937 | To compile this driver as a module, choose M here: the | |
938 | module will be called touchit213. | |
939 | ||
f01536e3 SAS |
940 | config TOUCHSCREEN_TSC_SERIO |
941 | tristate "TSC-10/25/40 serial touchscreen support" | |
942 | select SERIO | |
943 | help | |
944 | Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected | |
945 | to your system. | |
946 | ||
947 | If unsure, say N. | |
948 | ||
949 | To compile this driver as a module, choose M here: the | |
950 | module will be called tsc40. | |
951 | ||
6ac24381 MW |
952 | config TOUCHSCREEN_TSC200X_CORE |
953 | tristate | |
954 | ||
a748941c MW |
955 | config TOUCHSCREEN_TSC2004 |
956 | tristate "TSC2004 based touchscreens" | |
957 | depends on I2C | |
958 | select REGMAP_I2C | |
959 | select TOUCHSCREEN_TSC200X_CORE | |
960 | help | |
961 | Say Y here if you have a TSC2004 based touchscreen. | |
962 | ||
963 | If unsure, say N. | |
964 | ||
965 | To compile this driver as a module, choose M here: the | |
966 | module will be called tsc2004. | |
967 | ||
37bd4469 | 968 | config TOUCHSCREEN_TSC2005 |
f00d1f8f SR |
969 | tristate "TSC2005 based touchscreens" |
970 | depends on SPI_MASTER | |
273cf48a | 971 | select REGMAP_SPI |
6ac24381 | 972 | select TOUCHSCREEN_TSC200X_CORE |
f00d1f8f SR |
973 | help |
974 | Say Y here if you have a TSC2005 based touchscreen. | |
37bd4469 LL |
975 | |
976 | If unsure, say N. | |
977 | ||
978 | To compile this driver as a module, choose M here: the | |
979 | module will be called tsc2005. | |
980 | ||
50b6f1f4 KL |
981 | config TOUCHSCREEN_TSC2007 |
982 | tristate "TSC2007 based touchscreens" | |
983 | depends on I2C | |
984 | help | |
985 | Say Y here if you have a TSC2007 based touchscreen. | |
986 | ||
987 | If unsure, say N. | |
988 | ||
989 | To compile this driver as a module, choose M here: the | |
990 | module will be called tsc2007. | |
991 | ||
7e3f7375 WZ |
992 | config TOUCHSCREEN_W90X900 |
993 | tristate "W90P910 touchscreen driver" | |
e5e0937c | 994 | depends on ARCH_W90X900 |
7e3f7375 WZ |
995 | help |
996 | Say Y here if you have a W90P910 based touchscreen. | |
997 | ||
998 | To compile this driver as a module, choose M here: the | |
999 | module will be called w90p910_ts. | |
1000 | ||
0387e107 DR |
1001 | config TOUCHSCREEN_PCAP |
1002 | tristate "Motorola PCAP touchscreen" | |
1003 | depends on EZX_PCAP | |
1004 | help | |
1005 | Say Y here if you have a Motorola EZX telephone and | |
1006 | want to enable support for the built-in touchscreen. | |
1007 | ||
1008 | To compile this driver as a module, choose M here: the | |
1009 | module will be called pcap_ts. | |
75259966 | 1010 | |
56a8bd6d TS |
1011 | config TOUCHSCREEN_ST1232 |
1012 | tristate "Sitronix ST1232 touchscreen controllers" | |
75259966 TF |
1013 | depends on I2C |
1014 | help | |
56a8bd6d TS |
1015 | Say Y here if you want to support Sitronix ST1232 |
1016 | touchscreen controller. | |
75259966 TF |
1017 | |
1018 | If unsure, say N. | |
1019 | ||
1020 | To compile this driver as a module, choose M here: the | |
56a8bd6d | 1021 | module will be called st1232_ts. |
75259966 | 1022 | |
f94add3b LF |
1023 | config TOUCHSCREEN_STMPE |
1024 | tristate "STMicroelectronics STMPE touchscreens" | |
1025 | depends on MFD_STMPE | |
e4b88e19 | 1026 | depends on (OF || COMPILE_TEST) |
f94add3b LF |
1027 | help |
1028 | Say Y here if you want support for STMicroelectronics | |
1029 | STMPE touchscreen controllers. | |
1030 | ||
1031 | To compile this driver as a module, choose M here: the | |
1032 | module will be called stmpe-ts. | |
1033 | ||
6decea7c HG |
1034 | config TOUCHSCREEN_SUN4I |
1035 | tristate "Allwinner sun4i resistive touchscreen controller support" | |
1036 | depends on ARCH_SUNXI || COMPILE_TEST | |
f09f98d3 | 1037 | depends on HWMON |
4a6155a4 | 1038 | depends on THERMAL || !THERMAL_OF |
6decea7c HG |
1039 | help |
1040 | This selects support for the resistive touchscreen controller | |
1041 | found on Allwinner sunxi SoCs. | |
1042 | ||
1043 | To compile this driver as a module, choose M here: the | |
1044 | module will be called sun4i-ts. | |
1045 | ||
bdb5c57f FE |
1046 | config TOUCHSCREEN_SUR40 |
1047 | tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen" | |
ef403bca | 1048 | depends on USB && MEDIA_USB_SUPPORT && HAS_DMA |
c8a1978e | 1049 | depends on VIDEO_V4L2 |
bdb5c57f | 1050 | select INPUT_POLLDEV |
e831cd25 | 1051 | select VIDEOBUF2_DMA_SG |
bdb5c57f FE |
1052 | help |
1053 | Say Y here if you want support for the Samsung SUR40 touchscreen | |
1054 | (also known as Microsoft Surface 2.0 or Microsoft PixelSense). | |
1055 | ||
1056 | To compile this driver as a module, choose M here: the | |
1057 | module will be called sur40. | |
1058 | ||
902cb3af SS |
1059 | config TOUCHSCREEN_SX8654 |
1060 | tristate "Semtech SX8654 touchscreen" | |
1061 | depends on I2C | |
1062 | help | |
1063 | Say Y here if you have a Semtech SX8654 touchscreen controller. | |
1064 | ||
1065 | If unsure, say N | |
1066 | ||
1067 | To compile this driver as a module, choose M here: the | |
1068 | module will be called sx8654. | |
1069 | ||
56a8bd6d TS |
1070 | config TOUCHSCREEN_TPS6507X |
1071 | tristate "TPS6507x based touchscreens" | |
1072 | depends on I2C | |
9ff9f6da | 1073 | select INPUT_POLLDEV |
56a8bd6d TS |
1074 | help |
1075 | Say Y here if you have a TPS6507x based touchscreen | |
1076 | controller. | |
1077 | ||
1078 | If unsure, say N. | |
1079 | ||
1080 | To compile this driver as a module, choose M here: the | |
1081 | module will be called tps6507x_ts. | |
1082 | ||
c6d81bd7 HS |
1083 | config TOUCHSCREEN_ZFORCE |
1084 | tristate "Neonode zForce infrared touchscreens" | |
1085 | depends on I2C | |
7d6548ab | 1086 | depends on GPIOLIB || COMPILE_TEST |
c6d81bd7 HS |
1087 | help |
1088 | Say Y here if you have a touchscreen using the zforce | |
1089 | infraread technology from Neonode. | |
1090 | ||
1091 | If unsure, say N. | |
1092 | ||
1093 | To compile this driver as a module, choose M here: the | |
1094 | module will be called zforce_ts. | |
1095 | ||
48ead50c SM |
1096 | config TOUCHSCREEN_COLIBRI_VF50 |
1097 | tristate "Toradex Colibri on board touchscreen driver" | |
1098 | depends on GPIOLIB && IIO && VF610_ADC | |
1099 | help | |
1100 | Say Y here if you have a Colibri VF50 and plan to use | |
1101 | the on-board provided 4-wire touchscreen driver. | |
1102 | ||
1103 | If unsure, say N. | |
1104 | ||
1105 | To compile this driver as a module, choose M here: the | |
1106 | module will be called colibri_vf50_ts. | |
1107 | ||
c7efd123 YY |
1108 | config TOUCHSCREEN_ROHM_BU21023 |
1109 | tristate "ROHM BU21023/24 Dual touch support resistive touchscreens" | |
1110 | depends on I2C | |
1111 | help | |
1112 | Say Y here if you have a touchscreen using ROHM BU21023/24. | |
1113 | ||
1114 | If unsure, say N. | |
1115 | ||
1116 | To compile this driver as a module, choose M here: the | |
1117 | module will be called bu21023_ts. | |
1118 | ||
1da177e4 | 1119 | endif |