Kconfig 25 KB

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