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