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