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