Kconfig 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757
  1. #
  2. # Touchscreen driver configuration
  3. #
  4. menuconfig INPUT_TOUCHSCREEN
  5. bool "Touchscreens"
  6. help
  7. Say Y here, and a list of supported touchscreens will be displayed.
  8. This option doesn't affect the kernel.
  9. If unsure, say Y.
  10. if INPUT_TOUCHSCREEN
  11. config TOUCHSCREEN_88PM860X
  12. tristate "Marvell 88PM860x touchscreen"
  13. depends on MFD_88PM860X
  14. help
  15. Say Y here if you have a 88PM860x PMIC and want to enable
  16. support for the built-in touchscreen.
  17. If unsure, say N.
  18. To compile this driver as a module, choose M here: the
  19. module will be called 88pm860x-ts.
  20. config TOUCHSCREEN_ADS7846
  21. tristate "ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens"
  22. depends on SPI_MASTER
  23. depends on HWMON = n || HWMON
  24. help
  25. Say Y here if you have a touchscreen interface using the
  26. ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
  27. and your board-specific setup code includes that in its
  28. table of SPI devices.
  29. If HWMON is selected, and the driver is told the reference voltage
  30. on your board, you will also get hwmon interfaces for the voltage
  31. (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
  32. If unsure, say N (but it's safe to say "Y").
  33. To compile this driver as a module, choose M here: the
  34. module will be called ads7846.
  35. config TOUCHSCREEN_AD7877
  36. tristate "AD7877 based touchscreens"
  37. depends on SPI_MASTER
  38. help
  39. Say Y here if you have a touchscreen interface using the
  40. AD7877 controller, and your board-specific initialization
  41. code includes that in its table of SPI devices.
  42. If unsure, say N (but it's safe to say "Y").
  43. To compile this driver as a module, choose M here: the
  44. module will be called ad7877.
  45. config TOUCHSCREEN_AD7879
  46. tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
  47. help
  48. Say Y here if you want to support a touchscreen interface using
  49. the AD7879-1/AD7889-1 controller.
  50. You should select a bus connection too.
  51. To compile this driver as a module, choose M here: the
  52. module will be called ad7879.
  53. config TOUCHSCREEN_AD7879_I2C
  54. tristate "support I2C bus connection"
  55. depends on TOUCHSCREEN_AD7879 && I2C
  56. help
  57. Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
  58. To compile this driver as a module, choose M here: the
  59. module will be called ad7879-i2c.
  60. config TOUCHSCREEN_AD7879_SPI
  61. tristate "support SPI bus connection"
  62. depends on TOUCHSCREEN_AD7879 && SPI_MASTER
  63. help
  64. Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
  65. If unsure, say N (but it's safe to say "Y").
  66. To compile this driver as a module, choose M here: the
  67. module will be called ad7879-spi.
  68. config TOUCHSCREEN_ATMEL_MXT
  69. tristate "Atmel mXT I2C Touchscreen"
  70. depends on I2C
  71. help
  72. Say Y here if you have Atmel mXT series I2C touchscreen,
  73. such as AT42QT602240/ATMXT224, connected to your system.
  74. If unsure, say N.
  75. To compile this driver as a module, choose M here: the
  76. module will be called atmel_mxt_ts.
  77. config TOUCHSCREEN_BITSY
  78. tristate "Compaq iPAQ H3600 (Bitsy) touchscreen"
  79. depends on SA1100_BITSY
  80. select SERIO
  81. help
  82. Say Y here if you have the h3600 (Bitsy) touchscreen.
  83. If unsure, say N.
  84. To compile this driver as a module, choose M here: the
  85. module will be called h3600_ts_input.
  86. config TOUCHSCREEN_BU21013
  87. tristate "BU21013 based touch panel controllers"
  88. depends on I2C
  89. help
  90. Say Y here if you have a bu21013 touchscreen connected to
  91. your system.
  92. If unsure, say N.
  93. To compile this driver as a module, choose M here: the
  94. module will be called bu21013_ts.
  95. config TOUCHSCREEN_CY8CTMG110
  96. tristate "cy8ctmg110 touchscreen"
  97. depends on I2C
  98. depends on GPIOLIB
  99. help
  100. Say Y here if you have a cy8ctmg110 capacitive touchscreen on
  101. an AAVA device.
  102. If unsure, say N.
  103. To compile this driver as a module, choose M here: the
  104. module will be called cy8ctmg110_ts.
  105. config TOUCHSCREEN_DA9034
  106. tristate "Touchscreen support for Dialog Semiconductor DA9034"
  107. depends on PMIC_DA903X
  108. default y
  109. help
  110. Say Y here to enable the support for the touchscreen found
  111. on Dialog Semiconductor DA9034 PMIC.
  112. config TOUCHSCREEN_DYNAPRO
  113. tristate "Dynapro serial touchscreen"
  114. select SERIO
  115. help
  116. Say Y here if you have a Dynapro serial touchscreen connected to
  117. your system.
  118. If unsure, say N.
  119. To compile this driver as a module, choose M here: the
  120. module will be called dynapro.
  121. config TOUCHSCREEN_HAMPSHIRE
  122. tristate "Hampshire serial touchscreen"
  123. select SERIO
  124. help
  125. Say Y here if you have a Hampshire serial touchscreen connected to
  126. your system.
  127. If unsure, say N.
  128. To compile this driver as a module, choose M here: the
  129. module will be called hampshire.
  130. config TOUCHSCREEN_EETI
  131. tristate "EETI touchscreen panel support"
  132. depends on I2C
  133. help
  134. Say Y here to enable support for I2C connected EETI touch panels.
  135. To compile this driver as a module, choose M here: the
  136. module will be called eeti_ts.
  137. config TOUCHSCREEN_EGALAX
  138. tristate "EETI eGalax multi-touch panel support"
  139. depends on I2C
  140. help
  141. Say Y here to enable support for I2C connected EETI
  142. eGalax multi-touch panels.
  143. To compile this driver as a module, choose M here: the
  144. module will be called egalax_ts.
  145. config TOUCHSCREEN_FUJITSU
  146. tristate "Fujitsu serial touchscreen"
  147. select SERIO
  148. help
  149. Say Y here if you have the Fujitsu touchscreen (such as one
  150. installed in Lifebook P series laptop) connected to your
  151. system.
  152. If unsure, say N.
  153. To compile this driver as a module, choose M here: the
  154. module will be called fujitsu-ts.
  155. config TOUCHSCREEN_S3C2410
  156. tristate "Samsung S3C2410/generic touchscreen input driver"
  157. depends on ARCH_S3C2410 || SAMSUNG_DEV_TS
  158. select S3C_ADC
  159. help
  160. Say Y here if you have the s3c2410 touchscreen.
  161. If unsure, say N.
  162. To compile this driver as a module, choose M here: the
  163. module will be called s3c2410_ts.
  164. config TOUCHSCREEN_GUNZE
  165. tristate "Gunze AHL-51S touchscreen"
  166. select SERIO
  167. help
  168. Say Y here if you have the Gunze AHL-51 touchscreen connected to
  169. your system.
  170. If unsure, say N.
  171. To compile this driver as a module, choose M here: the
  172. module will be called gunze.
  173. config TOUCHSCREEN_ELO
  174. tristate "Elo serial touchscreens"
  175. select SERIO
  176. help
  177. Say Y here if you have an Elo serial touchscreen connected to
  178. your system.
  179. If unsure, say N.
  180. To compile this driver as a module, choose M here: the
  181. module will be called elo.
  182. config TOUCHSCREEN_WACOM_W8001
  183. tristate "Wacom W8001 penabled serial touchscreen"
  184. select SERIO
  185. help
  186. Say Y here if you have an Wacom W8001 penabled serial touchscreen
  187. connected to your system.
  188. If unsure, say N.
  189. To compile this driver as a module, choose M here: the
  190. module will be called wacom_w8001.
  191. config TOUCHSCREEN_LPC32XX
  192. tristate "LPC32XX touchscreen controller"
  193. depends on ARCH_LPC32XX
  194. help
  195. Say Y here if you have a LPC32XX device and want
  196. to support the built-in touchscreen.
  197. To compile this driver as a module, choose M here: the
  198. module will be called lpc32xx_ts.
  199. config TOUCHSCREEN_MAX11801
  200. tristate "MAX11801 based touchscreens"
  201. depends on I2C
  202. help
  203. Say Y here if you have a MAX11801 based touchscreen
  204. controller.
  205. If unsure, say N.
  206. To compile this driver as a module, choose M here: the
  207. module will be called max11801_ts.
  208. config TOUCHSCREEN_MCS5000
  209. tristate "MELFAS MCS-5000 touchscreen"
  210. depends on I2C
  211. help
  212. Say Y here if you have the MELFAS MCS-5000 touchscreen controller
  213. 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 mcs5000_ts.
  217. config TOUCHSCREEN_MTOUCH
  218. tristate "MicroTouch serial touchscreens"
  219. select SERIO
  220. help
  221. Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
  222. your system.
  223. If unsure, say N.
  224. To compile this driver as a module, choose M here: the
  225. module will be called mtouch.
  226. config TOUCHSCREEN_INEXIO
  227. tristate "iNexio serial touchscreens"
  228. select SERIO
  229. help
  230. Say Y here if you have an iNexio serial touchscreen connected to
  231. your system.
  232. If unsure, say N.
  233. To compile this driver as a module, choose M here: the
  234. module will be called inexio.
  235. config TOUCHSCREEN_INTEL_MID
  236. tristate "Intel MID platform resistive touchscreen"
  237. depends on INTEL_SCU_IPC
  238. help
  239. Say Y here if you have a Intel MID based touchscreen in
  240. your system.
  241. If unsure, say N.
  242. To compile this driver as a module, choose M here: the
  243. module will be called intel_mid_touch.
  244. config TOUCHSCREEN_MK712
  245. tristate "ICS MicroClock MK712 touchscreen"
  246. help
  247. Say Y here if you have the ICS MicroClock MK712 touchscreen
  248. controller chip in your system.
  249. If unsure, say N.
  250. To compile this driver as a module, choose M here: the
  251. module will be called mk712.
  252. config TOUCHSCREEN_HP600
  253. tristate "HP Jornada 6xx touchscreen"
  254. depends on SH_HP6XX && SH_ADC
  255. help
  256. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  257. support the built-in touchscreen.
  258. To compile this driver as a module, choose M here: the
  259. module will be called hp680_ts_input.
  260. config TOUCHSCREEN_HP7XX
  261. tristate "HP Jornada 7xx touchscreen"
  262. depends on SA1100_JORNADA720_SSP
  263. help
  264. Say Y here if you have a HP Jornada 710/720/728 and want
  265. to support the built-in touchscreen.
  266. To compile this driver as a module, choose M here: the
  267. module will be called jornada720_ts.
  268. config TOUCHSCREEN_HTCPEN
  269. tristate "HTC Shift X9500 touchscreen"
  270. depends on ISA
  271. help
  272. Say Y here if you have an HTC Shift UMPC also known as HTC X9500
  273. Clio / Shangrila and want to support the built-in touchscreen.
  274. If unsure, say N.
  275. To compile this driver as a module, choose M here: the
  276. module will be called htcpen.
  277. config TOUCHSCREEN_PENMOUNT
  278. tristate "Penmount serial touchscreen"
  279. select SERIO
  280. help
  281. Say Y here if you have a Penmount 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 penmount.
  286. config TOUCHSCREEN_MIGOR
  287. tristate "Renesas MIGO-R touchscreen"
  288. depends on SH_MIGOR && I2C
  289. help
  290. Say Y here to enable MIGO-R touchscreen support.
  291. If unsure, say N.
  292. To compile this driver as a module, choose M here: the
  293. module will be called migor_ts.
  294. config TOUCHSCREEN_TNETV107X
  295. tristate "TI TNETV107X touchscreen support"
  296. depends on ARCH_DAVINCI_TNETV107X
  297. help
  298. Say Y here if you want to use the TNETV107X touchscreen.
  299. To compile this driver as a module, choose M here: the
  300. module will be called tnetv107x-ts.
  301. config TOUCHSCREEN_TOUCHRIGHT
  302. tristate "Touchright serial touchscreen"
  303. select SERIO
  304. help
  305. Say Y here if you have a Touchright serial touchscreen connected to
  306. your system.
  307. If unsure, say N.
  308. To compile this driver as a module, choose M here: the
  309. module will be called touchright.
  310. config TOUCHSCREEN_TOUCHWIN
  311. tristate "Touchwin serial touchscreen"
  312. select SERIO
  313. help
  314. Say Y here if you have a Touchwin 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 touchwin.
  319. config TOUCHSCREEN_ATMEL_TSADCC
  320. tristate "Atmel Touchscreen Interface"
  321. depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
  322. help
  323. Say Y here if you have a 4-wire touchscreen connected to the
  324. ADC Controller on your Atmel SoC (such as the AT91SAM9RL).
  325. If unsure, say N.
  326. To compile this driver as a module, choose M here: the
  327. module will be called atmel_tsadcc.
  328. config TOUCHSCREEN_UCB1400
  329. tristate "Philips UCB1400 touchscreen"
  330. depends on AC97_BUS
  331. depends on UCB1400_CORE
  332. help
  333. This enables support for the Philips UCB1400 touchscreen interface.
  334. The UCB1400 is an AC97 audio codec. The touchscreen interface
  335. will be initialized only after the ALSA subsystem has been
  336. brought up and the UCB1400 detected. You therefore have to
  337. configure ALSA support as well (either built-in or modular,
  338. independently of whether this driver is itself built-in or
  339. modular) for this driver to work.
  340. To compile this driver as a module, choose M here: the
  341. module will be called ucb1400_ts.
  342. config TOUCHSCREEN_WM831X
  343. tristate "Support for WM831x touchscreen controllers"
  344. depends on MFD_WM831X
  345. help
  346. This enables support for the touchscreen controller on the WM831x
  347. series of PMICs.
  348. To compile this driver as a module, choose M here: the
  349. module will be called wm831x-ts.
  350. config TOUCHSCREEN_WM97XX
  351. tristate "Support for WM97xx AC97 touchscreen controllers"
  352. depends on AC97_BUS
  353. help
  354. Say Y here if you have a Wolfson Microelectronics WM97xx
  355. touchscreen connected to your system. Note that this option
  356. only enables core driver, you will also need to select
  357. support for appropriate chip below.
  358. If unsure, say N.
  359. To compile this driver as a module, choose M here: the
  360. module will be called wm97xx-ts.
  361. config TOUCHSCREEN_WM9705
  362. bool "WM9705 Touchscreen interface support"
  363. depends on TOUCHSCREEN_WM97XX
  364. default y
  365. help
  366. Say Y here to enable support for the Wolfson Microelectronics
  367. WM9705 touchscreen controller.
  368. config TOUCHSCREEN_WM9712
  369. bool "WM9712 Touchscreen interface support"
  370. depends on TOUCHSCREEN_WM97XX
  371. default y
  372. help
  373. Say Y here to enable support for the Wolfson Microelectronics
  374. WM9712 touchscreen controller.
  375. config TOUCHSCREEN_WM9713
  376. bool "WM9713 Touchscreen interface support"
  377. depends on TOUCHSCREEN_WM97XX
  378. default y
  379. help
  380. Say Y here to enable support for the Wolfson Microelectronics
  381. WM9713 touchscreen controller.
  382. config TOUCHSCREEN_WM97XX_ATMEL
  383. tristate "WM97xx Atmel accelerated touch"
  384. depends on TOUCHSCREEN_WM97XX && (AVR32 || ARCH_AT91)
  385. help
  386. Say Y here for support for streaming mode with WM97xx touchscreens
  387. on Atmel AT91 or AVR32 systems with an AC97C module.
  388. Be aware that this will use channel B in the controller for
  389. streaming data, this must not conflict with other AC97C drivers.
  390. If unsure, say N.
  391. To compile this driver as a module, choose M here: the module will
  392. be called atmel-wm97xx.
  393. config TOUCHSCREEN_WM97XX_MAINSTONE
  394. tristate "WM97xx Mainstone/Palm accelerated touch"
  395. depends on TOUCHSCREEN_WM97XX && ARCH_PXA
  396. help
  397. Say Y here for support for streaming mode with WM97xx touchscreens
  398. on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
  399. If unsure, say N.
  400. To compile this driver as a module, choose M here: the
  401. module will be called mainstone-wm97xx.
  402. config TOUCHSCREEN_WM97XX_ZYLONITE
  403. tristate "Zylonite accelerated touch"
  404. depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
  405. select TOUCHSCREEN_WM9713
  406. help
  407. Say Y here for support for streaming mode with the touchscreen
  408. on Zylonite systems.
  409. If unsure, say N.
  410. To compile this driver as a module, choose M here: the
  411. module will be called zylonite-wm97xx.
  412. config TOUCHSCREEN_USB_COMPOSITE
  413. tristate "USB Touchscreen Driver"
  414. depends on USB_ARCH_HAS_HCD
  415. select USB
  416. help
  417. USB Touchscreen driver for:
  418. - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
  419. - PanJit TouchSet USB
  420. - 3M MicroTouch USB (EX II series)
  421. - ITM
  422. - some other eTurboTouch
  423. - Gunze AHL61
  424. - DMC TSC-10/25
  425. - IRTOUCHSYSTEMS/UNITOP
  426. - IdealTEK URTC1000
  427. - GoTop Super_Q2/GogoPen/PenPower tablets
  428. - JASTEC USB Touch Controller/DigiTech DTR-02U
  429. - Zytronic controllers
  430. - Elo TouchSystems 2700 IntelliTouch
  431. Have a look at <http://linux.chapter7.ch/touchkit/> for
  432. a usage description and the required user-space stuff.
  433. To compile this driver as a module, choose M here: the
  434. module will be called usbtouchscreen.
  435. config TOUCHSCREEN_MC13783
  436. tristate "Freescale MC13783 touchscreen input driver"
  437. depends on MFD_MC13783
  438. help
  439. Say Y here if you have an Freescale MC13783 PMIC on your
  440. board and want to use its touchscreen
  441. If unsure, say N.
  442. To compile this driver as a module, choose M here: the
  443. module will be called mc13783_ts.
  444. config TOUCHSCREEN_USB_EGALAX
  445. default y
  446. bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
  447. depends on TOUCHSCREEN_USB_COMPOSITE
  448. config TOUCHSCREEN_USB_PANJIT
  449. default y
  450. bool "PanJit device support" if EXPERT
  451. depends on TOUCHSCREEN_USB_COMPOSITE
  452. config TOUCHSCREEN_USB_3M
  453. default y
  454. bool "3M/Microtouch EX II series device support" if EXPERT
  455. depends on TOUCHSCREEN_USB_COMPOSITE
  456. config TOUCHSCREEN_USB_ITM
  457. default y
  458. bool "ITM device support" if EXPERT
  459. depends on TOUCHSCREEN_USB_COMPOSITE
  460. config TOUCHSCREEN_USB_ETURBO
  461. default y
  462. bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
  463. depends on TOUCHSCREEN_USB_COMPOSITE
  464. config TOUCHSCREEN_USB_GUNZE
  465. default y
  466. bool "Gunze AHL61 device support" if EXPERT
  467. depends on TOUCHSCREEN_USB_COMPOSITE
  468. config TOUCHSCREEN_USB_DMC_TSC10
  469. default y
  470. bool "DMC TSC-10/25 device support" if EXPERT
  471. depends on TOUCHSCREEN_USB_COMPOSITE
  472. config TOUCHSCREEN_USB_IRTOUCH
  473. default y
  474. bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
  475. depends on TOUCHSCREEN_USB_COMPOSITE
  476. config TOUCHSCREEN_USB_IDEALTEK
  477. default y
  478. bool "IdealTEK URTC1000 device support" if EXPERT
  479. depends on TOUCHSCREEN_USB_COMPOSITE
  480. config TOUCHSCREEN_USB_GENERAL_TOUCH
  481. default y
  482. bool "GeneralTouch Touchscreen device support" if EXPERT
  483. depends on TOUCHSCREEN_USB_COMPOSITE
  484. config TOUCHSCREEN_USB_GOTOP
  485. default y
  486. bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
  487. depends on TOUCHSCREEN_USB_COMPOSITE
  488. config TOUCHSCREEN_USB_JASTEC
  489. default y
  490. bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
  491. depends on TOUCHSCREEN_USB_COMPOSITE
  492. config TOUCHSCREEN_USB_ELO
  493. default y
  494. bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
  495. depends on TOUCHSCREEN_USB_COMPOSITE
  496. config TOUCHSCREEN_USB_E2I
  497. default y
  498. bool "e2i Touchscreen controller (e.g. from Mimo 740)"
  499. depends on TOUCHSCREEN_USB_COMPOSITE
  500. config TOUCHSCREEN_USB_ZYTRONIC
  501. default y
  502. bool "Zytronic controller" if EXPERT
  503. depends on TOUCHSCREEN_USB_COMPOSITE
  504. config TOUCHSCREEN_USB_ETT_TC45USB
  505. default y
  506. bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
  507. depends on TOUCHSCREEN_USB_COMPOSITE
  508. config TOUCHSCREEN_USB_NEXIO
  509. default y
  510. bool "NEXIO/iNexio device support" if EXPERT
  511. depends on TOUCHSCREEN_USB_COMPOSITE
  512. config TOUCHSCREEN_TOUCHIT213
  513. tristate "Sahara TouchIT-213 touchscreen"
  514. select SERIO
  515. help
  516. Say Y here if you have a Sahara TouchIT-213 Tablet PC.
  517. If unsure, say N.
  518. To compile this driver as a module, choose M here: the
  519. module will be called touchit213.
  520. config TOUCHSCREEN_TSC_SERIO
  521. tristate "TSC-10/25/40 serial touchscreen support"
  522. select SERIO
  523. help
  524. Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
  525. to your system.
  526. If unsure, say N.
  527. To compile this driver as a module, choose M here: the
  528. module will be called tsc40.
  529. config TOUCHSCREEN_TSC2005
  530. tristate "TSC2005 based touchscreens"
  531. depends on SPI_MASTER && GENERIC_HARDIRQS
  532. help
  533. Say Y here if you have a TSC2005 based touchscreen.
  534. If unsure, say N.
  535. To compile this driver as a module, choose M here: the
  536. module will be called tsc2005.
  537. config TOUCHSCREEN_TSC2007
  538. tristate "TSC2007 based touchscreens"
  539. depends on I2C
  540. help
  541. Say Y here if you have a TSC2007 based touchscreen.
  542. If unsure, say N.
  543. To compile this driver as a module, choose M here: the
  544. module will be called tsc2007.
  545. config TOUCHSCREEN_W90X900
  546. tristate "W90P910 touchscreen driver"
  547. depends on HAVE_CLK
  548. help
  549. Say Y here if you have a W90P910 based touchscreen.
  550. To compile this driver as a module, choose M here: the
  551. module will be called w90p910_ts.
  552. config TOUCHSCREEN_PCAP
  553. tristate "Motorola PCAP touchscreen"
  554. depends on EZX_PCAP
  555. help
  556. Say Y here if you have a Motorola EZX telephone and
  557. want to enable support for the built-in touchscreen.
  558. To compile this driver as a module, choose M here: the
  559. module will be called pcap_ts.
  560. config TOUCHSCREEN_ST1232
  561. tristate "Sitronix ST1232 touchscreen controllers"
  562. depends on I2C
  563. help
  564. Say Y here if you want to support Sitronix ST1232
  565. touchscreen controller.
  566. If unsure, say N.
  567. To compile this driver as a module, choose M here: the
  568. module will be called st1232_ts.
  569. config TOUCHSCREEN_STMPE
  570. tristate "STMicroelectronics STMPE touchscreens"
  571. depends on MFD_STMPE
  572. help
  573. Say Y here if you want support for STMicroelectronics
  574. STMPE touchscreen controllers.
  575. To compile this driver as a module, choose M here: the
  576. module will be called stmpe-ts.
  577. config TOUCHSCREEN_TPS6507X
  578. tristate "TPS6507x based touchscreens"
  579. depends on I2C
  580. help
  581. Say Y here if you have a TPS6507x based touchscreen
  582. controller.
  583. If unsure, say N.
  584. To compile this driver as a module, choose M here: the
  585. module will be called tps6507x_ts.
  586. endif