Kconfig 24 KB

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