xref: /linux/drivers/i2c/busses/Kconfig (revision fcc79e1714e8c2b8e216dc3149812edd37884eef)
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_CGBC
539	tristate "Congatec I2C Controller"
540	depends on MFD_CGBC
541	help
542	  This driver supports the 2 I2C interfaces on the Congatec Board
543	  Controller.
544
545	  This driver can also be built as a module. If so, the module will
546	  be called i2c-cgbc.ko.
547
548config I2C_CPM
549	tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
550	depends on CPM1 || CPM2
551	help
552	  This supports the use of the I2C interface on Freescale
553	  processors with CPM1 or CPM2.
554
555	  This driver can also be built as a module.  If so, the module
556	  will be called i2c-cpm.
557
558config I2C_DAVINCI
559	tristate "DaVinci I2C driver"
560	depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
561	help
562	  Support for TI DaVinci I2C controller driver.
563
564	  This driver can also be built as a module.  If so, the module
565	  will be called i2c-davinci.
566
567	  Please note that this driver might be needed to bring up other
568	  devices such as DaVinci NIC.
569	  For details please see http://www.ti.com/davinci
570
571config I2C_DESIGNWARE_CORE
572	tristate "Synopsys DesignWare I2C adapter"
573	select REGMAP
574	help
575	  This option enables support for the Synopsys DesignWare I2C adapter.
576	  This driver includes support for the I2C host on the Synopsys
577	  Designware I2C adapter.
578
579	  To compile the driver as a module, choose M here: the module will be
580	  called i2c-designware-core.
581
582if I2C_DESIGNWARE_CORE
583
584config I2C_DESIGNWARE_SLAVE
585	bool "Synopsys DesignWare Slave"
586	select I2C_SLAVE
587	help
588	  If you say yes to this option, support will be included for the
589	  Synopsys DesignWare I2C slave adapter.
590
591config I2C_DESIGNWARE_PLATFORM
592	tristate "Synopsys DesignWare Platform driver"
593	depends on (ACPI && COMMON_CLK) || !ACPI
594	select MFD_SYSCON if MIPS_BAIKAL_T1
595	default I2C_DESIGNWARE_CORE
596	help
597	  If you say yes to this option, support will be included for the
598	  Synopsys DesignWare I2C adapters on the platform bus.
599
600	  This driver can also be built as a module.  If so, the module
601	  will be called i2c-designware-platform.
602
603config I2C_DESIGNWARE_AMDPSP
604	bool "AMD PSP I2C semaphore support"
605	depends on ACPI
606	depends on CRYPTO_DEV_SP_PSP
607	depends on PCI
608	depends on I2C_DESIGNWARE_PLATFORM
609	depends on (I2C_DESIGNWARE_PLATFORM=y && CRYPTO_DEV_CCP_DD=y) || \
610		   (I2C_DESIGNWARE_PLATFORM=m && CRYPTO_DEV_CCP_DD)
611	help
612	  This driver enables managed host access to the selected I2C bus shared
613	  between AMD CPU and AMD PSP.
614
615	  You should say Y if running on an AMD system equipped with the PSP.
616
617config I2C_DESIGNWARE_BAYTRAIL
618	bool "Intel Baytrail I2C semaphore support"
619	depends on ACPI
620	depends on I2C_DESIGNWARE_PLATFORM
621	depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
622		   (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
623	help
624	  This driver enables managed host access to the PMIC I2C bus on select
625	  Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
626	  the host to request uninterrupted access to the PMIC's I2C bus from
627	  the platform firmware controlling it. You should say Y if running on
628	  a BayTrail system using the AXP288.
629
630config I2C_DESIGNWARE_PCI
631	tristate "Synopsys DesignWare PCI driver"
632	depends on PCI
633	select I2C_CCGX_UCSI
634	help
635	  If you say yes to this option, support will be included for the
636	  Synopsys DesignWare I2C adapters on the PCI bus. Only master mode is
637	  supported.
638
639	  This driver can also be built as a module.  If so, the module
640	  will be called i2c-designware-pci.
641
642endif
643
644config I2C_DIGICOLOR
645	tristate "Conexant Digicolor I2C driver"
646	depends on ARCH_DIGICOLOR || COMPILE_TEST
647	help
648	  Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
649
650	  This driver can also be built as a module.  If so, the module
651	  will be called i2c-digicolor.
652
653config I2C_EG20T
654	tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
655	depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
656	help
657	  This driver is for PCH(Platform controller Hub) I2C of EG20T which
658	  is an IOH(Input/Output Hub) for x86 embedded processor.
659	  This driver can access PCH I2C bus device.
660
661	  This driver also can be used for LAPIS Semiconductor IOH(Input/
662	  Output Hub), ML7213, ML7223 and ML7831.
663	  ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
664	  for MP(Media Phone) use and ML7831 IOH is for general purpose use.
665	  ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
666	  ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
667
668config I2C_EMEV2
669	tristate "EMMA Mobile series I2C adapter"
670	depends on HAVE_CLK
671	select I2C_SLAVE
672	help
673	  If you say yes to this option, support will be included for the
674	  I2C interface on the Renesas Electronics EM/EV family of processors.
675
676config I2C_EXYNOS5
677	tristate "Exynos high-speed I2C driver"
678	depends on OF
679	depends on ARCH_EXYNOS || COMPILE_TEST
680	default y if ARCH_EXYNOS
681	help
682	  High-speed I2C controller on Samsung Exynos5 and newer Samsung SoCs:
683	  Exynos5250, Exynos5260, Exynos5410, Exynos542x, Exynos5800,
684	  Exynos5433, Exynos7, Exynos850 and ExynosAutoV9.
685	  Choose Y here only if you build for such Samsung SoC.
686
687config I2C_GPIO
688	tristate "GPIO-based bitbanging I2C"
689	depends on GPIOLIB || COMPILE_TEST
690	select I2C_ALGOBIT
691	help
692	  This is a very simple bitbanging I2C driver utilizing the
693	  arch-neutral GPIO API to control the SCL and SDA lines.
694
695config I2C_GPIO_FAULT_INJECTOR
696	bool "GPIO-based fault injector"
697	depends on I2C_GPIO
698	help
699	  This adds some functionality to the i2c-gpio driver which can inject
700	  faults to an I2C bus, so another bus master can be stress-tested.
701	  This is for debugging. If unsure, say 'no'.
702
703config I2C_GXP
704	tristate "GXP I2C Interface"
705	depends on ARCH_HPE_GXP || COMPILE_TEST
706	help
707	  This enables support for GXP I2C interface. The I2C engines can be
708	  either I2C master or I2C slaves.
709
710config I2C_HIGHLANDER
711	tristate "Highlander FPGA SMBus interface"
712	depends on SH_HIGHLANDER || COMPILE_TEST
713	help
714	  If you say yes to this option, support will be included for
715	  the SMBus interface located in the FPGA on various Highlander
716	  boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
717	  FPGAs. This is wholly unrelated to the SoC I2C.
718
719	  This driver can also be built as a module.  If so, the module
720	  will be called i2c-highlander.
721
722config I2C_HISI
723	tristate "HiSilicon I2C controller"
724	depends on ARM64 || COMPILE_TEST
725	help
726	  Say Y here if you want to have Hisilicon I2C controller support
727	  available on the Kunpeng Server.
728
729	  This driver can also be built as a module. If so, the module
730	  will be called i2c-hisi.
731
732config I2C_IBM_IIC
733	tristate "IBM PPC 4xx on-chip I2C interface"
734	depends on 4xx
735	help
736	  Say Y here if you want to use IIC peripheral found on
737	  embedded IBM PPC 4xx based systems.
738
739	  This driver can also be built as a module.  If so, the module
740	  will be called i2c-ibm_iic.
741
742config I2C_IMG
743	tristate "Imagination Technologies I2C SCB Controller"
744	depends on MIPS || COMPILE_TEST
745	help
746	  Say Y here if you want to use the IMG I2C SCB controller,
747	  available on the TZ1090 and other IMG SoCs.
748
749	  This driver can also be built as a module.  If so, the module
750	  will be called i2c-img-scb.
751
752config I2C_IMX
753	tristate "IMX I2C interface"
754	depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE || 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, 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	help
767	  Say Y here if you want to use the Low Power IIC bus controller
768	  on the Freescale i.MX processors.
769
770	  This driver can also be built as a module. If so, the module
771	  will be called i2c-imx-lpi2c.
772
773config I2C_IOP3XX
774	tristate "Intel IXP4xx on-chip I2C interface"
775	depends on ARCH_IXP4XX || COMPILE_TEST
776	help
777	  Say Y here if you want to use the IIC bus controller on
778	  the Intel IXP4xx Network Processors.
779
780	  This driver can also be built as a module.  If so, the module
781	  will be called i2c-iop3xx.
782
783config I2C_JZ4780
784	tristate "JZ4780 I2C controller interface support"
785	depends on MIPS || COMPILE_TEST
786	help
787	 If you say yes to this option, support will be included for the
788	 Ingenic JZ4780 I2C controller.
789
790	 If you don't know what to do here, say N.
791
792config I2C_KEBA
793	tristate "KEBA I2C controller support"
794	depends on HAS_IOMEM
795	depends on KEBA_CP500 || COMPILE_TEST
796	select AUXILIARY_BUS
797	help
798	  This driver supports the I2C controller found in KEBA system FPGA
799	  devices.
800
801	  This driver can also be built as a module. If so, the module
802	  will be called i2c-keba.
803
804config I2C_KEMPLD
805	tristate "Kontron COM I2C Controller"
806	depends on MFD_KEMPLD
807	help
808	  This enables support for the I2C bus interface on some Kontron ETX
809	  and COMexpress (ETXexpress) modules.
810
811	  This driver can also be built as a module. If so, the module
812	  will be called i2c-kempld.
813
814config I2C_LPC2K
815	tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
816	depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
817	help
818	  This driver supports the I2C interface found several NXP
819	  devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
820
821	  This driver can also be built as a module.  If so, the module
822	  will be called i2c-lpc2k.
823
824config I2C_LS2X
825	tristate "Loongson LS2X I2C adapter"
826	depends on MACH_LOONGSON64 || COMPILE_TEST
827	help
828	  If you say yes to this option, support will be included for the
829	  I2C interface on the Loongson-2K SoCs and Loongson LS7A bridge
830	  chip.
831
832	  This driver can also be built as a module. If so, the module
833	  will be called i2c-ls2x.
834
835config I2C_MLXBF
836        tristate "Mellanox BlueField I2C controller"
837        depends on MELLANOX_PLATFORM && ARM64
838	depends on ACPI
839	select I2C_SLAVE
840        help
841          Enabling this option will add I2C SMBus support for Mellanox BlueField
842          system.
843
844          This driver can also be built as a module. If so, the module will be
845          called i2c-mlxbf.
846
847          This driver implements an I2C SMBus host controller and enables both
848          master and slave functions.
849
850config I2C_MESON
851	tristate "Amlogic Meson I2C controller"
852	depends on ARCH_MESON || COMPILE_TEST
853	depends on COMMON_CLK
854	help
855	  If you say yes to this option, support will be included for the
856	  I2C interface on the Amlogic Meson family of SoCs.
857
858config I2C_MICROCHIP_CORE
859	tristate "Microchip FPGA I2C controller"
860	depends on ARCH_MICROCHIP_POLARFIRE || COMPILE_TEST
861	depends on OF
862	help
863	  If you say yes to this option, support will be included for the
864	  I2C interface on Microchip FPGAs.
865
866	  This driver can also be built as a module. If so, the module will be
867	  called i2c-microchip-core.
868
869config I2C_MPC
870	tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
871	depends on PPC
872	help
873	  If you say yes to this option, support will be included for the
874	  built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
875	  MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
876
877	  This driver can also be built as a module.  If so, the module
878	  will be called i2c-mpc.
879
880config I2C_MT65XX
881	tristate "MediaTek I2C adapter"
882	depends on ARCH_MEDIATEK || COMPILE_TEST
883	help
884	  This selects the MediaTek(R) Integrated Inter Circuit bus driver
885	  for MT65xx and MT81xx.
886	  If you want to use MediaTek(R) I2C interface, say Y or M here.
887	  If unsure, say N.
888
889config I2C_MT7621
890	tristate "MT7621/MT7628 I2C Controller"
891	depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || ARCH_AIROHA || COMPILE_TEST
892	help
893	  Say Y here to include support for I2C controller in the
894	  MediaTek MT7621/MT7628 SoCs.
895
896config I2C_MV64XXX
897	tristate "Marvell mv64xxx I2C Controller"
898	depends on PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
899	help
900	  If you say yes to this option, support will be included for the
901	  built-in I2C interface on the Marvell 64xxx line of host bridges.
902	  This driver is also used for Allwinner SoCs I2C controllers.
903
904	  This driver can also be built as a module.  If so, the module
905	  will be called i2c-mv64xxx.
906
907config I2C_MXS
908	tristate "Freescale i.MX28 I2C interface"
909	depends on SOC_IMX28 || COMPILE_TEST
910	select STMP_DEVICE
911	help
912	  Say Y here if you want to use the I2C bus controller on
913	  the Freescale i.MX28 processors.
914
915	  This driver can also be built as a module.  If so, the module
916	  will be called i2c-mxs.
917
918config I2C_NOMADIK
919	tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
920	depends on ARM_AMBA
921	help
922	  If you say yes to this option, support will be included for the
923	  I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
924	  as well as the STA2X11 PCIe I/O HUB.
925
926config I2C_NPCM
927	tristate "Nuvoton I2C Controller"
928	depends on ARCH_NPCM || COMPILE_TEST
929	help
930	  If you say yes to this option, support will be included for the
931	  Nuvoton I2C controller, which is available on the NPCM BMC
932	  controllers.
933	  Driver can also support slave mode (select I2C_SLAVE).
934
935config I2C_OCORES
936	tristate "OpenCores I2C Controller"
937	help
938	  If you say yes to this option, support will be included for the
939	  OpenCores I2C controller. For details see
940	  http://www.opencores.org/projects.cgi/web/i2c/overview
941
942	  This driver can also be built as a module.  If so, the module
943	  will be called i2c-ocores.
944
945config I2C_OMAP
946	tristate "OMAP I2C adapter"
947	depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
948	default MACH_OMAP_OSK
949	help
950	  If you say yes to this option, support will be included for the
951	  I2C interface on the Texas Instruments OMAP1/2 family of processors.
952	  Like OMAP1510/1610/1710/5912 and OMAP242x.
953	  For details see http://www.ti.com/omap.
954
955config I2C_OWL
956	tristate "Actions Semiconductor Owl I2C Controller"
957	depends on ARCH_ACTIONS || COMPILE_TEST
958	help
959	  Say Y here if you want to use the I2C bus controller on
960	  the Actions Semiconductor Owl SoC's.
961
962config I2C_PASEMI
963	tristate "PA Semi SMBus interface"
964	depends on PPC_PASEMI && PCI
965	help
966	  Supports the PA Semi PWRficient on-chip SMBus interfaces.
967
968config I2C_APPLE
969	tristate "Apple SMBus platform driver"
970	depends on !I2C_PASEMI
971	depends on ARCH_APPLE || COMPILE_TEST
972	default ARCH_APPLE
973	help
974	  Say Y here if you want to use the I2C controller present on Apple
975	  Silicon chips such as the M1.
976
977	  This driver can also be built as a module. If so, the module
978	  will be called i2c-apple.
979
980config I2C_PCA_PLATFORM
981	tristate "PCA9564/PCA9665 as platform device"
982	select I2C_ALGOPCA
983	help
984	  This driver supports a memory mapped Philips PCA9564/PCA9665
985	  parallel bus to I2C bus controller.
986
987	  This driver can also be built as a module.  If so, the module
988	  will be called i2c-pca-platform.
989
990config I2C_PNX
991	tristate "I2C bus support for Philips PNX and NXP LPC targets"
992	depends on ARCH_LPC32XX || COMPILE_TEST
993	help
994	  This driver supports the Philips IP3204 I2C IP block master and/or
995	  slave controller
996
997	  This driver can also be built as a module.  If so, the module
998	  will be called i2c-pnx.
999
1000config I2C_PXA
1001	tristate "Intel PXA2XX I2C adapter"
1002	depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
1003	help
1004	  If you have devices in the PXA I2C bus, say yes to this option.
1005	  This driver can also be built as a module.  If so, the module
1006	  will be called i2c-pxa.
1007
1008config I2C_PXA_PCI
1009	def_bool I2C_PXA && X86_32 && PCI && OF
1010
1011config I2C_PXA_SLAVE
1012	bool "Intel PXA2XX I2C Slave comms support"
1013	depends on I2C_PXA && !X86_32
1014	select I2C_SLAVE
1015	help
1016	  Support I2C slave mode communications on the PXA I2C bus.  This
1017	  is necessary for systems where the PXA may be a target on the
1018	  I2C bus.
1019
1020config I2C_QCOM_CCI
1021	tristate "Qualcomm Camera Control Interface"
1022	depends on ARCH_QCOM || COMPILE_TEST
1023	help
1024	  If you say yes to this option, support will be included for the
1025	  built-in camera control interface on the Qualcomm SoCs.
1026
1027	  This driver can also be built as a module.  If so, the module
1028	  will be called i2c-qcom-cci.
1029
1030config I2C_QCOM_GENI
1031	tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
1032	depends on ARCH_QCOM || COMPILE_TEST
1033	depends on QCOM_GENI_SE
1034	help
1035	  This driver supports GENI serial engine based I2C controller in
1036	  master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
1037	  yes to this option, support will be included for the built-in I2C
1038	  interface on the Qualcomm Technologies Inc.'s SoCs.
1039
1040	  This driver can also be built as a module.  If so, the module
1041	  will be called i2c-qcom-geni.
1042
1043config I2C_QUP
1044	tristate "Qualcomm QUP based I2C controller"
1045	depends on ARCH_QCOM || COMPILE_TEST
1046	help
1047	  If you say yes to this option, support will be included for the
1048	  built-in I2C interface on the Qualcomm SoCs.
1049
1050	  This driver can also be built as a module.  If so, the module
1051	  will be called i2c-qup.
1052
1053config I2C_RIIC
1054	tristate "Renesas RIIC adapter"
1055	depends on ARCH_RENESAS || COMPILE_TEST
1056	help
1057	  If you say yes to this option, support will be included for the
1058	  Renesas RIIC I2C interface.
1059
1060	  This driver can also be built as a module.  If so, the module
1061	  will be called i2c-riic.
1062
1063config I2C_RK3X
1064	tristate "Rockchip RK3xxx I2C adapter"
1065	depends on OF && COMMON_CLK
1066	help
1067	  Say Y here to include support for the I2C adapter in Rockchip RK3xxx
1068	  SoCs.
1069
1070	  This driver can also be built as a module. If so, the module will
1071	  be called i2c-rk3x.
1072
1073config I2C_RZV2M
1074	tristate "Renesas RZ/V2M adapter"
1075	depends on ARCH_RENESAS || COMPILE_TEST
1076	help
1077	  If you say yes to this option, support will be included for the
1078	  Renesas RZ/V2M I2C interface.
1079
1080	  This driver can also be built as a module.  If so, the module
1081	  will be called i2c-rzv2m.
1082
1083config I2C_S3C2410
1084	tristate "S3C/Exynos I2C Driver"
1085	depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || COMPILE_TEST
1086	help
1087	  Say Y here to include support for I2C controller in the
1088	  Samsung SoCs (S3C, S5Pv210, Exynos).
1089
1090config I2C_SH7760
1091	tristate "Renesas SH7760 I2C Controller"
1092	depends on CPU_SUBTYPE_SH7760
1093	help
1094	  This driver supports the 2 I2C interfaces on the Renesas SH7760.
1095
1096	  This driver can also be built as a module.  If so, the module
1097	  will be called i2c-sh7760.
1098
1099config I2C_SH_MOBILE
1100	tristate "SuperH Mobile I2C Controller"
1101	depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
1102	help
1103	  If you say yes to this option, support will be included for the
1104	  built-in I2C interface on the Renesas SH-Mobile processor.
1105
1106	  This driver can also be built as a module.  If so, the module
1107	  will be called i2c-sh_mobile.
1108
1109config I2C_SIMTEC
1110	tristate "Simtec Generic I2C interface"
1111	select I2C_ALGOBIT
1112	help
1113	  If you say yes to this option, support will be included for
1114	  the Simtec Generic I2C interface. This driver is for the
1115	  simple I2C bus used on newer Simtec products for general
1116	  I2C, such as DDC on the Simtec BBD2016A.
1117
1118	  This driver can also be built as a module. If so, the module
1119	  will be called i2c-simtec.
1120
1121config I2C_SPRD
1122	tristate "Spreadtrum I2C interface"
1123	depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
1124	depends on COMMON_CLK
1125	help
1126	  If you say yes to this option, support will be included for the
1127	  Spreadtrum I2C interface.
1128
1129config I2C_ST
1130	tristate "STMicroelectronics SSC I2C support"
1131	depends on ARCH_STI || COMPILE_TEST
1132	help
1133	  Enable this option to add support for STMicroelectronics SoCs
1134	  hardware SSC (Synchronous Serial Controller) as an I2C controller.
1135
1136	  This driver can also be built as module. If so, the module
1137	  will be called i2c-st.
1138
1139config I2C_STM32F4
1140	tristate "STMicroelectronics STM32F4 I2C support"
1141	depends on ARCH_STM32 || COMPILE_TEST
1142	help
1143	  Enable this option to add support for STM32 I2C controller embedded
1144	  in STM32F4 SoCs.
1145
1146	  This driver can also be built as module. If so, the module
1147	  will be called i2c-stm32f4.
1148
1149config I2C_STM32F7
1150	tristate "STMicroelectronics STM32F7 I2C support"
1151	depends on ARCH_STM32 || COMPILE_TEST
1152	select I2C_SLAVE
1153	select I2C_SMBUS
1154	help
1155	  Enable this option to add support for STM32 I2C controller embedded
1156	  in STM32F7 SoCs.
1157
1158	  This driver can also be built as module. If so, the module
1159	  will be called i2c-stm32f7.
1160
1161config I2C_SUN6I_P2WI
1162	tristate "Allwinner sun6i internal P2WI controller"
1163	depends on RESET_CONTROLLER
1164	depends on MACH_SUN6I || COMPILE_TEST
1165	help
1166	  If you say yes to this option, support will be included for the
1167	  P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1168	  SOCs.
1169	  The P2WI looks like an SMBus controller (which supports only byte
1170	  accesses), except that it only supports one slave device.
1171	  This interface is used to connect to specific PMIC devices (like the
1172	  AXP221).
1173
1174config I2C_SYNQUACER
1175	tristate "Socionext SynQuacer I2C controller"
1176	depends on ARCH_SYNQUACER || COMPILE_TEST
1177	help
1178	  Say Y here to include support for the I2C controller used in some
1179	  Fujitsu and Socionext SoCs.
1180
1181	  This driver can also be built as a module. If so, the module
1182	  will be called i2c-synquacer.
1183
1184config I2C_TEGRA
1185	tristate "NVIDIA Tegra internal I2C controller"
1186	depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
1187	# COMPILE_TEST needs architectures with readsX()/writesX() primitives
1188	help
1189	  If you say yes to this option, support will be included for the
1190	  I2C controller embedded in NVIDIA Tegra SOCs
1191
1192config I2C_TEGRA_BPMP
1193	tristate "NVIDIA Tegra BPMP I2C controller"
1194	depends on TEGRA_BPMP || COMPILE_TEST
1195	default y if TEGRA_BPMP
1196	help
1197	  If you say yes to this option, support will be included for the I2C
1198	  controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1199
1200	  This I2C driver is a 'virtual' I2C driver. The real driver is part
1201	  of the BPMP firmware, and this driver merely communicates with that
1202	  real driver.
1203
1204config I2C_UNIPHIER
1205	tristate "UniPhier FIFO-less I2C controller"
1206	depends on ARCH_UNIPHIER || COMPILE_TEST
1207	help
1208	  If you say yes to this option, support will be included for
1209	  the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1210	  or older UniPhier SoCs.
1211
1212config I2C_UNIPHIER_F
1213	tristate "UniPhier FIFO-builtin I2C controller"
1214	depends on ARCH_UNIPHIER || COMPILE_TEST
1215	help
1216	  If you say yes to this option, support will be included for
1217	  the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1218	  PH1-Pro5, or newer UniPhier SoCs.
1219
1220config I2C_VERSATILE
1221	tristate "ARM Versatile/Realview I2C bus support"
1222	depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1223	select I2C_ALGOBIT
1224	help
1225	  Say yes if you want to support the I2C serial bus on ARMs Versatile
1226	  range of platforms.
1227
1228	  This driver can also be built as a module.  If so, the module
1229	  will be called i2c-versatile.
1230
1231config I2C_WMT
1232	tristate "Wondermedia WM8xxx SoC I2C bus support"
1233	depends on ARCH_VT8500 || COMPILE_TEST
1234	help
1235	  Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1236	  SoCs.
1237
1238	  This driver can also be built as a module. If so, the module will be
1239	  called i2c-wmt.
1240
1241config I2C_OCTEON
1242	tristate "Cavium OCTEON I2C bus support"
1243	depends on CAVIUM_OCTEON_SOC
1244	help
1245	  Say yes if you want to support the I2C serial bus on Cavium
1246	  OCTEON SOC.
1247
1248	  This driver can also be built as a module.  If so, the module
1249	  will be called i2c-octeon.
1250
1251config I2C_THUNDERX
1252	tristate "Cavium ThunderX I2C bus support"
1253	depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1254	select I2C_SMBUS
1255	help
1256	  Say yes if you want to support the I2C serial bus on Cavium
1257	  ThunderX SOC.
1258
1259	  This driver can also be built as a module.  If so, the module
1260	  will be called i2c-thunderx.
1261
1262config I2C_XILINX
1263	tristate "Xilinx I2C Controller"
1264	depends on HAS_IOMEM
1265	help
1266	  If you say yes to this option, support will be included for the
1267	  Xilinx I2C controller.
1268
1269	  This driver can also be built as a module.  If so, the module
1270	  will be called xilinx_i2c.
1271
1272config I2C_XLP9XX
1273	tristate "Cavium ThunderX2 I2C support"
1274	depends on ARCH_THUNDER2 || COMPILE_TEST
1275	help
1276	  This driver enables support for the on-chip I2C interface of
1277	  the Cavium ThunderX2 processors. (Originally on Netlogic XLP SoCs.)
1278
1279	  This driver can also be built as a module.  If so, the module will
1280	  be called i2c-xlp9xx.
1281
1282config I2C_RCAR
1283	tristate "Renesas R-Car I2C Controller"
1284	depends on ARCH_RENESAS || COMPILE_TEST
1285	select I2C_SLAVE
1286	select I2C_SMBUS
1287	select RESET_CONTROLLER if ARCH_RCAR_GEN3 || ARCH_RCAR_GEN4
1288	help
1289	  If you say yes to this option, support will be included for the
1290	  R-Car I2C controller.
1291
1292	  This driver can also be built as a module.  If so, the module
1293	  will be called i2c-rcar.
1294
1295comment "External I2C/SMBus adapter drivers"
1296
1297config I2C_DIOLAN_U2C
1298	tristate "Diolan U2C-12 USB adapter"
1299	depends on USB
1300	help
1301	  If you say yes to this option, support will be included for Diolan
1302	  U2C-12, 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-diolan-u2c.
1306
1307config I2C_DLN2
1308	tristate "Diolan DLN-2 USB I2C adapter"
1309	depends on MFD_DLN2
1310	help
1311	 If you say yes to this option, support will be included for Diolan
1312	 DLN2, a USB to I2C interface.
1313
1314	 This driver can also be built as a module.  If so, the module
1315	 will be called i2c-dln2.
1316
1317config I2C_LJCA
1318	tristate "I2C functionality of Intel La Jolla Cove Adapter"
1319	depends on USB_LJCA
1320	default USB_LJCA
1321	help
1322	  If you say yes to this option, I2C functionality support of Intel
1323	  La Jolla Cove Adapter (LJCA) will be included.
1324
1325	  This driver can also be built as a module.  If so, the module
1326	  will be called i2c-ljca.
1327
1328config I2C_CP2615
1329	tristate "Silicon Labs CP2615 USB sound card and I2C adapter"
1330	depends on USB
1331	help
1332	  If you say yes to this option, support will be included for Silicon
1333	  Labs CP2615's I2C interface.
1334
1335	  This driver can also be built as a module.  If so, the module
1336	  will be called i2c-cp2615.
1337
1338config I2C_PARPORT
1339	tristate "Parallel port adapter"
1340	depends on PARPORT
1341	select I2C_ALGOBIT
1342	select I2C_SMBUS
1343	help
1344	  This supports parallel port I2C adapters such as the ones made by
1345	  Philips or Velleman, Analog Devices evaluation boards, and more.
1346	  Basically any adapter using the parallel port as an I2C bus with
1347	  no extra chipset is supported by this driver, or could be. Please
1348	  read the file Documentation/i2c/busses/i2c-parport.rst for details.
1349
1350	  This support is also available as a module.  If so, the module
1351	  will be called i2c-parport.
1352
1353config I2C_PCI1XXXX
1354	tristate "PCI1XXXX I2C Host Adapter"
1355	depends on PCI
1356	help
1357	  If you say yes to this option, support will be included for
1358	  Microchip PCI1XXXX's I2C interface.
1359
1360	  This driver can also be built as a module. If so, the module will
1361	  be called i2c-mchp-pci1xxxx.
1362
1363config I2C_ROBOTFUZZ_OSIF
1364	tristate "RobotFuzz Open Source InterFace USB adapter"
1365	depends on USB
1366	help
1367	  If you say yes to this option, support will be included for the
1368	  RobotFuzz Open Source InterFace USB to I2C interface.
1369
1370	  This driver can also be built as a module.  If so, the module
1371	  will be called i2c-osif.
1372
1373config I2C_TAOS_EVM
1374	tristate "TAOS evaluation module"
1375	depends on TTY
1376	select SERIO
1377	select SERIO_SERPORT
1378	help
1379	  This supports TAOS evaluation modules on serial port. In order to
1380	  use this driver, you will need the inputattach tool, which is part
1381	  of the input-utils package.
1382
1383	  If unsure, say N.
1384
1385	  This support is also available as a module.  If so, the module
1386	  will be called i2c-taos-evm.
1387
1388config I2C_TINY_USB
1389	tristate "Tiny-USB adapter"
1390	depends on USB
1391	help
1392	  If you say yes to this option, support will be included for the
1393	  i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1394	  http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1395
1396	  This driver can also be built as a module.  If so, the module
1397	  will be called i2c-tiny-usb.
1398
1399config I2C_VIPERBOARD
1400	tristate "Viperboard I2C master support"
1401	depends on MFD_VIPERBOARD && USB
1402	help
1403	  Say yes here to access the I2C part of the Nano River
1404	  Technologies Viperboard as I2C master.
1405	  See viperboard API specification and Nano
1406	  River Tech's viperboard.h for detailed meaning
1407	  of the module parameters.
1408
1409comment "Other I2C/SMBus bus drivers"
1410
1411config I2C_ACORN
1412	tristate "Acorn IOC/IOMD I2C bus support"
1413	depends on ARCH_ACORN
1414	default y
1415	select I2C_ALGOBIT
1416	help
1417	  Say yes if you want to support the I2C bus on Acorn platforms.
1418
1419	  If you don't know, say Y.
1420
1421config I2C_ELEKTOR
1422	tristate "Elektor ISA card"
1423	depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1424	select I2C_ALGOPCF
1425	help
1426	  This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
1427	  such an adapter.
1428
1429	  This support is also available as a module.  If so, the module
1430	  will be called i2c-elektor.
1431
1432config I2C_ICY
1433	tristate "ICY Zorro card"
1434	depends on ZORRO
1435	select I2C_ALGOPCF
1436	help
1437	  This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
1438	  Say Y if you own such an adapter.
1439
1440	  This support is also available as a module.  If so, the module
1441	  will be called i2c-icy.
1442
1443	  If you have a 2019 edition board with an LTC2990 sensor at address
1444	  0x4c, loading the module 'ltc2990' is sufficient to enable it.
1445
1446config I2C_MLXCPLD
1447	tristate "Mellanox I2C driver"
1448	depends on X86_64 || (ARM64 && ACPI) || COMPILE_TEST
1449	depends on HAS_IOPORT
1450	help
1451	  This exposes the Mellanox platform I2C busses to the linux I2C layer
1452	  for X86 and ARM64/ACPI based systems.
1453	  Controller is implemented as CPLD logic.
1454
1455	  This driver can also be built as a module. If so, the module will be
1456	  called as i2c-mlxcpld.
1457
1458config I2C_PCA_ISA
1459	tristate "PCA9564/PCA9665 on an ISA bus"
1460	depends on ISA
1461	select I2C_ALGOPCA
1462	help
1463	  This driver supports ISA boards using the Philips PCA9564/PCA9665
1464	  parallel bus to I2C bus controller.
1465
1466	  This driver can also be built as a module.  If so, the module
1467	  will be called i2c-pca-isa.
1468
1469	  This device is almost undetectable and using this driver on a
1470	  system which doesn't have this device will result in long
1471	  delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1472	  time).  If unsure, say N.
1473
1474config I2C_SIBYTE
1475	tristate "SiByte SMBus interface"
1476	depends on SIBYTE_SB1xxx_SOC
1477	help
1478	  Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1479
1480config I2C_CROS_EC_TUNNEL
1481	tristate "ChromeOS EC tunnel I2C bus"
1482	depends on CROS_EC
1483	help
1484	  If you say yes here you get an I2C bus that will tunnel i2c commands
1485	  through to the other side of the ChromeOS EC to the i2c bus
1486	  connected there. This will work whatever the interface used to
1487	  talk to the EC (SPI, I2C or LPC).
1488
1489config I2C_XGENE_SLIMPRO
1490	tristate "APM X-Gene SoC I2C SLIMpro devices support"
1491	depends on ARCH_XGENE && MAILBOX
1492	help
1493	  Enable I2C bus access using the APM X-Gene SoC SLIMpro
1494	  co-processor. The I2C device access the I2C bus via the X-Gene
1495	  to SLIMpro (On chip coprocessor) mailbox mechanism.
1496	  If unsure, say N.
1497
1498config SCx200_ACB
1499	tristate "Geode ACCESS.bus support"
1500	depends on X86_32 && PCI
1501	help
1502	  Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1503	  SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1504
1505	  If you don't know what to do here, say N.
1506
1507	  This support is also available as a module.  If so, the module
1508	  will be called scx200_acb.
1509
1510config I2C_OPAL
1511	tristate "IBM OPAL I2C driver"
1512	depends on PPC_POWERNV
1513	default y
1514	help
1515	  This exposes the PowerNV platform i2c busses to the linux i2c layer,
1516	  the driver is based on the OPAL interfaces.
1517
1518	  This driver can also be built as a module. If so, the module will be
1519	  called as i2c-opal.
1520
1521config I2C_FSI
1522	tristate "FSI I2C driver"
1523	depends on FSI
1524	help
1525	  Driver for FSI bus attached I2C masters. These are I2C masters that
1526	  are connected to the system over an FSI bus, instead of the more
1527	  common PCI or MMIO interface.
1528
1529	  This driver can also be built as a module. If so, the module will be
1530	  called as i2c-fsi.
1531
1532config I2C_VIRTIO
1533        tristate "Virtio I2C Adapter"
1534        select VIRTIO
1535        help
1536          If you say yes to this option, support will be included for the virtio
1537          I2C adapter driver. The hardware can be emulated by any device model
1538          software according to the virtio protocol.
1539
1540          This driver can also be built as a module. If so, the module
1541          will be called i2c-virtio.
1542
1543endmenu
1544