xref: /openbmc/linux/drivers/i2c/busses/Kconfig (revision a701d28e)
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_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_EFM32
590	tristate "EFM32 I2C controller"
591	depends on ARCH_EFM32 || COMPILE_TEST
592	help
593	  This driver supports the i2c block found in Energy Micro's EFM32
594	  SoCs.
595
596config I2C_EG20T
597	tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
598	depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
599	help
600	  This driver is for PCH(Platform controller Hub) I2C of EG20T which
601	  is an IOH(Input/Output Hub) for x86 embedded processor.
602	  This driver can access PCH I2C bus device.
603
604	  This driver also can be used for LAPIS Semiconductor IOH(Input/
605	  Output Hub), ML7213, ML7223 and ML7831.
606	  ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
607	  for MP(Media Phone) use and ML7831 IOH is for general purpose use.
608	  ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
609	  ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
610
611config I2C_EMEV2
612	tristate "EMMA Mobile series I2C adapter"
613	depends on HAVE_CLK
614	select I2C_SLAVE
615	help
616	  If you say yes to this option, support will be included for the
617	  I2C interface on the Renesas Electronics EM/EV family of processors.
618
619config I2C_EXYNOS5
620	tristate "Exynos high-speed I2C driver"
621	depends on OF
622	depends on ARCH_EXYNOS || COMPILE_TEST
623	default y if ARCH_EXYNOS
624	help
625	  High-speed I2C controller on Exynos5 and newer Samsung SoCs.
626
627config I2C_GPIO
628	tristate "GPIO-based bitbanging I2C"
629	depends on GPIOLIB || COMPILE_TEST
630	select I2C_ALGOBIT
631	help
632	  This is a very simple bitbanging I2C driver utilizing the
633	  arch-neutral GPIO API to control the SCL and SDA lines.
634
635config I2C_GPIO_FAULT_INJECTOR
636	bool "GPIO-based fault injector"
637	depends on I2C_GPIO
638	help
639	  This adds some functionality to the i2c-gpio driver which can inject
640	  faults to an I2C bus, so another bus master can be stress-tested.
641	  This is for debugging. If unsure, say 'no'.
642
643config I2C_HIGHLANDER
644	tristate "Highlander FPGA SMBus interface"
645	depends on SH_HIGHLANDER || COMPILE_TEST
646	help
647	  If you say yes to this option, support will be included for
648	  the SMBus interface located in the FPGA on various Highlander
649	  boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
650	  FPGAs. This is wholly unrelated to the SoC I2C.
651
652	  This driver can also be built as a module.  If so, the module
653	  will be called i2c-highlander.
654
655config I2C_IBM_IIC
656	tristate "IBM PPC 4xx on-chip I2C interface"
657	depends on 4xx
658	help
659	  Say Y here if you want to use IIC peripheral found on
660	  embedded IBM PPC 4xx based systems.
661
662	  This driver can also be built as a module.  If so, the module
663	  will be called i2c-ibm_iic.
664
665config I2C_IMG
666	tristate "Imagination Technologies I2C SCB Controller"
667	depends on MIPS || COMPILE_TEST
668	help
669	  Say Y here if you want to use the IMG I2C SCB controller,
670	  available on the TZ1090 and other IMG SoCs.
671
672	  This driver can also be built as a module.  If so, the module
673	  will be called i2c-img-scb.
674
675config I2C_IMX
676	tristate "IMX I2C interface"
677	depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
678	help
679	  Say Y here if you want to use the IIC bus controller on
680	  the Freescale i.MX/MXC, Layerscape or ColdFire processors.
681
682	  This driver can also be built as a module.  If so, the module
683	  will be called i2c-imx.
684
685config I2C_IMX_LPI2C
686	tristate "IMX Low Power I2C interface"
687	depends on ARCH_MXC || COMPILE_TEST
688	help
689	  Say Y here if you want to use the Low Power IIC bus controller
690	  on the Freescale i.MX processors.
691
692	  This driver can also be built as a module. If so, the module
693	  will be called i2c-imx-lpi2c.
694
695config I2C_IOP3XX
696	tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
697	depends on ARCH_IOP32X || ARCH_IXP4XX || COMPILE_TEST
698	help
699	  Say Y here if you want to use the IIC bus controller on
700	  the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
701
702	  This driver can also be built as a module.  If so, the module
703	  will be called i2c-iop3xx.
704
705config I2C_JZ4780
706	tristate "JZ4780 I2C controller interface support"
707	depends on MIPS || COMPILE_TEST
708	help
709	 If you say yes to this option, support will be included for the
710	 Ingenic JZ4780 I2C controller.
711
712	 If you don't know what to do here, say N.
713
714config I2C_KEMPLD
715	tristate "Kontron COM I2C Controller"
716	depends on MFD_KEMPLD
717	help
718	  This enables support for the I2C bus interface on some Kontron ETX
719	  and COMexpress (ETXexpress) modules.
720
721	  This driver can also be built as a module. If so, the module
722	  will be called i2c-kempld.
723
724config I2C_LPC2K
725	tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
726	depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
727	help
728	  This driver supports the I2C interface found several NXP
729	  devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
730
731	  This driver can also be built as a module.  If so, the module
732	  will be called i2c-lpc2k.
733
734config I2C_MLXBF
735        tristate "Mellanox BlueField I2C controller"
736        depends on ARM64
737        help
738          Enabling this option will add I2C SMBus support for Mellanox BlueField
739          system.
740
741          This driver can also be built as a module. If so, the module will be
742          called i2c-mlxbf.
743
744          This driver implements an I2C SMBus host controller and enables both
745          master and slave functions.
746
747config I2C_MESON
748	tristate "Amlogic Meson I2C controller"
749	depends on ARCH_MESON || COMPILE_TEST
750	depends on COMMON_CLK
751	help
752	  If you say yes to this option, support will be included for the
753	  I2C interface on the Amlogic Meson family of SoCs.
754
755config I2C_MPC
756	tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
757	depends on PPC
758	help
759	  If you say yes to this option, support will be included for the
760	  built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
761	  MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
762
763	  This driver can also be built as a module.  If so, the module
764	  will be called i2c-mpc.
765
766config I2C_MT65XX
767	tristate "MediaTek I2C adapter"
768	depends on ARCH_MEDIATEK || COMPILE_TEST
769	help
770	  This selects the MediaTek(R) Integrated Inter Circuit bus driver
771	  for MT65xx and MT81xx.
772	  If you want to use MediaTek(R) I2C interface, say Y or M here.
773	  If unsure, say N.
774
775config I2C_MT7621
776	tristate "MT7621/MT7628 I2C Controller"
777	depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || COMPILE_TEST
778	help
779	  Say Y here to include support for I2C controller in the
780	  MediaTek MT7621/MT7628 SoCs.
781
782config I2C_MV64XXX
783	tristate "Marvell mv64xxx I2C Controller"
784	depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
785	help
786	  If you say yes to this option, support will be included for the
787	  built-in I2C interface on the Marvell 64xxx line of host bridges.
788	  This driver is also used for Allwinner SoCs I2C controllers.
789
790	  This driver can also be built as a module.  If so, the module
791	  will be called i2c-mv64xxx.
792
793config I2C_MXS
794	tristate "Freescale i.MX28 I2C interface"
795	depends on SOC_IMX28 || COMPILE_TEST
796	select STMP_DEVICE
797	help
798	  Say Y here if you want to use the I2C bus controller on
799	  the Freescale i.MX28 processors.
800
801	  This driver can also be built as a module.  If so, the module
802	  will be called i2c-mxs.
803
804config I2C_NOMADIK
805	tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
806	depends on ARM_AMBA
807	help
808	  If you say yes to this option, support will be included for the
809	  I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
810	  as well as the STA2X11 PCIe I/O HUB.
811
812config I2C_NPCM7XX
813	tristate "Nuvoton I2C Controller"
814	depends on ARCH_NPCM7XX || COMPILE_TEST
815	help
816	  If you say yes to this option, support will be included for the
817	  Nuvoton I2C controller, which is available on the NPCM7xx BMC
818	  controller.
819	  Driver can also support slave mode (select I2C_SLAVE).
820
821config I2C_OCORES
822	tristate "OpenCores I2C Controller"
823	help
824	  If you say yes to this option, support will be included for the
825	  OpenCores I2C controller. For details see
826	  http://www.opencores.org/projects.cgi/web/i2c/overview
827
828	  This driver can also be built as a module.  If so, the module
829	  will be called i2c-ocores.
830
831config I2C_OMAP
832	tristate "OMAP I2C adapter"
833	depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
834	default y if MACH_OMAP_H3 || MACH_OMAP_OSK
835	help
836	  If you say yes to this option, support will be included for the
837	  I2C interface on the Texas Instruments OMAP1/2 family of processors.
838	  Like OMAP1510/1610/1710/5912 and OMAP242x.
839	  For details see http://www.ti.com/omap.
840
841config I2C_OWL
842	tristate "Actions Semiconductor Owl I2C Controller"
843	depends on ARCH_ACTIONS || COMPILE_TEST
844	help
845	  Say Y here if you want to use the I2C bus controller on
846	  the Actions Semiconductor Owl SoC's.
847
848config I2C_PASEMI
849	tristate "PA Semi SMBus interface"
850	depends on PPC_PASEMI && PCI
851	help
852	  Supports the PA Semi PWRficient on-chip SMBus interfaces.
853
854config I2C_PCA_PLATFORM
855	tristate "PCA9564/PCA9665 as platform device"
856	select I2C_ALGOPCA
857	help
858	  This driver supports a memory mapped Philips PCA9564/PCA9665
859	  parallel bus to I2C bus controller.
860
861	  This driver can also be built as a module.  If so, the module
862	  will be called i2c-pca-platform.
863
864config I2C_PMCMSP
865	tristate "PMC MSP I2C TWI Controller"
866	depends on PMC_MSP || COMPILE_TEST
867	help
868	  This driver supports the PMC TWI controller on MSP devices.
869
870	  This driver can also be built as module. If so, the module
871	  will be called i2c-pmcmsp.
872
873config I2C_PNX
874	tristate "I2C bus support for Philips PNX and NXP LPC targets"
875	depends on ARCH_LPC32XX || COMPILE_TEST
876	help
877	  This driver supports the Philips IP3204 I2C IP block master and/or
878	  slave controller
879
880	  This driver can also be built as a module.  If so, the module
881	  will be called i2c-pnx.
882
883config I2C_PXA
884	tristate "Intel PXA2XX I2C adapter"
885	depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
886	help
887	  If you have devices in the PXA I2C bus, say yes to this option.
888	  This driver can also be built as a module.  If so, the module
889	  will be called i2c-pxa.
890
891config I2C_PXA_PCI
892	def_bool I2C_PXA && X86_32 && PCI && OF
893
894config I2C_PXA_SLAVE
895	bool "Intel PXA2XX I2C Slave comms support"
896	depends on I2C_PXA && !X86_32
897	select I2C_SLAVE
898	help
899	  Support I2C slave mode communications on the PXA I2C bus.  This
900	  is necessary for systems where the PXA may be a target on the
901	  I2C bus.
902
903config I2C_QCOM_CCI
904	tristate "Qualcomm Camera Control Interface"
905	depends on ARCH_QCOM || COMPILE_TEST
906	help
907	  If you say yes to this option, support will be included for the
908	  built-in camera control interface on the Qualcomm SoCs.
909
910	  This driver can also be built as a module.  If so, the module
911	  will be called i2c-qcom-cci.
912
913config I2C_QCOM_GENI
914	tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
915	depends on ARCH_QCOM || COMPILE_TEST
916	depends on QCOM_GENI_SE
917	help
918	  This driver supports GENI serial engine based I2C controller in
919	  master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
920	  yes to this option, support will be included for the built-in I2C
921	  interface on the Qualcomm Technologies Inc.'s SoCs.
922
923	  This driver can also be built as a module.  If so, the module
924	  will be called i2c-qcom-geni.
925
926config I2C_QUP
927	tristate "Qualcomm QUP based I2C controller"
928	depends on ARCH_QCOM
929	help
930	  If you say yes to this option, support will be included for the
931	  built-in I2C interface on the Qualcomm SoCs.
932
933	  This driver can also be built as a module.  If so, the module
934	  will be called i2c-qup.
935
936config I2C_RIIC
937	tristate "Renesas RIIC adapter"
938	depends on ARCH_RENESAS || COMPILE_TEST
939	help
940	  If you say yes to this option, support will be included for the
941	  Renesas RIIC I2C interface.
942
943	  This driver can also be built as a module.  If so, the module
944	  will be called i2c-riic.
945
946config I2C_RK3X
947	tristate "Rockchip RK3xxx I2C adapter"
948	depends on OF && COMMON_CLK
949	help
950	  Say Y here to include support for the I2C adapter in Rockchip RK3xxx
951	  SoCs.
952
953	  This driver can also be built as a module. If so, the module will
954	  be called i2c-rk3x.
955
956config HAVE_S3C2410_I2C
957	bool
958	help
959	  This will include I2C support for Samsung SoCs. If you want to
960	  include I2C support for any machine, kindly select this in the
961	  respective Kconfig file.
962
963config I2C_S3C2410
964	tristate "S3C/Exynos I2C Driver"
965	depends on HAVE_S3C2410_I2C || COMPILE_TEST
966	help
967	  Say Y here to include support for I2C controller in the
968	  Samsung SoCs (S3C, S5Pv210, Exynos).
969
970config I2C_SH7760
971	tristate "Renesas SH7760 I2C Controller"
972	depends on CPU_SUBTYPE_SH7760
973	help
974	  This driver supports the 2 I2C interfaces on the Renesas SH7760.
975
976	  This driver can also be built as a module.  If so, the module
977	  will be called i2c-sh7760.
978
979config I2C_SH_MOBILE
980	tristate "SuperH Mobile I2C Controller"
981	depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
982	help
983	  If you say yes to this option, support will be included for the
984	  built-in I2C interface on the Renesas SH-Mobile processor.
985
986	  This driver can also be built as a module.  If so, the module
987	  will be called i2c-sh_mobile.
988
989config I2C_SIMTEC
990	tristate "Simtec Generic I2C interface"
991	select I2C_ALGOBIT
992	help
993	  If you say yes to this option, support will be included for
994	  the Simtec Generic I2C interface. This driver is for the
995	  simple I2C bus used on newer Simtec products for general
996	  I2C, such as DDC on the Simtec BBD2016A.
997
998	  This driver can also be built as a module. If so, the module
999	  will be called i2c-simtec.
1000
1001config I2C_SIRF
1002	tristate "CSR SiRFprimaII I2C interface"
1003	depends on ARCH_SIRF || COMPILE_TEST
1004	help
1005	  If you say yes to this option, support will be included for the
1006	  CSR SiRFprimaII I2C interface.
1007
1008	  This driver can also be built as a module.  If so, the module
1009	  will be called i2c-sirf.
1010
1011config I2C_SPRD
1012	tristate "Spreadtrum I2C interface"
1013	depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
1014	help
1015	  If you say yes to this option, support will be included for the
1016	  Spreadtrum I2C interface.
1017
1018config I2C_ST
1019	tristate "STMicroelectronics SSC I2C support"
1020	depends on ARCH_STI || COMPILE_TEST
1021	help
1022	  Enable this option to add support for STMicroelectronics SoCs
1023	  hardware SSC (Synchronous Serial Controller) as an I2C controller.
1024
1025	  This driver can also be built as module. If so, the module
1026	  will be called i2c-st.
1027
1028config I2C_STM32F4
1029	tristate "STMicroelectronics STM32F4 I2C support"
1030	depends on ARCH_STM32 || COMPILE_TEST
1031	help
1032	  Enable this option to add support for STM32 I2C controller embedded
1033	  in STM32F4 SoCs.
1034
1035	  This driver can also be built as module. If so, the module
1036	  will be called i2c-stm32f4.
1037
1038config I2C_STM32F7
1039	tristate "STMicroelectronics STM32F7 I2C support"
1040	depends on ARCH_STM32 || COMPILE_TEST
1041	select I2C_SLAVE
1042	select I2C_SMBUS
1043	help
1044	  Enable this option to add support for STM32 I2C controller embedded
1045	  in STM32F7 SoCs.
1046
1047	  This driver can also be built as module. If so, the module
1048	  will be called i2c-stm32f7.
1049
1050config I2C_STU300
1051	tristate "ST Microelectronics DDC I2C interface"
1052	depends on MACH_U300 || COMPILE_TEST
1053	default y if MACH_U300
1054	help
1055	  If you say yes to this option, support will be included for the
1056	  I2C interface from ST Microelectronics simply called "DDC I2C"
1057	  supporting both I2C and DDC, used in e.g. the U300 series
1058	  mobile platforms.
1059
1060	  This driver can also be built as a module. If so, the module
1061	  will be called i2c-stu300.
1062
1063config I2C_SUN6I_P2WI
1064	tristate "Allwinner sun6i internal P2WI controller"
1065	depends on RESET_CONTROLLER
1066	depends on MACH_SUN6I || COMPILE_TEST
1067	help
1068	  If you say yes to this option, support will be included for the
1069	  P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1070	  SOCs.
1071	  The P2WI looks like an SMBus controller (which supports only byte
1072	  accesses), except that it only supports one slave device.
1073	  This interface is used to connect to specific PMIC devices (like the
1074	  AXP221).
1075
1076config I2C_SYNQUACER
1077	tristate "Socionext SynQuacer I2C controller"
1078	depends on ARCH_SYNQUACER || COMPILE_TEST
1079	help
1080	  Say Y here to include support for the I2C controller used in some
1081	  Fujitsu and Socionext SoCs.
1082
1083	  This driver can also be built as a module. If so, the module
1084	  will be called i2c-synquacer.
1085
1086config I2C_TEGRA
1087	tristate "NVIDIA Tegra internal I2C controller"
1088	depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
1089	# COMPILE_TEST needs architectures with readsX()/writesX() primitives
1090	help
1091	  If you say yes to this option, support will be included for the
1092	  I2C controller embedded in NVIDIA Tegra SOCs
1093
1094config I2C_TEGRA_BPMP
1095	tristate "NVIDIA Tegra BPMP I2C controller"
1096	depends on TEGRA_BPMP || COMPILE_TEST
1097	default y if TEGRA_BPMP
1098	help
1099	  If you say yes to this option, support will be included for the I2C
1100	  controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1101
1102	  This I2C driver is a 'virtual' I2C driver. The real driver is part
1103	  of the BPMP firmware, and this driver merely communicates with that
1104	  real driver.
1105
1106config I2C_UNIPHIER
1107	tristate "UniPhier FIFO-less I2C controller"
1108	depends on ARCH_UNIPHIER || COMPILE_TEST
1109	help
1110	  If you say yes to this option, support will be included for
1111	  the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1112	  or older UniPhier SoCs.
1113
1114config I2C_UNIPHIER_F
1115	tristate "UniPhier FIFO-builtin I2C controller"
1116	depends on ARCH_UNIPHIER || COMPILE_TEST
1117	help
1118	  If you say yes to this option, support will be included for
1119	  the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1120	  PH1-Pro5, or newer UniPhier SoCs.
1121
1122config I2C_VERSATILE
1123	tristate "ARM Versatile/Realview I2C bus support"
1124	depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1125	select I2C_ALGOBIT
1126	help
1127	  Say yes if you want to support the I2C serial bus on ARMs Versatile
1128	  range of platforms.
1129
1130	  This driver can also be built as a module.  If so, the module
1131	  will be called i2c-versatile.
1132
1133config I2C_WMT
1134	tristate "Wondermedia WM8xxx SoC I2C bus support"
1135	depends on ARCH_VT8500 || COMPILE_TEST
1136	help
1137	  Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1138	  SoCs.
1139
1140	  This driver can also be built as a module. If so, the module will be
1141	  called i2c-wmt.
1142
1143config I2C_OCTEON
1144	tristate "Cavium OCTEON I2C bus support"
1145	depends on CAVIUM_OCTEON_SOC
1146	help
1147	  Say yes if you want to support the I2C serial bus on Cavium
1148	  OCTEON SOC.
1149
1150	  This driver can also be built as a module.  If so, the module
1151	  will be called i2c-octeon.
1152
1153config I2C_THUNDERX
1154	tristate "Cavium ThunderX I2C bus support"
1155	depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1156	select I2C_SMBUS
1157	help
1158	  Say yes if you want to support the I2C serial bus on Cavium
1159	  ThunderX SOC.
1160
1161	  This driver can also be built as a module.  If so, the module
1162	  will be called i2c-thunderx.
1163
1164config I2C_XILINX
1165	tristate "Xilinx I2C Controller"
1166	depends on HAS_IOMEM
1167	help
1168	  If you say yes to this option, support will be included for the
1169	  Xilinx I2C controller.
1170
1171	  This driver can also be built as a module.  If so, the module
1172	  will be called xilinx_i2c.
1173
1174config I2C_XLR
1175	tristate "Netlogic XLR and Sigma Designs I2C support"
1176	depends on CPU_XLR || ARCH_TANGO || COMPILE_TEST
1177	help
1178	  This driver enables support for the on-chip I2C interface of
1179	  the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1180
1181	  This driver can also be built as a module.  If so, the module
1182	  will be called i2c-xlr.
1183
1184config I2C_XLP9XX
1185	tristate "XLP9XX I2C support"
1186	depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1187	help
1188	  This driver enables support for the on-chip I2C interface of
1189	  the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1190
1191	  This driver can also be built as a module.  If so, the module will
1192	  be called i2c-xlp9xx.
1193
1194config I2C_RCAR
1195	tristate "Renesas R-Car I2C Controller"
1196	depends on ARCH_RENESAS || COMPILE_TEST
1197	select I2C_SLAVE
1198	select I2C_SMBUS
1199	select RESET_CONTROLLER if ARCH_RCAR_GEN3
1200	help
1201	  If you say yes to this option, support will be included for the
1202	  R-Car I2C controller.
1203
1204	  This driver can also be built as a module.  If so, the module
1205	  will be called i2c-rcar.
1206
1207comment "External I2C/SMBus adapter drivers"
1208
1209config I2C_DIOLAN_U2C
1210	tristate "Diolan U2C-12 USB adapter"
1211	depends on USB
1212	help
1213	  If you say yes to this option, support will be included for Diolan
1214	  U2C-12, a USB to I2C interface.
1215
1216	  This driver can also be built as a module.  If so, the module
1217	  will be called i2c-diolan-u2c.
1218
1219config I2C_DLN2
1220	tristate "Diolan DLN-2 USB I2C adapter"
1221	depends on MFD_DLN2
1222	help
1223	 If you say yes to this option, support will be included for Diolan
1224	 DLN2, a USB to I2C interface.
1225
1226	 This driver can also be built as a module.  If so, the module
1227	 will be called i2c-dln2.
1228
1229config I2C_PARPORT
1230	tristate "Parallel port adapter"
1231	depends on PARPORT
1232	select I2C_ALGOBIT
1233	select I2C_SMBUS
1234	help
1235	  This supports parallel port I2C adapters such as the ones made by
1236	  Philips or Velleman, Analog Devices evaluation boards, and more.
1237	  Basically any adapter using the parallel port as an I2C bus with
1238	  no extra chipset is supported by this driver, or could be. Please
1239	  read the file Documentation/i2c/busses/i2c-parport.rst for details.
1240
1241	  This support is also available as a module.  If so, the module
1242	  will be called i2c-parport.
1243
1244config I2C_ROBOTFUZZ_OSIF
1245	tristate "RobotFuzz Open Source InterFace USB adapter"
1246	depends on USB
1247	help
1248	  If you say yes to this option, support will be included for the
1249	  RobotFuzz Open Source InterFace USB to I2C interface.
1250
1251	  This driver can also be built as a module.  If so, the module
1252	  will be called i2c-osif.
1253
1254config I2C_TAOS_EVM
1255	tristate "TAOS evaluation module"
1256	depends on TTY
1257	select SERIO
1258	select SERIO_SERPORT
1259	help
1260	  This supports TAOS evaluation modules on serial port. In order to
1261	  use this driver, you will need the inputattach tool, which is part
1262	  of the input-utils package.
1263
1264	  If unsure, say N.
1265
1266	  This support is also available as a module.  If so, the module
1267	  will be called i2c-taos-evm.
1268
1269config I2C_TINY_USB
1270	tristate "Tiny-USB adapter"
1271	depends on USB
1272	help
1273	  If you say yes to this option, support will be included for the
1274	  i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1275	  http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1276
1277	  This driver can also be built as a module.  If so, the module
1278	  will be called i2c-tiny-usb.
1279
1280config I2C_VIPERBOARD
1281	tristate "Viperboard I2C master support"
1282	depends on MFD_VIPERBOARD && USB
1283	help
1284	  Say yes here to access the I2C part of the Nano River
1285	  Technologies Viperboard as I2C master.
1286	  See viperboard API specification and Nano
1287	  River Tech's viperboard.h for detailed meaning
1288	  of the module parameters.
1289
1290comment "Other I2C/SMBus bus drivers"
1291
1292config I2C_ACORN
1293	tristate "Acorn IOC/IOMD I2C bus support"
1294	depends on ARCH_ACORN
1295	default y
1296	select I2C_ALGOBIT
1297	help
1298	  Say yes if you want to support the I2C bus on Acorn platforms.
1299
1300	  If you don't know, say Y.
1301
1302config I2C_ELEKTOR
1303	tristate "Elektor ISA card"
1304	depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1305	select I2C_ALGOPCF
1306	help
1307	  This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
1308	  such an adapter.
1309
1310	  This support is also available as a module.  If so, the module
1311	  will be called i2c-elektor.
1312
1313config I2C_ICY
1314	tristate "ICY Zorro card"
1315	depends on ZORRO
1316	select I2C_ALGOPCF
1317	help
1318	  This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
1319	  Say Y if you own such an adapter.
1320
1321	  This support is also available as a module.  If so, the module
1322	  will be called i2c-icy.
1323
1324	  If you have a 2019 edition board with an LTC2990 sensor at address
1325	  0x4c, loading the module 'ltc2990' is sufficient to enable it.
1326
1327config I2C_MLXCPLD
1328	tristate "Mellanox I2C driver"
1329	depends on X86_64 || COMPILE_TEST
1330	help
1331	  This exposes the Mellanox platform I2C busses to the linux I2C layer
1332	  for X86 based systems.
1333	  Controller is implemented as CPLD logic.
1334
1335	  This driver can also be built as a module. If so, the module will be
1336	  called as i2c-mlxcpld.
1337
1338config I2C_PCA_ISA
1339	tristate "PCA9564/PCA9665 on an ISA bus"
1340	depends on ISA
1341	select I2C_ALGOPCA
1342	help
1343	  This driver supports ISA boards using the Philips PCA9564/PCA9665
1344	  parallel bus to I2C bus controller.
1345
1346	  This driver can also be built as a module.  If so, the module
1347	  will be called i2c-pca-isa.
1348
1349	  This device is almost undetectable and using this driver on a
1350	  system which doesn't have this device will result in long
1351	  delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1352	  time).  If unsure, say N.
1353
1354config I2C_SIBYTE
1355	tristate "SiByte SMBus interface"
1356	depends on SIBYTE_SB1xxx_SOC
1357	help
1358	  Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1359
1360config I2C_CROS_EC_TUNNEL
1361	tristate "ChromeOS EC tunnel I2C bus"
1362	depends on CROS_EC
1363	help
1364	  If you say yes here you get an I2C bus that will tunnel i2c commands
1365	  through to the other side of the ChromeOS EC to the i2c bus
1366	  connected there. This will work whatever the interface used to
1367	  talk to the EC (SPI, I2C or LPC).
1368
1369config I2C_XGENE_SLIMPRO
1370	tristate "APM X-Gene SoC I2C SLIMpro devices support"
1371	depends on ARCH_XGENE && MAILBOX
1372	help
1373	  Enable I2C bus access using the APM X-Gene SoC SLIMpro
1374	  co-processor. The I2C device access the I2C bus via the X-Gene
1375	  to SLIMpro (On chip coprocessor) mailbox mechanism.
1376	  If unsure, say N.
1377
1378config SCx200_ACB
1379	tristate "Geode ACCESS.bus support"
1380	depends on X86_32 && PCI
1381	help
1382	  Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1383	  SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1384
1385	  If you don't know what to do here, say N.
1386
1387	  This support is also available as a module.  If so, the module
1388	  will be called scx200_acb.
1389
1390config I2C_OPAL
1391	tristate "IBM OPAL I2C driver"
1392	depends on PPC_POWERNV
1393	default y
1394	help
1395	  This exposes the PowerNV platform i2c busses to the linux i2c layer,
1396	  the driver is based on the OPAL interfaces.
1397
1398	  This driver can also be built as a module. If so, the module will be
1399	  called as i2c-opal.
1400
1401config I2C_ZX2967
1402	tristate "ZTE ZX2967 I2C support"
1403	depends on ARCH_ZX
1404	default y
1405	help
1406	  Selecting this option will add ZX2967 I2C driver.
1407	  This driver can also be built as a module. If so, the module will be
1408	  called i2c-zx2967.
1409
1410config I2C_FSI
1411	tristate "FSI I2C driver"
1412	depends on FSI
1413	help
1414	  Driver for FSI bus attached I2C masters. These are I2C masters that
1415	  are connected to the system over an FSI bus, instead of the more
1416	  common PCI or MMIO interface.
1417
1418	  This driver can also be built as a module. If so, the module will be
1419	  called as i2c-fsi.
1420
1421endmenu
1422