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