xref: /linux/drivers/mfd/Kconfig (revision 03bd36838e18a5b36444f273bfd3546789ac86c8)
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Multifunction miscellaneous devices
4#
5
6if HAS_IOMEM
7menu "Multifunction device drivers"
8
9config MFD_CORE
10	tristate
11	select IRQ_DOMAIN
12	default n
13
14config MFD_CS5535
15	tristate "AMD CS5535 and CS5536 southbridge core functions"
16	select MFD_CORE
17	depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18	depends on !UML
19	help
20	  This is the core driver for CS5535/CS5536 MFD functions.  This is
21	  necessary for using the board's GPIO and MFGPT functionality.
22
23config MFD_ADP5585
24	tristate "Analog Devices ADP5585 keypad decoder and I/O expander driver"
25	select MFD_CORE
26	select REGMAP_I2C
27	depends on I2C
28	depends on OF || COMPILE_TEST
29	help
30	  Say yes here to add support for the Analog Devices ADP5585 GPIO
31	  expander, PWM and keypad controller. This includes the I2C driver and
32	  the core APIs _only_, you have to select individual components like
33	  the GPIO and PWM functions under the corresponding menus.
34
35config MFD_ALTERA_A10SR
36	bool "Altera Arria10 DevKit System Resource chip"
37	depends on ARCH_INTEL_SOCFPGA && SPI_MASTER=y && OF
38	select REGMAP_SPI
39	select MFD_CORE
40	help
41	  Support for the Altera Arria10 DevKit MAX5 System Resource chip
42	  using the SPI interface. This driver provides common support for
43	  accessing the external gpio extender (LEDs & buttons) and
44	  power supply alarms (hwmon).
45
46config MFD_ALTERA_SYSMGR
47	bool "Altera SOCFPGA System Manager"
48	depends on ARCH_INTEL_SOCFPGA && OF
49	select MFD_SYSCON
50	help
51	  Select this to get System Manager support for all Altera branded
52	  SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by
53	  using regmap_mmio accesses for ARM32 parts and SMC calls to
54	  EL3 for ARM64 parts.
55
56config MFD_ACT8945A
57	tristate "Active-semi ACT8945A"
58	select MFD_CORE
59	select REGMAP_I2C
60	depends on I2C && OF
61	help
62	  Support for the ACT8945A PMIC from Active-semi. This device
63	  features three step-down DC/DC converters and four low-dropout
64	  linear regulators, along with a complete ActivePath battery
65	  charger.
66
67config MFD_SUN4I_GPADC
68	tristate "Allwinner sunxi platforms' GPADC MFD driver"
69	select MFD_CORE
70	select REGMAP_MMIO
71	select REGMAP_IRQ
72	depends on ARCH_SUNXI || COMPILE_TEST
73	depends on !TOUCHSCREEN_SUN4I
74	help
75	  Select this to get support for Allwinner SoCs (A10, A13 and A31) ADC.
76	  This driver will only map the hardware interrupt and registers, you
77	  have to select individual drivers based on this MFD to be able to use
78	  the ADC or the thermal sensor. This will try to probe the ADC driver
79	  sun4i-gpadc-iio and the hwmon driver iio_hwmon.
80
81	  To compile this driver as a module, choose M here: the module will be
82	  called sun4i-gpadc.
83
84config MFD_AS3711
85	bool "AMS AS3711"
86	select MFD_CORE
87	select REGMAP_I2C
88	select REGMAP_IRQ
89	depends on I2C=y
90	help
91	  Support for the AS3711 PMIC from AMS
92
93config MFD_SMPRO
94	tristate "Ampere Computing SMpro core driver"
95	depends on I2C
96	select MFD_CORE
97	select REGMAP_I2C
98	help
99	  Say yes here to enable SMpro driver support for Ampere's Altra
100	  processor family.
101
102	  Ampere's Altra SMpro exposes an I2C regmap interface that can
103	  be accessed by child devices.
104
105config MFD_AS3722
106	tristate "ams AS3722 Power Management IC"
107	select MFD_CORE
108	select REGMAP_I2C
109	select REGMAP_IRQ
110	depends on I2C=y && OF
111	help
112	  The ams AS3722 is a compact system PMU suitable for mobile phones,
113	  tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
114	  controllers, 11 LDOs, RTC, automatic battery, temperature and
115	  over current monitoring, GPIOs, ADC and a watchdog.
116
117config PMIC_ADP5520
118	bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
119	depends on I2C=y
120	help
121	  Say yes here to add support for Analog Devices ADP5520 and ADP5501,
122	  Multifunction Power Management IC. This includes
123	  the I2C driver and the core APIs _only_, you have to select
124	  individual components like LCD backlight, LEDs, GPIOs and Kepad
125	  under the corresponding menus.
126
127config MFD_AAT2870_CORE
128	bool "AnalogicTech AAT2870"
129	select MFD_CORE
130	depends on I2C=y
131	depends on GPIOLIB || COMPILE_TEST
132	help
133	  If you say yes here you get support for the AAT2870.
134	  This driver provides common support for accessing the device,
135	  additional drivers must be enabled in order to use the
136	  functionality of the device.
137
138config MFD_AT91_USART
139	tristate "AT91 USART Driver"
140	select MFD_CORE
141	depends on ARCH_AT91 || COMPILE_TEST
142	help
143	  Select this to get support for AT91 USART IP. This is a wrapper
144	  over at91-usart-serial driver and usart-spi-driver. Only one function
145	  can be used at a time. The choice is done at boot time by the probe
146	  function of this MFD driver according to a device tree property.
147
148config MFD_ATMEL_FLEXCOM
149	tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
150	select MFD_CORE
151	depends on OF
152	help
153	  Select this to get support for Atmel Flexcom. This is a wrapper
154	  which embeds a SPI controller, a I2C controller and a USART. Only
155	  one function can be used at a time. The choice is done at boot time
156	  by the probe function of this MFD driver according to a device tree
157	  property.
158
159config MFD_ATMEL_HLCDC
160	tristate "Atmel HLCDC (High-end LCD Controller)"
161	select MFD_CORE
162	select REGMAP_MMIO
163	depends on OF
164	help
165	  If you say yes here you get support for the HLCDC block.
166	  This driver provides common support for accessing the device,
167	  additional drivers must be enabled in order to use the
168	  functionality of the device.
169
170config MFD_ATMEL_SMC
171	bool
172	select MFD_SYSCON
173
174config MFD_BCM590XX
175	tristate "Broadcom BCM590xx PMUs"
176	select MFD_CORE
177	select REGMAP_I2C
178	depends on I2C
179	help
180	  Support for the BCM590xx PMUs from Broadcom
181
182config MFD_BD9571MWV
183	tristate "ROHM BD9571MWV PMIC"
184	select MFD_CORE
185	select REGMAP_I2C
186	select REGMAP_IRQ
187	depends on I2C
188	help
189	  Support for the ROHM BD9571MWV PMIC, which contains single
190	  voltage regulator, voltage sampling units, GPIO block and
191	  watchdog block.
192
193	  This driver can also be built as a module. If so, the module
194	  will be called bd9571mwv.
195
196config MFD_AC100
197	tristate "X-Powers AC100"
198	select MFD_CORE
199	depends on SUNXI_RSB
200	help
201	  If you say Y here you get support for the X-Powers AC100 audio codec
202	  IC.
203	  This driver include only the core APIs. You have to select individual
204	  components like codecs or RTC under the corresponding menus.
205
206config MFD_AXP20X
207	tristate
208	select MFD_CORE
209	select REGMAP_IRQ
210
211config MFD_AXP20X_I2C
212	tristate "X-Powers AXP series PMICs with I2C"
213	select MFD_AXP20X
214	select REGMAP_I2C
215	depends on I2C
216	help
217	  If you say Y here you get support for the X-Powers AXP series power
218	  management ICs (PMICs) controlled with I2C.
219	  This driver include only the core APIs. You have to select individual
220	  components like regulators or the PEK (Power Enable Key) under the
221	  corresponding menus.
222
223	  Note on x86 this provides an ACPI OpRegion, so this must be 'y'
224	  (builtin) and not a module, as the OpRegion must be available as
225	  soon as possible. For the same reason the I2C bus driver options
226	  I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too.
227
228config MFD_AXP20X_RSB
229	tristate "X-Powers AXP series PMICs with RSB"
230	select MFD_AXP20X
231	depends on SUNXI_RSB
232	help
233	  If you say Y here you get support for the X-Powers AXP series power
234	  management ICs (PMICs) controlled with RSB.
235	  This driver include only the core APIs. You have to select individual
236	  components like regulators or the PEK (Power Enable Key) under the
237	  corresponding menus.
238
239config MFD_CROS_EC_DEV
240	tristate "ChromeOS Embedded Controller multifunction device"
241	select MFD_CORE
242	depends on CROS_EC
243	default CROS_EC
244	help
245	  Select this to get support for ChromeOS Embedded Controller
246	  sub-devices. This driver will instantiate additional drivers such
247	  as RTC, USBPD, etc. but you have to select the individual drivers.
248
249	  To compile this driver as a module, choose M here: the module will be
250	  called cros-ec-dev.
251
252config MFD_CS42L43
253	tristate
254	select MFD_CORE
255	select REGMAP
256	select REGMAP_IRQ
257
258config MFD_CS42L43_I2C
259	tristate "Cirrus Logic CS42L43 (I2C)"
260	depends on I2C
261	select REGMAP_I2C
262	select MFD_CS42L43
263	help
264	  Select this to support the Cirrus Logic CS42L43 PC CODEC with
265	  headphone and class D speaker drivers over I2C.
266
267config MFD_CS42L43_SDW
268	tristate "Cirrus Logic CS42L43 (SoundWire)"
269	depends on SOUNDWIRE
270	select REGMAP_SOUNDWIRE
271	select MFD_CS42L43
272	help
273	  Select this to support the Cirrus Logic CS42L43 PC CODEC with
274	  headphone and class D speaker drivers over SoundWire.
275
276config MFD_MADERA
277	tristate "Cirrus Logic Madera codecs"
278	select MFD_CORE
279	select REGMAP
280	select REGMAP_IRQ
281	select MADERA_IRQ
282	select PINCTRL
283	select PINCTRL_MADERA
284	help
285	  Support for the Cirrus Logic Madera platform audio codecs
286
287config MFD_MADERA_I2C
288	tristate "Cirrus Logic Madera codecs with I2C"
289	depends on MFD_MADERA
290	depends on I2C
291	select REGMAP_I2C
292	help
293	  Support for the Cirrus Logic Madera platform audio SoC
294	  core functionality controlled via I2C.
295
296config MFD_MADERA_SPI
297	tristate "Cirrus Logic Madera codecs with SPI"
298	depends on MFD_MADERA
299	depends on SPI_MASTER
300	select REGMAP_SPI
301	help
302	  Support for the Cirrus Logic Madera platform audio SoC
303	  core functionality controlled via SPI.
304
305config MFD_MAX5970
306	tristate "Maxim 5970/5978 power switch and monitor"
307	depends on I2C && OF
308	select MFD_SIMPLE_MFD_I2C
309	help
310	  This driver controls a Maxim 5970/5978 switch via I2C bus.
311	  The MAX5970/5978 is a smart switch with no output regulation, but
312	  fault protection and voltage and current monitoring capabilities.
313	  Also it supports upto 4 indication leds.
314
315config MFD_CS47L15
316	bool "Cirrus Logic CS47L15"
317	select PINCTRL_CS47L15
318	depends on MFD_MADERA
319	help
320	  Support for Cirrus Logic CS47L15 Smart Codec
321
322config MFD_CS47L35
323	bool "Cirrus Logic CS47L35"
324	select PINCTRL_CS47L35
325	depends on MFD_MADERA
326	help
327	  Support for Cirrus Logic CS47L35 Smart Codec
328
329config MFD_CS47L85
330	bool "Cirrus Logic CS47L85"
331	select PINCTRL_CS47L85
332	depends on MFD_MADERA
333	help
334	  Support for Cirrus Logic CS47L85 Smart Codec
335
336config MFD_CS47L90
337	bool "Cirrus Logic CS47L90/91"
338	select PINCTRL_CS47L90
339	depends on MFD_MADERA
340	help
341	  Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs
342
343config MFD_CS47L92
344	bool "Cirrus Logic CS47L92/93"
345	select PINCTRL_CS47L92
346	depends on MFD_MADERA
347	help
348	  Support for Cirrus Logic CS42L92, CS47L92 and CS47L93 Smart Codecs
349
350config PMIC_DA903X
351	bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
352	depends on I2C=y
353	help
354	  Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
355	  ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
356	  usually found on PXA processors-based platforms. This includes
357	  the I2C driver and the core APIs _only_, you have to select
358	  individual components like LCD backlight, voltage regulators,
359	  LEDs and battery-charger under the corresponding menus.
360
361config PMIC_DA9052
362	bool
363	select MFD_CORE
364
365config MFD_DA9052_SPI
366	bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
367	select REGMAP_SPI
368	select REGMAP_IRQ
369	select PMIC_DA9052
370	depends on SPI_MASTER=y
371	help
372	  Support for the Dialog Semiconductor DA9052 PMIC
373	  when controlled using SPI. This driver provides common support
374	  for accessing the device, additional drivers must be enabled in
375	  order to use the functionality of the device.
376
377config MFD_DA9052_I2C
378	bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
379	select REGMAP_I2C
380	select REGMAP_IRQ
381	select PMIC_DA9052
382	depends on I2C=y
383	help
384	  Support for the Dialog Semiconductor DA9052 PMIC
385	  when controlled using I2C. This driver provides common support
386	  for accessing the device, additional drivers must be enabled in
387	  order to use the functionality of the device.
388
389config MFD_DA9055
390	bool "Dialog Semiconductor DA9055 PMIC Support"
391	select REGMAP_I2C
392	select REGMAP_IRQ
393	select MFD_CORE
394	depends on I2C=y
395	help
396	  Say yes here for support of Dialog Semiconductor DA9055. This is
397	  a Power Management IC. This driver provides common support for
398	  accessing the device as well as the I2C interface to the chip itself.
399	  Additional drivers must be enabled in order to use the functionality
400	  of the device.
401
402config MFD_DA9062
403	tristate "Dialog Semiconductor DA9062/61 PMIC Support"
404	select MFD_CORE
405	select REGMAP_I2C
406	select REGMAP_IRQ
407	depends on I2C
408	help
409	  Say yes here for support for the Dialog Semiconductor DA9061 and
410	  DA9062 PMICs.
411	  This includes the I2C driver and core APIs.
412	  Additional drivers must be enabled in order to use the functionality
413	  of the device.
414
415config MFD_DA9063
416	tristate "Dialog Semiconductor DA9063 PMIC Support"
417	select MFD_CORE
418	select REGMAP_I2C
419	select REGMAP_IRQ
420	depends on I2C
421	help
422	  Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
423	  This includes the I2C driver and core APIs.
424	  Additional drivers must be enabled in order to use the functionality
425	  of the device.
426
427config MFD_DA9150
428	tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
429	depends on I2C
430	select MFD_CORE
431	select REGMAP_I2C
432	select REGMAP_IRQ
433	help
434	  This adds support for the DA9150 integrated charger and fuel-gauge
435	  chip. This driver provides common support for accessing the device.
436	  Additional drivers must be enabled in order to use the specific
437	  features of the device.
438
439config MFD_DLN2
440	tristate "Diolan DLN2 support"
441	select MFD_CORE
442	depends on USB
443	help
444	  This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
445	  DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
446	  etc. must be enabled in order to use the functionality of
447	  the device.
448
449config MFD_ENE_KB3930
450	tristate "ENE KB3930 Embedded Controller support"
451	depends on I2C
452	depends on MACH_MMP3_DT || COMPILE_TEST
453	select MFD_CORE
454	help
455	  This adds support for the power-off functionality and access to
456	  the registers that control LEDS and USB port power on ENE KB3930
457	  Embedded Controller. To use the LED functionality LEDS_ARIEL must
458	  be enabled.
459
460config MFD_EXYNOS_LPASS
461	tristate "Samsung Exynos SoC Low Power Audio Subsystem"
462	depends on ARCH_EXYNOS || COMPILE_TEST
463	select MFD_CORE
464	select REGMAP_MMIO
465	help
466	  Select this option to enable support for Samsung Exynos Low Power
467	  Audio Subsystem present on some of Samsung Exynos
468	  SoCs (e.g. Exynos5433).
469	  Choose Y here only if you build for such Samsung SoC.
470
471config MFD_GATEWORKS_GSC
472	tristate "Gateworks System Controller"
473	depends on I2C && OF
474	select MFD_CORE
475	select REGMAP_I2C
476	select REGMAP_IRQ
477	help
478	  Enable support for the Gateworks System Controller (GSC) found
479	  on Gateworks Single Board Computers supporting system functions
480	  such as push-button monitor, multiple ADC's for voltage and
481	  temperature monitoring, fan controller and watchdog monitor.
482	  This driver provides common support for accessing the device.
483	  Additional drivers must be enabled in order to use the
484	  functionality of the device.
485
486config MFD_MC13XXX
487	tristate
488	depends on SPI_MASTER || I2C
489	select MFD_CORE
490	select REGMAP_IRQ
491	help
492	  Enable support for the Freescale MC13783 and MC13892 PMICs.
493	  This driver provides common support for accessing the device,
494	  additional drivers must be enabled in order to use the
495	  functionality of the device.
496
497config MFD_MC13XXX_SPI
498	tristate "Freescale MC13783 and MC13892 SPI interface"
499	depends on SPI_MASTER
500	select REGMAP_SPI
501	select MFD_MC13XXX
502	help
503	  Select this if your MC13xxx is connected via an SPI bus.
504
505config MFD_MC13XXX_I2C
506	tristate "Freescale MC13892 I2C interface"
507	depends on I2C
508	select REGMAP_I2C
509	select MFD_MC13XXX
510	help
511	  Select this if your MC13xxx is connected via an I2C bus.
512
513config MFD_MP2629
514	tristate "Monolithic Power Systems MP2629 ADC and Battery charger"
515	depends on I2C
516	select REGMAP_I2C
517	select MFD_CORE
518	help
519	  Select this option to enable support for Monolithic Power Systems
520	  battery charger. This provides ADC, thermal and battery charger power
521	  management functions.
522
523config MFD_MXS_LRADC
524	tristate "Freescale i.MX23/i.MX28 LRADC"
525	depends on ARCH_MXS || COMPILE_TEST
526	select MFD_CORE
527	select STMP_DEVICE
528	help
529	  Say yes here to build support for the Low Resolution
530	  Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
531	  processors. This driver provides common support for accessing the
532	  device, additional drivers must be enabled in order to use the
533	  functionality of the device:
534		mxs-lradc-adc for ADC readings
535		mxs-lradc-ts  for touchscreen support
536
537	  This driver can also be built as a module. If so, the module will be
538	  called mxs-lradc.
539
540config MFD_MX25_TSADC
541	tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
542	select REGMAP_MMIO
543	depends on (SOC_IMX25 && OF) || COMPILE_TEST
544	help
545	  Enable support for the integrated Touchscreen and ADC unit of the
546	  i.MX25 processors. They consist of a conversion queue for general
547	  purpose ADC and a queue for Touchscreens.
548
549config MFD_HI6421_PMIC
550	tristate "HiSilicon Hi6421 PMU/Codec IC"
551	depends on OF
552	select MFD_CORE
553	select REGMAP_MMIO
554	help
555	  Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
556	  functions, such as regulators, RTC, codec, Coulomb counter, etc.
557	  This driver includes core APIs _only_. You have to select
558	  individual components like voltage regulators under corresponding
559	  menus in order to enable them.
560	  We communicate with the Hi6421 via memory-mapped I/O.
561
562config MFD_HI6421_SPMI
563	tristate "HiSilicon Hi6421v600 SPMI PMU/Codec IC"
564	depends on OF
565	depends on SPMI
566	select MFD_CORE
567	select REGMAP_SPMI
568	help
569	  Add support for HiSilicon Hi6421v600 SPMI PMIC. Hi6421 includes
570	  multi-functions, such as regulators, RTC, codec, Coulomb counter,
571	  etc.
572
573	  This driver includes core APIs _only_. You have to select
574	  individual components like voltage regulators under corresponding
575	  menus in order to enable them.
576	  We communicate with the Hi6421v600 via a SPMI bus.
577
578config MFD_HI655X_PMIC
579	tristate "HiSilicon Hi655X series PMU/Codec IC"
580	depends on ARCH_HISI || COMPILE_TEST
581	depends on OF
582	select MFD_CORE
583	select REGMAP_MMIO
584	select REGMAP_IRQ
585	help
586	  Select this option to enable Hisilicon hi655x series pmic driver.
587
588config MFD_INTEL_QUARK_I2C_GPIO
589	tristate "Intel Quark MFD I2C GPIO"
590	depends on PCI
591	depends on X86
592	depends on COMMON_CLK
593	select MFD_CORE
594	help
595	  This MFD provides support for I2C and GPIO that exist only
596	  in a single PCI device. It splits the 2 IO devices to
597	  their respective IO driver.
598	  The GPIO exports a total amount of 8 interrupt-capable GPIOs.
599
600config LPC_ICH
601	tristate "Intel ICH LPC"
602	depends on PCI
603	select MFD_CORE
604	select P2SB if X86
605	help
606	  The LPC bridge function of the Intel ICH provides support for
607	  many functional units. This driver provides needed support for
608	  other drivers to control these functions, currently GPIO and
609	  watchdog.
610
611config LPC_SCH
612	tristate "Intel SCH LPC"
613	depends on PCI
614	select MFD_CORE
615	help
616	  LPC bridge function of the Intel SCH provides support for
617	  System Management Bus and General Purpose I/O.
618
619config INTEL_SOC_PMIC
620	bool "Support for Crystal Cove PMIC"
621	depends on HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
622	depends on (X86 && ACPI) || COMPILE_TEST
623	depends on I2C_DESIGNWARE_PLATFORM=y || COMPILE_TEST
624	select MFD_CORE
625	select REGMAP_I2C
626	select REGMAP_IRQ
627	help
628	  Select this option to enable support for Crystal Cove PMIC
629	  on some Intel SoC systems. The PMIC provides ADC, GPIO,
630	  thermal, charger and related power management functions
631	  on these systems.
632
633	  This option is a bool as it provides an ACPI OpRegion which must be
634	  available before any devices using it are probed. This option also
635	  causes the designware-i2c driver to be builtin for the same reason.
636
637config INTEL_SOC_PMIC_BXTWC
638	tristate "Support for Intel Broxton Whiskey Cove PMIC"
639	depends on MFD_INTEL_PMC_BXT
640	select MFD_CORE
641	select REGMAP_IRQ
642	help
643	  Select this option to enable support for Whiskey Cove PMIC
644	  on Intel Broxton systems. The PMIC provides ADC, GPIO,
645	  thermal, charger and related power management functions
646	  on these systems.
647
648config INTEL_SOC_PMIC_CHTWC
649	bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
650	depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
651	depends on X86 || COMPILE_TEST
652	depends on I2C_DESIGNWARE_PLATFORM=y
653	select MFD_CORE
654	select REGMAP_I2C
655	select REGMAP_IRQ
656	help
657	  Select this option to enable support for the Intel Cherry Trail
658	  Whiskey Cove PMIC found on some Intel Cherry Trail systems.
659
660	  This option is a bool as it provides an ACPI OpRegion which must be
661	  available before any devices using it are probed. This option also
662	  causes the designware-i2c driver to be builtin for the same reason.
663
664config INTEL_SOC_PMIC_CHTDC_TI
665	tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC"
666	depends on GPIOLIB
667	depends on I2C=y && I2C_DESIGNWARE_PLATFORM=y
668	depends on ACPI
669	depends on X86
670	select MFD_CORE
671	select REGMAP_I2C
672	select REGMAP_IRQ
673	help
674	  Select this option for supporting Dollar Cove (TI version) PMIC
675	  device that is found on some Intel Cherry Trail systems.
676
677	  This option is a bool as it provides an ACPI OpRegion which must be
678	  available before any devices using it are probed. This option also
679	  needs the designware-i2c driver to be builtin for the same reason.
680
681config INTEL_SOC_PMIC_MRFLD
682	tristate "Support for Intel Merrifield Basin Cove PMIC"
683	depends on GPIOLIB
684	depends on ACPI
685	depends on INTEL_SCU
686	select MFD_CORE
687	select REGMAP_IRQ
688	help
689	  Select this option for supporting Basin Cove PMIC device
690	  that is found on Intel Merrifield systems.
691
692config MFD_INTEL_LPSS
693	tristate
694	select COMMON_CLK
695	select MFD_CORE
696
697config MFD_INTEL_LPSS_ACPI
698	tristate "Intel Low Power Subsystem support in ACPI mode"
699	select MFD_INTEL_LPSS
700	depends on X86 && ACPI
701	help
702	  This driver supports Intel Low Power Subsystem (LPSS) devices such as
703	  I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
704	  PCH) in ACPI mode.
705
706config MFD_INTEL_LPSS_PCI
707	tristate "Intel Low Power Subsystem support in PCI mode"
708	select MFD_INTEL_LPSS
709	depends on X86 && PCI
710	help
711	  This driver supports Intel Low Power Subsystem (LPSS) devices such as
712	  I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
713	  PCH) in PCI mode.
714
715config MFD_INTEL_PMC_BXT
716	tristate "Intel PMC Driver for Broxton"
717	depends on X86
718	depends on X86_PLATFORM_DEVICES
719	depends on ACPI
720	select INTEL_SCU_IPC
721	select MFD_CORE
722	help
723	  This driver provides support for the PMC (Power Management
724	  Controller) on Intel Broxton and Apollo Lake. The PMC is a
725	  multi-function device that exposes IPC, General Control
726	  Register and P-unit access. In addition this creates devices
727	  for iTCO watchdog and telemetry that are part of the PMC.
728
729config MFD_IPAQ_MICRO
730	bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
731	depends on SA1100_H3600
732	select MFD_CORE
733	help
734	  Select this to get support for the Microcontroller found in
735	  the Compaq iPAQ handheld computers. This is an Atmel
736	  AT90LS8535 microcontroller flashed with a special iPAQ
737	  firmware using the custom protocol implemented in this driver.
738
739config MFD_IQS62X
740	tristate "Azoteq IQS620A/621/622/624/625 core support"
741	depends on I2C
742	select MFD_CORE
743	select REGMAP_I2C
744	help
745	  Say Y here if you want to build core support for the Azoteq IQS620A,
746	  IQS621, IQS622, IQS624 and IQS625 multi-function sensors. Additional
747	  options must be selected to enable device-specific functions.
748
749	  To compile this driver as a module, choose M here: the module will
750	  be called iqs62x.
751
752config MFD_JANZ_CMODIO
753	tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
754	select MFD_CORE
755	depends on PCI
756	help
757	  This is the core driver for the Janz CMOD-IO PCI MODULbus
758	  carrier board. This device is a PCI to MODULbus bridge which may
759	  host many different types of MODULbus daughterboards, including
760	  CAN and GPIO controllers.
761
762config MFD_KEMPLD
763	tristate "Kontron module PLD device"
764	select MFD_CORE
765	help
766	  This is the core driver for the PLD (Programmable Logic Device) found
767	  on some Kontron ETX and nearly all COMexpress (ETXexpress) modules as
768	  well as on some other Kontron products. The PLD device may provide
769	  functions like watchdog, GPIO, UART and I2C bus.
770
771	  This driver can also be built as a module. If so, the module
772	  will be called kempld-core.
773
774config MFD_88PM800
775	tristate "Marvell 88PM800"
776	depends on I2C
777	select REGMAP_I2C
778	select REGMAP_IRQ
779	select MFD_CORE
780	help
781	  This supports for Marvell 88PM800 Power Management IC.
782	  This includes the I2C driver and the core APIs _only_, you have to
783	  select individual components like voltage regulators, RTC and
784	  battery-charger under the corresponding menus.
785
786config MFD_88PM805
787	tristate "Marvell 88PM805"
788	depends on I2C
789	select REGMAP_I2C
790	select REGMAP_IRQ
791	select MFD_CORE
792	help
793	  This supports for Marvell 88PM805 Power Management IC. This includes
794	  the I2C driver and the core APIs _only_, you have to select individual
795	  components like codec device, headset/Mic device under the
796	  corresponding menus.
797
798config MFD_88PM860X
799	bool "Marvell 88PM8606/88PM8607"
800	depends on I2C=y
801	select REGMAP_I2C
802	select MFD_CORE
803	help
804	  This supports for Marvell 88PM8606/88PM8607 Power Management IC.
805	  This includes the I2C driver and the core APIs _only_, you have to
806	  select individual components like voltage regulators, RTC and
807	  battery-charger under the corresponding menus.
808
809config MFD_88PM886_PMIC
810	bool "Marvell 88PM886 PMIC"
811	depends on I2C=y
812	depends on OF
813	select REGMAP_I2C
814	select REGMAP_IRQ
815	select MFD_CORE
816	help
817	  This enables support for Marvell 88PM886 Power Management IC.
818	  This includes the I2C driver and the core APIs _only_, you have to
819	  select individual components like onkey under the corresponding menus.
820
821config MFD_MAX14577
822	tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
823	depends on I2C
824	select MFD_CORE
825	select REGMAP_I2C
826	select REGMAP_IRQ
827	select IRQ_DOMAIN
828	help
829	  Say yes here to add support for Maxim Semiconductor MAX14577 and
830	  MAX77836 Micro-USB ICs with battery charger.
831	  This driver provides common support for accessing the device;
832	  additional drivers must be enabled in order to use the functionality
833	  of the device.
834
835config MFD_MAX77541
836	tristate "Analog Devices MAX77541/77540 PMIC Support"
837	depends on I2C=y
838	select MFD_CORE
839	select REGMAP_I2C
840	select REGMAP_IRQ
841	help
842	  Say yes here to add support for Analog Devices MAX77541 and
843	  MAX77540 Power Management ICs. This driver provides
844	  common support for accessing the device; additional drivers
845	  must be enabled in order to use the functionality of the device.
846	  There are regulators and adc.
847
848config MFD_MAX77620
849	bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
850	depends on I2C=y
851	depends on OF
852	select MFD_CORE
853	select REGMAP_I2C
854	select REGMAP_IRQ
855	select IRQ_DOMAIN
856	help
857	  Say yes here to add support for Maxim Semiconductor MAX77620 and
858	  MAX20024 which are Power Management IC with General purpose pins,
859	  RTC, regulators, clock generator, watchdog etc. This driver
860	  provides common support for accessing the device; additional drivers
861	  must be enabled in order to use the functionality of the device.
862
863config MFD_MAX77650
864	tristate "Maxim MAX77650/77651 PMIC Support"
865	depends on I2C
866	depends on OF
867	select MFD_CORE
868	select REGMAP_I2C
869	select REGMAP_IRQ
870	help
871	  Say Y here to add support for Maxim Semiconductor MAX77650 and
872	  MAX77651 Power Management ICs. This is the core multifunction
873	  driver for interacting with the device. The module name is
874	  'max77650'. Additional drivers can be enabled in order to use
875	  the following functionalities of the device: GPIO, regulator,
876	  charger, LED, onkey.
877
878config MFD_MAX77686
879	tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
880	depends on I2C
881	depends on OF
882	select MFD_CORE
883	select REGMAP_I2C
884	select REGMAP_IRQ
885	select IRQ_DOMAIN
886	help
887	  Say yes here to add support for Maxim Semiconductor MAX77686 and
888	  MAX77802 which are Power Management IC with an RTC on chip.
889	  This driver provides common support for accessing the device;
890	  additional drivers must be enabled in order to use the functionality
891	  of the device.
892
893config MFD_MAX77693
894	tristate "Maxim Semiconductor MAX77693 PMIC Support"
895	depends on I2C
896	select MFD_CORE
897	select REGMAP_I2C
898	select REGMAP_IRQ
899	help
900	  Say yes here to add support for Maxim Semiconductor MAX77693.
901	  This is a companion Power Management IC with Flash, Haptic, Charger,
902	  and MUIC(Micro USB Interface Controller) controls on chip.
903	  This driver provides common support for accessing the device;
904	  additional drivers must be enabled in order to use the functionality
905	  of the device.
906
907config MFD_MAX77714
908	tristate "Maxim Semiconductor MAX77714 PMIC Support"
909	depends on I2C
910	depends on OF
911	select MFD_CORE
912	select REGMAP_I2C
913	help
914	  Say yes here to add support for Maxim Semiconductor MAX77714.
915	  This is a Power Management IC with 4 buck regulators, 9
916	  low-dropout regulators, 8 GPIOs, RTC, watchdog etc. This driver
917	  provides common support for accessing the device; additional
918	  drivers must be enabled in order to use each functionality of the
919	  device.
920
921config MFD_MAX77843
922	bool "Maxim Semiconductor MAX77843 PMIC Support"
923	depends on I2C=y
924	select MFD_CORE
925	select REGMAP_I2C
926	select REGMAP_IRQ
927	help
928	  Say yes here to add support for Maxim Semiconductor MAX77843.
929	  This is companion Power Management IC with LEDs, Haptic, Charger,
930	  Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
931	  This driver provides common support for accessing the device;
932	  additional drivers must be enabled in order to use the functionality
933	  of the device.
934
935config MFD_MAX8907
936	tristate "Maxim Semiconductor MAX8907 PMIC Support"
937	select MFD_CORE
938	depends on I2C
939	select REGMAP_I2C
940	select REGMAP_IRQ
941	help
942	  Say yes here to add support for Maxim Semiconductor MAX8907. This is
943	  a Power Management IC. This driver provides common support for
944	  accessing the device; additional drivers must be enabled in order
945	  to use the functionality of the device.
946
947config MFD_MAX8925
948	bool "Maxim Semiconductor MAX8925 PMIC Support"
949	depends on I2C=y
950	select MFD_CORE
951	help
952	  Say yes here to add support for Maxim Semiconductor MAX8925. This is
953	  a Power Management IC. This driver provides common support for
954	  accessing the device, additional drivers must be enabled in order
955	  to use the functionality of the device.
956
957config MFD_MAX8997
958	bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
959	depends on I2C=y
960	select MFD_CORE
961	select IRQ_DOMAIN
962	help
963	  Say yes here to add support for Maxim Semiconductor MAX8997/8966.
964	  This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
965	  MUIC controls on chip.
966	  This driver provides common support for accessing the device;
967	  additional drivers must be enabled in order to use the functionality
968	  of the device.
969
970config MFD_MAX8998
971	bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
972	depends on I2C=y
973	select MFD_CORE
974	select IRQ_DOMAIN
975	help
976	  Say yes here to add support for Maxim Semiconductor MAX8998 and
977	  National Semiconductor LP3974. This is a Power Management IC.
978	  This driver provides common support for accessing the device,
979	  additional drivers must be enabled in order to use the functionality
980	  of the device.
981
982config MFD_MT6360
983	tristate "Mediatek MT6360 SubPMIC"
984	select MFD_CORE
985	select REGMAP_I2C
986	select REGMAP_IRQ
987	select CRC8
988	depends on I2C
989	help
990	  Say Y here to enable MT6360 PMU/PMIC/LDO functional support.
991	  PMU part includes Charger, Flashlight, RGB LED
992	  PMIC part includes 2-channel BUCKs and 2-channel LDOs
993	  LDO part includes 4-channel LDOs
994
995config MFD_MT6370
996	tristate "MediaTek MT6370 SubPMIC"
997	select MFD_CORE
998	select REGMAP_I2C
999	select REGMAP_IRQ
1000	depends on I2C
1001	help
1002	  Say Y here to enable MT6370 SubPMIC functional support.
1003	  It consists of a single cell battery charger with ADC monitoring, RGB
1004	  LEDs, dual channel flashlight, WLED backlight driver, display bias
1005	  voltage supply, one general purpose LDO, and the USB Type-C & PD
1006	  controller complies with the latest USB Type-C and PD standards.
1007
1008	  This driver can also be built as a module. If so, the module
1009	  will be called "mt6370".
1010
1011config MFD_MT6397
1012	tristate "MediaTek MT6397 PMIC Support"
1013	select MFD_CORE
1014	select IRQ_DOMAIN
1015	help
1016	  Say yes here to add support for MediaTek MT6397 PMIC. This is
1017	  a Power Management IC. This driver provides common support for
1018	  accessing the device; additional drivers must be enabled in order
1019	  to use the functionality of the device.
1020
1021config MFD_MENF21BMC
1022	tristate "MEN 14F021P00 Board Management Controller Support"
1023	depends on I2C
1024	select MFD_CORE
1025	help
1026	  Say yes here to add support for the MEN 14F021P00 BMC
1027	  which is a Board Management Controller connected to the I2C bus.
1028	  The device supports multiple sub-devices like LED, HWMON and WDT.
1029	  This driver provides common support for accessing the devices;
1030	  additional drivers must be enabled in order to use the
1031	  functionality of the BMC device.
1032
1033	  This driver can also be built as a module. If so the module
1034	  will be called menf21bmc.
1035
1036config MFD_OCELOT
1037	tristate "Microsemi Ocelot External Control Support"
1038	depends on SPI_MASTER
1039	select MFD_CORE
1040	select REGMAP_SPI
1041	help
1042	  Ocelot is a family of networking chips that support multiple ethernet
1043	  and fibre interfaces. In addition to networking, they contain several
1044	  other functions, including pinctrl, MDIO, and communication with
1045	  external chips. While some chips have an internal processor capable of
1046	  running an OS, others don't. All chips can be controlled externally
1047	  through different interfaces, including SPI, I2C, and PCIe.
1048
1049	  Say yes here to add support for Ocelot chips (VSC7511, VSC7512,
1050	  VSC7513, VSC7514) controlled externally.
1051
1052	  To compile this driver as a module, choose M here: the module will be
1053	  called ocelot-soc.
1054
1055	  If unsure, say N.
1056
1057config EZX_PCAP
1058	bool "Motorola EZXPCAP Support"
1059	depends on SPI_MASTER
1060	help
1061	  This enables the PCAP ASIC present on EZX Phones. This is
1062	  needed for MMC, TouchScreen, Sound, USB, etc..
1063
1064config MFD_CPCAP
1065	tristate "Support for Motorola CPCAP"
1066	depends on SPI
1067	depends on OF
1068	select MFD_CORE
1069	select REGMAP_SPI
1070	select REGMAP_IRQ
1071	help
1072	  Say yes here if you want to include driver for CPCAP.
1073	  It is used on many Motorola phones and tablets as a PMIC.
1074	  At least Motorola Droid 4 is known to use CPCAP.
1075
1076config MFD_VIPERBOARD
1077	tristate "Nano River Technologies Viperboard"
1078	select MFD_CORE
1079	depends on USB
1080	default n
1081	help
1082	  Say yes here if you want support for Nano River Technologies
1083	  Viperboard.
1084	  There are mfd cell drivers available for i2c master, adc and
1085	  both gpios found on the board. The spi part does not yet
1086	  have a driver.
1087	  You need to select the mfd cell drivers separately.
1088	  The drivers do not support all features the board exposes.
1089
1090config MFD_NTXEC
1091	tristate "Netronix embedded controller (EC)"
1092	depends on OF
1093	depends on I2C
1094	select REGMAP_I2C
1095	select MFD_CORE
1096	help
1097	  Say yes here if you want to support the embedded controller found in
1098	  certain e-book readers designed by the original design manufacturer
1099	  Netronix.
1100
1101config MFD_RETU
1102	tristate "Nokia Retu and Tahvo multi-function device"
1103	select MFD_CORE
1104	depends on I2C
1105	select REGMAP_IRQ
1106	help
1107	  Retu and Tahvo are a multi-function devices found on Nokia
1108	  Internet Tablets (770, N800 and N810).
1109
1110config MFD_PCF50633
1111	tristate "NXP PCF50633"
1112	depends on I2C
1113	select REGMAP_I2C
1114	help
1115	  Say yes here if you have NXP PCF50633 chip on your board.
1116	  This core driver provides register access and IRQ handling
1117	  facilities, and registers devices for the various functions
1118	  so that function-specific drivers can bind to them.
1119
1120config PCF50633_ADC
1121	tristate "NXP PCF50633 ADC"
1122	depends on MFD_PCF50633
1123	help
1124	  Say yes here if you want to include support for ADC in the
1125	  NXP PCF50633 chip.
1126
1127config PCF50633_GPIO
1128	tristate "NXP PCF50633 GPIO"
1129	depends on MFD_PCF50633
1130	help
1131	  Say yes here if you want to include support GPIO for pins on
1132	  the PCF50633 chip.
1133
1134config MFD_PM8XXX
1135	tristate "Qualcomm PM8xxx PMIC chips driver"
1136	depends on ARM || HEXAGON || COMPILE_TEST
1137	select IRQ_DOMAIN_HIERARCHY
1138	select MFD_CORE
1139	select REGMAP
1140	help
1141	  If you say yes to this option, support will be included for the
1142	  built-in PM8xxx PMIC chips.
1143
1144	  This is required if your board has a PM8xxx and uses its features,
1145	  such as: MPPs, GPIOs, regulators, interrupts, and PWM.
1146
1147	  Say M here if you want to include support for PM8xxx chips as a
1148	  module. This will build a module called "pm8xxx-core".
1149
1150config MFD_QCOM_RPM
1151	tristate "Qualcomm Resource Power Manager (RPM)"
1152	depends on ARCH_QCOM && OF
1153	help
1154	  If you say yes to this option, support will be included for the
1155	  Resource Power Manager system found in the Qualcomm 8660, 8960 and
1156	  8064 based devices.
1157
1158	  This is required to access many regulators, clocks and bus
1159	  frequencies controlled by the RPM on these devices.
1160
1161	  Say M here if you want to include support for the Qualcomm RPM as a
1162	  module. This will build a module called "qcom_rpm".
1163
1164config MFD_SPMI_PMIC
1165	tristate "Qualcomm SPMI PMICs"
1166	depends on ARCH_QCOM || COMPILE_TEST
1167	depends on OF
1168	depends on SPMI
1169	select REGMAP_SPMI
1170	help
1171	  This enables support for the Qualcomm SPMI PMICs.
1172	  These PMICs are currently used with the Snapdragon 800 series of
1173	  SoCs.  Note, that this will only be useful paired with descriptions
1174	  of the independent functions as children nodes in the device tree.
1175
1176	  Say M here if you want to include support for the SPMI PMIC
1177	  series as a module.  The module will be called "qcom-spmi-pmic".
1178
1179config MFD_SY7636A
1180	tristate "Silergy SY7636A voltage regulator"
1181	depends on I2C
1182	select MFD_SIMPLE_MFD_I2C
1183	help
1184	  Enable support for Silergy SY7636A voltage regulator.
1185
1186	  To enable support for building sub-devices as modules,
1187	  choose M here.
1188
1189config MFD_RDC321X
1190	tristate "RDC R-321x southbridge"
1191	select MFD_CORE
1192	depends on PCI
1193	help
1194	  Say yes here if you want to have support for the RDC R-321x SoC
1195	  southbridge which provides access to GPIOs and Watchdog using the
1196	  southbridge PCI device configuration space.
1197
1198config MFD_RT4831
1199	tristate "Richtek RT4831 four channel WLED and Display Bias Voltage"
1200	depends on I2C
1201	select MFD_CORE
1202	select REGMAP_I2C
1203	help
1204	  This enables support for the Richtek RT4831 that includes 4 channel
1205	  WLED driving and Display Bias Voltage. It's commonly used to provide
1206	  power to the LCD display and LCD backlight.
1207
1208config MFD_RT5033
1209	tristate "Richtek RT5033 Power Management IC"
1210	depends on I2C
1211	select MFD_CORE
1212	select REGMAP_I2C
1213	select REGMAP_IRQ
1214	help
1215	  This driver provides for the Richtek RT5033 Power Management IC,
1216	  which includes the I2C driver and the Core APIs. This driver provides
1217	  common support for accessing the device. The device supports multiple
1218	  sub-devices like charger, fuel gauge, flash LED, current source,
1219	  LDO and Buck.
1220
1221config MFD_RT5120
1222	tristate "Richtek RT5120 Power Management IC"
1223	depends on I2C
1224	select MFD_CORE
1225	select REGMAP_I2C
1226	select REGMAP_IRQ
1227	help
1228	  The enables support for Richtek RT5120 PMIC. It includes four high
1229	  efficiency buck converters and one LDO voltage regulator. The device
1230	  is targeted at providing the CPU voltage, memory, I/O and peripheral
1231	  power rails in home entertainment devices.
1232
1233config MFD_RC5T583
1234	bool "Ricoh RC5T583 Power Management system device"
1235	depends on I2C=y
1236	select MFD_CORE
1237	select REGMAP_I2C
1238	help
1239	  Select this option to get support for the RICOH583 Power
1240	  Management system device.
1241	  This driver provides common support for accessing the device
1242	  through i2c interface. The device supports multiple sub-devices
1243	  like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1244	  Additional drivers must be enabled in order to use the
1245	  different functionality of the device.
1246
1247config MFD_RK8XX
1248	tristate
1249	select MFD_CORE
1250
1251config MFD_RK8XX_I2C
1252	tristate "Rockchip RK805/RK808/RK809/RK816/RK817/RK818 Power Management Chip"
1253	depends on I2C && OF
1254	select MFD_CORE
1255	select REGMAP_I2C
1256	select REGMAP_IRQ
1257	select MFD_RK8XX
1258	help
1259	  If you say yes here you get support for the RK805, RK808, RK809,
1260	  RK816, RK817 and RK818 Power Management chips.
1261	  This driver provides common support for accessing the device
1262	  through I2C interface. The device supports multiple sub-devices
1263	  including interrupts, RTC, LDO & DCDC regulators, and onkey.
1264
1265config MFD_RK8XX_SPI
1266	tristate "Rockchip RK806 Power Management Chip"
1267	depends on SPI && OF
1268	select MFD_CORE
1269	select REGMAP_SPI
1270	select REGMAP_IRQ
1271	select MFD_RK8XX
1272	help
1273	  If you say yes here you get support for the RK806 Power Management
1274	  chip.
1275	  This driver provides common support for accessing the device
1276	  through an SPI interface. The device supports multiple sub-devices
1277	  including interrupts, LDO & DCDC regulators, and power on-key.
1278
1279config MFD_RN5T618
1280	tristate "Ricoh RN5T567/618 PMIC"
1281	depends on I2C
1282	depends on OF
1283	select MFD_CORE
1284	select REGMAP_I2C
1285	select REGMAP_IRQ
1286	help
1287	  Say yes here to add support for the Ricoh RN5T567,
1288	  RN5T618, RC5T619 PMIC.
1289	  This driver provides common support for accessing the device,
1290	  additional drivers must be enabled in order to use the
1291	  functionality of the device.
1292
1293config MFD_SEC_CORE
1294	tristate "Samsung Electronics PMIC Series Support"
1295	depends on I2C=y
1296	depends on OF
1297	select MFD_CORE
1298	select REGMAP_I2C
1299	select REGMAP_IRQ
1300	help
1301	  Support for the Samsung Electronics PMIC devices coming
1302	  usually along with Samsung Exynos SoC chipset.
1303	  This driver provides common support for accessing the device,
1304	  additional drivers must be enabled in order to use the functionality
1305	  of the device
1306
1307	  To compile this driver as a module, choose M here: the
1308	  module will be called sec-core.
1309	  Have in mind that important core drivers (like regulators) depend
1310	  on this driver so building this as a module might require proper
1311	  initial ramdisk or might not boot up as well in certain scenarios.
1312
1313config MFD_SI476X_CORE
1314	tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1315	depends on I2C
1316	select MFD_CORE
1317	select REGMAP_I2C
1318	help
1319	  This is the core driver for the SI476x series of AM/FM
1320	  radio. This MFD driver connects the radio-si476x V4L2 module
1321	  and the si476x audio codec.
1322
1323	  To compile this driver as a module, choose M here: the
1324	  module will be called si476x-core.
1325
1326config MFD_SIMPLE_MFD_I2C
1327	tristate
1328	depends on I2C
1329	select MFD_CORE
1330	select REGMAP_I2C
1331	help
1332	  This driver creates a single register map with the intention for it
1333	  to be shared by all sub-devices.
1334
1335	  Once the register map has been successfully initialised, any
1336	  sub-devices represented by child nodes in Device Tree will be
1337	  subsequently registered.
1338
1339config MFD_SL28CPLD
1340	tristate "Kontron sl28cpld Board Management Controller"
1341	depends on I2C
1342	depends on ARCH_LAYERSCAPE || COMPILE_TEST
1343	select MFD_SIMPLE_MFD_I2C
1344	help
1345	  Say yes here to enable support for the Kontron sl28cpld board
1346	  management controller.
1347
1348	  It can be found on the following boards:
1349		* SMARC-sAL28
1350
1351config MFD_SM501
1352	tristate "Silicon Motion SM501"
1353	depends on HAS_DMA
1354	help
1355	  This is the core driver for the Silicon Motion SM501 multimedia
1356	  companion chip. This device is a multifunction device which may
1357	  provide numerous interfaces including USB host controller, USB gadget,
1358	  asynchronous serial ports, audio functions, and a dual display video
1359	  interface. The device may be connected by PCI or local bus with
1360	  varying functions enabled.
1361
1362config MFD_SM501_GPIO
1363	bool "Export GPIO via GPIO layer"
1364	depends on MFD_SM501 && GPIOLIB
1365	help
1366	  This option uses the gpio library layer to export the 64 GPIO
1367	  lines on the SM501. The platform data is used to supply the
1368	  base number for the first GPIO line to register.
1369
1370config MFD_SKY81452
1371	tristate "Skyworks Solutions SKY81452"
1372	select MFD_CORE
1373	select REGMAP_I2C
1374	depends on I2C
1375	help
1376	  This is the core driver for the Skyworks SKY81452 backlight and
1377	  voltage regulator device.
1378
1379	  This driver can also be built as a module.  If so, the module
1380	  will be called sky81452.
1381
1382config MFD_SC27XX_PMIC
1383	tristate "Spreadtrum SC27xx PMICs"
1384	depends on ARCH_SPRD || COMPILE_TEST
1385	depends on SPI_MASTER
1386	select MFD_CORE
1387	select REGMAP_SPI
1388	select REGMAP_IRQ
1389	help
1390	  This enables support for the Spreadtrum SC27xx PMICs with SPI
1391	  interface. The SC27xx series PMICs integrate power management,
1392	  audio codec, battery management and user interface support
1393	  function (such as RTC, Typec, indicator and so on) in a single chip.
1394
1395	  This driver provides common support for accessing the SC27xx PMICs,
1396	  and it also adds the irq_chip parts for handling the PMIC chip events.
1397
1398config RZ_MTU3
1399	tristate "Renesas RZ/G2L MTU3a core driver"
1400	depends on (ARCH_RZG2L && OF) || COMPILE_TEST
1401	select MFD_CORE
1402	help
1403	  Select this option to enable Renesas RZ/G2L MTU3a core driver for
1404	  the Multi-Function Timer Pulse Unit 3 (MTU3a) hardware available
1405	  on SoCs from Renesas. The core driver shares the clk and channel
1406	  register access for the other child devices like Counter, PWM,
1407	  Clock Source, and Clock event.
1408
1409config ABX500_CORE
1410	bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1411	depends on ARCH_U8500 || COMPILE_TEST
1412	default y if ARCH_U8500
1413	help
1414	  Say yes here if you have the ABX500 Mixed Signal IC family
1415	  chips. This core driver expose register access functions.
1416	  Functionality specific drivers using these functions can
1417	  remain unchanged when IC changes. Binding of the functions to
1418	  actual register access is done by the IC core driver.
1419
1420config AB8500_CORE
1421	bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1422	depends on ABX500_CORE && MFD_DB8500_PRCMU
1423	select POWER_SUPPLY
1424	select MFD_CORE
1425	select IRQ_DOMAIN
1426	help
1427	  Select this option to enable access to AB8500 power management
1428	  chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1429	  since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1430	  the irq_chip parts for handling the Mixed Signal chip events.
1431	  This chip embeds various other multimedia functionalities as well.
1432
1433config MFD_DB8500_PRCMU
1434	bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1435	depends on UX500_SOC_DB8500
1436	select MFD_CORE
1437	help
1438	  Select this option to enable support for the DB8500 Power Reset
1439	  and Control Management Unit. This is basically an autonomous
1440	  system controller running an XP70 microprocessor, which is accessed
1441	  through a register map.
1442
1443config MFD_STMPE
1444	bool "STMicroelectronics STMPE"
1445	depends on I2C=y || SPI_MASTER=y
1446	depends on OF
1447	select MFD_CORE
1448	help
1449	  Support for the STMPE family of I/O Expanders from
1450	  STMicroelectronics.
1451
1452	  Currently supported devices are:
1453
1454		STMPE811: GPIO, Touchscreen, ADC
1455		STMPE1601: GPIO, Keypad
1456		STMPE1801: GPIO, Keypad
1457		STMPE2401: GPIO, Keypad
1458		STMPE2403: GPIO, Keypad
1459
1460	  This driver provides common support for accessing the device,
1461	  additional drivers must be enabled in order to use the functionality
1462	  of the device.  Currently available sub drivers are:
1463
1464		GPIO: stmpe-gpio
1465		Keypad: stmpe-keypad
1466		Touchscreen: stmpe-ts
1467		ADC: stmpe-adc
1468
1469menu "STMicroelectronics STMPE Interface Drivers"
1470depends on MFD_STMPE
1471
1472config STMPE_I2C
1473	bool "STMicroelectronics STMPE I2C Interface"
1474	depends on I2C=y
1475	default y
1476	help
1477	  This is used to enable I2C interface of STMPE
1478
1479config STMPE_SPI
1480	bool "STMicroelectronics STMPE SPI Interface"
1481	depends on SPI_MASTER
1482	help
1483	  This is used to enable SPI interface of STMPE
1484endmenu
1485
1486config MFD_STA2X11
1487	bool "STMicroelectronics STA2X11"
1488	depends on STA2X11
1489	select MFD_CORE
1490	select REGMAP_MMIO
1491
1492config MFD_SUN6I_PRCM
1493	bool "Allwinner A31/A23/A33 PRCM controller"
1494	depends on ARCH_SUNXI || COMPILE_TEST
1495	select MFD_CORE
1496	help
1497	  Support for the PRCM (Power/Reset/Clock Management) unit available
1498	  in the A31, A23, and A33 SoCs. Other Allwinner SoCs contain similar
1499	  hardware, but they do not use this driver.
1500
1501config MFD_SYSCON
1502	bool "System Controller Register R/W Based on Regmap"
1503	select REGMAP_MMIO
1504	help
1505	  Select this option to enable accessing system control registers
1506	  via regmap.
1507
1508config MFD_TI_AM335X_TSCADC
1509	tristate "TI ADC / Touch Screen chip support"
1510	depends on ARCH_OMAP2PLUS || ARCH_K3 || COMPILE_TEST
1511	select MFD_CORE
1512	select REGMAP
1513	select REGMAP_MMIO
1514	help
1515	  If you say yes here you get support for Texas Instruments series
1516	  of Touch Screen /ADC chips.
1517	  To compile this driver as a module, choose M here: the
1518	  module will be called ti_am335x_tscadc.
1519
1520config MFD_LP3943
1521	tristate "TI/National Semiconductor LP3943 MFD Driver"
1522	depends on I2C
1523	select MFD_CORE
1524	select REGMAP_I2C
1525	help
1526	  Support for the TI/National Semiconductor LP3943.
1527	  This driver consists of GPIO and PWM drivers.
1528	  With these functionalities, it can be used for LED string control or
1529	  general usage such like a GPIO controller and a PWM controller.
1530
1531config MFD_LP8788
1532	bool "TI LP8788 Power Management Unit Driver"
1533	depends on I2C=y
1534	select MFD_CORE
1535	select REGMAP_I2C
1536	select IRQ_DOMAIN
1537	help
1538	  TI LP8788 PMU supports regulators, battery charger, RTC,
1539	  ADC, backlight driver and current sinks.
1540
1541config MFD_TI_LMU
1542	tristate "TI Lighting Management Unit driver"
1543	depends on I2C
1544	select MFD_CORE
1545	select REGMAP_I2C
1546	help
1547	  Say yes here to enable support for TI LMU chips.
1548	  TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and
1549	  LM36274.  It consists of backlight, LED and regulator driver.
1550	  It provides consistent device controls for lighting functions.
1551
1552config MFD_OMAP_USB_HOST
1553	bool "TI OMAP USBHS core and TLL driver"
1554	depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1555	depends on COMMON_CLK
1556	default y
1557	help
1558	  This is the core driver for the OAMP EHCI and OHCI drivers.
1559	  This MFD driver does the required setup functionalities for
1560	  OMAP USB Host drivers.
1561
1562config MFD_PALMAS
1563	tristate "TI Palmas series chips"
1564	select MFD_CORE
1565	select REGMAP_I2C
1566	select REGMAP_IRQ
1567	depends on I2C=y
1568	help
1569	  If you say yes here you get support for the Palmas
1570	  series of PMIC chips from Texas Instruments.
1571
1572config TPS6105X
1573	tristate "TI TPS61050/61052 Boost Converters"
1574	depends on I2C
1575	select REGMAP_I2C
1576	select REGULATOR
1577	select MFD_CORE
1578	select REGULATOR_FIXED_VOLTAGE
1579	help
1580	  This option enables a driver for the TP61050/TPS61052
1581	  high-power "white LED driver". This boost converter is
1582	  sometimes used for other things than white LEDs, and
1583	  also contains a GPIO pin.
1584
1585config TPS65010
1586	tristate "TI TPS6501x Power Management chips"
1587	depends on I2C && GPIOLIB
1588	default MACH_OMAP_OSK
1589	help
1590	  If you say yes here you get support for the TPS6501x series of
1591	  Power Management chips.  These include voltage regulators,
1592	  lithium ion/polymer battery charging, and other features that
1593	  are often used in portable devices like cell phones and cameras.
1594
1595	  This driver can also be built as a module.  If so, the module
1596	  will be called tps65010.
1597
1598config TPS6507X
1599	tristate "TI TPS6507x Power Management / Touch Screen chips"
1600	select MFD_CORE
1601	depends on I2C
1602	help
1603	  If you say yes here you get support for the TPS6507x series of
1604	  Power Management / Touch Screen chips.  These include voltage
1605	  regulators, lithium ion/polymer battery charging, touch screen
1606	  and other features that are often used in portable devices.
1607	  This driver can also be built as a module.  If so, the module
1608	  will be called tps6507x.
1609
1610config MFD_TPS65086
1611	tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1612	select MFD_CORE
1613	select REGMAP
1614	select REGMAP_IRQ
1615	select REGMAP_I2C
1616	depends on I2C
1617	help
1618	  If you say yes here you get support for the TPS65086 series of
1619	  Power Management chips.
1620	  This driver provides common support for accessing the device,
1621	  additional drivers must be enabled in order to use the
1622	  functionality of the device.
1623
1624config TPS65911_COMPARATOR
1625	tristate
1626
1627config MFD_TPS65090
1628	bool "TI TPS65090 Power Management chips"
1629	depends on I2C=y
1630	select MFD_CORE
1631	select REGMAP_I2C
1632	select REGMAP_IRQ
1633	help
1634	  If you say yes here you get support for the TPS65090 series of
1635	  Power Management chips.
1636	  This driver provides common support for accessing the device,
1637	  additional drivers must be enabled in order to use the
1638	  functionality of the device.
1639
1640config MFD_TPS65217
1641	tristate "TI TPS65217 Power Management / White LED chips"
1642	depends on I2C && OF
1643	select MFD_CORE
1644	select REGMAP_I2C
1645	select IRQ_DOMAIN
1646	help
1647	  If you say yes here you get support for the TPS65217 series of
1648	  Power Management / White LED chips.
1649	  These include voltage regulators, lithium ion/polymer battery
1650	  charger, wled and other features that are often used in portable
1651	  devices.
1652
1653	  This driver can also be built as a module.  If so, the module
1654	  will be called tps65217.
1655
1656config MFD_TI_LP873X
1657	tristate "TI LP873X Power Management IC"
1658	depends on I2C
1659	select MFD_CORE
1660	select REGMAP_I2C
1661	help
1662	  If you say yes here then you get support for the LP873X series of
1663	  Power Management Integrated Circuits (PMIC).
1664	  These include voltage regulators, thermal protection, configurable
1665	  General Purpose Outputs (GPO) that are used in portable devices.
1666
1667	  This driver can also be built as a module. If so, the module
1668	  will be called lp873x.
1669
1670config MFD_TI_LP87565
1671	tristate "TI LP87565 Power Management IC"
1672	depends on I2C && OF
1673	select MFD_CORE
1674	select REGMAP_I2C
1675	help
1676	  If you say yes here then you get support for the LP87565 series of
1677	  Power Management Integrated Circuits (PMIC).
1678	  These include voltage regulators, thermal protection, configurable
1679	  General Purpose Outputs (GPO) that are used in portable devices.
1680
1681	  This driver can also be built as a module. If so, the module
1682	  will be called lp87565.
1683
1684config MFD_TPS65218
1685	tristate "TI TPS65218 Power Management chips"
1686	depends on I2C && OF
1687	select MFD_CORE
1688	select REGMAP_I2C
1689	select REGMAP_IRQ
1690	help
1691	  If you say yes here you get support for the TPS65218 series of
1692	  Power Management chips.
1693	  These include voltage regulators, gpio and other features
1694	  that are often used in portable devices.
1695
1696	  This driver can also be built as a module.  If so, the module
1697	  will be called tps65218.
1698
1699config MFD_TPS65219
1700	tristate "TI TPS65219 Power Management IC"
1701	depends on I2C && OF
1702	select MFD_CORE
1703	select REGMAP_I2C
1704	select REGMAP_IRQ
1705	help
1706	  If you say yes here you get support for the TPS65219 series of Power
1707	  Management ICs. These include voltage regulators, GPIOs and
1708	  push/power button that is often used in portable devices.
1709
1710	  This driver can also be built as a module. If so, the module
1711	  will be called tps65219.
1712
1713config MFD_TPS6586X
1714	bool "TI TPS6586x Power Management chips"
1715	depends on I2C=y
1716	select MFD_CORE
1717	select REGMAP_I2C
1718	help
1719	  If you say yes here you get support for the TPS6586X series of
1720	  Power Management chips.
1721	  This driver provides common support for accessing the device,
1722	  additional drivers must be enabled in order to use the
1723	  functionality of the device.
1724
1725	  This driver can also be built as a module.  If so, the module
1726	  will be called tps6586x.
1727
1728config MFD_TPS65910
1729	bool "TI TPS65910 Power Management chip"
1730	depends on I2C=y
1731	depends on GPIOLIB || COMPILE_TEST
1732	select MFD_CORE
1733	select REGMAP_I2C
1734	select REGMAP_IRQ
1735	select IRQ_DOMAIN
1736	help
1737	  if you say yes here you get support for the TPS65910 series of
1738	  Power Management chips.
1739
1740config MFD_TPS65912
1741	tristate
1742	select MFD_CORE
1743	select REGMAP
1744	select REGMAP_IRQ
1745
1746config MFD_TPS65912_I2C
1747	tristate "TI TPS65912 Power Management chip with I2C"
1748	select MFD_TPS65912
1749	select REGMAP_I2C
1750	depends on I2C
1751	help
1752	  If you say yes here you get support for the TPS65912 series of
1753	  PM chips with I2C interface.
1754
1755config MFD_TPS65912_SPI
1756	tristate "TI TPS65912 Power Management chip with SPI"
1757	select MFD_TPS65912
1758	select REGMAP_SPI
1759	depends on SPI_MASTER
1760	help
1761	  If you say yes here you get support for the TPS65912 series of
1762	  PM chips with SPI interface.
1763
1764config MFD_TPS6594
1765	tristate
1766	select MFD_CORE
1767	select REGMAP
1768	select REGMAP_IRQ
1769
1770config MFD_TPS6594_I2C
1771	tristate "TI TPS6594 Power Management chip with I2C"
1772	select MFD_TPS6594
1773	select REGMAP_I2C
1774	select CRC8
1775	depends on I2C
1776	help
1777	  If you say yes here you get support for the TPS6594 series of
1778	  PM chips with I2C interface.
1779
1780	  This driver can also be built as a module.  If so, the module
1781	  will be called tps6594-i2c.
1782
1783config MFD_TPS6594_SPI
1784	tristate "TI TPS6594 Power Management chip with SPI"
1785	select MFD_TPS6594
1786	select REGMAP_SPI
1787	select CRC8
1788	depends on SPI_MASTER
1789	help
1790	  If you say yes here you get support for the TPS6594 series of
1791	  PM chips with SPI interface.
1792
1793	  This driver can also be built as a module.  If so, the module
1794	  will be called tps6594-spi.
1795
1796config TWL4030_CORE
1797	bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1798	depends on I2C=y
1799	select IRQ_DOMAIN
1800	select MFD_CORE
1801	select REGMAP_I2C
1802	help
1803	  Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1804	  This core driver provides register access and IRQ handling
1805	  facilities, and registers devices for the various functions
1806	  so that function-specific drivers can bind to them.
1807
1808	  These multi-function chips are found on many OMAP2 and OMAP3
1809	  boards, providing power management, RTC, GPIO, keypad, a
1810	  high speed USB OTG transceiver, an audio codec (on most
1811	  versions) and many other features.
1812
1813config TWL4030_POWER
1814	bool "TI TWL4030 power resources"
1815	depends on TWL4030_CORE && ARM
1816	help
1817	  Say yes here if you want to use the power resources on the
1818	  TWL4030 family chips.  Most of these resources are regulators,
1819	  which have a separate driver; some are control signals, such
1820	  as clock request handshaking.
1821
1822	  This driver uses board-specific data to initialize the resources
1823	  and load scripts controlling which resources are switched off/on
1824	  or reset when a sleep, wakeup or warm reset event occurs.
1825
1826config MFD_TWL4030_AUDIO
1827	bool "TI TWL4030 Audio"
1828	depends on TWL4030_CORE
1829	select MFD_CORE
1830	default n
1831
1832config TWL6040_CORE
1833	bool "TI TWL6040 audio codec"
1834	depends on I2C=y
1835	select MFD_CORE
1836	select REGMAP_I2C
1837	select REGMAP_IRQ
1838	default n
1839	help
1840	  Say yes here if you want support for Texas Instruments TWL6040 audio
1841	  codec.
1842	  This driver provides common support for accessing the device,
1843	  additional drivers must be enabled in order to use the
1844	  functionality of the device (audio, vibra).
1845
1846config MENELAUS
1847	bool "TI TWL92330/Menelaus PM chip"
1848	depends on I2C=y && ARCH_OMAP2
1849	help
1850	  If you say yes here you get support for the Texas Instruments
1851	  TWL92330/Menelaus Power Management chip. This include voltage
1852	  regulators, Dual slot memory card transceivers, real-time clock
1853	  and other features that are often used in portable devices like
1854	  cell phones and PDAs.
1855
1856config MFD_WL1273_CORE
1857	tristate "TI WL1273 FM radio"
1858	depends on I2C
1859	select MFD_CORE
1860	default n
1861	help
1862	  This is the core driver for the TI WL1273 FM radio. This MFD
1863	  driver connects the radio-wl1273 V4L2 module and the wl1273
1864	  audio codec.
1865
1866config MFD_LM3533
1867	tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1868	depends on I2C
1869	select MFD_CORE
1870	select REGMAP_I2C
1871	help
1872	  Say yes here to enable support for National Semiconductor / TI
1873	  LM3533 Lighting Power chips.
1874
1875	  This driver provides common support for accessing the device;
1876	  additional drivers must be enabled in order to use the LED,
1877	  backlight or ambient-light-sensor functionality of the device.
1878
1879config MFD_TIMBERDALE
1880	tristate "Timberdale FPGA"
1881	select MFD_CORE
1882	depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1883	help
1884	This is the core driver for the timberdale FPGA. This device is a
1885	multifunction device which exposes numerous platform devices.
1886
1887	The timberdale FPGA can be found on the Intel Atom development board
1888	for in-vehicle infontainment, called Russellville.
1889
1890config MFD_TC3589X
1891	bool "Toshiba TC35892 and variants"
1892	depends on I2C=y
1893	depends on OF
1894	select MFD_CORE
1895	help
1896	  Support for the Toshiba TC35892 and variants I/O Expander.
1897
1898	  This driver provides common support for accessing the device,
1899	  additional drivers must be enabled in order to use the
1900	  functionality of the device.
1901
1902config MFD_TQMX86
1903	tristate "TQ-Systems IO controller TQMX86"
1904	select MFD_CORE
1905	help
1906	  Say yes here to enable support for various functions of the
1907	  TQ-Systems IO controller and watchdog device, found on their
1908	  ComExpress CPU modules.
1909
1910config MFD_VX855
1911	tristate "VIA VX855/VX875 integrated south bridge"
1912	depends on PCI
1913	select MFD_CORE
1914	help
1915	  Say yes here to enable support for various functions of the
1916	  VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1917	  and/or vx855_gpio drivers for this to do anything useful.
1918
1919config MFD_LOCHNAGAR
1920	bool "Cirrus Logic Lochnagar Audio Development Board"
1921	select MFD_CORE
1922	select REGMAP_I2C
1923	depends on I2C=y && OF
1924	help
1925	  Support for Cirrus Logic Lochnagar audio development board.
1926
1927config MFD_ARIZONA
1928	select REGMAP
1929	select REGMAP_IRQ
1930	select MFD_CORE
1931	tristate
1932
1933config MFD_ARIZONA_I2C
1934	tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1935	select MFD_ARIZONA
1936	select REGMAP_I2C
1937	depends on I2C
1938	help
1939	  Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1940	  audio SoC core functionality controlled via I2C.
1941
1942config MFD_ARIZONA_SPI
1943	tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1944	select MFD_ARIZONA
1945	select REGMAP_SPI
1946	depends on SPI_MASTER
1947	help
1948	  Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1949	  audio SoC core functionality controlled via SPI.
1950
1951config MFD_CS47L24
1952	bool "Cirrus Logic CS47L24 and WM1831"
1953	depends on MFD_ARIZONA
1954	help
1955	  Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1956
1957config MFD_WM5102
1958	bool "Wolfson Microelectronics WM5102"
1959	depends on MFD_ARIZONA
1960	help
1961	  Support for Wolfson Microelectronics WM5102 low power audio SoC
1962
1963config MFD_WM5110
1964	bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1965	depends on MFD_ARIZONA
1966	help
1967	  Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1968	  low power audio SoC
1969
1970config MFD_WM8997
1971	bool "Wolfson Microelectronics WM8997"
1972	depends on MFD_ARIZONA
1973	help
1974	  Support for Wolfson Microelectronics WM8997 low power audio SoC
1975
1976config MFD_WM8998
1977	bool "Wolfson Microelectronics WM8998"
1978	depends on MFD_ARIZONA
1979	help
1980	  Support for Wolfson Microelectronics WM8998 low power audio SoC
1981
1982config MFD_WM8400
1983	bool "Wolfson Microelectronics WM8400"
1984	select MFD_CORE
1985	depends on I2C=y
1986	select REGMAP_I2C
1987	help
1988	  Support for the Wolfson Microelecronics WM8400 PMIC and audio
1989	  CODEC.  This driver provides common support for accessing
1990	  the device, additional drivers must be enabled in order to use
1991	  the functionality of the device.
1992
1993config MFD_WM831X
1994	bool
1995
1996config MFD_WM831X_I2C
1997	bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1998	select MFD_CORE
1999	select MFD_WM831X
2000	select REGMAP_I2C
2001	select IRQ_DOMAIN
2002	depends on I2C=y
2003	help
2004	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
2005	  when controlled using I2C.  This driver provides common support
2006	  for accessing the device, additional drivers must be enabled in
2007	  order to use the functionality of the device.
2008
2009config MFD_WM831X_SPI
2010	bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
2011	select MFD_CORE
2012	select MFD_WM831X
2013	select REGMAP_SPI
2014	select IRQ_DOMAIN
2015	depends on SPI_MASTER
2016	help
2017	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
2018	  when controlled using SPI.  This driver provides common support
2019	  for accessing the device, additional drivers must be enabled in
2020	  order to use the functionality of the device.
2021
2022config MFD_WM8350
2023	bool
2024
2025config MFD_WM8350_I2C
2026	bool "Wolfson Microelectronics WM8350 with I2C"
2027	select MFD_WM8350
2028	select REGMAP_I2C
2029	depends on I2C=y
2030	help
2031	  The WM8350 is an integrated audio and power management
2032	  subsystem with watchdog and RTC functionality for embedded
2033	  systems.  This option enables core support for the WM8350 with
2034	  I2C as the control interface.  Additional options must be
2035	  selected to enable support for the functionality of the chip.
2036
2037config MFD_WM8994
2038	tristate "Wolfson Microelectronics WM8994"
2039	select MFD_CORE
2040	select REGMAP_I2C
2041	select REGMAP_IRQ
2042	depends on I2C
2043	help
2044	  The WM8994 is a highly integrated hi-fi CODEC designed for
2045	  smartphone applications.  As well as audio functionality it
2046	  has on board GPIO and regulator functionality which is
2047	  supported via the relevant subsystems.  This driver provides
2048	  core support for the WM8994, in order to use the actual
2049	  functionality of the device other drivers must be enabled.
2050
2051config MFD_WM97xx
2052	tristate "Wolfson Microelectronics WM97xx"
2053	select MFD_CORE
2054	select REGMAP_AC97
2055	select AC97_BUS_COMPAT
2056	depends on AC97_BUS_NEW
2057	help
2058	  The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC
2059	  designed for smartphone applications.  As well as audio functionality
2060	  it has on board GPIO and a touchscreen functionality which is
2061	  supported via the relevant subsystems.  This driver provides core
2062	  support for the WM97xx, in order to use the actual functionality of
2063	  the device other drivers must be enabled.
2064
2065config MFD_STW481X
2066	tristate "Support for ST Microelectronics STw481x"
2067	depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
2068	select REGMAP_I2C
2069	select MFD_CORE
2070	help
2071	  Select this option to enable the STw481x chip driver used
2072	  in various ST Microelectronics and ST-Ericsson embedded
2073	  Nomadik series.
2074
2075config MFD_ROHM_BD718XX
2076	tristate "ROHM BD71837 Power Management IC"
2077	depends on I2C=y
2078	depends on OF
2079	select REGMAP_I2C
2080	select REGMAP_IRQ
2081	select MFD_CORE
2082	help
2083	  Select this option to get support for the ROHM BD71837
2084	  Power Management ICs. BD71837 is designed to power processors like
2085	  NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring
2086	  and emergency shut down as well as 32,768KHz clock output.
2087
2088config MFD_ROHM_BD71828
2089	tristate "ROHM BD71828 and BD71815 Power Management IC"
2090	depends on I2C=y
2091	depends on OF
2092	select REGMAP_I2C
2093	select REGMAP_IRQ
2094	select MFD_CORE
2095	help
2096	  Select this option to get support for the ROHM BD71828 and BD71815
2097	  Power Management ICs. BD71828GW and BD71815AGW are single-chip power
2098	  management ICs mainly for battery-powered portable devices.
2099	  The BD71828 integrates 7 buck converters and 7 LDOs. The BD71815
2100	  has 5 bucks, 7 LDOs, and a boost for driving LEDs. Both ICs provide
2101	  also a single-cell linear charger, a Coulomb counter, a real-time
2102	  clock (RTC), GPIOs and a 32.768 kHz clock gate.
2103
2104config MFD_ROHM_BD957XMUF
2105	tristate "ROHM BD9576MUF and BD9573MUF Power Management ICs"
2106	depends on I2C=y
2107	depends on OF
2108	select REGMAP_I2C
2109	select REGMAP_IRQ
2110	select MFD_CORE
2111	help
2112	  Select this option to get support for the ROHM BD9576MUF and
2113	  BD9573MUF Power Management ICs. BD9576 and BD9573 are primarily
2114	  designed to be used to power R-Car series processors.
2115
2116config MFD_ROHM_BD96801
2117	tristate "ROHM BD96801 Power Management IC"
2118	depends on I2C=y
2119	depends on OF
2120	select REGMAP_I2C
2121	select REGMAP_IRQ
2122	select MFD_CORE
2123	help
2124	  Select this option to get support for the ROHM BD96801 Power
2125	  Management IC. The ROHM BD96801 is a highly scalable Power Management
2126	  IC for industrial and automotive use. The BD96801 can be used as a
2127	  master PMIC in a chained PMIC solution with suitable companion PMICs.
2128
2129config MFD_STM32_LPTIMER
2130	tristate "Support for STM32 Low-Power Timer"
2131	depends on (ARCH_STM32 && OF) || COMPILE_TEST
2132	select MFD_CORE
2133	select REGMAP
2134	select REGMAP_MMIO
2135	help
2136	  Select this option to enable STM32 Low-Power Timer driver
2137	  used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
2138	  resources are also dealt with here.
2139
2140	  To compile this driver as a module, choose M here: the
2141	  module will be called stm32-lptimer.
2142
2143config MFD_STM32_TIMERS
2144	tristate "Support for STM32 Timers"
2145	depends on (ARCH_STM32 && OF) || COMPILE_TEST
2146	select MFD_CORE
2147	select REGMAP
2148	select REGMAP_MMIO
2149	help
2150	  Select this option to enable STM32 timers driver used
2151	  for PWM and IIO Timer. This driver allow to share the
2152	  registers between the others drivers.
2153
2154config MFD_STPMIC1
2155	tristate "Support for STPMIC1 PMIC"
2156	depends on I2C=y && OF
2157	select REGMAP_I2C
2158	select REGMAP_IRQ
2159	select MFD_CORE
2160	help
2161	  Support for ST Microelectronics STPMIC1 PMIC. STPMIC1 has power on
2162	  key, watchdog and regulator functionalities which are supported via
2163	  the relevant subsystems. This driver provides core support for the
2164	  STPMIC1. In order to use the actual functionality of the device other
2165	  drivers must be enabled.
2166
2167	  To compile this driver as a module, choose M here: the
2168	  module will be called stpmic1.
2169
2170config MFD_STMFX
2171	tristate "Support for STMicroelectronics Multi-Function eXpander (STMFX)"
2172	depends on I2C
2173	depends on OF
2174	select MFD_CORE
2175	select REGMAP_I2C
2176	help
2177	  Support for the STMicroelectronics Multi-Function eXpander.
2178
2179	  This driver provides common support for accessing the device,
2180	  additional drivers must be enabled in order to use the functionality
2181	  of the device.
2182
2183config MFD_WCD934X
2184	tristate "Support for WCD9340/WCD9341 Codec"
2185	depends on SLIMBUS
2186	select REGMAP
2187	select REGMAP_SLIMBUS
2188	select REGMAP_IRQ
2189	select MFD_CORE
2190	help
2191	  Support for the Qualcomm WCD9340/WCD9341 Codec.
2192	  This driver provides common support WCD934x audio codec and its
2193	  associated Pin Controller, Soundwire Controller and Audio codec.
2194
2195config MFD_ATC260X
2196	tristate
2197	select MFD_CORE
2198	select REGMAP
2199	select REGMAP_IRQ
2200
2201config MFD_ATC260X_I2C
2202	tristate "Actions Semi ATC260x PMICs with I2C"
2203	select MFD_ATC260X
2204	select REGMAP_I2C
2205	depends on I2C
2206	help
2207	  Support for the Actions Semi ATC260x PMICs controlled via I2C.
2208
2209	  This driver provides common support for accessing the ATC2603C
2210	  and ATC2609A chip variants, additional drivers must be enabled
2211	  in order to use the functionality of the device.
2212
2213config MFD_KHADAS_MCU
2214	tristate "Support for Khadas System control Microcontroller"
2215	depends on I2C
2216	depends on ARCH_MESON || ARCH_ROCKCHIP || COMPILE_TEST
2217	select MFD_CORE
2218	select REGMAP_I2C
2219	help
2220	  Support for the Khadas System control Microcontroller interface
2221	  present on their VIM and Edge boards.
2222
2223	  This Microcontroller is present on the Khadas VIM1, VIM2, VIM3 and
2224	  Edge boards.
2225
2226	  It provides multiple boot control features like password check,
2227	  power-on options, power-off control and system FAN control on recent
2228	  boards.
2229
2230	  This driver provides common support for accessing the device,
2231	  additional drivers must be enabled in order to use the functionality
2232	  of the device.
2233
2234config MFD_ACER_A500_EC
2235	tristate "Support for Acer Iconia Tab A500 Embedded Controller"
2236	depends on I2C
2237	depends on (ARCH_TEGRA_2x_SOC && OF) || COMPILE_TEST
2238	select MFD_CORE
2239	select REGMAP
2240	help
2241	  Support for Embedded Controller found on Acer Iconia Tab A500.
2242	  The controller itself is ENE KB930, it is running firmware
2243	  customized for the specific needs of the Acer A500 hardware.
2244
2245config MFD_QCOM_PM8008
2246	tristate "QCOM PM8008 Power Management IC"
2247	depends on I2C && OF
2248	select MFD_CORE
2249	select REGMAP_I2C
2250	select REGMAP_IRQ
2251	help
2252	  Select this option to get support for the Qualcomm Technologies, Inc.
2253	  PM8008 PMIC chip. PM8008 is a dedicated camera PMIC that integrates
2254	  all the necessary power management, housekeeping, and interface
2255	  support functions into a single IC. This driver provides common
2256	  support for accessing the device by instantiating all the child nodes
2257	  under it in the device tree. Additional drivers must be enabled in
2258	  order to use the functionality of the device.
2259
2260menu "Multimedia Capabilities Port drivers"
2261	depends on ARCH_SA1100
2262
2263config MCP
2264	tristate
2265
2266# Interface drivers
2267config MCP_SA11X0
2268	tristate "Support SA11x0 MCP interface"
2269	depends on ARCH_SA1100
2270	select MCP
2271
2272# Chip drivers
2273config MCP_UCB1200
2274	tristate "Support for UCB1200 / UCB1300"
2275	depends on MCP_SA11X0
2276	select MCP
2277
2278config MCP_UCB1200_TS
2279	tristate "Touchscreen interface support"
2280	depends on MCP_UCB1200 && INPUT
2281
2282endmenu
2283
2284config MFD_CS40L50_CORE
2285	tristate
2286	select MFD_CORE
2287	select FW_CS_DSP
2288	select REGMAP_IRQ
2289
2290config MFD_CS40L50_I2C
2291	tristate "Cirrus Logic CS40L50 (I2C)"
2292	select REGMAP_I2C
2293	select MFD_CS40L50_CORE
2294	depends on I2C
2295	help
2296	  Select this to support the Cirrus Logic CS40L50 Haptic
2297	  Driver over I2C.
2298
2299	  This driver can be built as a module. If built as a module it will be
2300	  called "cs40l50-i2c".
2301
2302config MFD_CS40L50_SPI
2303	tristate "Cirrus Logic CS40L50 (SPI)"
2304	select REGMAP_SPI
2305	select MFD_CS40L50_CORE
2306	depends on SPI
2307	help
2308	  Select this to support the Cirrus Logic CS40L50 Haptic
2309	  Driver over SPI.
2310
2311	  This driver can be built as a module. If built as a module it will be
2312	  called "cs40l50-spi".
2313
2314config MFD_VEXPRESS_SYSREG
2315	tristate "Versatile Express System Registers"
2316	depends on VEXPRESS_CONFIG && GPIOLIB
2317	default y
2318	select GPIO_GENERIC_PLATFORM
2319	select MFD_CORE
2320	select MFD_SYSCON
2321	help
2322	  System Registers are the platform configuration block
2323	  on the ARM Ltd. Versatile Express board.
2324
2325config RAVE_SP_CORE
2326	tristate "RAVE SP MCU core driver"
2327	depends on SERIAL_DEV_BUS
2328	select CRC_ITU_T
2329	help
2330	  Select this to get support for the Supervisory Processor
2331	  device found on several devices in RAVE line of hardware.
2332
2333config SGI_MFD_IOC3
2334	bool "SGI IOC3 core driver"
2335	depends on PCI && MIPS && 64BIT
2336	select MFD_CORE
2337	help
2338	  This option enables basic support for the SGI IOC3-based
2339	  controller cards.  This option does not enable any specific
2340	  functions on such a card, but provides necessary infrastructure
2341	  for other drivers to utilize.
2342
2343	  If you have an SGI Origin, Octane, or a PCI IOC3 card,
2344	  then say Y. Otherwise say N.
2345
2346config MFD_INTEL_M10_BMC_CORE
2347        tristate
2348        select MFD_CORE
2349        select REGMAP
2350        default n
2351
2352config MFD_INTEL_M10_BMC_SPI
2353        tristate "Intel MAX 10 Board Management Controller with SPI"
2354        depends on SPI_MASTER
2355        select MFD_INTEL_M10_BMC_CORE
2356        select REGMAP_SPI_AVMM
2357        help
2358          Support for the Intel MAX 10 board management controller using the
2359          SPI interface.
2360
2361          This driver provides common support for accessing the device,
2362          additional drivers must be enabled in order to use the functionality
2363          of the device.
2364
2365config MFD_INTEL_M10_BMC_PMCI
2366	tristate "Intel MAX 10 Board Management Controller with PMCI"
2367	depends on FPGA_DFL
2368	select MFD_INTEL_M10_BMC_CORE
2369	select REGMAP
2370	help
2371	  Support for the Intel MAX 10 board management controller via PMCI.
2372
2373	  This driver provides common support for accessing the device,
2374	  additional drivers must be enabled in order to use the functionality
2375	  of the device.
2376
2377config MFD_RSMU_I2C
2378	tristate "Renesas Synchronization Management Unit with I2C"
2379	depends on I2C && OF
2380	select MFD_CORE
2381	select REGMAP_I2C
2382	help
2383	  Support for the Renesas Synchronization Management Unit, such as
2384	  Clockmatrix and 82P33XXX series. This option supports I2C as
2385	  the control interface.
2386
2387	  This driver provides common support for accessing the device.
2388	  Additional drivers must be enabled in order to use the functionality
2389	  of the device.
2390
2391config MFD_RSMU_SPI
2392	tristate "Renesas Synchronization Management Unit with SPI"
2393	depends on SPI && OF
2394	select MFD_CORE
2395	select REGMAP_SPI
2396	help
2397	  Support for the Renesas Synchronization Management Unit, such as
2398	  Clockmatrix and 82P33XXX series. This option supports SPI as
2399	  the control interface.
2400
2401	  This driver provides common support for accessing the device.
2402	  Additional drivers must be enabled in order to use the functionality
2403	  of the device.
2404
2405endmenu
2406endif
2407