]>
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 |
1261d013 | 337 | depends on GPIOLIB || COMPILE_TEST |
ca96ea86 BN |
338 | help |
339 | Say Y here if you have the Goodix touchscreen (such as one | |
340 | installed in Onda v975w tablets) connected to your | |
771d8f1b AM |
341 | system. It also supports 5-finger chip models, which can be |
342 | found on ARM tablets, like Wexler TAB7200 and MSI Primo73. | |
ca96ea86 BN |
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 | ||
5c6a7a62 OS |
349 | config 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 | ||
d5ae685f JR |
364 | config 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 | ||
f5f96b93 | 376 | config TOUCHSCREEN_S3C2410 |
504d36e9 | 377 | tristate "Samsung S3C2410/generic touchscreen input driver" |
b130d5c2 | 378 | depends on ARCH_S3C24XX || SAMSUNG_DEV_TS |
94eb81ad | 379 | depends on S3C_ADC |
f5f96b93 AP |
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 | ||
1da177e4 LT |
388 | config 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 | ||
66aee900 SL |
400 | config 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 | ||
1da177e4 LT |
412 | config 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 | |
153ab429 | 422 | module will be called elo. |
1da177e4 | 423 | |
3eb1aa43 JK |
424 | config 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 | ||
5a966261 TT |
436 | config 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 | ||
3045a5f5 KW |
448 | config 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 | ||
42033065 ZJ |
458 | config 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 | ||
38e783b3 JS |
470 | config 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. | |
3eb1aa43 | 481 | |
07b8481d JS |
482 | config TOUCHSCREEN_MMS114 |
483 | tristate "MELFAS MMS114 touchscreen" | |
0244ad00 | 484 | depends on I2C |
07b8481d JS |
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 | ||
6ccb1d8f SJ |
494 | config 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 | ||
1da177e4 LT |
505 | config 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 | ||
9a436d52 HC |
517 | config 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 | ||
3cadd2d9 RL |
529 | config 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 | ||
d4f5f937 DT |
541 | config 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 | ||
1da177e4 LT |
553 | config 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 | ||
564 | config TOUCHSCREEN_HP600 | |
4ff891eb | 565 | tristate "HP Jornada 6xx touchscreen" |
0025835c | 566 | depends on SH_HP6XX && SH_ADC |
1da177e4 | 567 | help |
4ff891eb | 568 | Say Y here if you have a HP Jornada 620/660/680/690 and want to |
1da177e4 LT |
569 | support the built-in touchscreen. |
570 | ||
1da177e4 LT |
571 | To compile this driver as a module, choose M here: the |
572 | module will be called hp680_ts_input. | |
573 | ||
5637f02a | 574 | config TOUCHSCREEN_HP7XX |
4ff891eb | 575 | tristate "HP Jornada 7xx touchscreen" |
5637f02a KE |
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 | ||
3ea7e551 DA |
584 | config 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 | ||
5a18c343 POF |
596 | config 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 | ||
ee479999 RK |
608 | config 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 | ||
43c4d13e SB |
620 | config 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 | ||
885c316d MD |
633 | config 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 | ||
4003dff4 RK |
644 | config 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 | ||
11ea3173 RK |
656 | config 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 | ||
55c04de5 | 668 | config TOUCHSCREEN_TI_AM335X_TSC |
1b8be32e | 669 | tristate "TI Touchscreen Interface" |
2b99bafa | 670 | depends on MFD_TI_AM335X_TSCADC |
1b8be32e RP |
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 | |
55c04de5 | 678 | module will be called ti_am335x_tsc. |
1b8be32e | 679 | |
f40219bf NP |
680 | config TOUCHSCREEN_UCB1400 |
681 | tristate "Philips UCB1400 touchscreen" | |
64c12e9b | 682 | depends on AC97_BUS |
d9105c2b | 683 | depends on UCB1400_CORE |
f40219bf NP |
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 | ||
36a281e2 JB |
696 | config 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 | ||
3e30c11c HC |
708 | config 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 | ||
00cfa730 MB |
720 | config 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 | ||
febf1dff MB |
730 | config 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 | ||
9448cefc MB |
744 | config TOUCHSCREEN_WM9705 |
745 | bool "WM9705 Touchscreen interface support" | |
746 | depends on TOUCHSCREEN_WM97XX | |
558a171d | 747 | default y |
9448cefc | 748 | help |
558a171d MB |
749 | Say Y here to enable support for the Wolfson Microelectronics |
750 | WM9705 touchscreen controller. | |
9448cefc | 751 | |
de22b9ef MB |
752 | config TOUCHSCREEN_WM9712 |
753 | bool "WM9712 Touchscreen interface support" | |
754 | depends on TOUCHSCREEN_WM97XX | |
558a171d | 755 | default y |
de22b9ef | 756 | help |
558a171d MB |
757 | Say Y here to enable support for the Wolfson Microelectronics |
758 | WM9712 touchscreen controller. | |
de22b9ef | 759 | |
dca98e91 MB |
760 | config TOUCHSCREEN_WM9713 |
761 | bool "WM9713 Touchscreen interface support" | |
762 | depends on TOUCHSCREEN_WM97XX | |
558a171d | 763 | default y |
dca98e91 | 764 | help |
558a171d MB |
765 | Say Y here to enable support for the Wolfson Microelectronics |
766 | WM9713 touchscreen controller. | |
dca98e91 | 767 | |
864fe73c HCE |
768 | config TOUCHSCREEN_WM97XX_ATMEL |
769 | tristate "WM97xx Atmel accelerated touch" | |
ba77341c | 770 | depends on TOUCHSCREEN_WM97XX && AVR32 |
864fe73c HCE |
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 | ||
4db8a5f2 | 783 | config TOUCHSCREEN_WM97XX_MAINSTONE |
b833306f | 784 | tristate "WM97xx Mainstone/Palm accelerated touch" |
4db8a5f2 MB |
785 | depends on TOUCHSCREEN_WM97XX && ARCH_PXA |
786 | help | |
787 | Say Y here for support for streaming mode with WM97xx touchscreens | |
b833306f | 788 | on Mainstone, Palm Tungsten T5, TX and LifeDrive systems. |
4db8a5f2 MB |
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 | ||
22e39d34 MB |
795 | config 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 | ||
d05e84e6 DT |
808 | config TOUCHSCREEN_USB_COMPOSITE |
809 | tristate "USB Touchscreen Driver" | |
7a86edef | 810 | depends on USB_ARCH_HAS_HCD |
d05e84e6 DT |
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 | |
df561fcd | 821 | - IRTOUCHSYSTEMS/UNITOP |
a14a8401 | 822 | - IdealTEK URTC1000 |
14e40206 | 823 | - GoTop Super_Q2/GogoPen/PenPower tablets |
f7370699 | 824 | - JASTEC USB Touch Controller/DigiTech DTR-02U |
2330ed18 | 825 | - Zytronic controllers |
d2cc817a | 826 | - Elo TouchSystems 2700 IntelliTouch |
aa87512f | 827 | - EasyTouch USB Touch Controller from Data Modul |
df052676 | 828 | - e2i (Mimo monitors) |
d05e84e6 DT |
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 | ||
4f7ed234 MP |
836 | config 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 | ||
d201fd5d SH |
845 | config TOUCHSCREEN_MC13783 |
846 | tristate "Freescale MC13783 touchscreen input driver" | |
e5a3da21 | 847 | depends on MFD_MC13XXX |
d201fd5d SH |
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 | ||
d05e84e6 DT |
857 | config TOUCHSCREEN_USB_EGALAX |
858 | default y | |
6a108a14 | 859 | bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT |
d05e84e6 DT |
860 | depends on TOUCHSCREEN_USB_COMPOSITE |
861 | ||
862 | config TOUCHSCREEN_USB_PANJIT | |
863 | default y | |
6a108a14 | 864 | bool "PanJit device support" if EXPERT |
d05e84e6 DT |
865 | depends on TOUCHSCREEN_USB_COMPOSITE |
866 | ||
867 | config TOUCHSCREEN_USB_3M | |
868 | default y | |
6a108a14 | 869 | bool "3M/Microtouch EX II series device support" if EXPERT |
d05e84e6 DT |
870 | depends on TOUCHSCREEN_USB_COMPOSITE |
871 | ||
872 | config TOUCHSCREEN_USB_ITM | |
873 | default y | |
6a108a14 | 874 | bool "ITM device support" if EXPERT |
d05e84e6 DT |
875 | depends on TOUCHSCREEN_USB_COMPOSITE |
876 | ||
877 | config TOUCHSCREEN_USB_ETURBO | |
878 | default y | |
6a108a14 | 879 | bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT |
d05e84e6 DT |
880 | depends on TOUCHSCREEN_USB_COMPOSITE |
881 | ||
882 | config TOUCHSCREEN_USB_GUNZE | |
883 | default y | |
6a108a14 | 884 | bool "Gunze AHL61 device support" if EXPERT |
d05e84e6 DT |
885 | depends on TOUCHSCREEN_USB_COMPOSITE |
886 | ||
887 | config TOUCHSCREEN_USB_DMC_TSC10 | |
888 | default y | |
6a108a14 | 889 | bool "DMC TSC-10/25 device support" if EXPERT |
d05e84e6 DT |
890 | depends on TOUCHSCREEN_USB_COMPOSITE |
891 | ||
df561fcd OZ |
892 | config TOUCHSCREEN_USB_IRTOUCH |
893 | default y | |
6a108a14 | 894 | bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT |
df561fcd OZ |
895 | depends on TOUCHSCREEN_USB_COMPOSITE |
896 | ||
a14a8401 OZ |
897 | config TOUCHSCREEN_USB_IDEALTEK |
898 | default y | |
6a108a14 | 899 | bool "IdealTEK URTC1000 device support" if EXPERT |
a14a8401 OZ |
900 | depends on TOUCHSCREEN_USB_COMPOSITE |
901 | ||
9d5657db IF |
902 | config TOUCHSCREEN_USB_GENERAL_TOUCH |
903 | default y | |
6a108a14 | 904 | bool "GeneralTouch Touchscreen device support" if EXPERT |
9d5657db IF |
905 | depends on TOUCHSCREEN_USB_COMPOSITE |
906 | ||
14e40206 JJ |
907 | config TOUCHSCREEN_USB_GOTOP |
908 | default y | |
6a108a14 | 909 | bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT |
14e40206 JJ |
910 | depends on TOUCHSCREEN_USB_COMPOSITE |
911 | ||
f7370699 JP |
912 | config TOUCHSCREEN_USB_JASTEC |
913 | default y | |
6a108a14 | 914 | bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT |
f7370699 JP |
915 | depends on TOUCHSCREEN_USB_COMPOSITE |
916 | ||
d2cc817a MG |
917 | config TOUCHSCREEN_USB_ELO |
918 | default y | |
919 | bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT | |
920 | depends on TOUCHSCREEN_USB_COMPOSITE | |
921 | ||
9e3b2583 FE |
922 | config TOUCHSCREEN_USB_E2I |
923 | default y | |
df052676 | 924 | bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT |
9e3b2583 FE |
925 | depends on TOUCHSCREEN_USB_COMPOSITE |
926 | ||
2330ed18 DS |
927 | config TOUCHSCREEN_USB_ZYTRONIC |
928 | default y | |
6a108a14 | 929 | bool "Zytronic controller" if EXPERT |
2330ed18 DS |
930 | depends on TOUCHSCREEN_USB_COMPOSITE |
931 | ||
38771bb4 | 932 | config TOUCHSCREEN_USB_ETT_TC45USB |
dbe1420b | 933 | default y |
6a108a14 | 934 | bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT |
dbe1420b PŠ |
935 | depends on TOUCHSCREEN_USB_COMPOSITE |
936 | ||
5197424c OZ |
937 | config TOUCHSCREEN_USB_NEXIO |
938 | default y | |
6a108a14 | 939 | bool "NEXIO/iNexio device support" if EXPERT |
5197424c OZ |
940 | depends on TOUCHSCREEN_USB_COMPOSITE |
941 | ||
aa87512f AV |
942 | config TOUCHSCREEN_USB_EASYTOUCH |
943 | default y | |
944 | bool "EasyTouch USB Touch controller device support" if EMBEDDED | |
945 | depends on TOUCHSCREEN_USB_COMPOSITE | |
946 | help | |
41baf636 | 947 | Say Y here if you have an EasyTouch USB Touch controller. |
aa87512f AV |
948 | If unsure, say N. |
949 | ||
73422392 CN |
950 | config 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 | ||
40e3be39 DR |
961 | config TOUCHSCREEN_TS4800 |
962 | tristate "TS-4800 touchscreen" | |
963 | depends on HAS_IOMEM && OF | |
cd1480ae | 964 | depends on SOC_IMX51 || COMPILE_TEST |
40e3be39 DR |
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 | ||
f01536e3 SAS |
978 | config 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 | ||
6ac24381 MW |
990 | config TOUCHSCREEN_TSC200X_CORE |
991 | tristate | |
992 | ||
a748941c MW |
993 | config 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 | ||
37bd4469 | 1006 | config TOUCHSCREEN_TSC2005 |
f00d1f8f SR |
1007 | tristate "TSC2005 based touchscreens" |
1008 | depends on SPI_MASTER | |
273cf48a | 1009 | select REGMAP_SPI |
6ac24381 | 1010 | select TOUCHSCREEN_TSC200X_CORE |
f00d1f8f SR |
1011 | help |
1012 | Say Y here if you have a TSC2005 based touchscreen. | |
37bd4469 LL |
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 | ||
50b6f1f4 KL |
1019 | config 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 | ||
7e3f7375 WZ |
1030 | config TOUCHSCREEN_W90X900 |
1031 | tristate "W90P910 touchscreen driver" | |
e5e0937c | 1032 | depends on ARCH_W90X900 |
7e3f7375 WZ |
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 | ||
0387e107 DR |
1039 | config 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. | |
75259966 | 1048 | |
56a8bd6d TS |
1049 | config TOUCHSCREEN_ST1232 |
1050 | tristate "Sitronix ST1232 touchscreen controllers" | |
75259966 TF |
1051 | depends on I2C |
1052 | help | |
56a8bd6d TS |
1053 | Say Y here if you want to support Sitronix ST1232 |
1054 | touchscreen controller. | |
75259966 TF |
1055 | |
1056 | If unsure, say N. | |
1057 | ||
1058 | To compile this driver as a module, choose M here: the | |
56a8bd6d | 1059 | module will be called st1232_ts. |
75259966 | 1060 | |
f94add3b LF |
1061 | config TOUCHSCREEN_STMPE |
1062 | tristate "STMicroelectronics STMPE touchscreens" | |
1063 | depends on MFD_STMPE | |
e4b88e19 | 1064 | depends on (OF || COMPILE_TEST) |
f94add3b LF |
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 | ||
6decea7c HG |
1072 | config TOUCHSCREEN_SUN4I |
1073 | tristate "Allwinner sun4i resistive touchscreen controller support" | |
1074 | depends on ARCH_SUNXI || COMPILE_TEST | |
f09f98d3 | 1075 | depends on HWMON |
4a6155a4 | 1076 | depends on THERMAL || !THERMAL_OF |
6decea7c HG |
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 | ||
bdb5c57f FE |
1084 | config TOUCHSCREEN_SUR40 |
1085 | tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen" | |
ef403bca | 1086 | depends on USB && MEDIA_USB_SUPPORT && HAS_DMA |
c8a1978e | 1087 | depends on VIDEO_V4L2 |
bdb5c57f | 1088 | select INPUT_POLLDEV |
e831cd25 | 1089 | select VIDEOBUF2_DMA_SG |
bdb5c57f FE |
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 | ||
902cb3af SS |
1097 | config 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 | ||
56a8bd6d TS |
1108 | config TOUCHSCREEN_TPS6507X |
1109 | tristate "TPS6507x based touchscreens" | |
1110 | depends on I2C | |
9ff9f6da | 1111 | select INPUT_POLLDEV |
56a8bd6d TS |
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 | ||
c6d81bd7 HS |
1121 | config TOUCHSCREEN_ZFORCE |
1122 | tristate "Neonode zForce infrared touchscreens" | |
1123 | depends on I2C | |
7d6548ab | 1124 | depends on GPIOLIB || COMPILE_TEST |
c6d81bd7 HS |
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 | ||
48ead50c SM |
1134 | config TOUCHSCREEN_COLIBRI_VF50 |
1135 | tristate "Toradex Colibri on board touchscreen driver" | |
1261d013 GU |
1136 | depends on IIO && VF610_ADC |
1137 | depends on GPIOLIB || COMPILE_TEST | |
48ead50c SM |
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 | ||
c7efd123 YY |
1147 | config 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 | ||
1da177e4 | 1158 | endif |