Kconfig 25 KB

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