Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533
  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_ADS7846
  12. tristate "ADS7846/TSC2046 and ADS7843 based touchscreens"
  13. depends on SPI_MASTER
  14. depends on HWMON = n || HWMON
  15. help
  16. Say Y here if you have a touchscreen interface using the
  17. ADS7846/TSC2046 or ADS7843 controller, and your board-specific
  18. setup code includes that in its table of SPI devices.
  19. If HWMON is selected, and the driver is told the reference voltage
  20. on your board, you will also get hwmon interfaces for the voltage
  21. (and on ads7846/tsc2046, temperature) sensors of this chip.
  22. If unsure, say N (but it's safe to say "Y").
  23. To compile this driver as a module, choose M here: the
  24. module will be called ads7846.
  25. config TOUCHSCREEN_AD7877
  26. tristate "AD7877 based touchscreens"
  27. depends on SPI_MASTER
  28. help
  29. Say Y here if you have a touchscreen interface using the
  30. AD7877 controller, and your board-specific initialization
  31. code includes that in its table of SPI devices.
  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 ad7877.
  35. config TOUCHSCREEN_AD7879_I2C
  36. tristate "AD7879 based touchscreens: AD7879-1 I2C Interface"
  37. depends on I2C
  38. select TOUCHSCREEN_AD7879
  39. help
  40. Say Y here if you have a touchscreen interface using the
  41. AD7879-1/AD7889-1 controller, and your board-specific
  42. initialization code includes that in its table of I2C devices.
  43. If unsure, say N (but it's safe to say "Y").
  44. To compile this driver as a module, choose M here: the
  45. module will be called ad7879.
  46. config TOUCHSCREEN_AD7879_SPI
  47. tristate "AD7879 based touchscreens: AD7879 SPI Interface"
  48. depends on SPI_MASTER && TOUCHSCREEN_AD7879_I2C = n
  49. select TOUCHSCREEN_AD7879
  50. help
  51. Say Y here if you have a touchscreen interface using the
  52. AD7879/AD7889 controller, and your board-specific initialization
  53. code includes that in its table of SPI devices.
  54. If unsure, say N (but it's safe to say "Y").
  55. To compile this driver as a module, choose M here: the
  56. module will be called ad7879.
  57. config TOUCHSCREEN_AD7879
  58. tristate
  59. default n
  60. config TOUCHSCREEN_BITSY
  61. tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
  62. depends on SA1100_BITSY
  63. select SERIO
  64. help
  65. Say Y here if you have the h3600 (Bitsy) touchscreen.
  66. If unsure, say N.
  67. To compile this driver as a module, choose M here: the
  68. module will be called h3600_ts_input.
  69. config TOUCHSCREEN_CORGI
  70. tristate "SharpSL (Corgi and Spitz series) touchscreen driver (DEPRECATED)"
  71. depends on PXA_SHARPSL
  72. select CORGI_SSP_DEPRECATED
  73. default y
  74. help
  75. Say Y here to enable the driver for the touchscreen on the
  76. Sharp SL-C7xx and SL-Cxx00 series of PDAs.
  77. If unsure, say N.
  78. To compile this driver as a module, choose M here: the
  79. module will be called corgi_ts.
  80. NOTE: this driver is deprecated, try enable SPI and generic
  81. ADS7846-based touchscreen driver.
  82. config TOUCHSCREEN_DA9034
  83. tristate "Touchscreen support for Dialog Semiconductor DA9034"
  84. depends on PMIC_DA903X
  85. default y
  86. help
  87. Say Y here to enable the support for the touchscreen found
  88. on Dialog Semiconductor DA9034 PMIC.
  89. config TOUCHSCREEN_EETI
  90. tristate "EETI touchscreen panel support"
  91. depends on I2C
  92. help
  93. Say Y here to enable support for I2C connected EETI touch panels.
  94. To compile this driver as a module, choose M here: the
  95. module will be called eeti_ts.
  96. config TOUCHSCREEN_FUJITSU
  97. tristate "Fujitsu serial touchscreen"
  98. select SERIO
  99. help
  100. Say Y here if you have the Fujitsu touchscreen (such as one
  101. installed in Lifebook P series laptop) connected to your
  102. system.
  103. If unsure, say N.
  104. To compile this driver as a module, choose M here: the
  105. module will be called fujitsu-ts.
  106. config TOUCHSCREEN_GUNZE
  107. tristate "Gunze AHL-51S touchscreen"
  108. select SERIO
  109. help
  110. Say Y here if you have the Gunze AHL-51 touchscreen connected to
  111. your system.
  112. If unsure, say N.
  113. To compile this driver as a module, choose M here: the
  114. module will be called gunze.
  115. config TOUCHSCREEN_ELO
  116. tristate "Elo serial touchscreens"
  117. select SERIO
  118. help
  119. Say Y here if you have an Elo serial touchscreen connected to
  120. your system.
  121. If unsure, say N.
  122. To compile this driver as a module, choose M here: the
  123. module will be called elo.
  124. config TOUCHSCREEN_WACOM_W8001
  125. tristate "Wacom W8001 penabled serial touchscreen"
  126. select SERIO
  127. help
  128. Say Y here if you have an Wacom W8001 penabled serial touchscreen
  129. connected to your system.
  130. If unsure, say N.
  131. To compile this driver as a module, choose M here: the
  132. module will be called wacom_w8001.
  133. config TOUCHSCREEN_MCS5000
  134. tristate "MELFAS MCS-5000 touchscreen"
  135. depends on I2C
  136. help
  137. Say Y here if you have the MELFAS MCS-5000 touchscreen controller
  138. chip in your system.
  139. If unsure, say N.
  140. To compile this driver as a module, choose M here: the
  141. module will be called mcs5000_ts.
  142. config TOUCHSCREEN_MTOUCH
  143. tristate "MicroTouch serial touchscreens"
  144. select SERIO
  145. help
  146. Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
  147. your system.
  148. If unsure, say N.
  149. To compile this driver as a module, choose M here: the
  150. module will be called mtouch.
  151. config TOUCHSCREEN_INEXIO
  152. tristate "iNexio serial touchscreens"
  153. select SERIO
  154. help
  155. Say Y here if you have an iNexio serial touchscreen connected to
  156. your system.
  157. If unsure, say N.
  158. To compile this driver as a module, choose M here: the
  159. module will be called inexio.
  160. config TOUCHSCREEN_MK712
  161. tristate "ICS MicroClock MK712 touchscreen"
  162. help
  163. Say Y here if you have the ICS MicroClock MK712 touchscreen
  164. controller chip in your system.
  165. If unsure, say N.
  166. To compile this driver as a module, choose M here: the
  167. module will be called mk712.
  168. config TOUCHSCREEN_HP600
  169. tristate "HP Jornada 6xx touchscreen"
  170. depends on SH_HP6XX && SH_ADC
  171. help
  172. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  173. support the built-in touchscreen.
  174. To compile this driver as a module, choose M here: the
  175. module will be called hp680_ts_input.
  176. config TOUCHSCREEN_HP7XX
  177. tristate "HP Jornada 7xx touchscreen"
  178. depends on SA1100_JORNADA720_SSP
  179. help
  180. Say Y here if you have a HP Jornada 710/720/728 and want
  181. to support the built-in touchscreen.
  182. To compile this driver as a module, choose M here: the
  183. module will be called jornada720_ts.
  184. config TOUCHSCREEN_HTCPEN
  185. tristate "HTC Shift X9500 touchscreen"
  186. depends on ISA
  187. help
  188. Say Y here if you have an HTC Shift UMPC also known as HTC X9500
  189. Clio / Shangrila and want to support the built-in touchscreen.
  190. If unsure, say N.
  191. To compile this driver as a module, choose M here: the
  192. module will be called htcpen.
  193. config TOUCHSCREEN_PENMOUNT
  194. tristate "Penmount serial touchscreen"
  195. select SERIO
  196. help
  197. Say Y here if you have a Penmount 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 penmount.
  202. config TOUCHSCREEN_MIGOR
  203. tristate "Renesas MIGO-R touchscreen"
  204. depends on SH_MIGOR && I2C
  205. help
  206. Say Y here to enable MIGO-R touchscreen support.
  207. If unsure, say N.
  208. To compile this driver as a module, choose M here: the
  209. module will be called migor_ts.
  210. config TOUCHSCREEN_TOUCHRIGHT
  211. tristate "Touchright serial touchscreen"
  212. select SERIO
  213. help
  214. Say Y here if you have a Touchright serial touchscreen connected to
  215. your system.
  216. If unsure, say N.
  217. To compile this driver as a module, choose M here: the
  218. module will be called touchright.
  219. config TOUCHSCREEN_TOUCHWIN
  220. tristate "Touchwin serial touchscreen"
  221. select SERIO
  222. help
  223. Say Y here if you have a Touchwin serial touchscreen connected to
  224. your system.
  225. If unsure, say N.
  226. To compile this driver as a module, choose M here: the
  227. module will be called touchwin.
  228. config TOUCHSCREEN_ATMEL_TSADCC
  229. tristate "Atmel Touchscreen Interface"
  230. depends on ARCH_AT91SAM9RL
  231. help
  232. Say Y here if you have a 4-wire touchscreen connected to the
  233. ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
  234. If unsure, say N.
  235. To compile this driver as a module, choose M here: the
  236. module will be called atmel_tsadcc.
  237. config TOUCHSCREEN_UCB1400
  238. tristate "Philips UCB1400 touchscreen"
  239. depends on AC97_BUS
  240. depends on UCB1400_CORE
  241. help
  242. This enables support for the Philips UCB1400 touchscreen interface.
  243. The UCB1400 is an AC97 audio codec. The touchscreen interface
  244. will be initialized only after the ALSA subsystem has been
  245. brought up and the UCB1400 detected. You therefore have to
  246. configure ALSA support as well (either built-in or modular,
  247. independently of whether this driver is itself built-in or
  248. modular) for this driver to work.
  249. To compile this driver as a module, choose M here: the
  250. module will be called ucb1400_ts.
  251. config TOUCHSCREEN_WM97XX
  252. tristate "Support for WM97xx AC97 touchscreen controllers"
  253. depends on AC97_BUS
  254. help
  255. Say Y here if you have a Wolfson Microelectronics WM97xx
  256. touchscreen connected to your system. Note that this option
  257. only enables core driver, you will also need to select
  258. support for appropriate chip below.
  259. If unsure, say N.
  260. To compile this driver as a module, choose M here: the
  261. module will be called wm97xx-ts.
  262. config TOUCHSCREEN_WM9705
  263. bool "WM9705 Touchscreen interface support"
  264. depends on TOUCHSCREEN_WM97XX
  265. default y
  266. help
  267. Say Y here to enable support for the Wolfson Microelectronics
  268. WM9705 touchscreen controller.
  269. config TOUCHSCREEN_WM9712
  270. bool "WM9712 Touchscreen interface support"
  271. depends on TOUCHSCREEN_WM97XX
  272. default y
  273. help
  274. Say Y here to enable support for the Wolfson Microelectronics
  275. WM9712 touchscreen controller.
  276. config TOUCHSCREEN_WM9713
  277. bool "WM9713 Touchscreen interface support"
  278. depends on TOUCHSCREEN_WM97XX
  279. default y
  280. help
  281. Say Y here to enable support for the Wolfson Microelectronics
  282. WM9713 touchscreen controller.
  283. config TOUCHSCREEN_WM97XX_ATMEL
  284. tristate "WM97xx Atmel accelerated touch"
  285. depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
  286. help
  287. Say Y here for support for streaming mode with WM97xx touchscreens
  288. on Atmel AT91 or AVR32 systems with an AC97C module.
  289. Be aware that this will use channel B in the controller for
  290. streaming data, this must not conflict with other AC97C drivers.
  291. If unsure, say N.
  292. To compile this driver as a module, choose M here: the module will
  293. be called atmel-wm97xx.
  294. config TOUCHSCREEN_WM97XX_MAINSTONE
  295. tristate "WM97xx Mainstone/Palm accelerated touch"
  296. depends on TOUCHSCREEN_WM97XX && ARCH_PXA
  297. help
  298. Say Y here for support for streaming mode with WM97xx touchscreens
  299. on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
  300. If unsure, say N.
  301. To compile this driver as a module, choose M here: the
  302. module will be called mainstone-wm97xx.
  303. config TOUCHSCREEN_WM97XX_ZYLONITE
  304. tristate "Zylonite accelerated touch"
  305. depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
  306. select TOUCHSCREEN_WM9713
  307. help
  308. Say Y here for support for streaming mode with the touchscreen
  309. on Zylonite systems.
  310. If unsure, say N.
  311. To compile this driver as a module, choose M here: the
  312. module will be called zylonite-wm97xx.
  313. config TOUCHSCREEN_USB_COMPOSITE
  314. tristate "USB Touchscreen Driver"
  315. depends on USB_ARCH_HAS_HCD
  316. select USB
  317. help
  318. USB Touchscreen driver for:
  319. - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
  320. - PanJit TouchSet USB
  321. - 3M MicroTouch USB (EX II series)
  322. - ITM
  323. - some other eTurboTouch
  324. - Gunze AHL61
  325. - DMC TSC-10/25
  326. - IRTOUCHSYSTEMS/UNITOP
  327. - IdealTEK URTC1000
  328. - GoTop Super_Q2/GogoPen/PenPower tablets
  329. - JASTEC USB Touch Controller/DigiTech DTR-02U
  330. Have a look at <http://linux.chapter7.ch/touchkit/> for
  331. a usage description and the required user-space stuff.
  332. To compile this driver as a module, choose M here: the
  333. module will be called usbtouchscreen.
  334. config TOUCHSCREEN_USB_EGALAX
  335. default y
  336. bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
  337. depends on TOUCHSCREEN_USB_COMPOSITE
  338. config TOUCHSCREEN_USB_PANJIT
  339. default y
  340. bool "PanJit device support" if EMBEDDED
  341. depends on TOUCHSCREEN_USB_COMPOSITE
  342. config TOUCHSCREEN_USB_3M
  343. default y
  344. bool "3M/Microtouch EX II series device support" if EMBEDDED
  345. depends on TOUCHSCREEN_USB_COMPOSITE
  346. config TOUCHSCREEN_USB_ITM
  347. default y
  348. bool "ITM device support" if EMBEDDED
  349. depends on TOUCHSCREEN_USB_COMPOSITE
  350. config TOUCHSCREEN_USB_ETURBO
  351. default y
  352. bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
  353. depends on TOUCHSCREEN_USB_COMPOSITE
  354. config TOUCHSCREEN_USB_GUNZE
  355. default y
  356. bool "Gunze AHL61 device support" if EMBEDDED
  357. depends on TOUCHSCREEN_USB_COMPOSITE
  358. config TOUCHSCREEN_USB_DMC_TSC10
  359. default y
  360. bool "DMC TSC-10/25 device support" if EMBEDDED
  361. depends on TOUCHSCREEN_USB_COMPOSITE
  362. config TOUCHSCREEN_USB_IRTOUCH
  363. default y
  364. bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED
  365. depends on TOUCHSCREEN_USB_COMPOSITE
  366. config TOUCHSCREEN_USB_IDEALTEK
  367. default y
  368. bool "IdealTEK URTC1000 device support" if EMBEDDED
  369. depends on TOUCHSCREEN_USB_COMPOSITE
  370. config TOUCHSCREEN_USB_GENERAL_TOUCH
  371. default y
  372. bool "GeneralTouch Touchscreen device support" if EMBEDDED
  373. depends on TOUCHSCREEN_USB_COMPOSITE
  374. config TOUCHSCREEN_USB_GOTOP
  375. default y
  376. bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED
  377. depends on TOUCHSCREEN_USB_COMPOSITE
  378. config TOUCHSCREEN_USB_JASTEC
  379. default y
  380. bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EMBEDDED
  381. depends on TOUCHSCREEN_USB_COMPOSITE
  382. config TOUCHSCREEN_USB_E2I
  383. default y
  384. bool "e2i Touchscreen controller (e.g. from Mimo 740)"
  385. depends on TOUCHSCREEN_USB_COMPOSITE
  386. config TOUCHSCREEN_TOUCHIT213
  387. tristate "Sahara TouchIT-213 touchscreen"
  388. select SERIO
  389. help
  390. Say Y here if you have a Sahara TouchIT-213 Tablet PC.
  391. If unsure, say N.
  392. To compile this driver as a module, choose M here: the
  393. module will be called touchit213.
  394. config TOUCHSCREEN_TSC2007
  395. tristate "TSC2007 based touchscreens"
  396. depends on I2C
  397. help
  398. Say Y here if you have a TSC2007 based touchscreen.
  399. If unsure, say N.
  400. To compile this driver as a module, choose M here: the
  401. module will be called tsc2007.
  402. config TOUCHSCREEN_W90X900
  403. tristate "W90P910 touchscreen driver"
  404. depends on HAVE_CLK
  405. help
  406. Say Y here if you have a W90P910 based touchscreen.
  407. To compile this driver as a module, choose M here: the
  408. module will be called w90p910_ts.
  409. config TOUCHSCREEN_PCAP
  410. tristate "Motorola PCAP touchscreen"
  411. depends on EZX_PCAP
  412. help
  413. Say Y here if you have a Motorola EZX telephone and
  414. want to enable support for the built-in touchscreen.
  415. To compile this driver as a module, choose M here: the
  416. module will be called pcap_ts.
  417. endif