Kconfig 33 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218
  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_PROPERTIES
  12. def_tristate INPUT
  13. depends on INPUT
  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_ATMEL_MXT_T37
  91. bool "Support T37 Diagnostic Data"
  92. depends on TOUCHSCREEN_ATMEL_MXT
  93. depends on VIDEO_V4L2=y || (TOUCHSCREEN_ATMEL_MXT=m && VIDEO_V4L2=m)
  94. select VIDEOBUF2_VMALLOC
  95. help
  96. Say Y here if you want support to output data from the T37
  97. Diagnostic Data object using a V4L device.
  98. config TOUCHSCREEN_AUO_PIXCIR
  99. tristate "AUO in-cell touchscreen using Pixcir ICs"
  100. depends on I2C
  101. depends on GPIOLIB || COMPILE_TEST
  102. help
  103. Say Y here if you have a AUO display with in-cell touchscreen
  104. using Pixcir ICs.
  105. If unsure, say N.
  106. To compile this driver as a module, choose M here: the
  107. module will be called auo-pixcir-ts.
  108. config TOUCHSCREEN_BU21013
  109. tristate "BU21013 based touch panel controllers"
  110. depends on I2C
  111. help
  112. Say Y here if you have a bu21013 touchscreen connected to
  113. your system.
  114. If unsure, say N.
  115. To compile this driver as a module, choose M here: the
  116. module will be called bu21013_ts.
  117. config TOUCHSCREEN_CHIPONE_ICN8318
  118. tristate "chipone icn8318 touchscreen controller"
  119. depends on GPIOLIB || COMPILE_TEST
  120. depends on I2C
  121. depends on OF
  122. help
  123. Say Y here if you have a ChipOne icn8318 based I2C touchscreen.
  124. If unsure, say N.
  125. To compile this driver as a module, choose M here: the
  126. module will be called chipone_icn8318.
  127. config TOUCHSCREEN_CY8CTMG110
  128. tristate "cy8ctmg110 touchscreen"
  129. depends on I2C
  130. depends on GPIOLIB || COMPILE_TEST
  131. help
  132. Say Y here if you have a cy8ctmg110 capacitive touchscreen on
  133. an AAVA device.
  134. If unsure, say N.
  135. To compile this driver as a module, choose M here: the
  136. module will be called cy8ctmg110_ts.
  137. config TOUCHSCREEN_CYTTSP_CORE
  138. tristate "Cypress TTSP touchscreen"
  139. help
  140. Say Y here if you have a touchscreen using controller from
  141. the Cypress TrueTouch(tm) Standard Product family connected
  142. to your system. You will also need to select appropriate
  143. bus connection below.
  144. If unsure, say N.
  145. To compile this driver as a module, choose M here: the
  146. module will be called cyttsp_core.
  147. config TOUCHSCREEN_CYTTSP_I2C
  148. tristate "support I2C bus connection"
  149. depends on TOUCHSCREEN_CYTTSP_CORE && I2C
  150. help
  151. Say Y here if the touchscreen is connected via I2C bus.
  152. To compile this driver as a module, choose M here: the
  153. module will be called cyttsp_i2c.
  154. config TOUCHSCREEN_CYTTSP_SPI
  155. tristate "support SPI bus connection"
  156. depends on TOUCHSCREEN_CYTTSP_CORE && SPI_MASTER
  157. help
  158. Say Y here if the touchscreen is connected via SPI bus.
  159. To compile this driver as a module, choose M here: the
  160. module will be called cyttsp_spi.
  161. config TOUCHSCREEN_CYTTSP4_CORE
  162. tristate "Cypress TrueTouch Gen4 Touchscreen Driver"
  163. help
  164. Core driver for Cypress TrueTouch(tm) Standard Product
  165. Generation4 touchscreen controllers.
  166. Say Y here if you have a Cypress Gen4 touchscreen.
  167. If unsure, say N.
  168. To compile this driver as a module, choose M here.
  169. config TOUCHSCREEN_CYTTSP4_I2C
  170. tristate "support I2C bus connection"
  171. depends on TOUCHSCREEN_CYTTSP4_CORE && I2C
  172. help
  173. Say Y here if the touchscreen is connected via I2C bus.
  174. To compile this driver as a module, choose M here: the
  175. module will be called cyttsp4_i2c.
  176. config TOUCHSCREEN_CYTTSP4_SPI
  177. tristate "support SPI bus connection"
  178. depends on TOUCHSCREEN_CYTTSP4_CORE && SPI_MASTER
  179. help
  180. Say Y here if the touchscreen is connected via SPI bus.
  181. To compile this driver as a module, choose M here: the
  182. module will be called cyttsp4_spi.
  183. config TOUCHSCREEN_DA9034
  184. tristate "Touchscreen support for Dialog Semiconductor DA9034"
  185. depends on PMIC_DA903X
  186. default y
  187. help
  188. Say Y here to enable the support for the touchscreen found
  189. on Dialog Semiconductor DA9034 PMIC.
  190. If unsure, say N.
  191. To compile this driver as a module, choose M here: the
  192. module will be called da9034-ts.
  193. config TOUCHSCREEN_DA9052
  194. tristate "Dialog DA9052/DA9053 TSI"
  195. depends on PMIC_DA9052
  196. help
  197. Say Y here to support the touchscreen found on Dialog Semiconductor
  198. DA9052-BC and DA9053-AA/Bx PMICs.
  199. If unsure, say N.
  200. To compile this driver as a module, choose M here: the
  201. module will be called da9052_tsi.
  202. config TOUCHSCREEN_DYNAPRO
  203. tristate "Dynapro serial touchscreen"
  204. select SERIO
  205. help
  206. Say Y here if you have a Dynapro serial touchscreen connected to
  207. your system.
  208. If unsure, say N.
  209. To compile this driver as a module, choose M here: the
  210. module will be called dynapro.
  211. config TOUCHSCREEN_HAMPSHIRE
  212. tristate "Hampshire serial touchscreen"
  213. select SERIO
  214. help
  215. Say Y here if you have a Hampshire serial touchscreen connected to
  216. your system.
  217. If unsure, say N.
  218. To compile this driver as a module, choose M here: the
  219. module will be called hampshire.
  220. config TOUCHSCREEN_EETI
  221. tristate "EETI touchscreen panel support"
  222. depends on I2C
  223. help
  224. Say Y here to enable support for I2C connected EETI touch panels.
  225. To compile this driver as a module, choose M here: the
  226. module will be called eeti_ts.
  227. config TOUCHSCREEN_EGALAX
  228. tristate "EETI eGalax multi-touch panel support"
  229. depends on I2C && OF
  230. help
  231. Say Y here to enable support for I2C connected EETI
  232. eGalax multi-touch panels.
  233. To compile this driver as a module, choose M here: the
  234. module will be called egalax_ts.
  235. config TOUCHSCREEN_EGALAX_SERIAL
  236. tristate "EETI eGalax serial touchscreen"
  237. select SERIO
  238. help
  239. Say Y here to enable support for serial connected EETI
  240. eGalax touch panels.
  241. To compile this driver as a module, choose M here: the
  242. module will be called egalax_ts_serial.
  243. config TOUCHSCREEN_FUJITSU
  244. tristate "Fujitsu serial touchscreen"
  245. select SERIO
  246. help
  247. Say Y here if you have the Fujitsu touchscreen (such as one
  248. installed in Lifebook P series laptop) connected to your
  249. system.
  250. If unsure, say N.
  251. To compile this driver as a module, choose M here: the
  252. module will be called fujitsu-ts.
  253. config TOUCHSCREEN_GOODIX
  254. tristate "Goodix I2C touchscreen"
  255. depends on I2C
  256. depends on GPIOLIB || COMPILE_TEST
  257. help
  258. Say Y here if you have the Goodix touchscreen (such as one
  259. installed in Onda v975w tablets) connected to your
  260. system. It also supports 5-finger chip models, which can be
  261. found on ARM tablets, like Wexler TAB7200 and MSI Primo73.
  262. If unsure, say N.
  263. To compile this driver as a module, choose M here: the
  264. module will be called goodix.
  265. config TOUCHSCREEN_ILI210X
  266. tristate "Ilitek ILI210X based touchscreen"
  267. depends on I2C
  268. help
  269. Say Y here if you have a ILI210X based touchscreen
  270. controller. This driver supports models ILI2102,
  271. ILI2102s, ILI2103, ILI2103s and ILI2105.
  272. Such kind of chipsets can be found in Amazon Kindle Fire
  273. touchscreens.
  274. If unsure, say N.
  275. To compile this driver as a module, choose M here: the
  276. module will be called ili210x.
  277. config TOUCHSCREEN_IPROC
  278. tristate "IPROC touch panel driver support"
  279. depends on ARCH_BCM_IPROC || COMPILE_TEST
  280. help
  281. Say Y here if you want to add support for the IPROC touch
  282. controller to your system.
  283. If unsure, say N.
  284. To compile this driver as a module, choose M here: the
  285. module will be called bcm_iproc_tsc.
  286. config TOUCHSCREEN_S3C2410
  287. tristate "Samsung S3C2410/generic touchscreen input driver"
  288. depends on ARCH_S3C24XX || SAMSUNG_DEV_TS
  289. depends on S3C_ADC
  290. help
  291. Say Y here if you have the s3c2410 touchscreen.
  292. If unsure, say N.
  293. To compile this driver as a module, choose M here: the
  294. module will be called s3c2410_ts.
  295. config TOUCHSCREEN_GUNZE
  296. tristate "Gunze AHL-51S touchscreen"
  297. select SERIO
  298. help
  299. Say Y here if you have the Gunze AHL-51 touchscreen connected to
  300. your system.
  301. If unsure, say N.
  302. To compile this driver as a module, choose M here: the
  303. module will be called gunze.
  304. config TOUCHSCREEN_EKTF2127
  305. tristate "Elan eKTF2127 I2C touchscreen"
  306. depends on I2C
  307. help
  308. Say Y here if you have an Elan eKTF2127 touchscreen
  309. connected to your system.
  310. If unsure, say N.
  311. To compile this driver as a module, choose M here: the
  312. module will be called ektf2127.
  313. config TOUCHSCREEN_ELAN
  314. tristate "Elan eKTH I2C touchscreen"
  315. depends on I2C
  316. help
  317. Say Y here if you have an Elan eKTH I2C touchscreen
  318. connected to your system.
  319. If unsure, say N.
  320. To compile this driver as a module, choose M here: the
  321. module will be called elants_i2c.
  322. config TOUCHSCREEN_ELO
  323. tristate "Elo serial touchscreens"
  324. select SERIO
  325. help
  326. Say Y here if you have an Elo serial touchscreen connected to
  327. your system.
  328. If unsure, say N.
  329. To compile this driver as a module, choose M here: the
  330. module will be called elo.
  331. config TOUCHSCREEN_WACOM_W8001
  332. tristate "Wacom W8001 penabled serial touchscreen"
  333. select SERIO
  334. help
  335. Say Y here if you have an Wacom W8001 penabled serial touchscreen
  336. connected to your system.
  337. If unsure, say N.
  338. To compile this driver as a module, choose M here: the
  339. module will be called wacom_w8001.
  340. config TOUCHSCREEN_WACOM_I2C
  341. tristate "Wacom Tablet support (I2C)"
  342. depends on I2C
  343. help
  344. Say Y here if you want to use the I2C version of the Wacom
  345. Pen Tablet.
  346. If unsure, say N.
  347. To compile this driver as a module, choose M here: the module
  348. will be called wacom_i2c.
  349. config TOUCHSCREEN_LPC32XX
  350. tristate "LPC32XX touchscreen controller"
  351. depends on ARCH_LPC32XX
  352. help
  353. Say Y here if you have a LPC32XX device and want
  354. to support the built-in touchscreen.
  355. To compile this driver as a module, choose M here: the
  356. module will be called lpc32xx_ts.
  357. config TOUCHSCREEN_MAX11801
  358. tristate "MAX11801 based touchscreens"
  359. depends on I2C
  360. help
  361. Say Y here if you have a MAX11801 based touchscreen
  362. controller.
  363. If unsure, say N.
  364. To compile this driver as a module, choose M here: the
  365. module will be called max11801_ts.
  366. config TOUCHSCREEN_MCS5000
  367. tristate "MELFAS MCS-5000 touchscreen"
  368. depends on I2C
  369. help
  370. Say Y here if you have the MELFAS MCS-5000 touchscreen controller
  371. chip in your system.
  372. If unsure, say N.
  373. To compile this driver as a module, choose M here: the
  374. module will be called mcs5000_ts.
  375. config TOUCHSCREEN_MMS114
  376. tristate "MELFAS MMS114 touchscreen"
  377. depends on I2C
  378. help
  379. Say Y here if you have the MELFAS MMS114 touchscreen controller
  380. chip in your system.
  381. If unsure, say N.
  382. To compile this driver as a module, choose M here: the
  383. module will be called mms114.
  384. config TOUCHSCREEN_MELFAS_MIP4
  385. tristate "MELFAS MIP4 Touchscreen"
  386. depends on I2C
  387. help
  388. Say Y here if you have a MELFAS MIP4 Touchscreen device.
  389. If unsure, say N.
  390. To compile this driver as a module, choose M here:
  391. the module will be called melfas_mip4.
  392. config TOUCHSCREEN_MTOUCH
  393. tristate "MicroTouch serial touchscreens"
  394. select SERIO
  395. help
  396. Say Y here if you have a MicroTouch (3M) serial touchscreen connected to
  397. your system.
  398. If unsure, say N.
  399. To compile this driver as a module, choose M here: the
  400. module will be called mtouch.
  401. config TOUCHSCREEN_IMX6UL_TSC
  402. tristate "Freescale i.MX6UL touchscreen controller"
  403. depends on (OF && GPIOLIB) || COMPILE_TEST
  404. help
  405. Say Y here if you have a Freescale i.MX6UL, and want to
  406. use the internal touchscreen controller.
  407. If unsure, say N.
  408. To compile this driver as a module, choose M here: the
  409. module will be called imx6ul_tsc.
  410. config TOUCHSCREEN_INEXIO
  411. tristate "iNexio serial touchscreens"
  412. select SERIO
  413. help
  414. Say Y here if you have an iNexio serial touchscreen connected to
  415. your system.
  416. If unsure, say N.
  417. To compile this driver as a module, choose M here: the
  418. module will be called inexio.
  419. config TOUCHSCREEN_INTEL_MID
  420. tristate "Intel MID platform resistive touchscreen"
  421. depends on INTEL_SCU_IPC
  422. help
  423. Say Y here if you have a Intel MID based touchscreen in
  424. your system.
  425. If unsure, say N.
  426. To compile this driver as a module, choose M here: the
  427. module will be called intel_mid_touch.
  428. config TOUCHSCREEN_MK712
  429. tristate "ICS MicroClock MK712 touchscreen"
  430. help
  431. Say Y here if you have the ICS MicroClock MK712 touchscreen
  432. controller chip in your system.
  433. If unsure, say N.
  434. To compile this driver as a module, choose M here: the
  435. module will be called mk712.
  436. config TOUCHSCREEN_HP600
  437. tristate "HP Jornada 6xx touchscreen"
  438. depends on SH_HP6XX && SH_ADC
  439. help
  440. Say Y here if you have a HP Jornada 620/660/680/690 and want to
  441. support the built-in touchscreen.
  442. To compile this driver as a module, choose M here: the
  443. module will be called hp680_ts_input.
  444. config TOUCHSCREEN_HP7XX
  445. tristate "HP Jornada 7xx touchscreen"
  446. depends on SA1100_JORNADA720_SSP
  447. help
  448. Say Y here if you have a HP Jornada 710/720/728 and want
  449. to support the built-in touchscreen.
  450. To compile this driver as a module, choose M here: the
  451. module will be called jornada720_ts.
  452. config TOUCHSCREEN_IPAQ_MICRO
  453. tristate "HP iPAQ Atmel Micro ASIC touchscreen"
  454. depends on MFD_IPAQ_MICRO
  455. help
  456. Say Y here to enable support for the touchscreen attached to
  457. the Atmel Micro peripheral controller on iPAQ h3100/h3600/h3700
  458. If unsure, say N.
  459. To compile this driver as a module, choose M here: the
  460. module will be called ipaq-micro-ts.
  461. config TOUCHSCREEN_HTCPEN
  462. tristate "HTC Shift X9500 touchscreen"
  463. depends on ISA
  464. help
  465. Say Y here if you have an HTC Shift UMPC also known as HTC X9500
  466. Clio / Shangrila and want to support the built-in touchscreen.
  467. If unsure, say N.
  468. To compile this driver as a module, choose M here: the
  469. module will be called htcpen.
  470. config TOUCHSCREEN_PENMOUNT
  471. tristate "Penmount serial touchscreen"
  472. select SERIO
  473. help
  474. Say Y here if you have a Penmount serial touchscreen connected to
  475. your system.
  476. If unsure, say N.
  477. To compile this driver as a module, choose M here: the
  478. module will be called penmount.
  479. config TOUCHSCREEN_EDT_FT5X06
  480. tristate "EDT FocalTech FT5x06 I2C Touchscreen support"
  481. depends on I2C
  482. help
  483. Say Y here if you have an EDT "Polytouch" touchscreen based
  484. on the FocalTech FT5x06 family of controllers connected to
  485. your system.
  486. If unsure, say N.
  487. To compile this driver as a module, choose M here: the
  488. module will be called edt-ft5x06.
  489. config TOUCHSCREEN_MIGOR
  490. tristate "Renesas MIGO-R touchscreen"
  491. depends on (SH_MIGOR || COMPILE_TEST) && I2C
  492. help
  493. Say Y here to enable MIGO-R touchscreen support.
  494. If unsure, say N.
  495. To compile this driver as a module, choose M here: the
  496. module will be called migor_ts.
  497. config TOUCHSCREEN_TOUCHRIGHT
  498. tristate "Touchright serial touchscreen"
  499. select SERIO
  500. help
  501. Say Y here if you have a Touchright serial touchscreen connected to
  502. your system.
  503. If unsure, say N.
  504. To compile this driver as a module, choose M here: the
  505. module will be called touchright.
  506. config TOUCHSCREEN_TOUCHWIN
  507. tristate "Touchwin serial touchscreen"
  508. select SERIO
  509. help
  510. Say Y here if you have a Touchwin serial touchscreen connected to
  511. your system.
  512. If unsure, say N.
  513. To compile this driver as a module, choose M here: the
  514. module will be called touchwin.
  515. config TOUCHSCREEN_TI_AM335X_TSC
  516. tristate "TI Touchscreen Interface"
  517. depends on MFD_TI_AM335X_TSCADC
  518. help
  519. Say Y here if you have 4/5/8 wire touchscreen controller
  520. to be connected to the ADC controller on your TI AM335x SoC.
  521. If unsure, say N.
  522. To compile this driver as a module, choose M here: the
  523. module will be called ti_am335x_tsc.
  524. config TOUCHSCREEN_UCB1400
  525. tristate "Philips UCB1400 touchscreen"
  526. depends on AC97_BUS
  527. depends on UCB1400_CORE
  528. help
  529. This enables support for the Philips UCB1400 touchscreen interface.
  530. The UCB1400 is an AC97 audio codec. The touchscreen interface
  531. will be initialized only after the ALSA subsystem has been
  532. brought up and the UCB1400 detected. You therefore have to
  533. configure ALSA support as well (either built-in or modular,
  534. independently of whether this driver is itself built-in or
  535. modular) for this driver to work.
  536. To compile this driver as a module, choose M here: the
  537. module will be called ucb1400_ts.
  538. config TOUCHSCREEN_PIXCIR
  539. tristate "PIXCIR I2C touchscreens"
  540. depends on I2C
  541. help
  542. Say Y here if you have a pixcir i2c touchscreen
  543. controller.
  544. If unsure, say N.
  545. To compile this driver as a module, choose M here: the
  546. module will be called pixcir_i2c_ts.
  547. config TOUCHSCREEN_WDT87XX_I2C
  548. tristate "Weida HiTech I2C touchscreen"
  549. depends on I2C
  550. help
  551. Say Y here if you have a Weida WDT87XX I2C touchscreen
  552. connected to your system.
  553. If unsure, say N.
  554. To compile this driver as a module, choose M here: the
  555. module will be called wdt87xx_i2c.
  556. config TOUCHSCREEN_WM831X
  557. tristate "Support for WM831x touchscreen controllers"
  558. depends on MFD_WM831X
  559. help
  560. This enables support for the touchscreen controller on the WM831x
  561. series of PMICs.
  562. To compile this driver as a module, choose M here: the
  563. module will be called wm831x-ts.
  564. config TOUCHSCREEN_WM97XX
  565. tristate "Support for WM97xx AC97 touchscreen controllers"
  566. depends on AC97_BUS
  567. help
  568. Say Y here if you have a Wolfson Microelectronics WM97xx
  569. touchscreen connected to your system. Note that this option
  570. only enables core driver, you will also need to select
  571. support for appropriate chip below.
  572. If unsure, say N.
  573. To compile this driver as a module, choose M here: the
  574. module will be called wm97xx-ts.
  575. config TOUCHSCREEN_WM9705
  576. bool "WM9705 Touchscreen interface support"
  577. depends on TOUCHSCREEN_WM97XX
  578. default y
  579. help
  580. Say Y here to enable support for the Wolfson Microelectronics
  581. WM9705 touchscreen controller.
  582. config TOUCHSCREEN_WM9712
  583. bool "WM9712 Touchscreen interface support"
  584. depends on TOUCHSCREEN_WM97XX
  585. default y
  586. help
  587. Say Y here to enable support for the Wolfson Microelectronics
  588. WM9712 touchscreen controller.
  589. config TOUCHSCREEN_WM9713
  590. bool "WM9713 Touchscreen interface support"
  591. depends on TOUCHSCREEN_WM97XX
  592. default y
  593. help
  594. Say Y here to enable support for the Wolfson Microelectronics
  595. WM9713 touchscreen controller.
  596. config TOUCHSCREEN_WM97XX_ATMEL
  597. tristate "WM97xx Atmel accelerated touch"
  598. depends on TOUCHSCREEN_WM97XX && AVR32
  599. help
  600. Say Y here for support for streaming mode with WM97xx touchscreens
  601. on Atmel AT91 or AVR32 systems with an AC97C module.
  602. Be aware that this will use channel B in the controller for
  603. streaming data, this must not conflict with other AC97C drivers.
  604. If unsure, say N.
  605. To compile this driver as a module, choose M here: the module will
  606. be called atmel-wm97xx.
  607. config TOUCHSCREEN_WM97XX_MAINSTONE
  608. tristate "WM97xx Mainstone/Palm accelerated touch"
  609. depends on TOUCHSCREEN_WM97XX && ARCH_PXA
  610. help
  611. Say Y here for support for streaming mode with WM97xx touchscreens
  612. on Mainstone, Palm Tungsten T5, TX and LifeDrive systems.
  613. If unsure, say N.
  614. To compile this driver as a module, choose M here: the
  615. module will be called mainstone-wm97xx.
  616. config TOUCHSCREEN_WM97XX_ZYLONITE
  617. tristate "Zylonite accelerated touch"
  618. depends on TOUCHSCREEN_WM97XX && MACH_ZYLONITE
  619. select TOUCHSCREEN_WM9713
  620. help
  621. Say Y here for support for streaming mode with the touchscreen
  622. on Zylonite systems.
  623. If unsure, say N.
  624. To compile this driver as a module, choose M here: the
  625. module will be called zylonite-wm97xx.
  626. config TOUCHSCREEN_USB_COMPOSITE
  627. tristate "USB Touchscreen Driver"
  628. depends on USB_ARCH_HAS_HCD
  629. select USB
  630. help
  631. USB Touchscreen driver for:
  632. - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
  633. - PanJit TouchSet USB
  634. - 3M MicroTouch USB (EX II series)
  635. - ITM
  636. - some other eTurboTouch
  637. - Gunze AHL61
  638. - DMC TSC-10/25
  639. - IRTOUCHSYSTEMS/UNITOP
  640. - IdealTEK URTC1000
  641. - GoTop Super_Q2/GogoPen/PenPower tablets
  642. - JASTEC USB Touch Controller/DigiTech DTR-02U
  643. - Zytronic controllers
  644. - Elo TouchSystems 2700 IntelliTouch
  645. - EasyTouch USB Touch Controller from Data Modul
  646. - e2i (Mimo monitors)
  647. Have a look at <http://linux.chapter7.ch/touchkit/> for
  648. a usage description and the required user-space stuff.
  649. To compile this driver as a module, choose M here: the
  650. module will be called usbtouchscreen.
  651. config TOUCHSCREEN_MX25
  652. tristate "Freescale i.MX25 touchscreen input driver"
  653. depends on MFD_MX25_TSADC
  654. help
  655. Enable support for touchscreen connected to your i.MX25.
  656. To compile this driver as a module, choose M here: the
  657. module will be called fsl-imx25-tcq.
  658. config TOUCHSCREEN_MC13783
  659. tristate "Freescale MC13783 touchscreen input driver"
  660. depends on MFD_MC13XXX
  661. help
  662. Say Y here if you have an Freescale MC13783 PMIC on your
  663. board and want to use its touchscreen
  664. If unsure, say N.
  665. To compile this driver as a module, choose M here: the
  666. module will be called mc13783_ts.
  667. config TOUCHSCREEN_USB_EGALAX
  668. default y
  669. bool "eGalax, eTurboTouch CT-410/510/700 device support" if EXPERT
  670. depends on TOUCHSCREEN_USB_COMPOSITE
  671. config TOUCHSCREEN_USB_PANJIT
  672. default y
  673. bool "PanJit device support" if EXPERT
  674. depends on TOUCHSCREEN_USB_COMPOSITE
  675. config TOUCHSCREEN_USB_3M
  676. default y
  677. bool "3M/Microtouch EX II series device support" if EXPERT
  678. depends on TOUCHSCREEN_USB_COMPOSITE
  679. config TOUCHSCREEN_USB_ITM
  680. default y
  681. bool "ITM device support" if EXPERT
  682. depends on TOUCHSCREEN_USB_COMPOSITE
  683. config TOUCHSCREEN_USB_ETURBO
  684. default y
  685. bool "eTurboTouch (non-eGalax compatible) device support" if EXPERT
  686. depends on TOUCHSCREEN_USB_COMPOSITE
  687. config TOUCHSCREEN_USB_GUNZE
  688. default y
  689. bool "Gunze AHL61 device support" if EXPERT
  690. depends on TOUCHSCREEN_USB_COMPOSITE
  691. config TOUCHSCREEN_USB_DMC_TSC10
  692. default y
  693. bool "DMC TSC-10/25 device support" if EXPERT
  694. depends on TOUCHSCREEN_USB_COMPOSITE
  695. config TOUCHSCREEN_USB_IRTOUCH
  696. default y
  697. bool "IRTOUCHSYSTEMS/UNITOP device support" if EXPERT
  698. depends on TOUCHSCREEN_USB_COMPOSITE
  699. config TOUCHSCREEN_USB_IDEALTEK
  700. default y
  701. bool "IdealTEK URTC1000 device support" if EXPERT
  702. depends on TOUCHSCREEN_USB_COMPOSITE
  703. config TOUCHSCREEN_USB_GENERAL_TOUCH
  704. default y
  705. bool "GeneralTouch Touchscreen device support" if EXPERT
  706. depends on TOUCHSCREEN_USB_COMPOSITE
  707. config TOUCHSCREEN_USB_GOTOP
  708. default y
  709. bool "GoTop Super_Q2/GogoPen/PenPower tablet device support" if EXPERT
  710. depends on TOUCHSCREEN_USB_COMPOSITE
  711. config TOUCHSCREEN_USB_JASTEC
  712. default y
  713. bool "JASTEC/DigiTech DTR-02U USB touch controller device support" if EXPERT
  714. depends on TOUCHSCREEN_USB_COMPOSITE
  715. config TOUCHSCREEN_USB_ELO
  716. default y
  717. bool "Elo TouchSystems 2700 IntelliTouch controller device support" if EXPERT
  718. depends on TOUCHSCREEN_USB_COMPOSITE
  719. config TOUCHSCREEN_USB_E2I
  720. default y
  721. bool "e2i Touchscreen controller (e.g. from Mimo 740)" if EXPERT
  722. depends on TOUCHSCREEN_USB_COMPOSITE
  723. config TOUCHSCREEN_USB_ZYTRONIC
  724. default y
  725. bool "Zytronic controller" if EXPERT
  726. depends on TOUCHSCREEN_USB_COMPOSITE
  727. config TOUCHSCREEN_USB_ETT_TC45USB
  728. default y
  729. bool "ET&T USB series TC4UM/TC5UH touchscreen controller support" if EXPERT
  730. depends on TOUCHSCREEN_USB_COMPOSITE
  731. config TOUCHSCREEN_USB_NEXIO
  732. default y
  733. bool "NEXIO/iNexio device support" if EXPERT
  734. depends on TOUCHSCREEN_USB_COMPOSITE
  735. config TOUCHSCREEN_USB_EASYTOUCH
  736. default y
  737. bool "EasyTouch USB Touch controller device support" if EMBEDDED
  738. depends on TOUCHSCREEN_USB_COMPOSITE
  739. help
  740. Say Y here if you have an EasyTouch USB Touch controller.
  741. If unsure, say N.
  742. config TOUCHSCREEN_TOUCHIT213
  743. tristate "Sahara TouchIT-213 touchscreen"
  744. select SERIO
  745. help
  746. Say Y here if you have a Sahara TouchIT-213 Tablet PC.
  747. If unsure, say N.
  748. To compile this driver as a module, choose M here: the
  749. module will be called touchit213.
  750. config TOUCHSCREEN_TS4800
  751. tristate "TS-4800 touchscreen"
  752. depends on HAS_IOMEM && OF
  753. depends on SOC_IMX51 || COMPILE_TEST
  754. select MFD_SYSCON
  755. select INPUT_POLLDEV
  756. help
  757. Say Y here if you have a touchscreen on a TS-4800 board.
  758. On TS-4800, the touchscreen is not handled directly by Linux but by
  759. a companion FPGA.
  760. If unsure, say N.
  761. To compile this driver as a module, choose M here: the
  762. module will be called ts4800_ts.
  763. config TOUCHSCREEN_TSC_SERIO
  764. tristate "TSC-10/25/40 serial touchscreen support"
  765. select SERIO
  766. help
  767. Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
  768. to your system.
  769. If unsure, say N.
  770. To compile this driver as a module, choose M here: the
  771. module will be called tsc40.
  772. config TOUCHSCREEN_TSC200X_CORE
  773. tristate
  774. config TOUCHSCREEN_TSC2004
  775. tristate "TSC2004 based touchscreens"
  776. depends on I2C
  777. select REGMAP_I2C
  778. select TOUCHSCREEN_TSC200X_CORE
  779. help
  780. Say Y here if you have a TSC2004 based touchscreen.
  781. If unsure, say N.
  782. To compile this driver as a module, choose M here: the
  783. module will be called tsc2004.
  784. config TOUCHSCREEN_TSC2005
  785. tristate "TSC2005 based touchscreens"
  786. depends on SPI_MASTER
  787. select REGMAP_SPI
  788. select TOUCHSCREEN_TSC200X_CORE
  789. help
  790. Say Y here if you have a TSC2005 based touchscreen.
  791. If unsure, say N.
  792. To compile this driver as a module, choose M here: the
  793. module will be called tsc2005.
  794. config TOUCHSCREEN_TSC2007
  795. tristate "TSC2007 based touchscreens"
  796. depends on I2C
  797. help
  798. Say Y here if you have a TSC2007 based touchscreen.
  799. If unsure, say N.
  800. To compile this driver as a module, choose M here: the
  801. module will be called tsc2007.
  802. config TOUCHSCREEN_W90X900
  803. tristate "W90P910 touchscreen driver"
  804. depends on ARCH_W90X900
  805. help
  806. Say Y here if you have a W90P910 based touchscreen.
  807. To compile this driver as a module, choose M here: the
  808. module will be called w90p910_ts.
  809. config TOUCHSCREEN_PCAP
  810. tristate "Motorola PCAP touchscreen"
  811. depends on EZX_PCAP
  812. help
  813. Say Y here if you have a Motorola EZX telephone and
  814. want to enable support for the built-in touchscreen.
  815. To compile this driver as a module, choose M here: the
  816. module will be called pcap_ts.
  817. config TOUCHSCREEN_RM_TS
  818. tristate "Raydium I2C Touchscreen"
  819. depends on I2C
  820. depends on GPIOLIB || COMPILE_TEST
  821. help
  822. Say Y here if you have Raydium series I2C touchscreen,
  823. such as RM32380, connected to your system.
  824. If unsure, say N.
  825. To compile this driver as a module, choose M here: the
  826. module will be called raydium_i2c_ts.
  827. config TOUCHSCREEN_SILEAD
  828. tristate "Silead I2C touchscreen"
  829. depends on I2C
  830. help
  831. Say Y here if you have the Silead touchscreen connected to
  832. your system.
  833. If unsure, say N.
  834. To compile this driver as a module, choose M here: the
  835. module will be called silead.
  836. config TOUCHSCREEN_SIS_I2C
  837. tristate "SiS 9200 family I2C touchscreen"
  838. depends on I2C
  839. select CRC_ITU_T
  840. depends on GPIOLIB || COMPILE_TEST
  841. help
  842. This enables support for SiS 9200 family over I2C based touchscreens.
  843. If unsure, say N.
  844. To compile this driver as a module, choose M here: the
  845. module will be called sis_i2c.
  846. config TOUCHSCREEN_ST1232
  847. tristate "Sitronix ST1232 touchscreen controllers"
  848. depends on I2C
  849. help
  850. Say Y here if you want to support Sitronix ST1232
  851. touchscreen controller.
  852. If unsure, say N.
  853. To compile this driver as a module, choose M here: the
  854. module will be called st1232_ts.
  855. config TOUCHSCREEN_STMPE
  856. tristate "STMicroelectronics STMPE touchscreens"
  857. depends on MFD_STMPE
  858. depends on (OF || COMPILE_TEST)
  859. help
  860. Say Y here if you want support for STMicroelectronics
  861. STMPE touchscreen controllers.
  862. To compile this driver as a module, choose M here: the
  863. module will be called stmpe-ts.
  864. config TOUCHSCREEN_SUN4I
  865. tristate "Allwinner sun4i resistive touchscreen controller support"
  866. depends on ARCH_SUNXI || COMPILE_TEST
  867. depends on HWMON
  868. depends on THERMAL || !THERMAL_OF
  869. help
  870. This selects support for the resistive touchscreen controller
  871. found on Allwinner sunxi SoCs.
  872. To compile this driver as a module, choose M here: the
  873. module will be called sun4i-ts.
  874. config TOUCHSCREEN_SUR40
  875. tristate "Samsung SUR40 (Surface 2.0/PixelSense) touchscreen"
  876. depends on USB && MEDIA_USB_SUPPORT && HAS_DMA
  877. depends on VIDEO_V4L2
  878. select INPUT_POLLDEV
  879. select VIDEOBUF2_DMA_SG
  880. help
  881. Say Y here if you want support for the Samsung SUR40 touchscreen
  882. (also known as Microsoft Surface 2.0 or Microsoft PixelSense).
  883. To compile this driver as a module, choose M here: the
  884. module will be called sur40.
  885. config TOUCHSCREEN_SURFACE3_SPI
  886. tristate "Ntrig/Microsoft Surface 3 SPI touchscreen"
  887. depends on SPI
  888. depends on GPIOLIB || COMPILE_TEST
  889. help
  890. Say Y here if you have the Ntrig/Microsoft SPI touchscreen
  891. controller chip as found on the Surface 3 in your system.
  892. If unsure, say N.
  893. To compile this driver as a module, choose M here: the
  894. module will be called surface3_spi.
  895. config TOUCHSCREEN_SX8654
  896. tristate "Semtech SX8654 touchscreen"
  897. depends on I2C
  898. help
  899. Say Y here if you have a Semtech SX8654 touchscreen controller.
  900. If unsure, say N
  901. To compile this driver as a module, choose M here: the
  902. module will be called sx8654.
  903. config TOUCHSCREEN_TPS6507X
  904. tristate "TPS6507x based touchscreens"
  905. depends on I2C
  906. select INPUT_POLLDEV
  907. help
  908. Say Y here if you have a TPS6507x based touchscreen
  909. controller.
  910. If unsure, say N.
  911. To compile this driver as a module, choose M here: the
  912. module will be called tps6507x_ts.
  913. config TOUCHSCREEN_ZFORCE
  914. tristate "Neonode zForce infrared touchscreens"
  915. depends on I2C
  916. depends on GPIOLIB || COMPILE_TEST
  917. help
  918. Say Y here if you have a touchscreen using the zforce
  919. infraread technology from Neonode.
  920. If unsure, say N.
  921. To compile this driver as a module, choose M here: the
  922. module will be called zforce_ts.
  923. config TOUCHSCREEN_COLIBRI_VF50
  924. tristate "Toradex Colibri on board touchscreen driver"
  925. depends on IIO && VF610_ADC
  926. depends on GPIOLIB || COMPILE_TEST
  927. help
  928. Say Y here if you have a Colibri VF50 and plan to use
  929. the on-board provided 4-wire touchscreen driver.
  930. If unsure, say N.
  931. To compile this driver as a module, choose M here: the
  932. module will be called colibri_vf50_ts.
  933. config TOUCHSCREEN_ROHM_BU21023
  934. tristate "ROHM BU21023/24 Dual touch support resistive touchscreens"
  935. depends on I2C
  936. help
  937. Say Y here if you have a touchscreen using ROHM BU21023/24.
  938. If unsure, say N.
  939. To compile this driver as a module, choose M here: the
  940. module will be called bu21023_ts.
  941. endif