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