Kconfig 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663
  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_BITSY
  69. tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
  70. depends on SA1100_BITSY
  71. select SERIO
  72. help
  73. Say Y here if you have the h3600 (Bitsy) touchscreen.
  74. If unsure, say N.
  75. To compile this driver as a module, choose M here: the
  76. module will be called h3600_ts_input.
  77. config TOUCHSCREEN_CY8CTMG110
  78. tristate "cy8ctmg110 touchscreen"
  79. depends on I2C
  80. depends on GPIOLIB
  81. help
  82. Say Y here if you have a cy8ctmg110 capacitive touchscreen on
  83. an AAVA device.
  84. If unsure, say N.
  85. To compile this driver as a module, choose M here: the
  86. module will be called cy8ctmg110_ts.
  87. config TOUCHSCREEN_DA9034
  88. tristate "Touchscreen support for Dialog Semiconductor DA9034"
  89. depends on PMIC_DA903X
  90. default y
  91. help
  92. Say Y here to enable the support for the touchscreen found
  93. on Dialog Semiconductor DA9034 PMIC.
  94. config TOUCHSCREEN_DYNAPRO
  95. tristate "Dynapro serial touchscreen"
  96. select SERIO
  97. help
  98. Say Y here if you have a Dynapro serial touchscreen connected to
  99. your system.
  100. If unsure, say N.
  101. To compile this driver as a module, choose M here: the
  102. module will be called dynapro.
  103. config TOUCHSCREEN_HAMPSHIRE
  104. tristate "Hampshire serial touchscreen"
  105. select SERIO
  106. help
  107. Say Y here if you have a Hampshire serial touchscreen connected to
  108. your system.
  109. If unsure, say N.
  110. To compile this driver as a module, choose M here: the
  111. module will be called hampshire.
  112. config TOUCHSCREEN_EETI
  113. tristate "EETI touchscreen panel support"
  114. depends on I2C
  115. help
  116. Say Y here to enable support for I2C connected EETI touch panels.
  117. To compile this driver as a module, choose M here: the
  118. module will be called eeti_ts.
  119. config TOUCHSCREEN_FUJITSU
  120. tristate "Fujitsu serial touchscreen"
  121. select SERIO
  122. help
  123. Say Y here if you have the Fujitsu touchscreen (such as one
  124. installed in Lifebook P series laptop) connected to your
  125. system.
  126. If unsure, say N.
  127. To compile this driver as a module, choose M here: the
  128. module will be called fujitsu-ts.
  129. config TOUCHSCREEN_S3C2410
  130. tristate "Samsung S3C2410/generic touchscreen input driver"
  131. depends on ARCH_S3C2410 || SAMSUNG_DEV_TS
  132. select S3C_ADC
  133. help
  134. Say Y here if you have the s3c2410 touchscreen.
  135. If unsure, say N.
  136. To compile this driver as a module, choose M here: the
  137. module will be called s3c2410_ts.
  138. config TOUCHSCREEN_GUNZE
  139. tristate "Gunze AHL-51S touchscreen"
  140. select SERIO
  141. help
  142. Say Y here if you have the Gunze AHL-51 touchscreen connected to
  143. your system.
  144. If unsure, say N.
  145. To compile this driver as a module, choose M here: the
  146. module will be called gunze.
  147. config TOUCHSCREEN_ELO
  148. tristate "Elo serial touchscreens"
  149. select SERIO
  150. help
  151. Say Y here if you have an Elo serial touchscreen connected to
  152. your system.
  153. If unsure, say N.
  154. To compile this driver as a module, choose M here: the
  155. module will be called elo.
  156. config TOUCHSCREEN_WACOM_W8001
  157. tristate "Wacom W8001 penabled serial touchscreen"
  158. select SERIO
  159. help
  160. Say Y here if you have an Wacom W8001 penabled serial touchscreen
  161. connected to your system.
  162. If unsure, say N.
  163. To compile this driver as a module, choose M here: the
  164. module will be called wacom_w8001.
  165. config TOUCHSCREEN_LPC32XX
  166. tristate "LPC32XX touchscreen controller"
  167. depends on ARCH_LPC32XX
  168. help
  169. Say Y here if you have a LPC32XX device and want
  170. to support the built-in touchscreen.
  171. To compile this driver as a module, choose M here: the
  172. module will be called lpc32xx_ts.
  173. config TOUCHSCREEN_MCS5000
  174. tristate "MELFAS MCS-5000 touchscreen"
  175. depends on I2C
  176. help
  177. Say Y here if you have the MELFAS MCS-5000 touchscreen controller
  178. chip in your system.
  179. If unsure, say N.
  180. To compile this driver as a module, choose M here: the
  181. module will be called mcs5000_ts.
  182. config TOUCHSCREEN_MTOUCH
  183. tristate "MicroTouch serial touchscreens"
  184. select SERIO
  185. help
  186. Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
  187. your system.
  188. If unsure, say N.
  189. To compile this driver as a module, choose M here: the
  190. module will be called mtouch.
  191. config TOUCHSCREEN_INEXIO
  192. tristate "iNexio serial touchscreens"
  193. select SERIO
  194. help
  195. Say Y here if you have an iNexio serial touchscreen connected to
  196. your system.
  197. If unsure, say N.
  198. To compile this driver as a module, choose M here: the
  199. module will be called inexio.
  200. config TOUCHSCREEN_INTEL_MID
  201. tristate "Intel MID platform resistive touchscreen"
  202. depends on INTEL_SCU_IPC
  203. help
  204. Say Y here if you have a Intel MID based touchscreen in
  205. your system.
  206. If unsure, say N.
  207. To compile this driver as a module, choose M here: the
  208. module will be called intel_mid_touch.
  209. config TOUCHSCREEN_MK712
  210. tristate "ICS MicroClock MK712 touchscreen"
  211. help
  212. Say Y here if you have the ICS MicroClock MK712 touchscreen
  213. controller chip in your system.
  214. If unsure, say N.
  215. To compile this driver as a module, choose M here: the
  216. module will be called mk712.
  217. config TOUCHSCREEN_HP600
  218. tristate "HP Jornada 6xx touchscreen"
  219. depends on SH_HP6XX && SH_ADC
  220. help
  221. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  222. support the built-in touchscreen.
  223. To compile this driver as a module, choose M here: the
  224. module will be called hp680_ts_input.
  225. config TOUCHSCREEN_HP7XX
  226. tristate "HP Jornada 7xx touchscreen"
  227. depends on SA1100_JORNADA720_SSP
  228. help
  229. Say Y here if you have a HP Jornada 710/720/728 and want
  230. to support the built-in touchscreen.
  231. To compile this driver as a module, choose M here: the
  232. module will be called jornada720_ts.
  233. config TOUCHSCREEN_HTCPEN
  234. tristate "HTC Shift X9500 touchscreen"
  235. depends on ISA
  236. help
  237. Say Y here if you have an HTC Shift UMPC also known as HTC X9500
  238. Clio / Shangrila and want to support the built-in touchscreen.
  239. If unsure, say N.
  240. To compile this driver as a module, choose M here: the
  241. module will be called htcpen.
  242. config TOUCHSCREEN_PENMOUNT
  243. tristate "Penmount serial touchscreen"
  244. select SERIO
  245. help
  246. Say Y here if you have a Penmount serial touchscreen connected to
  247. your system.
  248. If unsure, say N.
  249. To compile this driver as a module, choose M here: the
  250. module will be called penmount.
  251. config TOUCHSCREEN_QT602240
  252. tristate "QT602240 I2C Touchscreen"
  253. depends on I2C
  254. help
  255. Say Y here if you have the AT42QT602240/ATMXT224 I2C touchscreen
  256. connected to your system.
  257. If unsure, say N.
  258. To compile this driver as a module, choose M here: the
  259. module will be called qt602240_ts.
  260. config TOUCHSCREEN_MIGOR
  261. tristate "Renesas MIGO-R touchscreen"
  262. depends on SH_MIGOR && I2C
  263. help
  264. Say Y here to enable MIGO-R touchscreen support.
  265. If unsure, say N.
  266. To compile this driver as a module, choose M here: the
  267. module will be called migor_ts.
  268. config TOUCHSCREEN_TOUCHRIGHT
  269. tristate "Touchright serial touchscreen"
  270. select SERIO
  271. help
  272. Say Y here if you have a Touchright serial touchscreen connected to
  273. your system.
  274. If unsure, say N.
  275. To compile this driver as a module, choose M here: the
  276. module will be called touchright.
  277. config TOUCHSCREEN_TOUCHWIN
  278. tristate "Touchwin serial touchscreen"
  279. select SERIO
  280. help
  281. Say Y here if you have a Touchwin serial touchscreen connected to
  282. your system.
  283. If unsure, say N.
  284. To compile this driver as a module, choose M here: the
  285. module will be called touchwin.
  286. config TOUCHSCREEN_ATMEL_TSADCC
  287. tristate "Atmel Touchscreen Interface"
  288. depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
  289. help
  290. Say Y here if you have a 4-wire touchscreen connected to the
  291. ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
  292. If unsure, say N.
  293. To compile this driver as a module, choose M here: the
  294. module will be called atmel_tsadcc.
  295. config TOUCHSCREEN_UCB1400
  296. tristate "Philips UCB1400 touchscreen"
  297. depends on AC97_BUS
  298. depends on UCB1400_CORE
  299. help
  300. This enables support for the Philips UCB1400 touchscreen interface.
  301. The UCB1400 is an AC97 audio codec. The touchscreen interface
  302. will be initialized only after the ALSA subsystem has been
  303. brought up and the UCB1400 detected. You therefore have to
  304. configure ALSA support as well (either built-in or modular,
  305. independently of whether this driver is itself built-in or
  306. modular) for this driver to work.
  307. To compile this driver as a module, choose M here: the
  308. module will be called ucb1400_ts.
  309. config TOUCHSCREEN_WM97XX
  310. tristate "Support for WM97xx AC97 touchscreen controllers"
  311. depends on AC97_BUS
  312. help
  313. Say Y here if you have a Wolfson Microelectronics WM97xx
  314. touchscreen connected to your system. Note that this option
  315. only enables core driver, you will also need to select
  316. support for appropriate chip below.
  317. If unsure, say N.
  318. To compile this driver as a module, choose M here: the
  319. module will be called wm97xx-ts.
  320. config TOUCHSCREEN_WM9705
  321. bool "WM9705 Touchscreen interface support"
  322. depends on TOUCHSCREEN_WM97XX
  323. default y
  324. help
  325. Say Y here to enable support for the Wolfson Microelectronics
  326. WM9705 touchscreen controller.
  327. config TOUCHSCREEN_WM9712
  328. bool "WM9712 Touchscreen interface support"
  329. depends on TOUCHSCREEN_WM97XX
  330. default y
  331. help
  332. Say Y here to enable support for the Wolfson Microelectronics
  333. WM9712 touchscreen controller.
  334. config TOUCHSCREEN_WM9713
  335. bool "WM9713 Touchscreen interface support"
  336. depends on TOUCHSCREEN_WM97XX
  337. default y
  338. help
  339. Say Y here to enable support for the Wolfson Microelectronics
  340. WM9713 touchscreen controller.
  341. config TOUCHSCREEN_WM97XX_ATMEL
  342. tristate "WM97xx Atmel accelerated touch"
  343. depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
  344. help
  345. Say Y here for support for streaming mode with WM97xx touchscreens
  346. on Atmel AT91 or AVR32 systems with an AC97C module.
  347. Be aware that this will use channel B in the controller for
  348. streaming data, this must not conflict with other AC97C drivers.
  349. If unsure, say N.
  350. To compile this driver as a module, choose M here: the module will
  351. be called atmel-wm97xx.
  352. config TOUCHSCREEN_WM97XX_MAINSTONE
  353. tristate "WM97xx Mainstone/Palm accelerated touch"
  354. depends on TOUCHSCREEN_WM97XX && ARCH_PXA
  355. help
  356. Say Y here for support for streaming mode with WM97xx touchscreens
  357. on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
  358. If unsure, say N.
  359. To compile this driver as a module, choose M here: the
  360. module will be called mainstone-wm97xx.
  361. config TOUCHSCREEN_WM97XX_ZYLONITE
  362. tristate "Zylonite accelerated touch"
  363. depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
  364. select TOUCHSCREEN_WM9713
  365. help
  366. Say Y here for support for streaming mode with the touchscreen
  367. on Zylonite systems.
  368. If unsure, say N.
  369. To compile this driver as a module, choose M here: the
  370. module will be called zylonite-wm97xx.
  371. config TOUCHSCREEN_USB_COMPOSITE
  372. tristate "USB Touchscreen Driver"
  373. depends on USB_ARCH_HAS_HCD
  374. select USB
  375. help
  376. USB Touchscreen driver for:
  377. - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
  378. - PanJit TouchSet USB
  379. - 3M MicroTouch USB (EX II series)
  380. - ITM
  381. - some other eTurboTouch
  382. - Gunze AHL61
  383. - DMC TSC-10/25
  384. - IRTOUCHSYSTEMS/UNITOP
  385. - IdealTEK URTC1000
  386. - GoTop Super_Q2/GogoPen/PenPower tablets
  387. - JASTEC USB Touch Controller/DigiTech DTR-02U
  388. - Zytronic controllers
  389. Have a look at <http://linux.chapter7.ch/touchkit/> for
  390. a usage description and the required user-space stuff.
  391. To compile this driver as a module, choose M here: the
  392. module will be called usbtouchscreen.
  393. config TOUCHSCREEN_MC13783
  394. tristate "Freescale MC13783 touchscreen input driver"
  395. depends on MFD_MC13783
  396. help
  397. Say Y here if you have an Freescale MC13783 PMIC on your
  398. board and want to use its touchscreen
  399. If unsure, say N.
  400. To compile this driver as a module, choose M here: the
  401. module will be called mc13783_ts.
  402. config TOUCHSCREEN_USB_EGALAX
  403. default y
  404. bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
  405. depends on TOUCHSCREEN_USB_COMPOSITE
  406. config TOUCHSCREEN_USB_PANJIT
  407. default y
  408. bool "PanJit device support" if EMBEDDED
  409. depends on TOUCHSCREEN_USB_COMPOSITE
  410. config TOUCHSCREEN_USB_3M
  411. default y
  412. bool "3M/Microtouch EX II series device support" if EMBEDDED
  413. depends on TOUCHSCREEN_USB_COMPOSITE
  414. config TOUCHSCREEN_USB_ITM
  415. default y
  416. bool "ITM device support" if EMBEDDED
  417. depends on TOUCHSCREEN_USB_COMPOSITE
  418. config TOUCHSCREEN_USB_ETURBO
  419. default y
  420. bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
  421. depends on TOUCHSCREEN_USB_COMPOSITE
  422. config TOUCHSCREEN_USB_GUNZE
  423. default y
  424. bool "Gunze AHL61 device support" if EMBEDDED
  425. depends on TOUCHSCREEN_USB_COMPOSITE
  426. config TOUCHSCREEN_USB_DMC_TSC10
  427. default y
  428. bool "DMC TSC-10/25 device support" if EMBEDDED
  429. depends on TOUCHSCREEN_USB_COMPOSITE
  430. config TOUCHSCREEN_USB_IRTOUCH
  431. default y
  432. bool "IRTOUCHSYSTEMS/UNITOP device support" if EMBEDDED
  433. depends on TOUCHSCREEN_USB_COMPOSITE
  434. config TOUCHSCREEN_USB_IDEALTEK
  435. default y
  436. bool "IdealTEK URTC1000 device support" if EMBEDDED
  437. depends on TOUCHSCREEN_USB_COMPOSITE
  438. config TOUCHSCREEN_USB_GENERAL_TOUCH
  439. default y
  440. bool "GeneralTouch Touchscreen device support" if EMBEDDED
  441. depends on TOUCHSCREEN_USB_COMPOSITE
  442. config TOUCHSCREEN_USB_GOTOP
  443. default y
  444. bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EMBEDDED
  445. depends on TOUCHSCREEN_USB_COMPOSITE
  446. config TOUCHSCREEN_USB_JASTEC
  447. default y
  448. bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EMBEDDED
  449. depends on TOUCHSCREEN_USB_COMPOSITE
  450. config TOUCHSCREEN_USB_E2I
  451. default y
  452. bool "e2i Touchscreen controller (e.g. from Mimo 740)"
  453. depends on TOUCHSCREEN_USB_COMPOSITE
  454. config TOUCHSCREEN_USB_ZYTRONIC
  455. default y
  456. bool "Zytronic controller" if EMBEDDED
  457. depends on TOUCHSCREEN_USB_COMPOSITE
  458. config TOUCHSCREEN_USB_ETT_TC45USB
  459. default y
  460. bool "ET&T USB series TC4UM/TC5UH touchscreen controler support" if EMBEDDED
  461. depends on TOUCHSCREEN_USB_COMPOSITE
  462. config TOUCHSCREEN_USB_NEXIO
  463. default y
  464. bool "NEXIO/iNexio device support" if EMBEDDED
  465. depends on TOUCHSCREEN_USB_COMPOSITE
  466. config TOUCHSCREEN_TOUCHIT213
  467. tristate "Sahara TouchIT-213 touchscreen"
  468. select SERIO
  469. help
  470. Say Y here if you have a Sahara TouchIT-213 Tablet PC.
  471. If unsure, say N.
  472. To compile this driver as a module, choose M here: the
  473. module will be called touchit213.
  474. config TOUCHSCREEN_TSC2007
  475. tristate "TSC2007 based touchscreens"
  476. depends on I2C
  477. help
  478. Say Y here if you have a TSC2007 based touchscreen.
  479. If unsure, say N.
  480. To compile this driver as a module, choose M here: the
  481. module will be called tsc2007.
  482. config TOUCHSCREEN_W90X900
  483. tristate "W90P910 touchscreen driver"
  484. depends on HAVE_CLK
  485. help
  486. Say Y here if you have a W90P910 based touchscreen.
  487. To compile this driver as a module, choose M here: the
  488. module will be called w90p910_ts.
  489. config TOUCHSCREEN_PCAP
  490. tristate "Motorola PCAP touchscreen"
  491. depends on EZX_PCAP
  492. help
  493. Say Y here if you have a Motorola EZX telephone and
  494. want to enable support for the built-in touchscreen.
  495. To compile this driver as a module, choose M here: the
  496. module will be called pcap_ts.
  497. config TOUCHSCREEN_TPS6507X
  498. tristate "TPS6507x based touchscreens"
  499. depends on I2C
  500. help
  501. Say Y here if you have a TPS6507x based touchscreen
  502. controller.
  503. If unsure, say N.
  504. To compile this driver as a module, choose M here: the
  505. module will be called tps6507x_ts.
  506. config TOUCHSCREEN_STMPE
  507. tristate "STMicroelectronics STMPE touchscreens"
  508. depends on MFD_STMPE
  509. help
  510. Say Y here if you want support for STMicroelectronics
  511. STMPE touchscreen controllers.
  512. To compile this driver as a module, choose M here: the
  513. module will be called stmpe-ts.
  514. endif