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