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	depends on KEBA_CP500 || COMPILE_TEST
786	select AUXILIARY_BUS
787	help
788	  This driver supports the I2C controller found in KEBA system FPGA
789	  devices.
790
791	  This driver can also be built as a module. If so, the module
792	  will be called i2c-keba.
793
794config I2C_KEMPLD
795	tristate "Kontron COM I2C Controller"
796	depends on MFD_KEMPLD
797	help
798	  This enables support for the I2C bus interface on some Kontron ETX
799	  and COMexpress (ETXexpress) modules.
800
801	  This driver can also be built as a module. If so, the module
802	  will be called i2c-kempld.
803
804config I2C_LPC2K
805	tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
806	depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
807	help
808	  This driver supports the I2C interface found several NXP
809	  devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
810
811	  This driver can also be built as a module.  If so, the module
812	  will be called i2c-lpc2k.
813
814config I2C_LS2X
815	tristate "Loongson LS2X I2C adapter"
816	depends on MACH_LOONGSON64 || COMPILE_TEST
817	help
818	  If you say yes to this option, support will be included for the
819	  I2C interface on the Loongson-2K SoCs and Loongson LS7A bridge
820	  chip.
821
822	  This driver can also be built as a module. If so, the module
823	  will be called i2c-ls2x.
824
825config I2C_MLXBF
826        tristate "Mellanox BlueField I2C controller"
827        depends on MELLANOX_PLATFORM && ARM64
828	depends on ACPI
829	select I2C_SLAVE
830        help
831          Enabling this option will add I2C SMBus support for Mellanox BlueField
832          system.
833
834          This driver can also be built as a module. If so, the module will be
835          called i2c-mlxbf.
836
837          This driver implements an I2C SMBus host controller and enables both
838          master and slave functions.
839
840config I2C_MESON
841	tristate "Amlogic Meson I2C controller"
842	depends on ARCH_MESON || COMPILE_TEST
843	depends on COMMON_CLK
844	help
845	  If you say yes to this option, support will be included for the
846	  I2C interface on the Amlogic Meson family of SoCs.
847
848config I2C_MICROCHIP_CORE
849	tristate "Microchip FPGA I2C controller"
850	depends on ARCH_MICROCHIP_POLARFIRE || COMPILE_TEST
851	depends on OF
852	help
853	  If you say yes to this option, support will be included for the
854	  I2C interface on Microchip FPGAs.
855
856	  This driver can also be built as a module. If so, the module will be
857	  called i2c-microchip-core.
858
859config I2C_MPC
860	tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
861	depends on PPC
862	help
863	  If you say yes to this option, support will be included for the
864	  built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
865	  MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
866
867	  This driver can also be built as a module.  If so, the module
868	  will be called i2c-mpc.
869
870config I2C_MT65XX
871	tristate "MediaTek I2C adapter"
872	depends on ARCH_MEDIATEK || COMPILE_TEST
873	help
874	  This selects the MediaTek(R) Integrated Inter Circuit bus driver
875	  for MT65xx and MT81xx.
876	  If you want to use MediaTek(R) I2C interface, say Y or M here.
877	  If unsure, say N.
878
879config I2C_MT7621
880	tristate "MT7621/MT7628 I2C Controller"
881	depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || ARCH_AIROHA || COMPILE_TEST
882	help
883	  Say Y here to include support for I2C controller in the
884	  MediaTek MT7621/MT7628 SoCs.
885
886config I2C_MV64XXX
887	tristate "Marvell mv64xxx I2C Controller"
888	depends on PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
889	help
890	  If you say yes to this option, support will be included for the
891	  built-in I2C interface on the Marvell 64xxx line of host bridges.
892	  This driver is also used for Allwinner SoCs I2C controllers.
893
894	  This driver can also be built as a module.  If so, the module
895	  will be called i2c-mv64xxx.
896
897config I2C_MXS
898	tristate "Freescale i.MX28 I2C interface"
899	depends on SOC_IMX28 || COMPILE_TEST
900	select STMP_DEVICE
901	help
902	  Say Y here if you want to use the I2C bus controller on
903	  the Freescale i.MX28 processors.
904
905	  This driver can also be built as a module.  If so, the module
906	  will be called i2c-mxs.
907
908config I2C_NOMADIK
909	tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
910	depends on ARM_AMBA
911	help
912	  If you say yes to this option, support will be included for the
913	  I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
914	  as well as the STA2X11 PCIe I/O HUB.
915
916config I2C_NPCM
917	tristate "Nuvoton I2C Controller"
918	depends on ARCH_NPCM || COMPILE_TEST
919	help
920	  If you say yes to this option, support will be included for the
921	  Nuvoton I2C controller, which is available on the NPCM BMC
922	  controllers.
923	  Driver can also support slave mode (select I2C_SLAVE).
924
925config I2C_OCORES
926	tristate "OpenCores I2C Controller"
927	help
928	  If you say yes to this option, support will be included for the
929	  OpenCores I2C controller. For details see
930	  http://www.opencores.org/projects.cgi/web/i2c/overview
931
932	  This driver can also be built as a module.  If so, the module
933	  will be called i2c-ocores.
934
935config I2C_OMAP
936	tristate "OMAP I2C adapter"
937	depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
938	default MACH_OMAP_OSK
939	help
940	  If you say yes to this option, support will be included for the
941	  I2C interface on the Texas Instruments OMAP1/2 family of processors.
942	  Like OMAP1510/1610/1710/5912 and OMAP242x.
943	  For details see http://www.ti.com/omap.
944
945config I2C_OWL
946	tristate "Actions Semiconductor Owl I2C Controller"
947	depends on ARCH_ACTIONS || COMPILE_TEST
948	help
949	  Say Y here if you want to use the I2C bus controller on
950	  the Actions Semiconductor Owl SoC's.
951
952config I2C_PASEMI
953	tristate "PA Semi SMBus interface"
954	depends on PPC_PASEMI && PCI
955	help
956	  Supports the PA Semi PWRficient on-chip SMBus interfaces.
957
958config I2C_APPLE
959	tristate "Apple SMBus platform driver"
960	depends on !I2C_PASEMI
961	depends on ARCH_APPLE || COMPILE_TEST
962	default ARCH_APPLE
963	help
964	  Say Y here if you want to use the I2C controller present on Apple
965	  Silicon chips such as the M1.
966
967	  This driver can also be built as a module. If so, the module
968	  will be called i2c-apple.
969
970config I2C_PCA_PLATFORM
971	tristate "PCA9564/PCA9665 as platform device"
972	select I2C_ALGOPCA
973	help
974	  This driver supports a memory mapped Philips PCA9564/PCA9665
975	  parallel bus to I2C bus controller.
976
977	  This driver can also be built as a module.  If so, the module
978	  will be called i2c-pca-platform.
979
980config I2C_PNX
981	tristate "I2C bus support for Philips PNX and NXP LPC targets"
982	depends on ARCH_LPC32XX || COMPILE_TEST
983	help
984	  This driver supports the Philips IP3204 I2C IP block master and/or
985	  slave controller
986
987	  This driver can also be built as a module.  If so, the module
988	  will be called i2c-pnx.
989
990config I2C_PXA
991	tristate "Intel PXA2XX I2C adapter"
992	depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
993	help
994	  If you have devices in the PXA I2C bus, say yes to this option.
995	  This driver can also be built as a module.  If so, the module
996	  will be called i2c-pxa.
997
998config I2C_PXA_PCI
999	def_bool I2C_PXA && X86_32 && PCI && OF
1000
1001config I2C_PXA_SLAVE
1002	bool "Intel PXA2XX I2C Slave comms support"
1003	depends on I2C_PXA && !X86_32
1004	select I2C_SLAVE
1005	help
1006	  Support I2C slave mode communications on the PXA I2C bus.  This
1007	  is necessary for systems where the PXA may be a target on the
1008	  I2C bus.
1009
1010config I2C_QCOM_CCI
1011	tristate "Qualcomm Camera Control Interface"
1012	depends on ARCH_QCOM || COMPILE_TEST
1013	help
1014	  If you say yes to this option, support will be included for the
1015	  built-in camera control interface on the Qualcomm SoCs.
1016
1017	  This driver can also be built as a module.  If so, the module
1018	  will be called i2c-qcom-cci.
1019
1020config I2C_QCOM_GENI
1021	tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
1022	depends on ARCH_QCOM || COMPILE_TEST
1023	depends on QCOM_GENI_SE
1024	help
1025	  This driver supports GENI serial engine based I2C controller in
1026	  master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
1027	  yes to this option, support will be included for the built-in I2C
1028	  interface on the Qualcomm Technologies Inc.'s SoCs.
1029
1030	  This driver can also be built as a module.  If so, the module
1031	  will be called i2c-qcom-geni.
1032
1033config I2C_QUP
1034	tristate "Qualcomm QUP based I2C controller"
1035	depends on ARCH_QCOM || COMPILE_TEST
1036	help
1037	  If you say yes to this option, support will be included for the
1038	  built-in I2C interface on the Qualcomm SoCs.
1039
1040	  This driver can also be built as a module.  If so, the module
1041	  will be called i2c-qup.
1042
1043config I2C_RIIC
1044	tristate "Renesas RIIC adapter"
1045	depends on ARCH_RENESAS || COMPILE_TEST
1046	help
1047	  If you say yes to this option, support will be included for the
1048	  Renesas RIIC I2C interface.
1049
1050	  This driver can also be built as a module.  If so, the module
1051	  will be called i2c-riic.
1052
1053config I2C_RK3X
1054	tristate "Rockchip RK3xxx I2C adapter"
1055	depends on OF && COMMON_CLK
1056	help
1057	  Say Y here to include support for the I2C adapter in Rockchip RK3xxx
1058	  SoCs.
1059
1060	  This driver can also be built as a module. If so, the module will
1061	  be called i2c-rk3x.
1062
1063config I2C_RZV2M
1064	tristate "Renesas RZ/V2M adapter"
1065	depends on ARCH_RENESAS || COMPILE_TEST
1066	help
1067	  If you say yes to this option, support will be included for the
1068	  Renesas RZ/V2M I2C interface.
1069
1070	  This driver can also be built as a module.  If so, the module
1071	  will be called i2c-rzv2m.
1072
1073config I2C_S3C2410
1074	tristate "S3C/Exynos I2C Driver"
1075	depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || COMPILE_TEST
1076	help
1077	  Say Y here to include support for I2C controller in the
1078	  Samsung SoCs (S3C, S5Pv210, Exynos).
1079
1080config I2C_SH7760
1081	tristate "Renesas SH7760 I2C Controller"
1082	depends on CPU_SUBTYPE_SH7760
1083	help
1084	  This driver supports the 2 I2C interfaces on the Renesas SH7760.
1085
1086	  This driver can also be built as a module.  If so, the module
1087	  will be called i2c-sh7760.
1088
1089config I2C_SH_MOBILE
1090	tristate "SuperH Mobile I2C Controller"
1091	depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
1092	help
1093	  If you say yes to this option, support will be included for the
1094	  built-in I2C interface on the Renesas SH-Mobile processor.
1095
1096	  This driver can also be built as a module.  If so, the module
1097	  will be called i2c-sh_mobile.
1098
1099config I2C_SIMTEC
1100	tristate "Simtec Generic I2C interface"
1101	select I2C_ALGOBIT
1102	help
1103	  If you say yes to this option, support will be included for
1104	  the Simtec Generic I2C interface. This driver is for the
1105	  simple I2C bus used on newer Simtec products for general
1106	  I2C, such as DDC on the Simtec BBD2016A.
1107
1108	  This driver can also be built as a module. If so, the module
1109	  will be called i2c-simtec.
1110
1111config I2C_SPRD
1112	tristate "Spreadtrum I2C interface"
1113	depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
1114	depends on COMMON_CLK
1115	help
1116	  If you say yes to this option, support will be included for the
1117	  Spreadtrum I2C interface.
1118
1119config I2C_ST
1120	tristate "STMicroelectronics SSC I2C support"
1121	depends on ARCH_STI || COMPILE_TEST
1122	help
1123	  Enable this option to add support for STMicroelectronics SoCs
1124	  hardware SSC (Synchronous Serial Controller) as an I2C controller.
1125
1126	  This driver can also be built as module. If so, the module
1127	  will be called i2c-st.
1128
1129config I2C_STM32F4
1130	tristate "STMicroelectronics STM32F4 I2C support"
1131	depends on ARCH_STM32 || COMPILE_TEST
1132	help
1133	  Enable this option to add support for STM32 I2C controller embedded
1134	  in STM32F4 SoCs.
1135
1136	  This driver can also be built as module. If so, the module
1137	  will be called i2c-stm32f4.
1138
1139config I2C_STM32F7
1140	tristate "STMicroelectronics STM32F7 I2C support"
1141	depends on ARCH_STM32 || COMPILE_TEST
1142	select I2C_SLAVE
1143	select I2C_SMBUS
1144	help
1145	  Enable this option to add support for STM32 I2C controller embedded
1146	  in STM32F7 SoCs.
1147
1148	  This driver can also be built as module. If so, the module
1149	  will be called i2c-stm32f7.
1150
1151config I2C_SUN6I_P2WI
1152	tristate "Allwinner sun6i internal P2WI controller"
1153	depends on RESET_CONTROLLER
1154	depends on MACH_SUN6I || COMPILE_TEST
1155	help
1156	  If you say yes to this option, support will be included for the
1157	  P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1158	  SOCs.
1159	  The P2WI looks like an SMBus controller (which supports only byte
1160	  accesses), except that it only supports one slave device.
1161	  This interface is used to connect to specific PMIC devices (like the
1162	  AXP221).
1163
1164config I2C_SYNQUACER
1165	tristate "Socionext SynQuacer I2C controller"
1166	depends on ARCH_SYNQUACER || COMPILE_TEST
1167	help
1168	  Say Y here to include support for the I2C controller used in some
1169	  Fujitsu and Socionext SoCs.
1170
1171	  This driver can also be built as a module. If so, the module
1172	  will be called i2c-synquacer.
1173
1174config I2C_TEGRA
1175	tristate "NVIDIA Tegra internal I2C controller"
1176	depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
1177	# COMPILE_TEST needs architectures with readsX()/writesX() primitives
1178	help
1179	  If you say yes to this option, support will be included for the
1180	  I2C controller embedded in NVIDIA Tegra SOCs
1181
1182config I2C_TEGRA_BPMP
1183	tristate "NVIDIA Tegra BPMP I2C controller"
1184	depends on TEGRA_BPMP || COMPILE_TEST
1185	default y if TEGRA_BPMP
1186	help
1187	  If you say yes to this option, support will be included for the I2C
1188	  controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1189
1190	  This I2C driver is a 'virtual' I2C driver. The real driver is part
1191	  of the BPMP firmware, and this driver merely communicates with that
1192	  real driver.
1193
1194config I2C_UNIPHIER
1195	tristate "UniPhier FIFO-less I2C controller"
1196	depends on ARCH_UNIPHIER || COMPILE_TEST
1197	help
1198	  If you say yes to this option, support will be included for
1199	  the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1200	  or older UniPhier SoCs.
1201
1202config I2C_UNIPHIER_F
1203	tristate "UniPhier FIFO-builtin I2C controller"
1204	depends on ARCH_UNIPHIER || COMPILE_TEST
1205	help
1206	  If you say yes to this option, support will be included for
1207	  the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1208	  PH1-Pro5, or newer UniPhier SoCs.
1209
1210config I2C_VERSATILE
1211	tristate "ARM Versatile/Realview I2C bus support"
1212	depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1213	select I2C_ALGOBIT
1214	help
1215	  Say yes if you want to support the I2C serial bus on ARMs Versatile
1216	  range of platforms.
1217
1218	  This driver can also be built as a module.  If so, the module
1219	  will be called i2c-versatile.
1220
1221config I2C_WMT
1222	tristate "Wondermedia WM8xxx SoC I2C bus support"
1223	depends on ARCH_VT8500 || COMPILE_TEST
1224	help
1225	  Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1226	  SoCs.
1227
1228	  This driver can also be built as a module. If so, the module will be
1229	  called i2c-wmt.
1230
1231config I2C_OCTEON
1232	tristate "Cavium OCTEON I2C bus support"
1233	depends on CAVIUM_OCTEON_SOC
1234	help
1235	  Say yes if you want to support the I2C serial bus on Cavium
1236	  OCTEON SOC.
1237
1238	  This driver can also be built as a module.  If so, the module
1239	  will be called i2c-octeon.
1240
1241config I2C_THUNDERX
1242	tristate "Cavium ThunderX I2C bus support"
1243	depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1244	select I2C_SMBUS
1245	help
1246	  Say yes if you want to support the I2C serial bus on Cavium
1247	  ThunderX SOC.
1248
1249	  This driver can also be built as a module.  If so, the module
1250	  will be called i2c-thunderx.
1251
1252config I2C_XILINX
1253	tristate "Xilinx I2C Controller"
1254	depends on HAS_IOMEM
1255	help
1256	  If you say yes to this option, support will be included for the
1257	  Xilinx I2C controller.
1258
1259	  This driver can also be built as a module.  If so, the module
1260	  will be called xilinx_i2c.
1261
1262config I2C_XLP9XX
1263	tristate "Cavium ThunderX2 I2C support"
1264	depends on ARCH_THUNDER2 || COMPILE_TEST
1265	help
1266	  This driver enables support for the on-chip I2C interface of
1267	  the Cavium ThunderX2 processors. (Originally on Netlogic XLP SoCs.)
1268
1269	  This driver can also be built as a module.  If so, the module will
1270	  be called i2c-xlp9xx.
1271
1272config I2C_RCAR
1273	tristate "Renesas R-Car I2C Controller"
1274	depends on ARCH_RENESAS || COMPILE_TEST
1275	select I2C_SLAVE
1276	select I2C_SMBUS
1277	select RESET_CONTROLLER if ARCH_RCAR_GEN3 || ARCH_RCAR_GEN4
1278	help
1279	  If you say yes to this option, support will be included for the
1280	  R-Car I2C controller.
1281
1282	  This driver can also be built as a module.  If so, the module
1283	  will be called i2c-rcar.
1284
1285comment "External I2C/SMBus adapter drivers"
1286
1287config I2C_DIOLAN_U2C
1288	tristate "Diolan U2C-12 USB adapter"
1289	depends on USB
1290	help
1291	  If you say yes to this option, support will be included for Diolan
1292	  U2C-12, a USB to I2C interface.
1293
1294	  This driver can also be built as a module.  If so, the module
1295	  will be called i2c-diolan-u2c.
1296
1297config I2C_DLN2
1298	tristate "Diolan DLN-2 USB I2C adapter"
1299	depends on MFD_DLN2
1300	help
1301	 If you say yes to this option, support will be included for Diolan
1302	 DLN2, a USB to I2C interface.
1303
1304	 This driver can also be built as a module.  If so, the module
1305	 will be called i2c-dln2.
1306
1307config I2C_LJCA
1308	tristate "I2C functionality of Intel La Jolla Cove Adapter"
1309	depends on USB_LJCA
1310	default USB_LJCA
1311	help
1312	  If you say yes to this option, I2C functionality support of Intel
1313	  La Jolla Cove Adapter (LJCA) will be included.
1314
1315	  This driver can also be built as a module.  If so, the module
1316	  will be called i2c-ljca.
1317
1318config I2C_CP2615
1319	tristate "Silicon Labs CP2615 USB sound card and I2C adapter"
1320	depends on USB
1321	help
1322	  If you say yes to this option, support will be included for Silicon
1323	  Labs CP2615's I2C interface.
1324
1325	  This driver can also be built as a module.  If so, the module
1326	  will be called i2c-cp2615.
1327
1328config I2C_PARPORT
1329	tristate "Parallel port adapter"
1330	depends on PARPORT
1331	select I2C_ALGOBIT
1332	select I2C_SMBUS
1333	help
1334	  This supports parallel port I2C adapters such as the ones made by
1335	  Philips or Velleman, Analog Devices evaluation boards, and more.
1336	  Basically any adapter using the parallel port as an I2C bus with
1337	  no extra chipset is supported by this driver, or could be. Please
1338	  read the file Documentation/i2c/busses/i2c-parport.rst for details.
1339
1340	  This support is also available as a module.  If so, the module
1341	  will be called i2c-parport.
1342
1343config I2C_PCI1XXXX
1344	tristate "PCI1XXXX I2C Host Adapter"
1345	depends on PCI
1346	help
1347	  If you say yes to this option, support will be included for
1348	  Microchip PCI1XXXX's I2C interface.
1349
1350	  This driver can also be built as a module. If so, the module will
1351	  be called i2c-mchp-pci1xxxx.
1352
1353config I2C_ROBOTFUZZ_OSIF
1354	tristate "RobotFuzz Open Source InterFace USB adapter"
1355	depends on USB
1356	help
1357	  If you say yes to this option, support will be included for the
1358	  RobotFuzz Open Source InterFace USB to I2C interface.
1359
1360	  This driver can also be built as a module.  If so, the module
1361	  will be called i2c-osif.
1362
1363config I2C_TAOS_EVM
1364	tristate "TAOS evaluation module"
1365	depends on TTY
1366	select SERIO
1367	select SERIO_SERPORT
1368	help
1369	  This supports TAOS evaluation modules on serial port. In order to
1370	  use this driver, you will need the inputattach tool, which is part
1371	  of the input-utils package.
1372
1373	  If unsure, say N.
1374
1375	  This support is also available as a module.  If so, the module
1376	  will be called i2c-taos-evm.
1377
1378config I2C_TINY_USB
1379	tristate "Tiny-USB adapter"
1380	depends on USB
1381	help
1382	  If you say yes to this option, support will be included for the
1383	  i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1384	  http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1385
1386	  This driver can also be built as a module.  If so, the module
1387	  will be called i2c-tiny-usb.
1388
1389config I2C_VIPERBOARD
1390	tristate "Viperboard I2C master support"
1391	depends on MFD_VIPERBOARD && USB
1392	help
1393	  Say yes here to access the I2C part of the Nano River
1394	  Technologies Viperboard as I2C master.
1395	  See viperboard API specification and Nano
1396	  River Tech's viperboard.h for detailed meaning
1397	  of the module parameters.
1398
1399comment "Other I2C/SMBus bus drivers"
1400
1401config I2C_ACORN
1402	tristate "Acorn IOC/IOMD I2C bus support"
1403	depends on ARCH_ACORN
1404	default y
1405	select I2C_ALGOBIT
1406	help
1407	  Say yes if you want to support the I2C bus on Acorn platforms.
1408
1409	  If you don't know, say Y.
1410
1411config I2C_ELEKTOR
1412	tristate "Elektor ISA card"
1413	depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1414	select I2C_ALGOPCF
1415	help
1416	  This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
1417	  such an adapter.
1418
1419	  This support is also available as a module.  If so, the module
1420	  will be called i2c-elektor.
1421
1422config I2C_ICY
1423	tristate "ICY Zorro card"
1424	depends on ZORRO
1425	select I2C_ALGOPCF
1426	help
1427	  This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
1428	  Say Y if you own such an adapter.
1429
1430	  This support is also available as a module.  If so, the module
1431	  will be called i2c-icy.
1432
1433	  If you have a 2019 edition board with an LTC2990 sensor at address
1434	  0x4c, loading the module 'ltc2990' is sufficient to enable it.
1435
1436config I2C_MLXCPLD
1437	tristate "Mellanox I2C driver"
1438	depends on X86_64 || (ARM64 && ACPI) || COMPILE_TEST
1439	depends on HAS_IOPORT
1440	help
1441	  This exposes the Mellanox platform I2C busses to the linux I2C layer
1442	  for X86 and ARM64/ACPI based systems.
1443	  Controller is implemented as CPLD logic.
1444
1445	  This driver can also be built as a module. If so, the module will be
1446	  called as i2c-mlxcpld.
1447
1448config I2C_PCA_ISA
1449	tristate "PCA9564/PCA9665 on an ISA bus"
1450	depends on ISA
1451	select I2C_ALGOPCA
1452	help
1453	  This driver supports ISA boards using the Philips PCA9564/PCA9665
1454	  parallel bus to I2C bus controller.
1455
1456	  This driver can also be built as a module.  If so, the module
1457	  will be called i2c-pca-isa.
1458
1459	  This device is almost undetectable and using this driver on a
1460	  system which doesn't have this device will result in long
1461	  delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1462	  time).  If unsure, say N.
1463
1464config I2C_SIBYTE
1465	tristate "SiByte SMBus interface"
1466	depends on SIBYTE_SB1xxx_SOC
1467	help
1468	  Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1469
1470config I2C_CROS_EC_TUNNEL
1471	tristate "ChromeOS EC tunnel I2C bus"
1472	depends on CROS_EC
1473	help
1474	  If you say yes here you get an I2C bus that will tunnel i2c commands
1475	  through to the other side of the ChromeOS EC to the i2c bus
1476	  connected there. This will work whatever the interface used to
1477	  talk to the EC (SPI, I2C or LPC).
1478
1479config I2C_XGENE_SLIMPRO
1480	tristate "APM X-Gene SoC I2C SLIMpro devices support"
1481	depends on ARCH_XGENE && MAILBOX
1482	help
1483	  Enable I2C bus access using the APM X-Gene SoC SLIMpro
1484	  co-processor. The I2C device access the I2C bus via the X-Gene
1485	  to SLIMpro (On chip coprocessor) mailbox mechanism.
1486	  If unsure, say N.
1487
1488config SCx200_ACB
1489	tristate "Geode ACCESS.bus support"
1490	depends on X86_32 && PCI
1491	help
1492	  Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1493	  SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1494
1495	  If you don't know what to do here, say N.
1496
1497	  This support is also available as a module.  If so, the module
1498	  will be called scx200_acb.
1499
1500config I2C_OPAL
1501	tristate "IBM OPAL I2C driver"
1502	depends on PPC_POWERNV
1503	default y
1504	help
1505	  This exposes the PowerNV platform i2c busses to the linux i2c layer,
1506	  the driver is based on the OPAL interfaces.
1507
1508	  This driver can also be built as a module. If so, the module will be
1509	  called as i2c-opal.
1510
1511config I2C_FSI
1512	tristate "FSI I2C driver"
1513	depends on FSI
1514	help
1515	  Driver for FSI bus attached I2C masters. These are I2C masters that
1516	  are connected to the system over an FSI bus, instead of the more
1517	  common PCI or MMIO interface.
1518
1519	  This driver can also be built as a module. If so, the module will be
1520	  called as i2c-fsi.
1521
1522config I2C_VIRTIO
1523        tristate "Virtio I2C Adapter"
1524        select VIRTIO
1525        help
1526          If you say yes to this option, support will be included for the virtio
1527          I2C adapter driver. The hardware can be emulated by any device model
1528          software according to the virtio protocol.
1529
1530          This driver can also be built as a module. If so, the module
1531          will be called i2c-virtio.
1532
1533endmenu
1534