Kconfig 19 KB

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