Kconfig 34 KB

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