Kconfig 34 KB

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