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