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