Kconfig 45 KB

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