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