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