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