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