Kconfig 27 KB

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