Kconfig 25 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941
  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 OF_TOUCHSCREEN
  12. def_tristate INPUT
  13. depends on INPUT && OF
  14. config TOUCHSCREEN_88PM860X
  15. tristate "Marvell 88PM860x touchscreen"
  16. depends on MFD_88PM860X
  17. help
  18. Say Y here if you have a 88PM860x PMIC and want to enable
  19. support for the built-in touchscreen.
  20. If unsure, say N.
  21. To compile this driver as a module, choose M here: the
  22. module will be called 88pm860x-ts.
  23. config TOUCHSCREEN_ADS7846
  24. tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens"
  25. depends on SPI_MASTER
  26. depends on HWMON = n || HWMON
  27. help
  28. Say Y here if you have a touchscreen interface using the
  29. ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
  30. and your board-specific setup code includes that in its
  31. table of SPI devices.
  32. If HWMON is selected, and the driver is told the reference voltage
  33. on your board, you will also get hwmon interfaces for the voltage
  34. (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
  35. If unsure, say N (but it's safe to say "Y").
  36. To compile this driver as a module, choose M here: the
  37. module will be called ads7846.
  38. config TOUCHSCREEN_AD7877
  39. tristate "AD7877 based touchscreens"
  40. depends on SPI_MASTER
  41. help
  42. Say Y here if you have a touchscreen interface using the
  43. AD7877 controller, and your board-specific initialization
  44. code includes that in its table of SPI devices.
  45. If unsure, say N (but it's safe to say "Y").
  46. To compile this driver as a module, choose M here: the
  47. module will be called ad7877.
  48. config TOUCHSCREEN_AD7879
  49. tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
  50. help
  51. Say Y here if you want to support a touchscreen interface using
  52. the AD7879-1/AD7889-1 controller.
  53. You should select a bus connection too.
  54. To compile this driver as a module, choose M here: the
  55. module will be called ad7879.
  56. config TOUCHSCREEN_AD7879_I2C
  57. tristate "support I2C bus connection"
  58. depends on TOUCHSCREEN_AD7879 && I2C
  59. help
  60. Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
  61. To compile this driver as a module, choose M here: the
  62. module will be called ad7879-i2c.
  63. config TOUCHSCREEN_AD7879_SPI
  64. tristate "support SPI bus connection"
  65. depends on TOUCHSCREEN_AD7879 && SPI_MASTER
  66. help
  67. Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
  68. If unsure, say N (but it's safe to say "Y").
  69. To compile this driver as a module, choose M here: the
  70. module will be called ad7879-spi.
  71. config TOUCHSCREEN_ATMEL_MXT
  72. tristate "Atmel mXT I2C Touchscreen"
  73. depends on I2C
  74. select FW_LOADER
  75. help
  76. Say Y here if you have Atmel mXT series I2C touchscreen,
  77. such as AT42QT602240/ATMXT224, connected to your system.
  78. If unsure, say N.
  79. To compile this driver as a module, choose M here: the
  80. module will be called atmel_mxt_ts.
  81. config TOUCHSCREEN_AUO_PIXCIR
  82. tristate "AUO in-cell touchscreen using Pixcir ICs"
  83. depends on I2C
  84. depends on GPIOLIB
  85. help
  86. Say Y here if you have a AUO display with in-cell touchscreen
  87. using Pixcir ICs.
  88. If unsure, say N.
  89. To compile this driver as a module, choose M here: the
  90. module will be called auo-pixcir-ts.
  91. config TOUCHSCREEN_BU21013
  92. tristate "BU21013 based touch panel controllers"
  93. depends on I2C
  94. help
  95. Say Y here if you have a bu21013 touchscreen connected to
  96. your system.
  97. If unsure, say N.
  98. To compile this driver as a module, choose M here: the
  99. module will be called bu21013_ts.
  100. config TOUCHSCREEN_CY8CTMG110
  101. tristate "cy8ctmg110 touchscreen"
  102. depends on I2C
  103. depends on GPIOLIB
  104. help
  105. Say Y here if you have a cy8ctmg110 capacitive touchscreen on
  106. an AAVA device.
  107. If unsure, say N.
  108. To compile this driver as a module, choose M here: the
  109. module will be called cy8ctmg110_ts.
  110. config TOUCHSCREEN_CYTTSP_CORE
  111. tristate "Cypress TTSP touchscreen"
  112. help
  113. Say Y here if you have a touchscreen using controller from
  114. the Cypress TrueTouch(tm) Standard Product family connected
  115. to your system. You will also need to select appropriate
  116. bus connection below.
  117. If unsure, say N.
  118. To compile this driver as a module, choose M here: the
  119. module will be called cyttsp_core.
  120. config TOUCHSCREEN_CYTTSP_I2C
  121. tristate "support I2C bus connection"
  122. depends on TOUCHSCREEN_CYTTSP_CORE && I2C
  123. help
  124. Say Y here if the touchscreen is connected via I2C bus.
  125. To compile this driver as a module, choose M here: the
  126. module will be called cyttsp_i2c.
  127. config TOUCHSCREEN_CYTTSP_SPI
  128. tristate "support SPI bus connection"
  129. depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
  130. help
  131. Say Y here if the touchscreen is connected via SPI bus.
  132. To compile this driver as a module, choose M here: the
  133. module will be called cyttsp_spi.
  134. config TOUCHSCREEN_CYTTSP4_CORE
  135. tristate "Cypress TrueTouch Gen4 Touchscreen Driver"
  136. help
  137. Core driver for Cypress TrueTouch(tm) Standard Product
  138. Generation4 touchscreen controllers.
  139. Say Y here if you have a Cypress Gen4 touchscreen.
  140. If unsure, say N.
  141. To compile this driver as a module, choose M here.
  142. config TOUCHSCREEN_CYTTSP4_I2C
  143. tristate "support I2C bus connection"
  144. depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
  145. help
  146. Say Y here if the touchscreen is connected via I2C bus.
  147. To compile this driver as a module, choose M here: the
  148. module will be called cyttsp4_i2c.
  149. config TOUCHSCREEN_CYTTSP4_SPI
  150. tristate "support SPI bus connection"
  151. depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
  152. help
  153. Say Y here if the touchscreen is connected via SPI bus.
  154. To compile this driver as a module, choose M here: the
  155. module will be called cyttsp4_spi.
  156. config TOUCHSCREEN_DA9034
  157. tristate "Touchscreen support for Dialog Semiconductor DA9034"
  158. depends on PMIC_DA903X
  159. default y
  160. help
  161. Say Y here to enable the support for the touchscreen found
  162. on Dialog Semiconductor DA9034 PMIC.
  163. If unsure, say N.
  164. To compile this driver as a module, choose M here: the
  165. module will be called da9034-ts.
  166. config TOUCHSCREEN_DA9052
  167. tristate "Dialog DA9052/DA9053 TSI"
  168. depends on PMIC_DA9052
  169. help
  170. Say Y here to support the touchscreen found on Dialog Semiconductor
  171. DA9052-BC and DA9053-AA/Bx PMICs.
  172. If unsure, say N.
  173. To compile this driver as a module, choose M here: the
  174. module will be called da9052_tsi.
  175. config TOUCHSCREEN_DYNAPRO
  176. tristate "Dynapro serial touchscreen"
  177. select SERIO
  178. help
  179. Say Y here if you have a Dynapro serial touchscreen connected to
  180. your system.
  181. If unsure, say N.
  182. To compile this driver as a module, choose M here: the
  183. module will be called dynapro.
  184. config TOUCHSCREEN_HAMPSHIRE
  185. tristate "Hampshire serial touchscreen"
  186. select SERIO
  187. help
  188. Say Y here if you have a Hampshire serial touchscreen connected to
  189. your system.
  190. If unsure, say N.
  191. To compile this driver as a module, choose M here: the
  192. module will be called hampshire.
  193. config TOUCHSCREEN_EETI
  194. tristate "EETI touchscreen panel support"
  195. depends on I2C
  196. help
  197. Say Y here to enable support for I2C connected EETI touch panels.
  198. To compile this driver as a module, choose M here: the
  199. module will be called eeti_ts.
  200. config TOUCHSCREEN_EGALAX
  201. tristate "EETI eGalax multi-touch panel support"
  202. depends on I2C && OF
  203. help
  204. Say Y here to enable support for I2C connected EETI
  205. eGalax multi-touch panels.
  206. To compile this driver as a module, choose M here: the
  207. module will be called egalax_ts.
  208. config TOUCHSCREEN_FUJITSU
  209. tristate "Fujitsu serial touchscreen"
  210. select SERIO
  211. help
  212. Say Y here if you have the Fujitsu touchscreen (such as one
  213. installed in Lifebook P series laptop) connected to your
  214. system.
  215. If unsure, say N.
  216. To compile this driver as a module, choose M here: the
  217. module will be called fujitsu-ts.
  218. config TOUCHSCREEN_ILI210X
  219. tristate "Ilitek ILI210X based touchscreen"
  220. depends on I2C
  221. help
  222. Say Y here if you have a ILI210X based touchscreen
  223. controller. This driver supports models ILI2102,
  224. ILI2102s, ILI2103, ILI2103s and ILI2105.
  225. Such kind of chipsets can be found in Amazon Kindle Fire
  226. touchscreens.
  227. If unsure, say N.
  228. To compile this driver as a module, choose M here: the
  229. module will be called ili210x.
  230. config TOUCHSCREEN_S3C2410
  231. tristate "Samsung S3C2410/generic touchscreen input driver"
  232. depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
  233. select S3C_ADC
  234. help
  235. Say Y here if you have the s3c2410 touchscreen.
  236. If unsure, say N.
  237. To compile this driver as a module, choose M here: the
  238. module will be called s3c2410_ts.
  239. config TOUCHSCREEN_GUNZE
  240. tristate "Gunze AHL-51S touchscreen"
  241. select SERIO
  242. help
  243. Say Y here if you have the Gunze AHL-51 touchscreen connected to
  244. your system.
  245. If unsure, say N.
  246. To compile this driver as a module, choose M here: the
  247. module will be called gunze.
  248. config TOUCHSCREEN_ELO
  249. tristate "Elo serial touchscreens"
  250. select SERIO
  251. help
  252. Say Y here if you have an Elo serial touchscreen connected to
  253. your system.
  254. If unsure, say N.
  255. To compile this driver as a module, choose M here: the
  256. module will be called elo.
  257. config TOUCHSCREEN_WACOM_W8001
  258. tristate "Wacom W8001 penabled serial touchscreen"
  259. select SERIO
  260. help
  261. Say Y here if you have an Wacom W8001 penabled serial touchscreen
  262. connected to your system.
  263. If unsure, say N.
  264. To compile this driver as a module, choose M here: the
  265. module will be called wacom_w8001.
  266. config TOUCHSCREEN_WACOM_I2C
  267. tristate "Wacom Tablet support (I2C)"
  268. depends on I2C
  269. help
  270. Say Y here if you want to use the I2C version of the Wacom
  271. Pen Tablet.
  272. If unsure, say N.
  273. To compile this driver as a module, choose M here: the module
  274. will be called wacom_i2c.
  275. config TOUCHSCREEN_LPC32XX
  276. tristate "LPC32XX touchscreen controller"
  277. depends on ARCH_LPC32XX
  278. help
  279. Say Y here if you have a LPC32XX device and want
  280. to support the built-in touchscreen.
  281. To compile this driver as a module, choose M here: the
  282. module will be called lpc32xx_ts.
  283. config TOUCHSCREEN_MAX11801
  284. tristate "MAX11801 based touchscreens"
  285. depends on I2C
  286. help
  287. Say Y here if you have a MAX11801 based touchscreen
  288. controller.
  289. If unsure, say N.
  290. To compile this driver as a module, choose M here: the
  291. module will be called max11801_ts.
  292. config TOUCHSCREEN_MCS5000
  293. tristate "MELFAS MCS-5000 touchscreen"
  294. depends on I2C
  295. help
  296. Say Y here if you have the MELFAS MCS-5000 touchscreen controller
  297. chip in your system.
  298. If unsure, say N.
  299. To compile this driver as a module, choose M here: the
  300. module will be called mcs5000_ts.
  301. config TOUCHSCREEN_MMS114
  302. tristate "MELFAS MMS114 touchscreen"
  303. depends on I2C
  304. help
  305. Say Y here if you have the MELFAS MMS114 touchscreen controller
  306. chip in your system.
  307. If unsure, say N.
  308. To compile this driver as a module, choose M here: the
  309. module will be called mms114.
  310. config TOUCHSCREEN_MTOUCH
  311. tristate "MicroTouch serial touchscreens"
  312. select SERIO
  313. help
  314. Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
  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 mtouch.
  319. config TOUCHSCREEN_INEXIO
  320. tristate "iNexio serial touchscreens"
  321. select SERIO
  322. help
  323. Say Y here if you have an iNexio serial touchscreen connected to
  324. your system.
  325. If unsure, say N.
  326. To compile this driver as a module, choose M here: the
  327. module will be called inexio.
  328. config TOUCHSCREEN_INTEL_MID
  329. tristate "Intel MID platform resistive touchscreen"
  330. depends on INTEL_SCU_IPC
  331. help
  332. Say Y here if you have a Intel MID based touchscreen in
  333. your system.
  334. If unsure, say N.
  335. To compile this driver as a module, choose M here: the
  336. module will be called intel_mid_touch.
  337. config TOUCHSCREEN_MK712
  338. tristate "ICS MicroClock MK712 touchscreen"
  339. help
  340. Say Y here if you have the ICS MicroClock MK712 touchscreen
  341. controller chip in your system.
  342. If unsure, say N.
  343. To compile this driver as a module, choose M here: the
  344. module will be called mk712.
  345. config TOUCHSCREEN_HP600
  346. tristate "HP Jornada 6xx touchscreen"
  347. depends on SH_HP6XX && SH_ADC
  348. help
  349. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  350. support the built-in touchscreen.
  351. To compile this driver as a module, choose M here: the
  352. module will be called hp680_ts_input.
  353. config TOUCHSCREEN_HP7XX
  354. tristate "HP Jornada 7xx touchscreen"
  355. depends on SA1100_JORNADA720_SSP
  356. help
  357. Say Y here if you have a HP Jornada 710/720/728 and want
  358. to support the built-in touchscreen.
  359. To compile this driver as a module, choose M here: the
  360. module will be called jornada720_ts.
  361. config TOUCHSCREEN_HTCPEN
  362. tristate "HTC Shift X9500 touchscreen"
  363. depends on ISA
  364. help
  365. Say Y here if you have an HTC Shift UMPC also known as HTC X9500
  366. Clio / Shangrila and want to support the built-in touchscreen.
  367. If unsure, say N.
  368. To compile this driver as a module, choose M here: the
  369. module will be called htcpen.
  370. config TOUCHSCREEN_PENMOUNT
  371. tristate "Penmount serial touchscreen"
  372. select SERIO
  373. help
  374. Say Y here if you have a Penmount serial touchscreen connected to
  375. your system.
  376. If unsure, say N.
  377. To compile this driver as a module, choose M here: the
  378. module will be called penmount.
  379. config TOUCHSCREEN_EDT_FT5X06
  380. tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
  381. depends on I2C
  382. help
  383. Say Y here if you have an EDT "Polytouch" touchscreen based
  384. on the FocalTech FT5x06 family of controllers connected to
  385. your system.
  386. If unsure, say N.
  387. To compile this driver as a module, choose M here: the
  388. module will be called edt-ft5x06.
  389. config TOUCHSCREEN_MIGOR
  390. tristate "Renesas MIGO-R touchscreen"
  391. depends on SH_MIGOR && I2C
  392. help
  393. Say Y here to enable MIGO-R touchscreen support.
  394. If unsure, say N.
  395. To compile this driver as a module, choose M here: the
  396. module will be called migor_ts.
  397. config TOUCHSCREEN_TOUCHRIGHT
  398. tristate "Touchright serial touchscreen"
  399. select SERIO
  400. help
  401. Say Y here if you have a Touchright serial touchscreen connected to
  402. your system.
  403. If unsure, say N.
  404. To compile this driver as a module, choose M here: the
  405. module will be called touchright.
  406. config TOUCHSCREEN_TOUCHWIN
  407. tristate "Touchwin serial touchscreen"
  408. select SERIO
  409. help
  410. Say Y here if you have a Touchwin serial touchscreen connected to
  411. your system.
  412. If unsure, say N.
  413. To compile this driver as a module, choose M here: the
  414. module will be called touchwin.
  415. config TOUCHSCREEN_TI_AM335X_TSC
  416. tristate "TI Touchscreen Interface"
  417. depends on MFD_TI_AM335X_TSCADC
  418. help
  419. Say Y here if you have 4/5/8 wire touchscreen controller
  420. to be connected to the ADC controller on your TI AM335x SoC.
  421. If unsure, say N.
  422. To compile this driver as a module, choose M here: the
  423. module will be called ti_am335x_tsc.
  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
  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_MC13XXX
  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. config TOUCHSCREEN_TOUCHIT213
  627. tristate "Sahara TouchIT-213 touchscreen"
  628. select SERIO
  629. help
  630. Say Y here if you have a Sahara TouchIT-213 Tablet PC.
  631. If unsure, say N.
  632. To compile this driver as a module, choose M here: the
  633. module will be called touchit213.
  634. config TOUCHSCREEN_TSC_SERIO
  635. tristate "TSC-10/25/40 serial touchscreen support"
  636. select SERIO
  637. help
  638. Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
  639. to your system.
  640. If unsure, say N.
  641. To compile this driver as a module, choose M here: the
  642. module will be called tsc40.
  643. config TOUCHSCREEN_TSC2005
  644. tristate "TSC2005 based touchscreens"
  645. depends on SPI_MASTER
  646. help
  647. Say Y here if you have a TSC2005 based touchscreen.
  648. If unsure, say N.
  649. To compile this driver as a module, choose M here: the
  650. module will be called tsc2005.
  651. config TOUCHSCREEN_TSC2007
  652. tristate "TSC2007 based touchscreens"
  653. depends on I2C
  654. help
  655. Say Y here if you have a TSC2007 based touchscreen.
  656. If unsure, say N.
  657. To compile this driver as a module, choose M here: the
  658. module will be called tsc2007.
  659. config TOUCHSCREEN_W90X900
  660. tristate "W90P910 touchscreen driver"
  661. depends on ARCH_W90X900
  662. help
  663. Say Y here if you have a W90P910 based touchscreen.
  664. To compile this driver as a module, choose M here: the
  665. module will be called w90p910_ts.
  666. config TOUCHSCREEN_PCAP
  667. tristate "Motorola PCAP touchscreen"
  668. depends on EZX_PCAP
  669. help
  670. Say Y here if you have a Motorola EZX telephone and
  671. want to enable support for the built-in touchscreen.
  672. To compile this driver as a module, choose M here: the
  673. module will be called pcap_ts.
  674. config TOUCHSCREEN_ST1232
  675. tristate "Sitronix ST1232 touchscreen controllers"
  676. depends on I2C
  677. help
  678. Say Y here if you want to support Sitronix ST1232
  679. touchscreen controller.
  680. If unsure, say N.
  681. To compile this driver as a module, choose M here: the
  682. module will be called st1232_ts.
  683. config TOUCHSCREEN_STMPE
  684. tristate "STMicroelectronics STMPE touchscreens"
  685. depends on MFD_STMPE
  686. help
  687. Say Y here if you want support for STMicroelectronics
  688. STMPE touchscreen controllers.
  689. To compile this driver as a module, choose M here: the
  690. module will be called stmpe-ts.
  691. config TOUCHSCREEN_SUN4I
  692. tristate "Allwinner sun4i resistive touchscreen controller support"
  693. depends on ARCH_SUNXI || COMPILE_TEST
  694. depends on HWMON
  695. help
  696. This selects support for the resistive touchscreen controller
  697. found on Allwinner sunxi SoCs.
  698. To compile this driver as a module, choose M here: the
  699. module will be called sun4i-ts.
  700. config TOUCHSCREEN_SUR40
  701. tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
  702. depends on USB
  703. select INPUT_POLLDEV
  704. help
  705. Say Y here if you want support for the Samsung SUR40 touchscreen
  706. (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
  707. To compile this driver as a module, choose M here: the
  708. module will be called sur40.
  709. config TOUCHSCREEN_TPS6507X
  710. tristate "TPS6507x based touchscreens"
  711. depends on I2C
  712. select INPUT_POLLDEV
  713. help
  714. Say Y here if you have a TPS6507x based touchscreen
  715. controller.
  716. If unsure, say N.
  717. To compile this driver as a module, choose M here: the
  718. module will be called tps6507x_ts.
  719. config TOUCHSCREEN_ZFORCE
  720. tristate "Neonode zForce infrared touchscreens"
  721. depends on I2C
  722. depends on GPIOLIB
  723. help
  724. Say Y here if you have a touchscreen using the zforce
  725. infraread technology from Neonode.
  726. If unsure, say N.
  727. To compile this driver as a module, choose M here: the
  728. module will be called zforce_ts.
  729. endif