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