Kconfig 47 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # Sensor device configuration
  4. #
  5. menu "I2C Hardware Bus support"
  6. depends on HAS_IOMEM
  7. comment "PC SMBus host controller drivers"
  8. depends on PCI
  9. config I2C_CCGX_UCSI
  10. tristate
  11. help
  12. A common module to provide an API to instantiate UCSI device
  13. for Cypress CCGx Type-C controller. Individual bus drivers
  14. need to select this one on demand.
  15. config I2C_ALI1535
  16. tristate "ALI 1535"
  17. depends on PCI && HAS_IOPORT
  18. help
  19. If you say yes to this option, support will be included for the SMB
  20. Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
  21. controller is part of the 7101 device, which is an ACPI-compliant
  22. Power Management Unit (PMU).
  23. This driver can also be built as a module. If so, the module
  24. will be called i2c-ali1535.
  25. config I2C_ALI1563
  26. tristate "ALI 1563"
  27. depends on PCI && HAS_IOPORT
  28. help
  29. If you say yes to this option, support will be included for the SMB
  30. Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
  31. controller is part of the 7101 device, which is an ACPI-compliant
  32. Power Management Unit (PMU).
  33. This driver can also be built as a module. If so, the module
  34. will be called i2c-ali1563.
  35. config I2C_ALI15X3
  36. tristate "ALI 15x3"
  37. depends on PCI && HAS_IOPORT
  38. help
  39. If you say yes to this option, support will be included for the
  40. Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
  41. This driver can also be built as a module. If so, the module
  42. will be called i2c-ali15x3.
  43. config I2C_AMD756
  44. tristate "AMD 756/766/768/8111 and nVidia nForce"
  45. depends on PCI && HAS_IOPORT
  46. help
  47. If you say yes to this option, support will be included for the AMD
  48. 756/766/768 mainboard I2C interfaces. The driver also includes
  49. support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
  50. the nVidia nForce I2C interface.
  51. This driver can also be built as a module. If so, the module
  52. will be called i2c-amd756.
  53. config I2C_AMD756_S4882
  54. tristate "SMBus multiplexing on the Tyan S4882"
  55. depends on I2C_AMD756 && X86
  56. help
  57. Enabling this option will add specific SMBus support for the Tyan
  58. S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
  59. over 8 different channels, where the various memory module EEPROMs
  60. and temperature sensors live. Saying yes here will give you access
  61. to these in addition to the trunk.
  62. This driver can also be built as a module. If so, the module
  63. will be called i2c-amd756-s4882.
  64. config I2C_AMD8111
  65. tristate "AMD 8111"
  66. depends on PCI && HAS_IOPORT
  67. help
  68. If you say yes to this option, support will be included for the
  69. second (SMBus 2.0) AMD 8111 mainboard I2C interface.
  70. This driver can also be built as a module. If so, the module
  71. will be called i2c-amd8111.
  72. config I2C_AMD_MP2
  73. tristate "AMD MP2 PCIe"
  74. depends on PCI && ACPI
  75. help
  76. If you say yes to this option, support will be included for the AMD
  77. MP2 PCIe I2C adapter.
  78. This driver can also be built as modules. If so, the modules will
  79. be called i2c-amd-mp2-pci and i2c-amd-mp2-plat.
  80. config I2C_HIX5HD2
  81. tristate "Hix5hd2 high-speed I2C driver"
  82. depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
  83. help
  84. Say Y here to include support for the high-speed I2C controller
  85. used in HiSilicon hix5hd2 SoCs.
  86. This driver can also be built as a module. If so, the module
  87. will be called i2c-hix5hd2.
  88. config I2C_I801
  89. tristate "Intel 82801 (ICH/PCH)"
  90. depends on PCI && HAS_IOPORT
  91. select P2SB if X86
  92. select CHECK_SIGNATURE if X86 && DMI
  93. select I2C_SMBUS
  94. help
  95. If you say yes to this option, support will be included for the Intel
  96. 801 family of mainboard I2C interfaces. Specifically, the following
  97. versions of the chipset are supported:
  98. 82801AA
  99. 82801AB
  100. 82801BA
  101. 82801CA/CAM
  102. 82801DB
  103. 82801EB/ER (ICH5/ICH5R)
  104. 6300ESB
  105. ICH6
  106. ICH7
  107. ESB2
  108. ICH8
  109. ICH9
  110. EP80579 (Tolapai)
  111. ICH10
  112. 5/3400 Series (PCH)
  113. 6 Series (PCH)
  114. Patsburg (PCH)
  115. DH89xxCC (PCH)
  116. Panther Point (PCH)
  117. Lynx Point (PCH)
  118. Avoton (SOC)
  119. Wellsburg (PCH)
  120. Coleto Creek (PCH)
  121. Wildcat Point (PCH)
  122. BayTrail (SOC)
  123. Braswell (SOC)
  124. Sunrise Point (PCH)
  125. Kaby Lake (PCH)
  126. DNV (SOC)
  127. Broxton (SOC)
  128. Lewisburg (PCH)
  129. Gemini Lake (SOC)
  130. Cannon Lake (PCH)
  131. Cedar Fork (PCH)
  132. Ice Lake (PCH)
  133. Comet Lake (PCH)
  134. Elkhart Lake (PCH)
  135. Tiger Lake (PCH)
  136. Jasper Lake (SOC)
  137. Emmitsburg (PCH)
  138. Alder Lake (PCH)
  139. Raptor Lake (PCH)
  140. Meteor Lake (SOC and PCH)
  141. Birch Stream (SOC)
  142. Arrow Lake (SOC)
  143. Panther Lake (SOC)
  144. This driver can also be built as a module. If so, the module
  145. will be called i2c-i801.
  146. config I2C_I801_MUX
  147. def_bool I2C_I801
  148. depends on DMI && I2C_MUX_GPIO
  149. depends on !(I2C_I801=y && I2C_MUX=m)
  150. help
  151. Optional support for multiplexed SMBUS on certain systems with
  152. more than 8 memory slots.
  153. config I2C_ISCH
  154. tristate "Intel SCH SMBus 1.0"
  155. depends on PCI && HAS_IOPORT
  156. select LPC_SCH
  157. help
  158. Say Y here if you want to use SMBus controller on the Intel SCH
  159. based systems.
  160. This driver can also be built as a module. If so, the module
  161. will be called i2c-isch.
  162. config I2C_ISMT
  163. tristate "Intel iSMT SMBus Controller"
  164. depends on PCI && X86
  165. help
  166. If you say yes to this option, support will be included for the Intel
  167. iSMT SMBus host controller interface.
  168. This driver can also be built as a module. If so, the module will be
  169. called i2c-ismt.
  170. config I2C_PIIX4
  171. tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
  172. depends on PCI && HAS_IOPORT
  173. select I2C_SMBUS
  174. help
  175. If you say yes to this option, support will be included for the Intel
  176. PIIX4 family of mainboard I2C interfaces. Specifically, the following
  177. versions of the chipset are supported (note that Serverworks is part
  178. of Broadcom):
  179. Intel PIIX4
  180. Intel 440MX
  181. ATI IXP200
  182. ATI IXP300
  183. ATI IXP400
  184. ATI SB600
  185. ATI SB700/SP5100
  186. ATI SB800
  187. AMD Hudson-2
  188. AMD ML
  189. AMD CZ
  190. Hygon CZ
  191. Serverworks OSB4
  192. Serverworks CSB5
  193. Serverworks CSB6
  194. Serverworks HT-1000
  195. Serverworks HT-1100
  196. SMSC Victory66
  197. Some AMD chipsets contain two PIIX4-compatible SMBus
  198. controllers. This driver will attempt to use both controllers
  199. on the SB700/SP5100, if they have been initialized by the BIOS.
  200. This driver can also be built as a module. If so, the module
  201. will be called i2c-piix4.
  202. config I2C_CHT_WC
  203. tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
  204. depends on INTEL_SOC_PMIC_CHTWC
  205. help
  206. If you say yes to this option, support will be included for the
  207. SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
  208. found on some Intel Cherry Trail systems.
  209. Note this controller is hooked up to a TI bq24292i charger-IC,
  210. combined with a FUSB302 Type-C port-controller as such it is advised
  211. to also select CONFIG_TYPEC_FUSB302=m.
  212. config I2C_NFORCE2
  213. tristate "Nvidia nForce2, nForce3 and nForce4"
  214. depends on PCI && HAS_IOPORT
  215. help
  216. If you say yes to this option, support will be included for the Nvidia
  217. nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
  218. This driver can also be built as a module. If so, the module
  219. will be called i2c-nforce2.
  220. config I2C_NFORCE2_S4985
  221. tristate "SMBus multiplexing on the Tyan S4985"
  222. depends on I2C_NFORCE2 && X86
  223. help
  224. Enabling this option will add specific SMBus support for the Tyan
  225. S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
  226. over 4 different channels, where the various memory module EEPROMs
  227. live. Saying yes here will give you access to these in addition
  228. to the trunk.
  229. This driver can also be built as a module. If so, the module
  230. will be called i2c-nforce2-s4985.
  231. config I2C_NVIDIA_GPU
  232. tristate "NVIDIA GPU I2C controller"
  233. depends on PCI
  234. select I2C_CCGX_UCSI
  235. help
  236. If you say yes to this option, support will be included for the
  237. NVIDIA GPU I2C controller which is used to communicate with the GPU's
  238. Type-C controller. This driver can also be built as a module called
  239. i2c-nvidia-gpu.
  240. config I2C_SIS5595
  241. tristate "SiS 5595"
  242. depends on PCI && HAS_IOPORT
  243. help
  244. If you say yes to this option, support will be included for the
  245. SiS5595 SMBus (a subset of I2C) interface.
  246. This driver can also be built as a module. If so, the module
  247. will be called i2c-sis5595.
  248. config I2C_SIS630
  249. tristate "SiS 630/730/964"
  250. depends on PCI && HAS_IOPORT
  251. help
  252. If you say yes to this option, support will be included for the
  253. SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
  254. This driver can also be built as a module. If so, the module
  255. will be called i2c-sis630.
  256. config I2C_SIS96X
  257. tristate "SiS 96x"
  258. depends on PCI && HAS_IOPORT
  259. help
  260. If you say yes to this option, support will be included for the SiS
  261. 96x SMBus (a subset of I2C) interfaces. Specifically, the following
  262. chipsets are supported:
  263. 645/961
  264. 645DX/961
  265. 645DX/962
  266. 648/961
  267. 650/961
  268. 735
  269. 745
  270. This driver can also be built as a module. If so, the module
  271. will be called i2c-sis96x.
  272. config I2C_VIA
  273. tristate "VIA VT82C586B"
  274. depends on PCI && HAS_IOPORT
  275. select I2C_ALGOBIT
  276. help
  277. If you say yes to this option, support will be included for the VIA
  278. 82C586B I2C interface
  279. This driver can also be built as a module. If so, the module
  280. will be called i2c-via.
  281. config I2C_VIAPRO
  282. tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
  283. depends on PCI && HAS_IOPORT
  284. help
  285. If you say yes to this option, support will be included for the VIA
  286. VT82C596 and later SMBus interface. Specifically, the following
  287. chipsets are supported:
  288. VT82C596A/B
  289. VT82C686A/B
  290. VT8231
  291. VT8233/A
  292. VT8235
  293. VT8237R/A/S
  294. VT8251
  295. CX700
  296. VX800/VX820
  297. VX855/VX875
  298. VX900
  299. This driver can also be built as a module. If so, the module
  300. will be called i2c-viapro.
  301. if ACPI
  302. config I2C_ZHAOXIN
  303. tristate "Zhaoxin I2C Interface"
  304. depends on PCI || COMPILE_TEST
  305. help
  306. If you say yes to this option, support will be included for the
  307. ZHAOXIN I2C interface
  308. This driver can also be built as a module. If so, the module
  309. will be called i2c-zhaoxin.
  310. comment "ACPI drivers"
  311. config I2C_SCMI
  312. tristate "SMBus Control Method Interface"
  313. help
  314. This driver supports the SMBus Control Method Interface. It needs the
  315. BIOS to declare ACPI control methods as described in the SMBus Control
  316. Method Interface specification.
  317. To compile this driver as a module, choose M here:
  318. the module will be called i2c-scmi.
  319. endif # ACPI
  320. comment "Mac SMBus host controller drivers"
  321. depends on PPC_CHRP || PPC_PMAC
  322. config I2C_HYDRA
  323. tristate "CHRP Apple Hydra Mac I/O I2C interface"
  324. depends on PCI && PPC_CHRP
  325. select I2C_ALGOBIT
  326. help
  327. This supports the use of the I2C interface in the Apple Hydra Mac
  328. I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
  329. have such a machine.
  330. This support is also available as a module. If so, the module
  331. will be called i2c-hydra.
  332. config I2C_POWERMAC
  333. tristate "Powermac I2C interface"
  334. depends on PPC_PMAC
  335. default y
  336. help
  337. This exposes the various PowerMac i2c interfaces to the linux i2c
  338. layer and to userland. It is used by various drivers on the PowerMac
  339. platform, and should generally be enabled.
  340. This support is also available as a module. If so, the module
  341. will be called i2c-powermac.
  342. comment "I2C system bus drivers (mostly embedded / system-on-chip)"
  343. config I2C_ALTERA
  344. tristate "Altera Soft IP I2C"
  345. depends on ARCH_INTEL_SOCFPGA || NIOS2 || COMPILE_TEST
  346. depends on OF
  347. help
  348. If you say yes to this option, support will be included for the
  349. Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
  350. This driver can also be built as a module. If so, the module
  351. will be called i2c-altera.
  352. config I2C_ASPEED
  353. tristate "Aspeed I2C Controller"
  354. depends on ARCH_ASPEED || COMPILE_TEST
  355. help
  356. If you say yes to this option, support will be included for the
  357. Aspeed I2C controller.
  358. This driver can also be built as a module. If so, the module
  359. will be called i2c-aspeed.
  360. config I2C_AT91
  361. tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
  362. depends on ARCH_AT91 || COMPILE_TEST
  363. help
  364. This supports the use of the I2C interface on Atmel AT91
  365. processors.
  366. A serious problem is that there is no documented way to issue
  367. repeated START conditions for more than two messages, as needed
  368. to support combined I2C messages. Use the i2c-gpio driver
  369. unless your system can cope with this limitation.
  370. Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
  371. don't have clock stretching in transmission mode. For that reason,
  372. you can encounter underrun issues causing premature stop sendings if
  373. the latency to fill the transmission register is too long. If you
  374. are facing this situation, use the i2c-gpio driver.
  375. config I2C_AT91_SLAVE_EXPERIMENTAL
  376. tristate "Microchip AT91 I2C experimental slave mode"
  377. depends on I2C_AT91
  378. select I2C_SLAVE
  379. help
  380. If you say yes to this option, support for the slave mode will be
  381. added. Caution: do not use it for production. This feature has not
  382. been tested in a heavy way, help wanted.
  383. There are known bugs:
  384. - It can hang, on a SAMA5D4, after several transfers.
  385. - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
  386. master.
  387. config I2C_AU1550
  388. tristate "Au1550/Au1200/Au1300 SMBus interface"
  389. depends on MIPS_ALCHEMY
  390. help
  391. If you say yes to this option, support will be included for the
  392. Au1550/Au1200/Au1300 SMBus interface.
  393. This driver can also be built as a module. If so, the module
  394. will be called i2c-au1550.
  395. config I2C_AXXIA
  396. tristate "Axxia I2C controller"
  397. depends on ARCH_AXXIA || COMPILE_TEST
  398. default ARCH_AXXIA
  399. select I2C_SLAVE
  400. help
  401. Say yes if you want to support the I2C bus on Axxia platforms.
  402. Please note that this controller is limited to transfers of maximum
  403. 255 bytes in length. Any attempt to to a larger transfer will return
  404. an error.
  405. config I2C_BCM2835
  406. tristate "Broadcom BCM2835 I2C controller"
  407. depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST
  408. depends on COMMON_CLK
  409. help
  410. If you say yes to this option, support will be included for the
  411. BCM2835 I2C controller.
  412. If you don't know what to do here, say N.
  413. This support is also available as a module. If so, the module
  414. will be called i2c-bcm2835.
  415. config I2C_BCM_IPROC
  416. tristate "Broadcom iProc I2C controller"
  417. depends on ARCH_BCM_IPROC || COMPILE_TEST
  418. default ARCH_BCM_IPROC
  419. select I2C_SLAVE
  420. help
  421. If you say yes to this option, support will be included for the
  422. Broadcom iProc I2C controller.
  423. If you don't know what to do here, say N.
  424. config I2C_BCM_KONA
  425. tristate "BCM Kona I2C adapter"
  426. depends on ARCH_BCM_MOBILE || COMPILE_TEST
  427. default y if ARCH_BCM_MOBILE
  428. help
  429. If you say yes to this option, support will be included for the
  430. I2C interface on the Broadcom Kona family of processors.
  431. If you do not need KONA I2C interface, say N.
  432. config I2C_BRCMSTB
  433. tristate "BRCM Settop/DSL I2C controller"
  434. depends on ARCH_BCM2835 || ARCH_BCMBCA || ARCH_BRCMSTB || \
  435. BMIPS_GENERIC || COMPILE_TEST
  436. default y
  437. help
  438. If you say yes to this option, support will be included for the
  439. I2C interface on the Broadcom Settop/DSL SoCs.
  440. If you do not need I2C interface, say N.
  441. config I2C_CADENCE
  442. tristate "Cadence I2C Controller"
  443. depends on ARCH_ZYNQ || ARM64 || XTENSA || RISCV || COMPILE_TEST
  444. help
  445. Say yes here to select Cadence I2C Host Controller. This controller is
  446. e.g. used by Xilinx Zynq.
  447. config I2C_CBUS_GPIO
  448. tristate "CBUS I2C driver"
  449. depends on GPIOLIB || COMPILE_TEST
  450. help
  451. Support for CBUS access using I2C API. Mostly relevant for Nokia
  452. Internet Tablets (770, N800 and N810).
  453. This driver can also be built as a module. If so, the module
  454. will be called i2c-cbus-gpio.
  455. config I2C_CPM
  456. tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
  457. depends on CPM1 || CPM2
  458. help
  459. This supports the use of the I2C interface on Freescale
  460. processors with CPM1 or CPM2.
  461. This driver can also be built as a module. If so, the module
  462. will be called i2c-cpm.
  463. config I2C_DAVINCI
  464. tristate "DaVinci I2C driver"
  465. depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
  466. help
  467. Support for TI DaVinci I2C controller driver.
  468. This driver can also be built as a module. If so, the module
  469. will be called i2c-davinci.
  470. Please note that this driver might be needed to bring up other
  471. devices such as DaVinci NIC.
  472. For details please see http://www.ti.com/davinci
  473. config I2C_DESIGNWARE_CORE
  474. tristate "Synopsys DesignWare I2C adapter"
  475. select REGMAP
  476. help
  477. This option enables support for the Synopsys DesignWare I2C adapter.
  478. This driver includes support for the I2C host on the Synopsys
  479. Designware I2C adapter.
  480. To compile the driver as a module, choose M here: the module will be
  481. called i2c-designware-core.
  482. if I2C_DESIGNWARE_CORE
  483. config I2C_DESIGNWARE_SLAVE
  484. bool "Synopsys DesignWare Slave"
  485. select I2C_SLAVE
  486. help
  487. If you say yes to this option, support will be included for the
  488. Synopsys DesignWare I2C slave adapter.
  489. config I2C_DESIGNWARE_PLATFORM
  490. tristate "Synopsys DesignWare Platform driver"
  491. depends on (ACPI && COMMON_CLK) || !ACPI
  492. select MFD_SYSCON if MIPS_BAIKAL_T1
  493. default I2C_DESIGNWARE_CORE
  494. help
  495. If you say yes to this option, support will be included for the
  496. Synopsys DesignWare I2C adapters on the platform bus.
  497. This driver can also be built as a module. If so, the module
  498. will be called i2c-designware-platform.
  499. config I2C_DESIGNWARE_AMDPSP
  500. bool "AMD PSP I2C semaphore support"
  501. depends on ACPI
  502. depends on CRYPTO_DEV_SP_PSP
  503. depends on PCI
  504. depends on I2C_DESIGNWARE_PLATFORM
  505. depends on (I2C_DESIGNWARE_PLATFORM=y && CRYPTO_DEV_CCP_DD=y) || \
  506. (I2C_DESIGNWARE_PLATFORM=m && CRYPTO_DEV_CCP_DD)
  507. help
  508. This driver enables managed host access to the selected I2C bus shared
  509. between AMD CPU and AMD PSP.
  510. You should say Y if running on an AMD system equipped with the PSP.
  511. config I2C_DESIGNWARE_BAYTRAIL
  512. bool "Intel Baytrail I2C semaphore support"
  513. depends on ACPI
  514. depends on I2C_DESIGNWARE_PLATFORM
  515. depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
  516. (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
  517. help
  518. This driver enables managed host access to the PMIC I2C bus on select
  519. Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
  520. the host to request uninterrupted access to the PMIC's I2C bus from
  521. the platform firmware controlling it. You should say Y if running on
  522. a BayTrail system using the AXP288.
  523. config I2C_DESIGNWARE_PCI
  524. tristate "Synopsys DesignWare PCI driver"
  525. depends on PCI
  526. select I2C_CCGX_UCSI
  527. help
  528. If you say yes to this option, support will be included for the
  529. Synopsys DesignWare I2C adapters on the PCI bus. Only master mode is
  530. supported.
  531. This driver can also be built as a module. If so, the module
  532. will be called i2c-designware-pci.
  533. endif
  534. config I2C_DIGICOLOR
  535. tristate "Conexant Digicolor I2C driver"
  536. depends on ARCH_DIGICOLOR || COMPILE_TEST
  537. help
  538. Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
  539. This driver can also be built as a module. If so, the module
  540. will be called i2c-digicolor.
  541. config I2C_EG20T
  542. tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
  543. depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
  544. help
  545. This driver is for PCH(Platform controller Hub) I2C of EG20T which
  546. is an IOH(Input/Output Hub) for x86 embedded processor.
  547. This driver can access PCH I2C bus device.
  548. This driver also can be used for LAPIS Semiconductor IOH(Input/
  549. Output Hub), ML7213, ML7223 and ML7831.
  550. ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
  551. for MP(Media Phone) use and ML7831 IOH is for general purpose use.
  552. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  553. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  554. config I2C_EMEV2
  555. tristate "EMMA Mobile series I2C adapter"
  556. depends on HAVE_CLK
  557. select I2C_SLAVE
  558. help
  559. If you say yes to this option, support will be included for the
  560. I2C interface on the Renesas Electronics EM/EV family of processors.
  561. config I2C_EXYNOS5
  562. tristate "Exynos high-speed I2C driver"
  563. depends on OF
  564. depends on ARCH_EXYNOS || COMPILE_TEST
  565. default y if ARCH_EXYNOS
  566. help
  567. High-speed I2C controller on Samsung Exynos5 and newer Samsung SoCs:
  568. Exynos5250, Exynos5260, Exynos5410, Exynos542x, Exynos5800,
  569. Exynos5433, Exynos7, Exynos850 and ExynosAutoV9.
  570. Choose Y here only if you build for such Samsung SoC.
  571. config I2C_GPIO
  572. tristate "GPIO-based bitbanging I2C"
  573. depends on GPIOLIB || COMPILE_TEST
  574. select I2C_ALGOBIT
  575. help
  576. This is a very simple bitbanging I2C driver utilizing the
  577. arch-neutral GPIO API to control the SCL and SDA lines.
  578. config I2C_GPIO_FAULT_INJECTOR
  579. bool "GPIO-based fault injector"
  580. depends on I2C_GPIO
  581. help
  582. This adds some functionality to the i2c-gpio driver which can inject
  583. faults to an I2C bus, so another bus master can be stress-tested.
  584. This is for debugging. If unsure, say 'no'.
  585. config I2C_GXP
  586. tristate "GXP I2C Interface"
  587. depends on ARCH_HPE_GXP || COMPILE_TEST
  588. help
  589. This enables support for GXP I2C interface. The I2C engines can be
  590. either I2C master or I2C slaves.
  591. config I2C_HIGHLANDER
  592. tristate "Highlander FPGA SMBus interface"
  593. depends on SH_HIGHLANDER || COMPILE_TEST
  594. help
  595. If you say yes to this option, support will be included for
  596. the SMBus interface located in the FPGA on various Highlander
  597. boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
  598. FPGAs. This is wholly unrelated to the SoC I2C.
  599. This driver can also be built as a module. If so, the module
  600. will be called i2c-highlander.
  601. config I2C_HISI
  602. tristate "HiSilicon I2C controller"
  603. depends on ARM64 || COMPILE_TEST
  604. help
  605. Say Y here if you want to have Hisilicon I2C controller support
  606. available on the Kunpeng Server.
  607. This driver can also be built as a module. If so, the module
  608. will be called i2c-hisi.
  609. config I2C_IBM_IIC
  610. tristate "IBM PPC 4xx on-chip I2C interface"
  611. depends on 4xx
  612. help
  613. Say Y here if you want to use IIC peripheral found on
  614. embedded IBM PPC 4xx based systems.
  615. This driver can also be built as a module. If so, the module
  616. will be called i2c-ibm_iic.
  617. config I2C_IMG
  618. tristate "Imagination Technologies I2C SCB Controller"
  619. depends on MIPS || COMPILE_TEST
  620. help
  621. Say Y here if you want to use the IMG I2C SCB controller,
  622. available on the TZ1090 and other IMG SoCs.
  623. This driver can also be built as a module. If so, the module
  624. will be called i2c-img-scb.
  625. config I2C_IMX
  626. tristate "IMX I2C interface"
  627. depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE || COMPILE_TEST
  628. select I2C_SLAVE
  629. help
  630. Say Y here if you want to use the IIC bus controller on
  631. the Freescale i.MX/MXC, Layerscape or ColdFire processors.
  632. This driver can also be built as a module. If so, the module
  633. will be called i2c-imx.
  634. config I2C_IMX_LPI2C
  635. tristate "IMX Low Power I2C interface"
  636. depends on ARCH_MXC || COMPILE_TEST
  637. help
  638. Say Y here if you want to use the Low Power IIC bus controller
  639. on the Freescale i.MX processors.
  640. This driver can also be built as a module. If so, the module
  641. will be called i2c-imx-lpi2c.
  642. config I2C_IOP3XX
  643. tristate "Intel IXP4xx on-chip I2C interface"
  644. depends on ARCH_IXP4XX || COMPILE_TEST
  645. help
  646. Say Y here if you want to use the IIC bus controller on
  647. the Intel IXP4xx Network Processors.
  648. This driver can also be built as a module. If so, the module
  649. will be called i2c-iop3xx.
  650. config I2C_JZ4780
  651. tristate "JZ4780 I2C controller interface support"
  652. depends on MIPS || COMPILE_TEST
  653. help
  654. If you say yes to this option, support will be included for the
  655. Ingenic JZ4780 I2C controller.
  656. If you don't know what to do here, say N.
  657. config I2C_KEBA
  658. tristate "KEBA I2C controller support"
  659. depends on HAS_IOMEM
  660. depends on KEBA_CP500 || COMPILE_TEST
  661. select AUXILIARY_BUS
  662. help
  663. This driver supports the I2C controller found in KEBA system FPGA
  664. devices.
  665. This driver can also be built as a module. If so, the module
  666. will be called i2c-keba.
  667. config I2C_KEMPLD
  668. tristate "Kontron COM I2C Controller"
  669. depends on MFD_KEMPLD
  670. help
  671. This enables support for the I2C bus interface on some Kontron ETX
  672. and COMexpress (ETXexpress) modules.
  673. This driver can also be built as a module. If so, the module
  674. will be called i2c-kempld.
  675. config I2C_LPC2K
  676. tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
  677. depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
  678. help
  679. This driver supports the I2C interface found several NXP
  680. devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
  681. This driver can also be built as a module. If so, the module
  682. will be called i2c-lpc2k.
  683. config I2C_LS2X
  684. tristate "Loongson LS2X I2C adapter"
  685. depends on MACH_LOONGSON64 || COMPILE_TEST
  686. help
  687. If you say yes to this option, support will be included for the
  688. I2C interface on the Loongson-2K SoCs and Loongson LS7A bridge
  689. chip.
  690. This driver can also be built as a module. If so, the module
  691. will be called i2c-ls2x.
  692. config I2C_MLXBF
  693. tristate "Mellanox BlueField I2C controller"
  694. depends on MELLANOX_PLATFORM && ARM64
  695. depends on ACPI
  696. select I2C_SLAVE
  697. help
  698. Enabling this option will add I2C SMBus support for Mellanox BlueField
  699. system.
  700. This driver can also be built as a module. If so, the module will be
  701. called i2c-mlxbf.
  702. This driver implements an I2C SMBus host controller and enables both
  703. master and slave functions.
  704. config I2C_MESON
  705. tristate "Amlogic Meson I2C controller"
  706. depends on ARCH_MESON || COMPILE_TEST
  707. depends on COMMON_CLK
  708. help
  709. If you say yes to this option, support will be included for the
  710. I2C interface on the Amlogic Meson family of SoCs.
  711. config I2C_MICROCHIP_CORE
  712. tristate "Microchip FPGA I2C controller"
  713. depends on ARCH_MICROCHIP_POLARFIRE || COMPILE_TEST
  714. depends on OF
  715. help
  716. If you say yes to this option, support will be included for the
  717. I2C interface on Microchip FPGAs.
  718. This driver can also be built as a module. If so, the module will be
  719. called i2c-microchip-core.
  720. config I2C_MPC
  721. tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
  722. depends on PPC
  723. help
  724. If you say yes to this option, support will be included for the
  725. built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
  726. MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
  727. This driver can also be built as a module. If so, the module
  728. will be called i2c-mpc.
  729. config I2C_MT65XX
  730. tristate "MediaTek I2C adapter"
  731. depends on ARCH_MEDIATEK || COMPILE_TEST
  732. help
  733. This selects the MediaTek(R) Integrated Inter Circuit bus driver
  734. for MT65xx and MT81xx.
  735. If you want to use MediaTek(R) I2C interface, say Y or M here.
  736. If unsure, say N.
  737. config I2C_MT7621
  738. tristate "MT7621/MT7628 I2C Controller"
  739. depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || ARCH_AIROHA || COMPILE_TEST
  740. help
  741. Say Y here to include support for I2C controller in the
  742. MediaTek MT7621/MT7628 SoCs.
  743. config I2C_MV64XXX
  744. tristate "Marvell mv64xxx I2C Controller"
  745. depends on PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
  746. help
  747. If you say yes to this option, support will be included for the
  748. built-in I2C interface on the Marvell 64xxx line of host bridges.
  749. This driver is also used for Allwinner SoCs I2C controllers.
  750. This driver can also be built as a module. If so, the module
  751. will be called i2c-mv64xxx.
  752. config I2C_MXS
  753. tristate "Freescale i.MX28 I2C interface"
  754. depends on SOC_IMX28 || COMPILE_TEST
  755. select STMP_DEVICE
  756. help
  757. Say Y here if you want to use the I2C bus controller on
  758. the Freescale i.MX28 processors.
  759. This driver can also be built as a module. If so, the module
  760. will be called i2c-mxs.
  761. config I2C_NOMADIK
  762. tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
  763. depends on ARM_AMBA
  764. help
  765. If you say yes to this option, support will be included for the
  766. I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
  767. as well as the STA2X11 PCIe I/O HUB.
  768. config I2C_NPCM
  769. tristate "Nuvoton I2C Controller"
  770. depends on ARCH_NPCM || COMPILE_TEST
  771. help
  772. If you say yes to this option, support will be included for the
  773. Nuvoton I2C controller, which is available on the NPCM BMC
  774. controllers.
  775. Driver can also support slave mode (select I2C_SLAVE).
  776. config I2C_OCORES
  777. tristate "OpenCores I2C Controller"
  778. help
  779. If you say yes to this option, support will be included for the
  780. OpenCores I2C controller. For details see
  781. http://www.opencores.org/projects.cgi/web/i2c/overview
  782. This driver can also be built as a module. If so, the module
  783. will be called i2c-ocores.
  784. config I2C_OMAP
  785. tristate "OMAP I2C adapter"
  786. depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
  787. default MACH_OMAP_OSK
  788. select MULTIPLEXER
  789. help
  790. If you say yes to this option, support will be included for the
  791. I2C interface on the Texas Instruments OMAP1/2 family of processors.
  792. Like OMAP1510/1610/1710/5912 and OMAP242x.
  793. For details see http://www.ti.com/omap.
  794. config I2C_OWL
  795. tristate "Actions Semiconductor Owl I2C Controller"
  796. depends on ARCH_ACTIONS || COMPILE_TEST
  797. help
  798. Say Y here if you want to use the I2C bus controller on
  799. the Actions Semiconductor Owl SoC's.
  800. config I2C_PASEMI
  801. tristate "PA Semi SMBus interface"
  802. depends on PPC_PASEMI && PCI
  803. help
  804. Supports the PA Semi PWRficient on-chip SMBus interfaces.
  805. config I2C_APPLE
  806. tristate "Apple SMBus platform driver"
  807. depends on !I2C_PASEMI
  808. depends on ARCH_APPLE || COMPILE_TEST
  809. default ARCH_APPLE
  810. help
  811. Say Y here if you want to use the I2C controller present on Apple
  812. Silicon chips such as the M1.
  813. This driver can also be built as a module. If so, the module
  814. will be called i2c-apple.
  815. config I2C_PCA_PLATFORM
  816. tristate "PCA9564/PCA9665 as platform device"
  817. select I2C_ALGOPCA
  818. help
  819. This driver supports a memory mapped Philips PCA9564/PCA9665
  820. parallel bus to I2C bus controller.
  821. This driver can also be built as a module. If so, the module
  822. will be called i2c-pca-platform.
  823. config I2C_PNX
  824. tristate "I2C bus support for Philips PNX and NXP LPC targets"
  825. depends on ARCH_LPC32XX || COMPILE_TEST
  826. help
  827. This driver supports the Philips IP3204 I2C IP block master and/or
  828. slave controller
  829. This driver can also be built as a module. If so, the module
  830. will be called i2c-pnx.
  831. config I2C_PXA
  832. tristate "Intel PXA2XX I2C adapter"
  833. depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
  834. help
  835. If you have devices in the PXA I2C bus, say yes to this option.
  836. This driver can also be built as a module. If so, the module
  837. will be called i2c-pxa.
  838. config I2C_PXA_PCI
  839. def_bool I2C_PXA && X86_32 && PCI && OF
  840. config I2C_PXA_SLAVE
  841. bool "Intel PXA2XX I2C Slave comms support"
  842. depends on I2C_PXA && !X86_32
  843. select I2C_SLAVE
  844. help
  845. Support I2C slave mode communications on the PXA I2C bus. This
  846. is necessary for systems where the PXA may be a target on the
  847. I2C bus.
  848. config I2C_QCOM_CCI
  849. tristate "Qualcomm Camera Control Interface"
  850. depends on ARCH_QCOM || COMPILE_TEST
  851. help
  852. If you say yes to this option, support will be included for the
  853. built-in camera control interface on the Qualcomm SoCs.
  854. This driver can also be built as a module. If so, the module
  855. will be called i2c-qcom-cci.
  856. config I2C_QCOM_GENI
  857. tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
  858. depends on ARCH_QCOM || COMPILE_TEST
  859. depends on QCOM_GENI_SE
  860. help
  861. This driver supports GENI serial engine based I2C controller in
  862. master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
  863. yes to this option, support will be included for the built-in I2C
  864. interface on the Qualcomm Technologies Inc.'s SoCs.
  865. This driver can also be built as a module. If so, the module
  866. will be called i2c-qcom-geni.
  867. config I2C_QUP
  868. tristate "Qualcomm QUP based I2C controller"
  869. depends on ARCH_QCOM || COMPILE_TEST
  870. help
  871. If you say yes to this option, support will be included for the
  872. built-in I2C interface on the Qualcomm SoCs.
  873. This driver can also be built as a module. If so, the module
  874. will be called i2c-qup.
  875. config I2C_RIIC
  876. tristate "Renesas RIIC adapter"
  877. depends on ARCH_RENESAS || COMPILE_TEST
  878. help
  879. If you say yes to this option, support will be included for the
  880. Renesas RIIC I2C interface.
  881. This driver can also be built as a module. If so, the module
  882. will be called i2c-riic.
  883. config I2C_RK3X
  884. tristate "Rockchip RK3xxx I2C adapter"
  885. depends on OF && COMMON_CLK
  886. help
  887. Say Y here to include support for the I2C adapter in Rockchip RK3xxx
  888. SoCs.
  889. This driver can also be built as a module. If so, the module will
  890. be called i2c-rk3x.
  891. config I2C_RZV2M
  892. tristate "Renesas RZ/V2M adapter"
  893. depends on ARCH_RENESAS || COMPILE_TEST
  894. help
  895. If you say yes to this option, support will be included for the
  896. Renesas RZ/V2M I2C interface.
  897. This driver can also be built as a module. If so, the module
  898. will be called i2c-rzv2m.
  899. config I2C_S3C2410
  900. tristate "S3C/Exynos I2C Driver"
  901. depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || COMPILE_TEST
  902. help
  903. Say Y here to include support for I2C controller in the
  904. Samsung SoCs (S3C, S5Pv210, Exynos).
  905. config I2C_SH7760
  906. tristate "Renesas SH7760 I2C Controller"
  907. depends on CPU_SUBTYPE_SH7760
  908. help
  909. This driver supports the 2 I2C interfaces on the Renesas SH7760.
  910. This driver can also be built as a module. If so, the module
  911. will be called i2c-sh7760.
  912. config I2C_SH_MOBILE
  913. tristate "SuperH Mobile I2C Controller"
  914. depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
  915. help
  916. If you say yes to this option, support will be included for the
  917. built-in I2C interface on the Renesas SH-Mobile processor.
  918. This driver can also be built as a module. If so, the module
  919. will be called i2c-sh_mobile.
  920. config I2C_SIMTEC
  921. tristate "Simtec Generic I2C interface"
  922. select I2C_ALGOBIT
  923. help
  924. If you say yes to this option, support will be included for
  925. the Simtec Generic I2C interface. This driver is for the
  926. simple I2C bus used on newer Simtec products for general
  927. I2C, such as DDC on the Simtec BBD2016A.
  928. This driver can also be built as a module. If so, the module
  929. will be called i2c-simtec.
  930. config I2C_SPRD
  931. tristate "Spreadtrum I2C interface"
  932. depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
  933. depends on COMMON_CLK
  934. help
  935. If you say yes to this option, support will be included for the
  936. Spreadtrum I2C interface.
  937. config I2C_ST
  938. tristate "STMicroelectronics SSC I2C support"
  939. depends on ARCH_STI || COMPILE_TEST
  940. help
  941. Enable this option to add support for STMicroelectronics SoCs
  942. hardware SSC (Synchronous Serial Controller) as an I2C controller.
  943. This driver can also be built as module. If so, the module
  944. will be called i2c-st.
  945. config I2C_STM32F4
  946. tristate "STMicroelectronics STM32F4 I2C support"
  947. depends on ARCH_STM32 || COMPILE_TEST
  948. help
  949. Enable this option to add support for STM32 I2C controller embedded
  950. in STM32F4 SoCs.
  951. This driver can also be built as module. If so, the module
  952. will be called i2c-stm32f4.
  953. config I2C_STM32F7
  954. tristate "STMicroelectronics STM32F7 I2C support"
  955. depends on ARCH_STM32 || COMPILE_TEST
  956. select I2C_SLAVE
  957. select I2C_SMBUS
  958. help
  959. Enable this option to add support for STM32 I2C controller embedded
  960. in STM32F7 SoCs.
  961. This driver can also be built as module. If so, the module
  962. will be called i2c-stm32f7.
  963. config I2C_SUN6I_P2WI
  964. tristate "Allwinner sun6i internal P2WI controller"
  965. depends on RESET_CONTROLLER
  966. depends on MACH_SUN6I || COMPILE_TEST
  967. help
  968. If you say yes to this option, support will be included for the
  969. P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
  970. SOCs.
  971. The P2WI looks like an SMBus controller (which supports only byte
  972. accesses), except that it only supports one slave device.
  973. This interface is used to connect to specific PMIC devices (like the
  974. AXP221).
  975. config I2C_SYNQUACER
  976. tristate "Socionext SynQuacer I2C controller"
  977. depends on ARCH_SYNQUACER || COMPILE_TEST
  978. help
  979. Say Y here to include support for the I2C controller used in some
  980. Fujitsu and Socionext SoCs.
  981. This driver can also be built as a module. If so, the module
  982. will be called i2c-synquacer.
  983. config I2C_TEGRA
  984. tristate "NVIDIA Tegra internal I2C controller"
  985. depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
  986. # COMPILE_TEST needs architectures with readsX()/writesX() primitives
  987. help
  988. If you say yes to this option, support will be included for the
  989. I2C controller embedded in NVIDIA Tegra SOCs
  990. config I2C_TEGRA_BPMP
  991. tristate "NVIDIA Tegra BPMP I2C controller"
  992. depends on TEGRA_BPMP || COMPILE_TEST
  993. default y if TEGRA_BPMP
  994. help
  995. If you say yes to this option, support will be included for the I2C
  996. controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
  997. This I2C driver is a 'virtual' I2C driver. The real driver is part
  998. of the BPMP firmware, and this driver merely communicates with that
  999. real driver.
  1000. config I2C_UNIPHIER
  1001. tristate "UniPhier FIFO-less I2C controller"
  1002. depends on ARCH_UNIPHIER || COMPILE_TEST
  1003. help
  1004. If you say yes to this option, support will be included for
  1005. the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
  1006. or older UniPhier SoCs.
  1007. config I2C_UNIPHIER_F
  1008. tristate "UniPhier FIFO-builtin I2C controller"
  1009. depends on ARCH_UNIPHIER || COMPILE_TEST
  1010. help
  1011. If you say yes to this option, support will be included for
  1012. the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
  1013. PH1-Pro5, or newer UniPhier SoCs.
  1014. config I2C_VERSATILE
  1015. tristate "ARM Versatile/Realview I2C bus support"
  1016. depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
  1017. select I2C_ALGOBIT
  1018. help
  1019. Say yes if you want to support the I2C serial bus on ARMs Versatile
  1020. range of platforms.
  1021. This driver can also be built as a module. If so, the module
  1022. will be called i2c-versatile.
  1023. config I2C_WMT
  1024. tristate "Wondermedia WM8xxx SoC I2C bus support"
  1025. depends on ARCH_VT8500 || COMPILE_TEST
  1026. help
  1027. Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
  1028. SoCs.
  1029. This driver can also be built as a module. If so, the module will be
  1030. called i2c-wmt.
  1031. config I2C_OCTEON
  1032. tristate "Cavium OCTEON I2C bus support"
  1033. depends on CAVIUM_OCTEON_SOC
  1034. help
  1035. Say yes if you want to support the I2C serial bus on Cavium
  1036. OCTEON SOC.
  1037. This driver can also be built as a module. If so, the module
  1038. will be called i2c-octeon.
  1039. config I2C_THUNDERX
  1040. tristate "Cavium ThunderX I2C bus support"
  1041. depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
  1042. select I2C_SMBUS
  1043. help
  1044. Say yes if you want to support the I2C serial bus on Cavium
  1045. ThunderX SOC.
  1046. This driver can also be built as a module. If so, the module
  1047. will be called i2c-thunderx.
  1048. config I2C_XILINX
  1049. tristate "Xilinx I2C Controller"
  1050. depends on HAS_IOMEM
  1051. help
  1052. If you say yes to this option, support will be included for the
  1053. Xilinx I2C controller.
  1054. This driver can also be built as a module. If so, the module
  1055. will be called xilinx_i2c.
  1056. config I2C_XLP9XX
  1057. tristate "Cavium ThunderX2 I2C support"
  1058. depends on ARCH_THUNDER2 || COMPILE_TEST
  1059. help
  1060. This driver enables support for the on-chip I2C interface of
  1061. the Cavium ThunderX2 processors. (Originally on Netlogic XLP SoCs.)
  1062. This driver can also be built as a module. If so, the module will
  1063. be called i2c-xlp9xx.
  1064. config I2C_RCAR
  1065. tristate "Renesas R-Car I2C Controller"
  1066. depends on ARCH_RENESAS || COMPILE_TEST
  1067. select I2C_SLAVE
  1068. select I2C_SMBUS
  1069. select RESET_CONTROLLER if ARCH_RCAR_GEN3 || ARCH_RCAR_GEN4
  1070. help
  1071. If you say yes to this option, support will be included for the
  1072. R-Car I2C controller.
  1073. This driver can also be built as a module. If so, the module
  1074. will be called i2c-rcar.
  1075. comment "External I2C/SMBus adapter drivers"
  1076. config I2C_DIOLAN_U2C
  1077. tristate "Diolan U2C-12 USB adapter"
  1078. depends on USB
  1079. help
  1080. If you say yes to this option, support will be included for Diolan
  1081. U2C-12, a USB to I2C interface.
  1082. This driver can also be built as a module. If so, the module
  1083. will be called i2c-diolan-u2c.
  1084. config I2C_DLN2
  1085. tristate "Diolan DLN-2 USB I2C adapter"
  1086. depends on MFD_DLN2
  1087. help
  1088. If you say yes to this option, support will be included for Diolan
  1089. DLN2, a USB to I2C interface.
  1090. This driver can also be built as a module. If so, the module
  1091. will be called i2c-dln2.
  1092. config I2C_LJCA
  1093. tristate "I2C functionality of Intel La Jolla Cove Adapter"
  1094. depends on USB_LJCA
  1095. default USB_LJCA
  1096. help
  1097. If you say yes to this option, I2C functionality support of Intel
  1098. La Jolla Cove Adapter (LJCA) will be included.
  1099. This driver can also be built as a module. If so, the module
  1100. will be called i2c-ljca.
  1101. config I2C_CP2615
  1102. tristate "Silicon Labs CP2615 USB sound card and I2C adapter"
  1103. depends on USB
  1104. help
  1105. If you say yes to this option, support will be included for Silicon
  1106. Labs CP2615's I2C interface.
  1107. This driver can also be built as a module. If so, the module
  1108. will be called i2c-cp2615.
  1109. config I2C_PARPORT
  1110. tristate "Parallel port adapter"
  1111. depends on PARPORT
  1112. select I2C_ALGOBIT
  1113. select I2C_SMBUS
  1114. help
  1115. This supports parallel port I2C adapters such as the ones made by
  1116. Philips or Velleman, Analog Devices evaluation boards, and more.
  1117. Basically any adapter using the parallel port as an I2C bus with
  1118. no extra chipset is supported by this driver, or could be. Please
  1119. read the file Documentation/i2c/busses/i2c-parport.rst for details.
  1120. This support is also available as a module. If so, the module
  1121. will be called i2c-parport.
  1122. config I2C_PCI1XXXX
  1123. tristate "PCI1XXXX I2C Host Adapter"
  1124. depends on PCI
  1125. help
  1126. If you say yes to this option, support will be included for
  1127. Microchip PCI1XXXX's I2C interface.
  1128. This driver can also be built as a module. If so, the module will
  1129. be called i2c-mchp-pci1xxxx.
  1130. config I2C_ROBOTFUZZ_OSIF
  1131. tristate "RobotFuzz Open Source InterFace USB adapter"
  1132. depends on USB
  1133. help
  1134. If you say yes to this option, support will be included for the
  1135. RobotFuzz Open Source InterFace USB to I2C interface.
  1136. This driver can also be built as a module. If so, the module
  1137. will be called i2c-osif.
  1138. config I2C_TAOS_EVM
  1139. tristate "TAOS evaluation module"
  1140. depends on TTY
  1141. select SERIO
  1142. select SERIO_SERPORT
  1143. help
  1144. This supports TAOS evaluation modules on serial port. In order to
  1145. use this driver, you will need the inputattach tool, which is part
  1146. of the input-utils package.
  1147. If unsure, say N.
  1148. This support is also available as a module. If so, the module
  1149. will be called i2c-taos-evm.
  1150. config I2C_TINY_USB
  1151. tristate "Tiny-USB adapter"
  1152. depends on USB
  1153. help
  1154. If you say yes to this option, support will be included for the
  1155. i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
  1156. http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
  1157. This driver can also be built as a module. If so, the module
  1158. will be called i2c-tiny-usb.
  1159. config I2C_VIPERBOARD
  1160. tristate "Viperboard I2C master support"
  1161. depends on MFD_VIPERBOARD && USB
  1162. help
  1163. Say yes here to access the I2C part of the Nano River
  1164. Technologies Viperboard as I2C master.
  1165. See viperboard API specification and Nano
  1166. River Tech's viperboard.h for detailed meaning
  1167. of the module parameters.
  1168. comment "Other I2C/SMBus bus drivers"
  1169. config I2C_ACORN
  1170. tristate "Acorn IOC/IOMD I2C bus support"
  1171. depends on ARCH_ACORN
  1172. default y
  1173. select I2C_ALGOBIT
  1174. help
  1175. Say yes if you want to support the I2C bus on Acorn platforms.
  1176. If you don't know, say Y.
  1177. config I2C_ELEKTOR
  1178. tristate "Elektor ISA card"
  1179. depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
  1180. select I2C_ALGOPCF
  1181. help
  1182. This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
  1183. such an adapter.
  1184. This support is also available as a module. If so, the module
  1185. will be called i2c-elektor.
  1186. config I2C_ICY
  1187. tristate "ICY Zorro card"
  1188. depends on ZORRO
  1189. select I2C_ALGOPCF
  1190. help
  1191. This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
  1192. Say Y if you own such an adapter.
  1193. This support is also available as a module. If so, the module
  1194. will be called i2c-icy.
  1195. If you have a 2019 edition board with an LTC2990 sensor at address
  1196. 0x4c, loading the module 'ltc2990' is sufficient to enable it.
  1197. config I2C_MLXCPLD
  1198. tristate "Mellanox I2C driver"
  1199. depends on X86_64 || (ARM64 && ACPI) || COMPILE_TEST
  1200. depends on HAS_IOPORT
  1201. help
  1202. This exposes the Mellanox platform I2C busses to the linux I2C layer
  1203. for X86 and ARM64/ACPI based systems.
  1204. Controller is implemented as CPLD logic.
  1205. This driver can also be built as a module. If so, the module will be
  1206. called as i2c-mlxcpld.
  1207. config I2C_PCA_ISA
  1208. tristate "PCA9564/PCA9665 on an ISA bus"
  1209. depends on ISA
  1210. select I2C_ALGOPCA
  1211. help
  1212. This driver supports ISA boards using the Philips PCA9564/PCA9665
  1213. parallel bus to I2C bus controller.
  1214. This driver can also be built as a module. If so, the module
  1215. will be called i2c-pca-isa.
  1216. This device is almost undetectable and using this driver on a
  1217. system which doesn't have this device will result in long
  1218. delays when I2C/SMBus chip drivers are loaded (e.g. at boot
  1219. time). If unsure, say N.
  1220. config I2C_SIBYTE
  1221. tristate "SiByte SMBus interface"
  1222. depends on SIBYTE_SB1xxx_SOC
  1223. help
  1224. Supports the SiByte SOC on-chip I2C interfaces (2 channels).
  1225. config I2C_CROS_EC_TUNNEL
  1226. tristate "ChromeOS EC tunnel I2C bus"
  1227. depends on CROS_EC
  1228. help
  1229. If you say yes here you get an I2C bus that will tunnel i2c commands
  1230. through to the other side of the ChromeOS EC to the i2c bus
  1231. connected there. This will work whatever the interface used to
  1232. talk to the EC (SPI, I2C or LPC).
  1233. config I2C_XGENE_SLIMPRO
  1234. tristate "APM X-Gene SoC I2C SLIMpro devices support"
  1235. depends on ARCH_XGENE && MAILBOX
  1236. help
  1237. Enable I2C bus access using the APM X-Gene SoC SLIMpro
  1238. co-processor. The I2C device access the I2C bus via the X-Gene
  1239. to SLIMpro (On chip coprocessor) mailbox mechanism.
  1240. If unsure, say N.
  1241. config SCx200_ACB
  1242. tristate "Geode ACCESS.bus support"
  1243. depends on X86_32 && PCI
  1244. help
  1245. Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
  1246. SC1100 processors and the CS5535 and CS5536 Geode companion devices.
  1247. If you don't know what to do here, say N.
  1248. This support is also available as a module. If so, the module
  1249. will be called scx200_acb.
  1250. config I2C_OPAL
  1251. tristate "IBM OPAL I2C driver"
  1252. depends on PPC_POWERNV
  1253. default y
  1254. help
  1255. This exposes the PowerNV platform i2c busses to the linux i2c layer,
  1256. the driver is based on the OPAL interfaces.
  1257. This driver can also be built as a module. If so, the module will be
  1258. called as i2c-opal.
  1259. config I2C_FSI
  1260. tristate "FSI I2C driver"
  1261. depends on FSI
  1262. help
  1263. Driver for FSI bus attached I2C masters. These are I2C masters that
  1264. are connected to the system over an FSI bus, instead of the more
  1265. common PCI or MMIO interface.
  1266. This driver can also be built as a module. If so, the module will be
  1267. called as i2c-fsi.
  1268. config I2C_VIRTIO
  1269. tristate "Virtio I2C Adapter"
  1270. select VIRTIO
  1271. help
  1272. If you say yes to this option, support will be included for the virtio
  1273. I2C adapter driver. The hardware can be emulated by any device model
  1274. software according to the virtio protocol.
  1275. This driver can also be built as a module. If so, the module
  1276. will be called i2c-virtio.
  1277. endmenu