Kconfig 21 KB

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