Kconfig 24 KB

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