xref: /openbmc/linux/drivers/mfd/Kconfig (revision faa16bc4)
1#
2# Multifunction miscellaneous devices
3#
4
5if HAS_IOMEM
6menu "Multifunction device drivers"
7
8config MFD_CORE
9	tristate
10	select IRQ_DOMAIN
11	default n
12
13config MFD_CS5535
14	tristate "AMD CS5535 and CS5536 southbridge core functions"
15	select MFD_CORE
16	depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
17	---help---
18	  This is the core driver for CS5535/CS5536 MFD functions.  This is
19          necessary for using the board's GPIO and MFGPT functionality.
20
21config MFD_ALTERA_A10SR
22	bool "Altera Arria10 DevKit System Resource chip"
23	depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
24	select REGMAP_SPI
25	select MFD_CORE
26	help
27	  Support for the Altera Arria10 DevKit MAX5 System Resource chip
28	  using the SPI interface. This driver provides common support for
29	  accessing the external gpio extender (LEDs & buttons) and
30	  power supply alarms (hwmon).
31
32config MFD_ACT8945A
33	tristate "Active-semi ACT8945A"
34	select MFD_CORE
35	select REGMAP_I2C
36	depends on I2C && OF
37	help
38	  Support for the ACT8945A PMIC from Active-semi. This device
39	  features three step-down DC/DC converters and four low-dropout
40	  linear regulators, along with a complete ActivePath battery
41	  charger.
42
43config MFD_SUN4I_GPADC
44	tristate "Allwinner sunxi platforms' GPADC MFD driver"
45	select MFD_CORE
46	select REGMAP_MMIO
47	select REGMAP_IRQ
48	depends on ARCH_SUNXI || COMPILE_TEST
49	depends on !TOUCHSCREEN_SUN4I
50	help
51	  Select this to get support for Allwinner SoCs (A10, A13 and A31) ADC.
52	  This driver will only map the hardware interrupt and registers, you
53	  have to select individual drivers based on this MFD to be able to use
54	  the ADC or the thermal sensor. This will try to probe the ADC driver
55	  sun4i-gpadc-iio and the hwmon driver iio_hwmon.
56
57	  To compile this driver as a module, choose M here: the module will be
58	  called sun4i-gpadc.
59
60config MFD_AS3711
61	bool "AMS AS3711"
62	select MFD_CORE
63	select REGMAP_I2C
64	select REGMAP_IRQ
65	depends on I2C=y
66	help
67	  Support for the AS3711 PMIC from AMS
68
69config MFD_AS3722
70	tristate "ams AS3722 Power Management IC"
71	select MFD_CORE
72	select REGMAP_I2C
73	select REGMAP_IRQ
74	depends on I2C=y && OF
75	help
76	  The ams AS3722 is a compact system PMU suitable for mobile phones,
77	  tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
78	  controllers, 11 LDOs, RTC, automatic battery, temperature and
79	  over current monitoring, GPIOs, ADC and a watchdog.
80
81config PMIC_ADP5520
82	bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
83	depends on I2C=y
84	help
85	  Say yes here to add support for Analog Devices AD5520 and ADP5501,
86	  Multifunction Power Management IC. This includes
87	  the I2C driver and the core APIs _only_, you have to select
88	  individual components like LCD backlight, LEDs, GPIOs and Kepad
89	  under the corresponding menus.
90
91config MFD_AAT2870_CORE
92	bool "AnalogicTech AAT2870"
93	select MFD_CORE
94	depends on I2C=y
95	depends on GPIOLIB || COMPILE_TEST
96	help
97	  If you say yes here you get support for the AAT2870.
98	  This driver provides common support for accessing the device,
99	  additional drivers must be enabled in order to use the
100	  functionality of the device.
101
102config MFD_ATMEL_FLEXCOM
103	tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
104	select MFD_CORE
105	depends on OF
106	help
107	  Select this to get support for Atmel Flexcom. This is a wrapper
108	  which embeds a SPI controller, a I2C controller and a USART. Only
109	  one function can be used at a time. The choice is done at boot time
110	  by the probe function of this MFD driver according to a device tree
111	  property.
112
113config MFD_ATMEL_HLCDC
114	tristate "Atmel HLCDC (High-end LCD Controller)"
115	select MFD_CORE
116	select REGMAP_MMIO
117	depends on OF
118	help
119	  If you say yes here you get support for the HLCDC block.
120	  This driver provides common support for accessing the device,
121	  additional drivers must be enabled in order to use the
122	  functionality of the device.
123
124config MFD_ATMEL_SMC
125	bool
126	select MFD_SYSCON
127
128config MFD_BCM590XX
129	tristate "Broadcom BCM590xx PMUs"
130	select MFD_CORE
131	select REGMAP_I2C
132	depends on I2C
133	help
134	  Support for the BCM590xx PMUs from Broadcom
135
136config MFD_BD9571MWV
137	tristate "ROHM BD9571MWV PMIC"
138	select MFD_CORE
139	select REGMAP_I2C
140	select REGMAP_IRQ
141	depends on I2C
142	help
143	  Support for the ROHM BD9571MWV PMIC, which contains single
144	  voltage regulator, voltage sampling units, GPIO block and
145	  watchdog block.
146
147	  This driver can also be built as a module. If so, the module
148	  will be called bd9571mwv.
149
150config MFD_AC100
151	tristate "X-Powers AC100"
152	select MFD_CORE
153	depends on SUNXI_RSB
154	help
155	  If you say Y here you get support for the X-Powers AC100 audio codec
156	  IC.
157	  This driver include only the core APIs. You have to select individual
158	  components like codecs or RTC under the corresponding menus.
159
160config MFD_AXP20X
161	tristate
162	select MFD_CORE
163	select REGMAP_IRQ
164
165config MFD_AXP20X_I2C
166	tristate "X-Powers AXP series PMICs with I2C"
167	select MFD_AXP20X
168	select REGMAP_I2C
169	depends on I2C
170	help
171	  If you say Y here you get support for the X-Powers AXP series power
172	  management ICs (PMICs) controlled with I2C.
173	  This driver include only the core APIs. You have to select individual
174	  components like regulators or the PEK (Power Enable Key) under the
175	  corresponding menus.
176
177	  Note on x86 this provides an ACPI OpRegion, so this must be 'y'
178	  (builtin) and not a module, as the OpRegion must be available as
179	  soon as possible. For the same reason the I2C bus driver options
180	  I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too.
181
182config MFD_AXP20X_RSB
183	tristate "X-Powers AXP series PMICs with RSB"
184	select MFD_AXP20X
185	depends on SUNXI_RSB
186	help
187	  If you say Y here you get support for the X-Powers AXP series power
188	  management ICs (PMICs) controlled with RSB.
189	  This driver include only the core APIs. You have to select individual
190	  components like regulators or the PEK (Power Enable Key) under the
191	  corresponding menus.
192
193config MFD_CROS_EC
194	tristate "ChromeOS Embedded Controller"
195	select MFD_CORE
196	select CHROME_PLATFORMS
197	select CROS_EC_PROTO
198	depends on X86 || ARM || ARM64 || COMPILE_TEST
199	help
200	  If you say Y here you get support for the ChromeOS Embedded
201	  Controller (EC) providing keyboard, battery and power services.
202	  You also need to enable the driver for the bus you are using. The
203	  protocol for talking to the EC is defined by the bus driver.
204
205config MFD_CROS_EC_I2C
206	tristate "ChromeOS Embedded Controller (I2C)"
207	depends on MFD_CROS_EC && I2C
208
209	help
210	  If you say Y here, you get support for talking to the ChromeOS
211	  EC through an I2C bus. This uses a simple byte-level protocol with
212	  a checksum. Failing accesses will be retried three times to
213	  improve reliability.
214
215config MFD_CROS_EC_SPI
216	tristate "ChromeOS Embedded Controller (SPI)"
217	depends on MFD_CROS_EC && SPI
218
219	---help---
220	  If you say Y here, you get support for talking to the ChromeOS EC
221	  through a SPI bus, using a byte-level protocol. Since the EC's
222	  response time cannot be guaranteed, we support ignoring
223	  'pre-amble' bytes before the response actually starts.
224
225config MFD_CROS_EC_CHARDEV
226        tristate "Chrome OS Embedded Controller userspace device interface"
227        depends on MFD_CROS_EC
228        select CROS_EC_CTL
229        ---help---
230          This driver adds support to talk with the ChromeOS EC from userspace.
231
232          If you have a supported Chromebook, choose Y or M here.
233          The module will be called cros_ec_dev.
234
235config MFD_ASIC3
236	bool "Compaq ASIC3"
237	depends on GPIOLIB && ARM
238	select MFD_CORE
239	 ---help---
240	  This driver supports the ASIC3 multifunction chip found on many
241	  PDAs (mainly iPAQ and HTC based ones)
242
243config PMIC_DA903X
244	bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
245	depends on I2C=y
246	help
247	  Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
248	  ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
249	  usually found on PXA processors-based platforms. This includes
250	  the I2C driver and the core APIs _only_, you have to select
251	  individual components like LCD backlight, voltage regulators,
252	  LEDs and battery-charger under the corresponding menus.
253
254config PMIC_DA9052
255	bool
256	select MFD_CORE
257
258config MFD_DA9052_SPI
259	bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
260	select REGMAP_SPI
261	select REGMAP_IRQ
262	select PMIC_DA9052
263	depends on SPI_MASTER=y
264	help
265	  Support for the Dialog Semiconductor DA9052 PMIC
266	  when controlled using SPI. This driver provides common support
267	  for accessing the device, additional drivers must be enabled in
268	  order to use the functionality of the device.
269
270config MFD_DA9052_I2C
271	bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
272	select REGMAP_I2C
273	select REGMAP_IRQ
274	select PMIC_DA9052
275	depends on I2C=y
276	help
277	  Support for the Dialog Semiconductor DA9052 PMIC
278	  when controlled using I2C. This driver provides common support
279	  for accessing the device, additional drivers must be enabled in
280	  order to use the functionality of the device.
281
282config MFD_DA9055
283	bool "Dialog Semiconductor DA9055 PMIC Support"
284	select REGMAP_I2C
285	select REGMAP_IRQ
286	select MFD_CORE
287	depends on I2C=y
288	help
289	  Say yes here for support of Dialog Semiconductor DA9055. This is
290	  a Power Management IC. This driver provides common support for
291	  accessing the device as well as the I2C interface to the chip itself.
292	  Additional drivers must be enabled in order to use the functionality
293	  of the device.
294
295	  This driver can be built as a module. If built as a module it will be
296	  called "da9055"
297
298config MFD_DA9062
299	tristate "Dialog Semiconductor DA9062/61 PMIC Support"
300	select MFD_CORE
301	select REGMAP_I2C
302	select REGMAP_IRQ
303	depends on I2C
304	help
305	  Say yes here for support for the Dialog Semiconductor DA9061 and
306	  DA9062 PMICs.
307	  This includes the I2C driver and core APIs.
308	  Additional drivers must be enabled in order to use the functionality
309	  of the device.
310
311config MFD_DA9063
312	tristate "Dialog Semiconductor DA9063 PMIC Support"
313	select MFD_CORE
314	select REGMAP_I2C
315	select REGMAP_IRQ
316	depends on I2C
317	help
318	  Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
319	  This includes the I2C driver and core APIs.
320	  Additional drivers must be enabled in order to use the functionality
321	  of the device.
322
323config MFD_DA9150
324	tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
325	depends on I2C
326	select MFD_CORE
327	select REGMAP_I2C
328	select REGMAP_IRQ
329	help
330	  This adds support for the DA9150 integrated charger and fuel-gauge
331	  chip. This driver provides common support for accessing the device.
332	  Additional drivers must be enabled in order to use the specific
333	  features of the device.
334
335config MFD_DLN2
336	tristate "Diolan DLN2 support"
337	select MFD_CORE
338	depends on USB
339	help
340	  This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
341	  DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
342	  etc. must be enabled in order to use the functionality of
343	  the device.
344
345config MFD_EXYNOS_LPASS
346	tristate "Samsung Exynos SoC Low Power Audio Subsystem"
347	depends on ARCH_EXYNOS || COMPILE_TEST
348	select MFD_CORE
349	select REGMAP_MMIO
350	help
351	  Select this option to enable support for Samsung Exynos Low Power
352	  Audio Subsystem.
353
354config MFD_MC13XXX
355	tristate
356	depends on (SPI_MASTER || I2C)
357	select MFD_CORE
358	select REGMAP_IRQ
359	help
360	  Enable support for the Freescale MC13783 and MC13892 PMICs.
361	  This driver provides common support for accessing the device,
362	  additional drivers must be enabled in order to use the
363	  functionality of the device.
364
365config MFD_MC13XXX_SPI
366	tristate "Freescale MC13783 and MC13892 SPI interface"
367	depends on SPI_MASTER
368	select REGMAP_SPI
369	select MFD_MC13XXX
370	help
371	  Select this if your MC13xxx is connected via an SPI bus.
372
373config MFD_MC13XXX_I2C
374	tristate "Freescale MC13892 I2C interface"
375	depends on I2C
376	select REGMAP_I2C
377	select MFD_MC13XXX
378	help
379	  Select this if your MC13xxx is connected via an I2C bus.
380
381config MFD_MXS_LRADC
382	tristate "Freescale i.MX23/i.MX28 LRADC"
383	depends on ARCH_MXS || COMPILE_TEST
384	select MFD_CORE
385	select STMP_DEVICE
386	help
387	  Say yes here to build support for the Low Resolution
388	  Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
389	  processors. This driver provides common support for accessing the
390	  device, additional drivers must be enabled in order to use the
391	  functionality of the device:
392		mxs-lradc-adc for ADC readings
393		mxs-lradc-ts  for touchscreen support
394
395	  This driver can also be built as a module. If so, the module will be
396	  called mxs-lradc.
397
398config MFD_MX25_TSADC
399	tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
400	select REGMAP_MMIO
401	depends on (SOC_IMX25 && OF) || COMPILE_TEST
402	help
403	  Enable support for the integrated Touchscreen and ADC unit of the
404	  i.MX25 processors. They consist of a conversion queue for general
405	  purpose ADC and a queue for Touchscreens.
406
407config MFD_HI6421_PMIC
408	tristate "HiSilicon Hi6421 PMU/Codec IC"
409	depends on OF
410	select MFD_CORE
411	select REGMAP_MMIO
412	help
413	  Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
414	  functions, such as regulators, RTC, codec, Coulomb counter, etc.
415	  This driver includes core APIs _only_. You have to select
416	  individul components like voltage regulators under corresponding
417	  menus in order to enable them.
418	  We communicate with the Hi6421 via memory-mapped I/O.
419
420config MFD_HI655X_PMIC
421	tristate "HiSilicon Hi655X series PMU/Codec IC"
422	depends on ARCH_HISI || COMPILE_TEST
423	depends on OF
424	select MFD_CORE
425	select REGMAP_MMIO
426	select REGMAP_IRQ
427	help
428	  Select this option to enable Hisilicon hi655x series pmic driver.
429
430config HTC_PASIC3
431	tristate "HTC PASIC3 LED/DS1WM chip support"
432	select MFD_CORE
433	help
434	  This core driver provides register access for the LED/DS1WM
435	  chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
436	  HTC Magician devices, respectively. Actual functionality is
437	  handled by the leds-pasic3 and ds1wm drivers.
438
439config HTC_I2CPLD
440	bool "HTC I2C PLD chip support"
441	depends on I2C=y && GPIOLIB
442	help
443	  If you say yes here you get support for the supposed CPLD
444	  found on omap850 HTC devices like the HTC Wizard and HTC Herald.
445	  This device provides input and output GPIOs through an I2C
446	  interface to one or more sub-chips.
447
448config MFD_INTEL_QUARK_I2C_GPIO
449	tristate "Intel Quark MFD I2C GPIO"
450	depends on PCI
451	depends on X86
452	depends on COMMON_CLK
453	select MFD_CORE
454	help
455	  This MFD provides support for I2C and GPIO that exist only
456	  in a single PCI device. It splits the 2 IO devices to
457	  their respective IO driver.
458	  The GPIO exports a total amount of 8 interrupt-capable GPIOs.
459
460config LPC_ICH
461	tristate "Intel ICH LPC"
462	depends on PCI
463	select MFD_CORE
464	help
465	  The LPC bridge function of the Intel ICH provides support for
466	  many functional units. This driver provides needed support for
467	  other drivers to control these functions, currently GPIO and
468	  watchdog.
469
470config LPC_SCH
471	tristate "Intel SCH LPC"
472	depends on PCI
473	select MFD_CORE
474	help
475	  LPC bridge function of the Intel SCH provides support for
476	  System Management Bus and General Purpose I/O.
477
478config INTEL_SOC_PMIC
479	bool "Support for Crystal Cove PMIC"
480	depends on ACPI && HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
481	depends on X86 || COMPILE_TEST
482	select MFD_CORE
483	select REGMAP_I2C
484	select REGMAP_IRQ
485	select I2C_DESIGNWARE_PLATFORM
486	help
487	  Select this option to enable support for Crystal Cove PMIC
488	  on some Intel SoC systems. The PMIC provides ADC, GPIO,
489	  thermal, charger and related power management functions
490	  on these systems.
491
492	  This option is a bool as it provides an ACPI OpRegion which must be
493	  available before any devices using it are probed. This option also
494	  causes the designware-i2c driver to be builtin for the same reason.
495
496config INTEL_SOC_PMIC_BXTWC
497	tristate "Support for Intel Broxton Whiskey Cove PMIC"
498	depends on INTEL_PMC_IPC
499	select MFD_CORE
500	select REGMAP_IRQ
501	help
502	  Select this option to enable support for Whiskey Cove PMIC
503	  on Intel Broxton systems. The PMIC provides ADC, GPIO,
504	  thermal, charger and related power management functions
505	  on these systems.
506
507config INTEL_SOC_PMIC_CHTWC
508	bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
509	depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
510	depends on X86 || COMPILE_TEST
511	select MFD_CORE
512	select REGMAP_I2C
513	select REGMAP_IRQ
514	select I2C_DESIGNWARE_PLATFORM
515	help
516	  Select this option to enable support for the Intel Cherry Trail
517	  Whiskey Cove PMIC found on some Intel Cherry Trail systems.
518
519	  This option is a bool as it provides an ACPI OpRegion which must be
520	  available before any devices using it are probed. This option also
521	  causes the designware-i2c driver to be builtin for the same reason.
522
523config INTEL_SOC_PMIC_CHTDC_TI
524	tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC"
525	depends on GPIOLIB
526	depends on I2C
527	depends on ACPI
528	depends on X86
529	select MFD_CORE
530	select REGMAP_I2C
531	select REGMAP_IRQ
532	help
533	  Select this option for supporting Dollar Cove (TI version) PMIC
534	  device that is found on some Intel Cherry Trail systems.
535
536config MFD_INTEL_LPSS
537	tristate
538	select COMMON_CLK
539	select MFD_CORE
540
541config MFD_INTEL_LPSS_ACPI
542	tristate "Intel Low Power Subsystem support in ACPI mode"
543	select MFD_INTEL_LPSS
544	depends on X86 && ACPI
545	help
546	  This driver supports Intel Low Power Subsystem (LPSS) devices such as
547	  I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
548	  PCH) in ACPI mode.
549
550config MFD_INTEL_LPSS_PCI
551	tristate "Intel Low Power Subsystem support in PCI mode"
552	select MFD_INTEL_LPSS
553	depends on X86 && PCI
554	help
555	  This driver supports Intel Low Power Subsystem (LPSS) devices such as
556	  I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
557	  PCH) in PCI mode.
558
559config MFD_INTEL_MSIC
560	bool "Intel MSIC"
561	depends on INTEL_SCU_IPC
562	select MFD_CORE
563	help
564	  Select this option to enable access to Intel MSIC (Avatele
565	  Passage) chip. This chip embeds audio, battery, GPIO, etc.
566	  devices used in Intel Medfield platforms.
567
568config MFD_IPAQ_MICRO
569	bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
570	depends on SA1100_H3100 || SA1100_H3600
571	select MFD_CORE
572	help
573	  Select this to get support for the Microcontroller found in
574	  the Compaq iPAQ handheld computers. This is an Atmel
575	  AT90LS8535 microcontroller flashed with a special iPAQ
576	  firmware using the custom protocol implemented in this driver.
577
578config MFD_JANZ_CMODIO
579	tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
580	select MFD_CORE
581	depends on PCI
582	help
583	  This is the core driver for the Janz CMOD-IO PCI MODULbus
584	  carrier board. This device is a PCI to MODULbus bridge which may
585	  host many different types of MODULbus daughterboards, including
586	  CAN and GPIO controllers.
587
588config MFD_JZ4740_ADC
589	bool "Janz JZ4740 ADC core"
590	select MFD_CORE
591	select GENERIC_IRQ_CHIP
592	depends on MACH_JZ4740
593	help
594	  Say yes here if you want support for the ADC unit in the JZ4740 SoC.
595	  This driver is necessary for jz4740-battery and jz4740-hwmon driver.
596
597config MFD_KEMPLD
598	tristate "Kontron module PLD device"
599	select MFD_CORE
600	help
601	  This is the core driver for the PLD (Programmable Logic Device) found
602	  on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
603	  device may provide functions like watchdog, GPIO, UART and I2C bus.
604
605	  The following modules are supported:
606		* COMe-bBD#
607		* COMe-bBL6
608		* COMe-bHL6
609		* COMe-bSL6
610		* COMe-bIP#
611		* COMe-bKL6
612		* COMe-bPC2 (ETXexpress-PC)
613		* COMe-bSC# (ETXexpress-SC T#)
614		* COMe-cAL6
615		* COMe-cBL6
616		* COMe-cBT6
617		* COMe-cBW6
618		* COMe-cCT6
619		* COMe-cDC2 (microETXexpress-DC)
620		* COMe-cHL6
621		* COMe-cKL6
622		* COMe-cPC2 (microETXexpress-PC)
623		* COMe-cSL6
624		* COMe-mAL10
625		* COMe-mBT10
626		* COMe-mCT10
627		* COMe-mTT10 (nanoETXexpress-TT)
628		* ETX-OH
629
630	  This driver can also be built as a module. If so, the module
631	  will be called kempld-core.
632
633config MFD_88PM800
634	tristate "Marvell 88PM800"
635	depends on I2C
636	select REGMAP_I2C
637	select REGMAP_IRQ
638	select MFD_CORE
639	help
640	  This supports for Marvell 88PM800 Power Management IC.
641	  This includes the I2C driver and the core APIs _only_, you have to
642	  select individual components like voltage regulators, RTC and
643	  battery-charger under the corresponding menus.
644
645config MFD_88PM805
646	tristate "Marvell 88PM805"
647	depends on I2C
648	select REGMAP_I2C
649	select REGMAP_IRQ
650	select MFD_CORE
651	help
652	  This supports for Marvell 88PM805 Power Management IC. This includes
653	  the I2C driver and the core APIs _only_, you have to select individual
654	  components like codec device, headset/Mic device under the
655	  corresponding menus.
656
657config MFD_88PM860X
658	bool "Marvell 88PM8606/88PM8607"
659	depends on I2C=y
660	select REGMAP_I2C
661	select MFD_CORE
662	help
663	  This supports for Marvell 88PM8606/88PM8607 Power Management IC.
664	  This includes the I2C driver and the core APIs _only_, you have to
665	  select individual components like voltage regulators, RTC and
666	  battery-charger under the corresponding menus.
667
668config MFD_MAX14577
669	tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
670	depends on I2C
671	select MFD_CORE
672	select REGMAP_I2C
673	select REGMAP_IRQ
674	select IRQ_DOMAIN
675	help
676	  Say yes here to add support for Maxim Semiconductor MAX14577 and
677	  MAX77836 Micro-USB ICs with battery charger.
678	  This driver provides common support for accessing the device;
679	  additional drivers must be enabled in order to use the functionality
680	  of the device.
681
682config MFD_MAX77620
683	bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
684	depends on I2C=y
685	depends on OF || COMPILE_TEST
686	select MFD_CORE
687	select REGMAP_I2C
688	select REGMAP_IRQ
689	select IRQ_DOMAIN
690	help
691	  Say yes here to add support for Maxim Semiconductor MAX77620 and
692	  MAX20024 which are Power Management IC with General purpose pins,
693	  RTC, regulators, clock generator, watchdog etc. This driver
694	  provides common support for accessing the device; additional drivers
695	  must be enabled in order to use the functionality of the device.
696
697config MFD_MAX77686
698	tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
699	depends on I2C
700	depends on OF || COMPILE_TEST
701	select MFD_CORE
702	select REGMAP_I2C
703	select REGMAP_IRQ
704	select IRQ_DOMAIN
705	help
706	  Say yes here to add support for Maxim Semiconductor MAX77686 and
707	  MAX77802 which are Power Management IC with an RTC on chip.
708	  This driver provides common support for accessing the device;
709	  additional drivers must be enabled in order to use the functionality
710	  of the device.
711
712config MFD_MAX77693
713	tristate "Maxim Semiconductor MAX77693 PMIC Support"
714	depends on I2C
715	select MFD_CORE
716	select REGMAP_I2C
717	select REGMAP_IRQ
718	help
719	  Say yes here to add support for Maxim Semiconductor MAX77693.
720	  This is a companion Power Management IC with Flash, Haptic, Charger,
721	  and MUIC(Micro USB Interface Controller) controls on chip.
722	  This driver provides common support for accessing the device;
723	  additional drivers must be enabled in order to use the functionality
724	  of the device.
725
726config MFD_MAX77843
727	bool "Maxim Semiconductor MAX77843 PMIC Support"
728	depends on I2C=y
729	select MFD_CORE
730	select REGMAP_I2C
731	select REGMAP_IRQ
732	help
733	  Say yes here to add support for Maxim Semiconductor MAX77843.
734	  This is companion Power Management IC with LEDs, Haptic, Charger,
735	  Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
736	  This driver provides common support for accessing the device;
737	  additional drivers must be enabled in order to use the functionality
738	  of the device.
739
740config MFD_MAX8907
741	tristate "Maxim Semiconductor MAX8907 PMIC Support"
742	select MFD_CORE
743	depends on I2C
744	select REGMAP_I2C
745	select REGMAP_IRQ
746	help
747	  Say yes here to add support for Maxim Semiconductor MAX8907. This is
748	  a Power Management IC. This driver provides common support for
749	  accessing the device; additional drivers must be enabled in order
750	  to use the functionality of the device.
751
752config MFD_MAX8925
753	bool "Maxim Semiconductor MAX8925 PMIC Support"
754	depends on I2C=y
755	select MFD_CORE
756	help
757	  Say yes here to add support for Maxim Semiconductor MAX8925. This is
758	  a Power Management IC. This driver provides common support for
759	  accessing the device, additional drivers must be enabled in order
760	  to use the functionality of the device.
761
762config MFD_MAX8997
763	bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
764	depends on I2C=y
765	select MFD_CORE
766	select IRQ_DOMAIN
767	help
768	  Say yes here to add support for Maxim Semiconductor MAX8997/8966.
769	  This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
770	  MUIC controls on chip.
771	  This driver provides common support for accessing the device;
772	  additional drivers must be enabled in order to use the functionality
773	  of the device.
774
775config MFD_MAX8998
776	bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
777	depends on I2C=y
778	select MFD_CORE
779	select IRQ_DOMAIN
780	help
781	  Say yes here to add support for Maxim Semiconductor MAX8998 and
782	  National Semiconductor LP3974. This is a Power Management IC.
783	  This driver provides common support for accessing the device,
784	  additional drivers must be enabled in order to use the functionality
785	  of the device.
786
787config MFD_MT6397
788	tristate "MediaTek MT6397 PMIC Support"
789	select MFD_CORE
790	select IRQ_DOMAIN
791	help
792	  Say yes here to add support for MediaTek MT6397 PMIC. This is
793	  a Power Management IC. This driver provides common support for
794	  accessing the device; additional drivers must be enabled in order
795	  to use the functionality of the device.
796
797config MFD_MENF21BMC
798	tristate "MEN 14F021P00 Board Management Controller Support"
799	depends on I2C
800	select MFD_CORE
801	help
802	  Say yes here to add support for the MEN 14F021P00 BMC
803	  which is a Board Management Controller connected to the I2C bus.
804	  The device supports multiple sub-devices like LED, HWMON and WDT.
805	  This driver provides common support for accessing the devices;
806	  additional drivers must be enabled in order to use the
807	  functionality of the BMC device.
808
809	  This driver can also be built as a module. If so the module
810	  will be called menf21bmc.
811
812config EZX_PCAP
813	bool "Motorola EZXPCAP Support"
814	depends on SPI_MASTER
815	help
816	  This enables the PCAP ASIC present on EZX Phones. This is
817	  needed for MMC, TouchScreen, Sound, USB, etc..
818
819config MFD_CPCAP
820	tristate "Support for Motorola CPCAP"
821	depends on SPI
822	depends on OF || COMPILE_TEST
823	select REGMAP_SPI
824	select REGMAP_IRQ
825	help
826	  Say yes here if you want to include driver for CPCAP.
827	  It is used on many Motorola phones and tablets as a PMIC.
828	  At least Motorola Droid 4 is known to use CPCAP.
829
830config MFD_VIPERBOARD
831        tristate "Nano River Technologies Viperboard"
832	select MFD_CORE
833	depends on USB
834	default n
835	help
836	  Say yes here if you want support for Nano River Technologies
837	  Viperboard.
838	  There are mfd cell drivers available for i2c master, adc and
839	  both gpios found on the board. The spi part does not yet
840	  have a driver.
841	  You need to select the mfd cell drivers separately.
842	  The drivers do not support all features the board exposes.
843
844config MFD_RETU
845	tristate "Nokia Retu and Tahvo multi-function device"
846	select MFD_CORE
847	depends on I2C
848	select REGMAP_IRQ
849	help
850	  Retu and Tahvo are a multi-function devices found on Nokia
851	  Internet Tablets (770, N800 and N810).
852
853config MFD_PCF50633
854	tristate "NXP PCF50633"
855	depends on I2C
856	select REGMAP_I2C
857	help
858	  Say yes here if you have NXP PCF50633 chip on your board.
859	  This core driver provides register access and IRQ handling
860	  facilities, and registers devices for the various functions
861	  so that function-specific drivers can bind to them.
862
863config PCF50633_ADC
864	tristate "NXP PCF50633 ADC"
865	depends on MFD_PCF50633
866	help
867	 Say yes here if you want to include support for ADC in the
868	 NXP PCF50633 chip.
869
870config PCF50633_GPIO
871	tristate "NXP PCF50633 GPIO"
872	depends on MFD_PCF50633
873	help
874	 Say yes here if you want to include support GPIO for pins on
875	 the PCF50633 chip.
876
877config UCB1400_CORE
878	tristate "Philips UCB1400 Core driver"
879	depends on AC97_BUS
880	depends on GPIOLIB
881	help
882	  This enables support for the Philips UCB1400 core functions.
883	  The UCB1400 is an AC97 audio codec.
884
885	  To compile this driver as a module, choose M here: the
886	  module will be called ucb1400_core.
887
888config MFD_PM8XXX
889	tristate "Qualcomm PM8xxx PMIC chips driver"
890	depends on (ARM || HEXAGON || COMPILE_TEST)
891	select IRQ_DOMAIN
892	select MFD_CORE
893	select REGMAP
894	help
895	  If you say yes to this option, support will be included for the
896	  built-in PM8xxx PMIC chips.
897
898	  This is required if your board has a PM8xxx and uses its features,
899	  such as: MPPs, GPIOs, regulators, interrupts, and PWM.
900
901	  Say M here if you want to include support for PM8xxx chips as a
902	  module. This will build a module called "pm8xxx-core".
903
904config MFD_QCOM_RPM
905	tristate "Qualcomm Resource Power Manager (RPM)"
906	depends on ARCH_QCOM && OF
907	help
908	  If you say yes to this option, support will be included for the
909	  Resource Power Manager system found in the Qualcomm 8660, 8960 and
910	  8064 based devices.
911
912	  This is required to access many regulators, clocks and bus
913	  frequencies controlled by the RPM on these devices.
914
915	  Say M here if you want to include support for the Qualcomm RPM as a
916	  module. This will build a module called "qcom_rpm".
917
918config MFD_SPMI_PMIC
919	tristate "Qualcomm SPMI PMICs"
920	depends on ARCH_QCOM || COMPILE_TEST
921	depends on OF
922	depends on SPMI
923	select REGMAP_SPMI
924	help
925	  This enables support for the Qualcomm SPMI PMICs.
926	  These PMICs are currently used with the Snapdragon 800 series of
927	  SoCs.  Note, that this will only be useful paired with descriptions
928	  of the independent functions as children nodes in the device tree.
929
930	  Say M here if you want to include support for the SPMI PMIC
931	  series as a module.  The module will be called "qcom-spmi-pmic".
932
933config MFD_RDC321X
934	tristate "RDC R-321x southbridge"
935	select MFD_CORE
936	depends on PCI
937	help
938	  Say yes here if you want to have support for the RDC R-321x SoC
939	  southbridge which provides access to GPIOs and Watchdog using the
940	  southbridge PCI device configuration space.
941
942config MFD_RT5033
943	tristate "Richtek RT5033 Power Management IC"
944	depends on I2C
945	select MFD_CORE
946	select REGMAP_I2C
947	select REGMAP_IRQ
948	help
949	  This driver provides for the Richtek RT5033 Power Management IC,
950	  which includes the I2C driver and the Core APIs. This driver provides
951	  common support for accessing the device. The device supports multiple
952	  sub-devices like charger, fuel gauge, flash LED, current source,
953	  LDO and Buck.
954
955config MFD_RC5T583
956	bool "Ricoh RC5T583 Power Management system device"
957	depends on I2C=y
958	select MFD_CORE
959	select REGMAP_I2C
960	help
961	  Select this option to get support for the RICOH583 Power
962	  Management system device.
963	  This driver provides common support for accessing the device
964	  through i2c interface. The device supports multiple sub-devices
965	  like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
966	  Additional drivers must be enabled in order to use the
967	  different functionality of the device.
968
969config MFD_RK808
970	tristate "Rockchip RK805/RK808/RK818 Power Management Chip"
971	depends on I2C && OF
972	select MFD_CORE
973	select REGMAP_I2C
974	select REGMAP_IRQ
975	help
976	  If you say yes here you get support for the RK805, RK808 and RK818
977	  Power Management chips.
978	  This driver provides common support for accessing the device
979	  through I2C interface. The device supports multiple sub-devices
980	  including interrupts, RTC, LDO & DCDC regulators, and onkey.
981
982config MFD_RN5T618
983	tristate "Ricoh RN5T567/618 PMIC"
984	depends on I2C
985	depends on OF
986	select MFD_CORE
987	select REGMAP_I2C
988	help
989	  Say yes here to add support for the Ricoh RN5T567,
990          RN5T618, RC5T619 PMIC.
991	  This driver provides common support for accessing the device,
992	  additional drivers must be enabled in order to use the
993	  functionality of the device.
994
995config MFD_SEC_CORE
996	bool "SAMSUNG Electronics PMIC Series Support"
997	depends on I2C=y
998	select MFD_CORE
999	select REGMAP_I2C
1000	select REGMAP_IRQ
1001	help
1002	 Support for the Samsung Electronics MFD series.
1003	 This driver provides common support for accessing the device,
1004	 additional drivers must be enabled in order to use the functionality
1005	 of the device
1006
1007config MFD_SI476X_CORE
1008	tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1009	depends on I2C
1010	select MFD_CORE
1011	select REGMAP_I2C
1012	help
1013	  This is the core driver for the SI476x series of AM/FM
1014	  radio. This MFD driver connects the radio-si476x V4L2 module
1015	  and the si476x audio codec.
1016
1017	  To compile this driver as a module, choose M here: the
1018	  module will be called si476x-core.
1019
1020config MFD_SM501
1021	tristate "Silicon Motion SM501"
1022	 ---help---
1023	  This is the core driver for the Silicon Motion SM501 multimedia
1024	  companion chip. This device is a multifunction device which may
1025	  provide numerous interfaces including USB host controller, USB gadget,
1026	  asynchronous serial ports, audio functions, and a dual display video
1027	  interface. The device may be connected by PCI or local bus with
1028	  varying functions enabled.
1029
1030config MFD_SM501_GPIO
1031	bool "Export GPIO via GPIO layer"
1032	depends on MFD_SM501 && GPIOLIB
1033	 ---help---
1034	 This option uses the gpio library layer to export the 64 GPIO
1035	 lines on the SM501. The platform data is used to supply the
1036	 base number for the first GPIO line to register.
1037
1038config MFD_SKY81452
1039	tristate "Skyworks Solutions SKY81452"
1040	select MFD_CORE
1041	select REGMAP_I2C
1042	depends on I2C
1043	help
1044	  This is the core driver for the Skyworks SKY81452 backlight and
1045	  voltage regulator device.
1046
1047	  This driver can also be built as a module.  If so, the module
1048	  will be called sky81452.
1049
1050config MFD_SMSC
1051       bool "SMSC ECE1099 series chips"
1052       depends on I2C=y
1053       select MFD_CORE
1054       select REGMAP_I2C
1055       help
1056        If you say yes here you get support for the
1057        ece1099 chips from SMSC.
1058
1059        To compile this driver as a module, choose M here: the
1060        module will be called smsc.
1061
1062config MFD_SC27XX_PMIC
1063	tristate "Spreadtrum SC27xx PMICs"
1064	depends on ARCH_SPRD || COMPILE_TEST
1065	depends on SPI_MASTER
1066	select MFD_CORE
1067	select REGMAP_SPI
1068	select REGMAP_IRQ
1069	help
1070	  This enables support for the Spreadtrum SC27xx PMICs with SPI
1071	  interface. The SC27xx series PMICs integrate power management,
1072	  audio codec, battery management and user interface support
1073	  function (such as RTC, Typec, indicator and so on) in a single chip.
1074
1075	  This driver provides common support for accessing the SC27xx PMICs,
1076	  and it also adds the irq_chip parts for handling the PMIC chip events.
1077
1078config ABX500_CORE
1079	bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1080	default y if ARCH_U300 || ARCH_U8500 || COMPILE_TEST
1081	help
1082	  Say yes here if you have the ABX500 Mixed Signal IC family
1083	  chips. This core driver expose register access functions.
1084	  Functionality specific drivers using these functions can
1085	  remain unchanged when IC changes. Binding of the functions to
1086	  actual register access is done by the IC core driver.
1087
1088config AB3100_CORE
1089	bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
1090	depends on I2C=y && ABX500_CORE
1091	select MFD_CORE
1092	default y if ARCH_U300
1093	help
1094	  Select this to enable the AB3100 Mixed Signal IC core
1095	  functionality. This connects to a AB3100 on the I2C bus
1096	  and expose a number of symbols needed for dependent devices
1097	  to read and write registers and subscribe to events from
1098	  this multi-functional IC. This is needed to use other features
1099	  of the AB3100 such as battery-backed RTC, charging control,
1100	  LEDs, vibrator, system power and temperature, power management
1101	  and ALSA sound.
1102
1103config AB3100_OTP
1104	tristate "ST-Ericsson AB3100 OTP functions"
1105	depends on AB3100_CORE
1106	default y if AB3100_CORE
1107	help
1108	  Select this to enable the AB3100 Mixed Signal IC OTP (one-time
1109	  programmable memory) support. This exposes a sysfs file to read
1110	  out OTP values.
1111
1112config AB8500_CORE
1113	bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1114	depends on ABX500_CORE && MFD_DB8500_PRCMU
1115	select POWER_SUPPLY
1116	select MFD_CORE
1117	select IRQ_DOMAIN
1118	help
1119	  Select this option to enable access to AB8500 power management
1120	  chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1121	  since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1122	  the irq_chip parts for handling the Mixed Signal chip events.
1123	  This chip embeds various other multimedia funtionalities as well.
1124
1125config AB8500_DEBUG
1126       bool "Enable debug info via debugfs"
1127       depends on AB8500_GPADC && DEBUG_FS
1128       default y if DEBUG_FS
1129       help
1130         Select this option if you want debug information using the debug
1131         filesystem, debugfs.
1132
1133config AB8500_GPADC
1134	bool "ST-Ericsson AB8500 GPADC driver"
1135	depends on AB8500_CORE && REGULATOR_AB8500
1136	default y
1137	help
1138	  AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1139
1140config MFD_DB8500_PRCMU
1141	bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1142	depends on UX500_SOC_DB8500
1143	select MFD_CORE
1144	help
1145	  Select this option to enable support for the DB8500 Power Reset
1146	  and Control Management Unit. This is basically an autonomous
1147	  system controller running an XP70 microprocessor, which is accessed
1148	  through a register map.
1149
1150config MFD_STMPE
1151	bool "STMicroelectronics STMPE"
1152	depends on (I2C=y || SPI_MASTER=y)
1153	depends on OF
1154	select MFD_CORE
1155	help
1156	  Support for the STMPE family of I/O Expanders from
1157	  STMicroelectronics.
1158
1159	  Currently supported devices are:
1160
1161		STMPE811: GPIO, Touchscreen
1162		STMPE1601: GPIO, Keypad
1163		STMPE1801: GPIO, Keypad
1164		STMPE2401: GPIO, Keypad
1165		STMPE2403: GPIO, Keypad
1166
1167	  This driver provides common support for accessing the device,
1168	  additional drivers must be enabled in order to use the functionality
1169	  of the device.  Currently available sub drivers are:
1170
1171		GPIO: stmpe-gpio
1172		Keypad: stmpe-keypad
1173		Touchscreen: stmpe-ts
1174
1175menu "STMicroelectronics STMPE Interface Drivers"
1176depends on MFD_STMPE
1177
1178config STMPE_I2C
1179	bool "STMicroelectronics STMPE I2C Interface"
1180	depends on I2C=y
1181	default y
1182	help
1183	  This is used to enable I2C interface of STMPE
1184
1185config STMPE_SPI
1186	bool "STMicroelectronics STMPE SPI Interface"
1187	depends on SPI_MASTER
1188	help
1189	  This is used to enable SPI interface of STMPE
1190endmenu
1191
1192config MFD_STA2X11
1193	bool "STMicroelectronics STA2X11"
1194	depends on STA2X11
1195	select MFD_CORE
1196	select REGMAP_MMIO
1197
1198config MFD_SUN6I_PRCM
1199	bool "Allwinner A31 PRCM controller"
1200	depends on ARCH_SUNXI
1201	select MFD_CORE
1202	help
1203	  Support for the PRCM (Power/Reset/Clock Management) unit available
1204	  in A31 SoC.
1205
1206config MFD_SYSCON
1207	bool "System Controller Register R/W Based on Regmap"
1208	select REGMAP_MMIO
1209	help
1210	  Select this option to enable accessing system control registers
1211	  via regmap.
1212
1213config MFD_DAVINCI_VOICECODEC
1214	tristate
1215	select MFD_CORE
1216	select REGMAP_MMIO
1217
1218config MFD_TI_AM335X_TSCADC
1219	tristate "TI ADC / Touch Screen chip support"
1220	select MFD_CORE
1221	select REGMAP
1222	select REGMAP_MMIO
1223	help
1224	  If you say yes here you get support for Texas Instruments series
1225	  of Touch Screen /ADC chips.
1226	  To compile this driver as a module, choose M here: the
1227	  module will be called ti_am335x_tscadc.
1228
1229config MFD_DM355EVM_MSP
1230	bool "TI DaVinci DM355 EVM microcontroller"
1231	depends on I2C=y && MACH_DAVINCI_DM355_EVM
1232	help
1233	  This driver supports the MSP430 microcontroller used on these
1234	  boards.  MSP430 firmware manages resets and power sequencing,
1235	  inputs from buttons and the IR remote, LEDs, an RTC, and more.
1236
1237config MFD_LP3943
1238	tristate "TI/National Semiconductor LP3943 MFD Driver"
1239	depends on I2C
1240	select MFD_CORE
1241	select REGMAP_I2C
1242	help
1243	  Support for the TI/National Semiconductor LP3943.
1244	  This driver consists of GPIO and PWM drivers.
1245	  With these functionalities, it can be used for LED string control or
1246	  general usage such like a GPIO controller and a PWM controller.
1247
1248config MFD_LP8788
1249	bool "TI LP8788 Power Management Unit Driver"
1250	depends on I2C=y
1251	select MFD_CORE
1252	select REGMAP_I2C
1253	select IRQ_DOMAIN
1254	help
1255	  TI LP8788 PMU supports regulators, battery charger, RTC,
1256	  ADC, backlight driver and current sinks.
1257
1258config MFD_TI_LMU
1259	tristate "TI Lighting Management Unit driver"
1260	depends on I2C
1261	select MFD_CORE
1262	select REGMAP_I2C
1263	help
1264	  Say yes here to enable support for TI LMU chips.
1265
1266	  TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
1267	  It consists of backlight, LED and regulator driver.
1268	  It provides consistent device controls for lighting functions.
1269
1270config MFD_OMAP_USB_HOST
1271	bool "TI OMAP USBHS core and TLL driver"
1272	depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1273	default y
1274	help
1275	  This is the core driver for the OAMP EHCI and OHCI drivers.
1276	  This MFD driver does the required setup functionalities for
1277	  OMAP USB Host drivers.
1278
1279config MFD_PALMAS
1280	bool "TI Palmas series chips"
1281	select MFD_CORE
1282	select REGMAP_I2C
1283	select REGMAP_IRQ
1284	depends on I2C=y
1285	help
1286	  If you say yes here you get support for the Palmas
1287	  series of PMIC chips from Texas Instruments.
1288
1289config TPS6105X
1290	tristate "TI TPS61050/61052 Boost Converters"
1291	depends on I2C
1292	select REGMAP_I2C
1293	select REGULATOR
1294	select MFD_CORE
1295	select REGULATOR_FIXED_VOLTAGE
1296	help
1297	  This option enables a driver for the TP61050/TPS61052
1298	  high-power "white LED driver". This boost converter is
1299	  sometimes used for other things than white LEDs, and
1300	  also contains a GPIO pin.
1301
1302config TPS65010
1303	tristate "TI TPS6501x Power Management chips"
1304	depends on I2C && GPIOLIB
1305	default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1306	help
1307	  If you say yes here you get support for the TPS6501x series of
1308	  Power Management chips.  These include voltage regulators,
1309	  lithium ion/polymer battery charging, and other features that
1310	  are often used in portable devices like cell phones and cameras.
1311
1312	  This driver can also be built as a module.  If so, the module
1313	  will be called tps65010.
1314
1315config TPS6507X
1316	tristate "TI TPS6507x Power Management / Touch Screen chips"
1317	select MFD_CORE
1318	depends on I2C
1319	help
1320	  If you say yes here you get support for the TPS6507x series of
1321	  Power Management / Touch Screen chips.  These include voltage
1322	  regulators, lithium ion/polymer battery charging, touch screen
1323	  and other features that are often used in portable devices.
1324	  This driver can also be built as a module.  If so, the module
1325	  will be called tps6507x.
1326
1327config MFD_TPS65086
1328	tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1329	select MFD_CORE
1330	select REGMAP
1331	select REGMAP_IRQ
1332	select REGMAP_I2C
1333	depends on I2C
1334	help
1335	  If you say yes here you get support for the TPS65086 series of
1336	  Power Management chips.
1337	  This driver provides common support for accessing the device,
1338	  additional drivers must be enabled in order to use the
1339	  functionality of the device.
1340
1341config TPS65911_COMPARATOR
1342	tristate
1343
1344config MFD_TPS65090
1345	bool "TI TPS65090 Power Management chips"
1346	depends on I2C=y
1347	select MFD_CORE
1348	select REGMAP_I2C
1349	select REGMAP_IRQ
1350	help
1351	  If you say yes here you get support for the TPS65090 series of
1352	  Power Management chips.
1353	  This driver provides common support for accessing the device,
1354	  additional drivers must be enabled in order to use the
1355	  functionality of the device.
1356
1357config MFD_TPS65217
1358	tristate "TI TPS65217 Power Management / White LED chips"
1359	depends on I2C && OF
1360	select MFD_CORE
1361	select REGMAP_I2C
1362	select IRQ_DOMAIN
1363	help
1364	  If you say yes here you get support for the TPS65217 series of
1365	  Power Management / White LED chips.
1366	  These include voltage regulators, lithium ion/polymer battery
1367	  charger, wled and other features that are often used in portable
1368	  devices.
1369
1370	  This driver can also be built as a module.  If so, the module
1371	  will be called tps65217.
1372
1373config MFD_TPS68470
1374	bool "TI TPS68470 Power Management / LED chips"
1375	depends on ACPI && I2C=y
1376	select MFD_CORE
1377	select REGMAP_I2C
1378	select I2C_DESIGNWARE_PLATFORM
1379	help
1380	  If you say yes here you get support for the TPS68470 series of
1381	  Power Management / LED chips.
1382
1383	  These include voltage regulators, LEDs and other features
1384	  that are often used in portable devices.
1385
1386	  This option is a bool as it provides an ACPI operation
1387	  region, which must be available before any of the devices
1388	  using this are probed. This option also configures the
1389	  designware-i2c driver to be built-in, for the same reason.
1390
1391config MFD_TI_LP873X
1392	tristate "TI LP873X Power Management IC"
1393	depends on I2C
1394	select MFD_CORE
1395	select REGMAP_I2C
1396	help
1397	  If you say yes here then you get support for the LP873X series of
1398	  Power Management Integrated Circuits (PMIC).
1399	  These include voltage regulators, thermal protection, configurable
1400	  General Purpose Outputs (GPO) that are used in portable devices.
1401
1402	  This driver can also be built as a module. If so, the module
1403	  will be called lp873x.
1404
1405config MFD_TI_LP87565
1406	tristate "TI LP87565 Power Management IC"
1407	depends on I2C && OF
1408	select MFD_CORE
1409	select REGMAP_I2C
1410	help
1411	  If you say yes here then you get support for the LP87565 series of
1412	  Power Management Integrated Circuits (PMIC).
1413	  These include voltage regulators, thermal protection, configurable
1414	  General Purpose Outputs (GPO) that are used in portable devices.
1415
1416	  This driver can also be built as a module. If so, the module
1417	  will be called lp87565.
1418
1419config MFD_TPS65218
1420	tristate "TI TPS65218 Power Management chips"
1421	depends on I2C && OF
1422	select MFD_CORE
1423	select REGMAP_I2C
1424	select REGMAP_IRQ
1425	help
1426	  If you say yes here you get support for the TPS65218 series of
1427	  Power Management chips.
1428	  These include voltage regulators, gpio and other features
1429	  that are often used in portable devices.
1430
1431	  This driver can also be built as a module.  If so, the module
1432	  will be called tps65218.
1433
1434config MFD_TPS6586X
1435	bool "TI TPS6586x Power Management chips"
1436	depends on I2C=y
1437	select MFD_CORE
1438	select REGMAP_I2C
1439	help
1440	  If you say yes here you get support for the TPS6586X series of
1441	  Power Management chips.
1442	  This driver provides common support for accessing the device,
1443	  additional drivers must be enabled in order to use the
1444	  functionality of the device.
1445
1446	  This driver can also be built as a module.  If so, the module
1447	  will be called tps6586x.
1448
1449config MFD_TPS65910
1450	bool "TI TPS65910 Power Management chip"
1451	depends on I2C=y
1452	depends on GPIOLIB || COMPILE_TEST
1453	select MFD_CORE
1454	select REGMAP_I2C
1455	select REGMAP_IRQ
1456	select IRQ_DOMAIN
1457	help
1458	  if you say yes here you get support for the TPS65910 series of
1459	  Power Management chips.
1460
1461config MFD_TPS65912
1462	tristate
1463	select MFD_CORE
1464	select REGMAP
1465	select REGMAP_IRQ
1466
1467config MFD_TPS65912_I2C
1468	tristate "TI TPS65912 Power Management chip with I2C"
1469	select MFD_TPS65912
1470	select REGMAP_I2C
1471	depends on I2C
1472	help
1473	  If you say yes here you get support for the TPS65912 series of
1474	  PM chips with I2C interface.
1475
1476config MFD_TPS65912_SPI
1477	tristate "TI TPS65912 Power Management chip with SPI"
1478	select MFD_TPS65912
1479	select REGMAP_SPI
1480	depends on SPI_MASTER
1481	help
1482	  If you say yes here you get support for the TPS65912 series of
1483	  PM chips with SPI interface.
1484
1485config MFD_TPS80031
1486	bool "TI TPS80031/TPS80032 Power Management chips"
1487	depends on I2C=y
1488	select MFD_CORE
1489	select REGMAP_I2C
1490	select REGMAP_IRQ
1491	help
1492	  If you say yes here you get support for the Texas Instruments
1493	  TPS80031/ TPS80032 Fully Integrated Power Management with Power
1494	  Path and Battery Charger. The device provides five configurable
1495	  step-down converters, 11 general purpose LDOs, USB OTG Module,
1496	  ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1497	  Power Path from USB, 32K clock generator.
1498
1499config TWL4030_CORE
1500	bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1501	depends on I2C=y
1502	select IRQ_DOMAIN
1503	select REGMAP_I2C
1504	help
1505	  Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1506	  This core driver provides register access and IRQ handling
1507	  facilities, and registers devices for the various functions
1508	  so that function-specific drivers can bind to them.
1509
1510	  These multi-function chips are found on many OMAP2 and OMAP3
1511	  boards, providing power management, RTC, GPIO, keypad, a
1512	  high speed USB OTG transceiver, an audio codec (on most
1513	  versions) and many other features.
1514
1515config TWL4030_POWER
1516	bool "TI TWL4030 power resources"
1517	depends on TWL4030_CORE && ARM
1518	help
1519	  Say yes here if you want to use the power resources on the
1520	  TWL4030 family chips.  Most of these resources are regulators,
1521	  which have a separate driver; some are control signals, such
1522	  as clock request handshaking.
1523
1524	  This driver uses board-specific data to initialize the resources
1525	  and load scripts controlling which resources are switched off/on
1526	  or reset when a sleep, wakeup or warm reset event occurs.
1527
1528config MFD_TWL4030_AUDIO
1529	bool "TI TWL4030 Audio"
1530	depends on TWL4030_CORE
1531	select MFD_CORE
1532	default n
1533
1534config TWL6040_CORE
1535	bool "TI TWL6040 audio codec"
1536	depends on I2C=y
1537	select MFD_CORE
1538	select REGMAP_I2C
1539	select REGMAP_IRQ
1540	default n
1541	help
1542	  Say yes here if you want support for Texas Instruments TWL6040 audio
1543	  codec.
1544	  This driver provides common support for accessing the device,
1545	  additional drivers must be enabled in order to use the
1546	  functionality of the device (audio, vibra).
1547
1548config MENELAUS
1549	bool "TI TWL92330/Menelaus PM chip"
1550	depends on I2C=y && ARCH_OMAP2
1551	help
1552	  If you say yes here you get support for the Texas Instruments
1553	  TWL92330/Menelaus Power Management chip. This include voltage
1554	  regulators, Dual slot memory card transceivers, real-time clock
1555	  and other features that are often used in portable devices like
1556	  cell phones and PDAs.
1557
1558config MFD_WL1273_CORE
1559	tristate "TI WL1273 FM radio"
1560	depends on I2C
1561	select MFD_CORE
1562	default n
1563	help
1564	  This is the core driver for the TI WL1273 FM radio. This MFD
1565	  driver connects the radio-wl1273 V4L2 module and the wl1273
1566	  audio codec.
1567
1568config MFD_LM3533
1569	tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1570	depends on I2C
1571	select MFD_CORE
1572	select REGMAP_I2C
1573	help
1574	  Say yes here to enable support for National Semiconductor / TI
1575	  LM3533 Lighting Power chips.
1576
1577	  This driver provides common support for accessing the device;
1578	  additional drivers must be enabled in order to use the LED,
1579	  backlight or ambient-light-sensor functionality of the device.
1580
1581config MFD_TIMBERDALE
1582	tristate "Timberdale FPGA"
1583	select MFD_CORE
1584	depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1585	---help---
1586	This is the core driver for the timberdale FPGA. This device is a
1587	multifunction device which exposes numerous platform devices.
1588
1589	The timberdale FPGA can be found on the Intel Atom development board
1590	for in-vehicle infontainment, called Russellville.
1591
1592config MFD_TC3589X
1593	bool "Toshiba TC35892 and variants"
1594	depends on I2C=y
1595	depends on OF
1596	select MFD_CORE
1597	help
1598	  Support for the Toshiba TC35892 and variants I/O Expander.
1599
1600	  This driver provides common support for accessing the device,
1601	  additional drivers must be enabled in order to use the
1602	  functionality of the device.
1603
1604config MFD_TMIO
1605	bool
1606	default n
1607
1608config MFD_T7L66XB
1609	bool "Toshiba T7L66XB"
1610	depends on ARM && HAVE_CLK
1611	select MFD_CORE
1612	select MFD_TMIO
1613	help
1614	  Support for Toshiba Mobile IO Controller T7L66XB
1615
1616config MFD_TC6387XB
1617	bool "Toshiba TC6387XB"
1618	depends on ARM && HAVE_CLK
1619	select MFD_CORE
1620	select MFD_TMIO
1621	help
1622	  Support for Toshiba Mobile IO Controller TC6387XB
1623
1624config MFD_TC6393XB
1625	bool "Toshiba TC6393XB"
1626	depends on ARM && HAVE_CLK
1627	select GPIOLIB
1628	select MFD_CORE
1629	select MFD_TMIO
1630	help
1631	  Support for Toshiba Mobile IO Controller TC6393XB
1632
1633config MFD_VX855
1634	tristate "VIA VX855/VX875 integrated south bridge"
1635	depends on PCI
1636	select MFD_CORE
1637	help
1638	  Say yes here to enable support for various functions of the
1639	  VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1640	  and/or vx855_gpio drivers for this to do anything useful.
1641
1642config MFD_ARIZONA
1643	select REGMAP
1644	select REGMAP_IRQ
1645	select MFD_CORE
1646	bool
1647
1648config MFD_ARIZONA_I2C
1649	tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1650	select MFD_ARIZONA
1651	select REGMAP_I2C
1652	depends on I2C
1653	help
1654	  Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1655	  audio SoC core functionality controlled via I2C.
1656
1657config MFD_ARIZONA_SPI
1658	tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1659	select MFD_ARIZONA
1660	select REGMAP_SPI
1661	depends on SPI_MASTER
1662	help
1663	  Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1664	  audio SoC core functionality controlled via SPI.
1665
1666config MFD_CS47L24
1667	bool "Cirrus Logic CS47L24 and WM1831"
1668	depends on MFD_ARIZONA
1669	help
1670	  Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1671
1672config MFD_WM5102
1673	bool "Wolfson Microelectronics WM5102"
1674	depends on MFD_ARIZONA
1675	help
1676	  Support for Wolfson Microelectronics WM5102 low power audio SoC
1677
1678config MFD_WM5110
1679	bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1680	depends on MFD_ARIZONA
1681	help
1682	  Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1683	  low power audio SoC
1684
1685config MFD_WM8997
1686	bool "Wolfson Microelectronics WM8997"
1687	depends on MFD_ARIZONA
1688	help
1689	  Support for Wolfson Microelectronics WM8997 low power audio SoC
1690
1691config MFD_WM8998
1692	bool "Wolfson Microelectronics WM8998"
1693	depends on MFD_ARIZONA
1694	help
1695	  Support for Wolfson Microelectronics WM8998 low power audio SoC
1696
1697config MFD_WM8400
1698	bool "Wolfson Microelectronics WM8400"
1699	select MFD_CORE
1700	depends on I2C=y
1701	select REGMAP_I2C
1702	help
1703	  Support for the Wolfson Microelecronics WM8400 PMIC and audio
1704	  CODEC.  This driver provides common support for accessing
1705	  the device, additional drivers must be enabled in order to use
1706	  the functionality of the device.
1707
1708config MFD_WM831X
1709	bool
1710
1711config MFD_WM831X_I2C
1712	bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1713	select MFD_CORE
1714	select MFD_WM831X
1715	select REGMAP_I2C
1716	select IRQ_DOMAIN
1717	depends on I2C=y
1718	help
1719	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1720	  when controlled using I2C.  This driver provides common support
1721	  for accessing the device, additional drivers must be enabled in
1722	  order to use the functionality of the device.
1723
1724config MFD_WM831X_SPI
1725	bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1726	select MFD_CORE
1727	select MFD_WM831X
1728	select REGMAP_SPI
1729	select IRQ_DOMAIN
1730	depends on SPI_MASTER
1731	help
1732	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1733	  when controlled using SPI.  This driver provides common support
1734	  for accessing the device, additional drivers must be enabled in
1735	  order to use the functionality of the device.
1736
1737config MFD_WM8350
1738	bool
1739
1740config MFD_WM8350_I2C
1741	bool "Wolfson Microelectronics WM8350 with I2C"
1742	select MFD_WM8350
1743	select REGMAP_I2C
1744	depends on I2C=y
1745	help
1746	  The WM8350 is an integrated audio and power management
1747	  subsystem with watchdog and RTC functionality for embedded
1748	  systems.  This option enables core support for the WM8350 with
1749	  I2C as the control interface.  Additional options must be
1750	  selected to enable support for the functionality of the chip.
1751
1752config MFD_WM8994
1753	tristate "Wolfson Microelectronics WM8994"
1754	select MFD_CORE
1755	select REGMAP_I2C
1756	select REGMAP_IRQ
1757	depends on I2C
1758	help
1759	  The WM8994 is a highly integrated hi-fi CODEC designed for
1760	  smartphone applications.  As well as audio functionality it
1761	  has on board GPIO and regulator functionality which is
1762	  supported via the relevant subsystems.  This driver provides
1763	  core support for the WM8994, in order to use the actual
1764	  functionaltiy of the device other drivers must be enabled.
1765
1766config MFD_WM97xx
1767	tristate "Wolfson Microelectronics WM97xx"
1768	select MFD_CORE
1769	select REGMAP_AC97
1770	select AC97_BUS_COMPAT
1771	depends on AC97_BUS_NEW
1772	help
1773	  The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC
1774	  designed for smartphone applications.  As well as audio functionality
1775	  it has on board GPIO and a touchscreen functionality which is
1776	  supported via the relevant subsystems.  This driver provides core
1777	  support for the WM97xx, in order to use the actual functionaltiy of
1778	  the device other drivers must be enabled.
1779
1780config MFD_STW481X
1781	tristate "Support for ST Microelectronics STw481x"
1782	depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1783	select REGMAP_I2C
1784	select MFD_CORE
1785	help
1786	  Select this option to enable the STw481x chip driver used
1787	  in various ST Microelectronics and ST-Ericsson embedded
1788	  Nomadik series.
1789
1790config MFD_STM32_LPTIMER
1791	tristate "Support for STM32 Low-Power Timer"
1792	depends on (ARCH_STM32 && OF) || COMPILE_TEST
1793	select MFD_CORE
1794	select REGMAP
1795	select REGMAP_MMIO
1796	help
1797	  Select this option to enable STM32 Low-Power Timer driver
1798	  used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
1799	  resources are also dealt with here.
1800
1801	  To compile this driver as a module, choose M here: the
1802	  module will be called stm32-lptimer.
1803
1804config MFD_STM32_TIMERS
1805	tristate "Support for STM32 Timers"
1806	depends on (ARCH_STM32 && OF) || COMPILE_TEST
1807	select MFD_CORE
1808	select REGMAP
1809	select REGMAP_MMIO
1810	help
1811	  Select this option to enable STM32 timers driver used
1812	  for PWM and IIO Timer. This driver allow to share the
1813	  registers between the others drivers.
1814
1815menu "Multimedia Capabilities Port drivers"
1816	depends on ARCH_SA1100
1817
1818config MCP
1819	tristate
1820
1821# Interface drivers
1822config MCP_SA11X0
1823	tristate "Support SA11x0 MCP interface"
1824	depends on ARCH_SA1100
1825	select MCP
1826
1827# Chip drivers
1828config MCP_UCB1200
1829	tristate "Support for UCB1200 / UCB1300"
1830	depends on MCP_SA11X0
1831	select MCP
1832
1833config MCP_UCB1200_TS
1834	tristate "Touchscreen interface support"
1835	depends on MCP_UCB1200 && INPUT
1836
1837endmenu
1838
1839config MFD_VEXPRESS_SYSREG
1840	bool "Versatile Express System Registers"
1841	depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1842	default y
1843	select CLKSRC_MMIO
1844	select GPIO_GENERIC_PLATFORM
1845	select MFD_CORE
1846	select MFD_SYSCON
1847	help
1848	  System Registers are the platform configuration block
1849	  on the ARM Ltd. Versatile Express board.
1850
1851config RAVE_SP_CORE
1852	tristate "RAVE SP MCU core driver"
1853	depends on SERIAL_DEV_BUS
1854	select CRC_CCITT
1855	help
1856	  Select this to get support for the Supervisory Processor
1857	  device found on several devices in RAVE line of hardware.
1858
1859endmenu
1860endif
1861