xref: /openbmc/linux/drivers/mfd/Kconfig (revision 179dd8c0)
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 && OF
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_MSIC
332	bool "Intel MSIC"
333	depends on INTEL_SCU_IPC
334	select MFD_CORE
335	help
336	  Select this option to enable access to Intel MSIC (Avatele
337	  Passage) chip. This chip embeds audio, battery, GPIO, etc.
338	  devices used in Intel Medfield platforms.
339
340config MFD_IPAQ_MICRO
341	bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
342	depends on SA1100_H3100 || SA1100_H3600
343	select MFD_CORE
344	help
345	  Select this to get support for the Microcontroller found in
346	  the Compaq iPAQ handheld computers. This is an Atmel
347	  AT90LS8535 microcontroller flashed with a special iPAQ
348	  firmware using the custom protocol implemented in this driver.
349
350config MFD_JANZ_CMODIO
351	tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
352	select MFD_CORE
353	depends on PCI
354	help
355	  This is the core driver for the Janz CMOD-IO PCI MODULbus
356	  carrier board. This device is a PCI to MODULbus bridge which may
357	  host many different types of MODULbus daughterboards, including
358	  CAN and GPIO controllers.
359
360config MFD_JZ4740_ADC
361	bool "Janz JZ4740 ADC core"
362	select MFD_CORE
363	select GENERIC_IRQ_CHIP
364	depends on MACH_JZ4740
365	help
366	  Say yes here if you want support for the ADC unit in the JZ4740 SoC.
367	  This driver is necessary for jz4740-battery and jz4740-hwmon driver.
368
369config MFD_KEMPLD
370	tristate "Kontron module PLD device"
371	select MFD_CORE
372	help
373	  This is the core driver for the PLD (Programmable Logic Device) found
374	  on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
375	  device may provide functions like watchdog, GPIO, UART and I2C bus.
376
377	  The following modules are supported:
378		* COMe-bHL6
379		* COMe-bIP#
380		* COMe-bPC2 (ETXexpress-PC)
381		* COMe-bSC# (ETXexpress-SC T#)
382		* COMe-cBL6
383		* COMe-cBT6
384		* COMe-cCT6
385		* COMe-cDC2 (microETXexpress-DC)
386		* COMe-cHL6
387		* COMe-cPC2 (microETXexpress-PC)
388		* COMe-mBT10
389		* COMe-mCT10
390		* COMe-mTT10 (nanoETXexpress-TT)
391		* ETX-OH
392
393	  This driver can also be built as a module. If so, the module
394	  will be called kempld-core.
395
396config MFD_88PM800
397	tristate "Marvell 88PM800"
398	depends on I2C=y
399	select REGMAP_I2C
400	select REGMAP_IRQ
401	select MFD_CORE
402	help
403	  This supports for Marvell 88PM800 Power Management IC.
404	  This includes the I2C driver and the core APIs _only_, you have to
405	  select individual components like voltage regulators, RTC and
406	  battery-charger under the corresponding menus.
407
408config MFD_88PM805
409	tristate "Marvell 88PM805"
410	depends on I2C=y
411	select REGMAP_I2C
412	select REGMAP_IRQ
413	select MFD_CORE
414	help
415	  This supports for Marvell 88PM805 Power Management IC. This includes
416	  the I2C driver and the core APIs _only_, you have to select individual
417	  components like codec device, headset/Mic device under the
418	  corresponding menus.
419
420config MFD_88PM860X
421	bool "Marvell 88PM8606/88PM8607"
422	depends on I2C=y
423	select REGMAP_I2C
424	select MFD_CORE
425	help
426	  This supports for Marvell 88PM8606/88PM8607 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_MAX14577
432	bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
433	depends on I2C=y
434	select MFD_CORE
435	select REGMAP_I2C
436	select REGMAP_IRQ
437	select IRQ_DOMAIN
438	help
439	  Say yes here to add support for Maxim Semiconductor MAX14577 and
440	  MAX77836 Micro-USB ICs with battery charger.
441	  This driver provides common support for accessing the device;
442	  additional drivers must be enabled in order to use the functionality
443	  of the device.
444
445config MFD_MAX77686
446	bool "Maxim Semiconductor MAX77686/802 PMIC Support"
447	depends on I2C=y
448	depends on OF
449	select MFD_CORE
450	select REGMAP_I2C
451	select REGMAP_IRQ
452	select IRQ_DOMAIN
453	help
454	  Say yes here to add support for Maxim Semiconductor MAX77686 and
455	  MAX77802 which are Power Management IC with an RTC on chip.
456	  This driver provides common support for accessing the device;
457	  additional drivers must be enabled in order to use the functionality
458	  of the device.
459
460config MFD_MAX77693
461	bool "Maxim Semiconductor MAX77693 PMIC Support"
462	depends on I2C=y
463	select MFD_CORE
464	select REGMAP_I2C
465	select REGMAP_IRQ
466	help
467	  Say yes here to add support for Maxim Semiconductor MAX77693.
468	  This is a companion Power Management IC with Flash, Haptic, Charger,
469	  and MUIC(Micro USB Interface Controller) controls on chip.
470	  This driver provides common support for accessing the device;
471	  additional drivers must be enabled in order to use the functionality
472	  of the device.
473
474config MFD_MAX77843
475	bool "Maxim Semiconductor MAX77843 PMIC Support"
476	depends on I2C=y
477	select MFD_CORE
478	select REGMAP_I2C
479	select REGMAP_IRQ
480	help
481	  Say yes here to add support for Maxim Semiconductor MAX77843.
482	  This is companion Power Management IC with LEDs, Haptic, Charger,
483	  Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
484	  This driver provides common support for accessing the device;
485	  additional drivers must be enabled in order to use the functionality
486	  of the device.
487
488config MFD_MAX8907
489	tristate "Maxim Semiconductor MAX8907 PMIC Support"
490	select MFD_CORE
491	depends on I2C=y
492	select REGMAP_I2C
493	select REGMAP_IRQ
494	help
495	  Say yes here to add support for Maxim Semiconductor MAX8907. This is
496	  a Power Management IC. This driver provides common support for
497	  accessing the device; additional drivers must be enabled in order
498	  to use the functionality of the device.
499
500config MFD_MAX8925
501	bool "Maxim Semiconductor MAX8925 PMIC Support"
502	depends on I2C=y
503	select MFD_CORE
504	help
505	  Say yes here to add support for Maxim Semiconductor MAX8925. This is
506	  a Power Management IC. This driver provides common support for
507	  accessing the device, additional drivers must be enabled in order
508	  to use the functionality of the device.
509
510config MFD_MAX8997
511	bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
512	depends on I2C=y
513	select MFD_CORE
514	select IRQ_DOMAIN
515	help
516	  Say yes here to add support for Maxim Semiconductor MAX8997/8966.
517	  This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
518	  MUIC controls on chip.
519	  This driver provides common support for accessing the device;
520	  additional drivers must be enabled in order to use the functionality
521	  of the device.
522
523config MFD_MAX8998
524	bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
525	depends on I2C=y
526	select MFD_CORE
527	select IRQ_DOMAIN
528	help
529	  Say yes here to add support for Maxim Semiconductor MAX8998 and
530	  National Semiconductor LP3974. This is a Power Management IC.
531	  This driver provides common support for accessing the device,
532	  additional drivers must be enabled in order to use the functionality
533	  of the device.
534
535config MFD_MT6397
536	tristate "MediaTek MT6397 PMIC Support"
537	select MFD_CORE
538	select IRQ_DOMAIN
539	help
540	  Say yes here to add support for MediaTek MT6397 PMIC. This is
541	  a Power Management IC. This driver provides common support for
542	  accessing the device; additional drivers must be enabled in order
543	  to use the functionality of the device.
544
545config MFD_MENF21BMC
546	tristate "MEN 14F021P00 Board Management Controller Support"
547	depends on I2C
548	select MFD_CORE
549	help
550	  Say yes here to add support for the MEN 14F021P00 BMC
551	  which is a Board Management Controller connected to the I2C bus.
552	  The device supports multiple sub-devices like LED, HWMON and WDT.
553	  This driver provides common support for accessing the devices;
554	  additional drivers must be enabled in order to use the
555	  functionality of the BMC device.
556
557	  This driver can also be built as a module. If so the module
558	  will be called menf21bmc.
559
560config EZX_PCAP
561	bool "Motorola EZXPCAP Support"
562	depends on SPI_MASTER
563	help
564	  This enables the PCAP ASIC present on EZX Phones. This is
565	  needed for MMC, TouchScreen, Sound, USB, etc..
566
567config MFD_VIPERBOARD
568        tristate "Nano River Technologies Viperboard"
569	select MFD_CORE
570	depends on USB
571	default n
572	help
573	  Say yes here if you want support for Nano River Technologies
574	  Viperboard.
575	  There are mfd cell drivers available for i2c master, adc and
576	  both gpios found on the board. The spi part does not yet
577	  have a driver.
578	  You need to select the mfd cell drivers separately.
579	  The drivers do not support all features the board exposes.
580
581config MFD_RETU
582	tristate "Nokia Retu and Tahvo multi-function device"
583	select MFD_CORE
584	depends on I2C
585	select REGMAP_IRQ
586	help
587	  Retu and Tahvo are a multi-function devices found on Nokia
588	  Internet Tablets (770, N800 and N810).
589
590config MFD_PCF50633
591	tristate "NXP PCF50633"
592	depends on I2C
593	select REGMAP_I2C
594	help
595	  Say yes here if you have NXP PCF50633 chip on your board.
596	  This core driver provides register access and IRQ handling
597	  facilities, and registers devices for the various functions
598	  so that function-specific drivers can bind to them.
599
600config PCF50633_ADC
601	tristate "NXP PCF50633 ADC"
602	depends on MFD_PCF50633
603	help
604	 Say yes here if you want to include support for ADC in the
605	 NXP PCF50633 chip.
606
607config PCF50633_GPIO
608	tristate "NXP PCF50633 GPIO"
609	depends on MFD_PCF50633
610	help
611	 Say yes here if you want to include support GPIO for pins on
612	 the PCF50633 chip.
613
614config UCB1400_CORE
615	tristate "Philips UCB1400 Core driver"
616	depends on AC97_BUS
617	depends on GPIOLIB
618	help
619	  This enables support for the Philips UCB1400 core functions.
620	  The UCB1400 is an AC97 audio codec.
621
622	  To compile this driver as a module, choose M here: the
623	  module will be called ucb1400_core.
624
625config MFD_PM8XXX
626	tristate
627
628config MFD_PM8921_CORE
629	tristate "Qualcomm PM8921 PMIC chip"
630	depends on (ARM || HEXAGON)
631	select IRQ_DOMAIN
632	select MFD_CORE
633	select MFD_PM8XXX
634	select REGMAP
635	help
636	  If you say yes to this option, support will be included for the
637	  built-in PM8921 PMIC chip.
638
639	  This is required if your board has a PM8921 and uses its features,
640	  such as: MPPs, GPIOs, regulators, interrupts, and PWM.
641
642	  Say M here if you want to include support for PM8921 chip as a module.
643	  This will build a module called "pm8921-core".
644
645config MFD_QCOM_RPM
646	tristate "Qualcomm Resource Power Manager (RPM)"
647	depends on ARCH_QCOM && OF
648	help
649	  If you say yes to this option, support will be included for the
650	  Resource Power Manager system found in the Qualcomm 8660, 8960 and
651	  8064 based devices.
652
653	  This is required to access many regulators, clocks and bus
654	  frequencies controlled by the RPM on these devices.
655
656	  Say M here if you want to include support for the Qualcomm RPM as a
657	  module. This will build a module called "qcom_rpm".
658
659config MFD_SPMI_PMIC
660	tristate "Qualcomm SPMI PMICs"
661	depends on ARCH_QCOM || COMPILE_TEST
662	depends on OF
663	depends on SPMI
664	select REGMAP_SPMI
665	help
666	  This enables support for the Qualcomm SPMI PMICs.
667	  These PMICs are currently used with the Snapdragon 800 series of
668	  SoCs.  Note, that this will only be useful paired with descriptions
669	  of the independent functions as children nodes in the device tree.
670
671	  Say M here if you want to include support for the SPMI PMIC
672	  series as a module.  The module will be called "qcom-spmi-pmic".
673
674config MFD_RDC321X
675	tristate "RDC R-321x southbridge"
676	select MFD_CORE
677	depends on PCI
678	help
679	  Say yes here if you want to have support for the RDC R-321x SoC
680	  southbridge which provides access to GPIOs and Watchdog using the
681	  southbridge PCI device configuration space.
682
683config MFD_RTSX_PCI
684	tristate "Realtek PCI-E card reader"
685	depends on PCI
686	select MFD_CORE
687	help
688	  This supports for Realtek PCI-Express card reader including rts5209,
689	  rts5229, rtl8411, etc. Realtek card reader supports access to many
690	  types of memory cards, such as Memory Stick, Memory Stick Pro,
691	  Secure Digital and MultiMediaCard.
692
693config MFD_RT5033
694	tristate "Richtek RT5033 Power Management IC"
695	depends on I2C=y
696	select MFD_CORE
697	select REGMAP_I2C
698	select REGMAP_IRQ
699	help
700	  This driver provides for the Richtek RT5033 Power Management IC,
701	  which includes the I2C driver and the Core APIs. This driver provides
702	  common support for accessing the device. The device supports multiple
703	  sub-devices like charger, fuel gauge, flash LED, current source,
704	  LDO and Buck.
705
706config MFD_RTSX_USB
707	tristate "Realtek USB card reader"
708	depends on USB
709	select MFD_CORE
710	help
711	  Select this option to get support for Realtek USB 2.0 card readers
712	  including RTS5129, RTS5139, RTS5179 and RTS5170.
713	  Realtek card reader supports access to many types of memory cards,
714	  such as Memory Stick Pro, Secure Digital and MultiMediaCard.
715
716config MFD_RC5T583
717	bool "Ricoh RC5T583 Power Management system device"
718	depends on I2C=y
719	select MFD_CORE
720	select REGMAP_I2C
721	help
722	  Select this option to get support for the RICOH583 Power
723	  Management system device.
724	  This driver provides common support for accessing the device
725	  through i2c interface. The device supports multiple sub-devices
726	  like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
727	  Additional drivers must be enabled in order to use the
728	  different functionality of the device.
729
730config MFD_RK808
731	tristate "Rockchip RK808 Power Management chip"
732	depends on I2C && OF
733	select MFD_CORE
734	select REGMAP_I2C
735	select REGMAP_IRQ
736	help
737	  If you say yes here you get support for the RK808
738	  Power Management chips.
739	  This driver provides common support for accessing the device
740	  through I2C interface. The device supports multiple sub-devices
741	  including interrupts, RTC, LDO & DCDC regulators, and onkey.
742
743config MFD_RN5T618
744	tristate "Ricoh RN5T5618 PMIC"
745	depends on I2C
746	select MFD_CORE
747	select REGMAP_I2C
748	help
749	  Say yes here to add support for the Ricoh RN5T618 PMIC. This
750	  driver provides common support for accessing the device,
751	  additional drivers must be enabled in order to use the
752	  functionality of the device.
753
754config MFD_SEC_CORE
755	bool "SAMSUNG Electronics PMIC Series Support"
756	depends on I2C=y
757	select MFD_CORE
758	select REGMAP_I2C
759	select REGMAP_IRQ
760	help
761	 Support for the Samsung Electronics MFD series.
762	 This driver provides common support for accessing the device,
763	 additional drivers must be enabled in order to use the functionality
764	 of the device
765
766config MFD_SI476X_CORE
767	tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
768	depends on I2C
769	select MFD_CORE
770	select REGMAP_I2C
771	help
772	  This is the core driver for the SI476x series of AM/FM
773	  radio. This MFD driver connects the radio-si476x V4L2 module
774	  and the si476x audio codec.
775
776	  To compile this driver as a module, choose M here: the
777	  module will be called si476x-core.
778
779config MFD_SM501
780	tristate "Silicon Motion SM501"
781	 ---help---
782	  This is the core driver for the Silicon Motion SM501 multimedia
783	  companion chip. This device is a multifunction device which may
784	  provide numerous interfaces including USB host controller, USB gadget,
785	  asynchronous serial ports, audio functions, and a dual display video
786	  interface. The device may be connected by PCI or local bus with
787	  varying functions enabled.
788
789config MFD_SM501_GPIO
790	bool "Export GPIO via GPIO layer"
791	depends on MFD_SM501 && GPIOLIB
792	 ---help---
793	 This option uses the gpio library layer to export the 64 GPIO
794	 lines on the SM501. The platform data is used to supply the
795	 base number for the first GPIO line to register.
796
797config MFD_SKY81452
798	tristate "Skyworks Solutions SKY81452"
799	select MFD_CORE
800	select REGMAP_I2C
801	depends on I2C
802	help
803	  This is the core driver for the Skyworks SKY81452 backlight and
804	  voltage regulator device.
805
806	  This driver can also be built as a module.  If so, the module
807	  will be called sky81452.
808
809config MFD_SMSC
810       bool "SMSC ECE1099 series chips"
811       depends on I2C=y
812       select MFD_CORE
813       select REGMAP_I2C
814       help
815        If you say yes here you get support for the
816        ece1099 chips from SMSC.
817
818        To compile this driver as a module, choose M here: the
819        module will be called smsc.
820
821config ABX500_CORE
822	bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
823	default y if ARCH_U300 || ARCH_U8500
824	help
825	  Say yes here if you have the ABX500 Mixed Signal IC family
826	  chips. This core driver expose register access functions.
827	  Functionality specific drivers using these functions can
828	  remain unchanged when IC changes. Binding of the functions to
829	  actual register access is done by the IC core driver.
830
831config AB3100_CORE
832	bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
833	depends on I2C=y && ABX500_CORE
834	select MFD_CORE
835	default y if ARCH_U300
836	help
837	  Select this to enable the AB3100 Mixed Signal IC core
838	  functionality. This connects to a AB3100 on the I2C bus
839	  and expose a number of symbols needed for dependent devices
840	  to read and write registers and subscribe to events from
841	  this multi-functional IC. This is needed to use other features
842	  of the AB3100 such as battery-backed RTC, charging control,
843	  LEDs, vibrator, system power and temperature, power management
844	  and ALSA sound.
845
846config AB3100_OTP
847	tristate "ST-Ericsson AB3100 OTP functions"
848	depends on AB3100_CORE
849	default y if AB3100_CORE
850	help
851	  Select this to enable the AB3100 Mixed Signal IC OTP (one-time
852	  programmable memory) support. This exposes a sysfs file to read
853	  out OTP values.
854
855config AB8500_CORE
856	bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
857	depends on ABX500_CORE && MFD_DB8500_PRCMU
858	select POWER_SUPPLY
859	select MFD_CORE
860	select IRQ_DOMAIN
861	help
862	  Select this option to enable access to AB8500 power management
863	  chip. This connects to U8500 either on the SSP/SPI bus (deprecated
864	  since hardware version v1.0) or the I2C bus via PRCMU. It also adds
865	  the irq_chip parts for handling the Mixed Signal chip events.
866	  This chip embeds various other multimedia funtionalities as well.
867
868config AB8500_DEBUG
869       bool "Enable debug info via debugfs"
870       depends on AB8500_GPADC && DEBUG_FS
871       default y if DEBUG_FS
872       help
873         Select this option if you want debug information using the debug
874         filesystem, debugfs.
875
876config AB8500_GPADC
877	bool "ST-Ericsson AB8500 GPADC driver"
878	depends on AB8500_CORE && REGULATOR_AB8500
879	default y
880	help
881	  AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
882
883config MFD_DB8500_PRCMU
884	bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
885	depends on UX500_SOC_DB8500
886	select MFD_CORE
887	help
888	  Select this option to enable support for the DB8500 Power Reset
889	  and Control Management Unit. This is basically an autonomous
890	  system controller running an XP70 microprocessor, which is accessed
891	  through a register map.
892
893config MFD_STMPE
894	bool "STMicroelectronics STMPE"
895	depends on (I2C=y || SPI_MASTER=y)
896	depends on OF
897	select MFD_CORE
898	help
899	  Support for the STMPE family of I/O Expanders from
900	  STMicroelectronics.
901
902	  Currently supported devices are:
903
904		STMPE811: GPIO, Touchscreen
905		STMPE1601: GPIO, Keypad
906		STMPE1801: GPIO, Keypad
907		STMPE2401: GPIO, Keypad
908		STMPE2403: GPIO, Keypad
909
910	  This driver provides common support for accessing the device,
911	  additional drivers must be enabled in order to use the functionality
912	  of the device.  Currently available sub drivers are:
913
914		GPIO: stmpe-gpio
915		Keypad: stmpe-keypad
916		Touchscreen: stmpe-ts
917
918menu "STMicroelectronics STMPE Interface Drivers"
919depends on MFD_STMPE
920
921config STMPE_I2C
922	bool "STMicroelectronics STMPE I2C Interface"
923	depends on I2C=y
924	default y
925	help
926	  This is used to enable I2C interface of STMPE
927
928config STMPE_SPI
929	bool "STMicroelectronics STMPE SPI Interface"
930	depends on SPI_MASTER
931	help
932	  This is used to enable SPI interface of STMPE
933endmenu
934
935config MFD_STA2X11
936	bool "STMicroelectronics STA2X11"
937	depends on STA2X11
938	select MFD_CORE
939	select REGMAP_MMIO
940
941config MFD_SUN6I_PRCM
942	bool "Allwinner A31 PRCM controller"
943	depends on ARCH_SUNXI
944	select MFD_CORE
945	help
946	  Support for the PRCM (Power/Reset/Clock Management) unit available
947	  in A31 SoC.
948
949config MFD_SYSCON
950	bool "System Controller Register R/W Based on Regmap"
951	select REGMAP_MMIO
952	help
953	  Select this option to enable accessing system control registers
954	  via regmap.
955
956config MFD_DAVINCI_VOICECODEC
957	tristate
958	select MFD_CORE
959	select REGMAP_MMIO
960
961config MFD_TI_AM335X_TSCADC
962	tristate "TI ADC / Touch Screen chip support"
963	select MFD_CORE
964	select REGMAP
965	select REGMAP_MMIO
966	help
967	  If you say yes here you get support for Texas Instruments series
968	  of Touch Screen /ADC chips.
969	  To compile this driver as a module, choose M here: the
970	  module will be called ti_am335x_tscadc.
971
972config MFD_DM355EVM_MSP
973	bool "TI DaVinci DM355 EVM microcontroller"
974	depends on I2C=y && MACH_DAVINCI_DM355_EVM
975	help
976	  This driver supports the MSP430 microcontroller used on these
977	  boards.  MSP430 firmware manages resets and power sequencing,
978	  inputs from buttons and the IR remote, LEDs, an RTC, and more.
979
980config MFD_LP3943
981	tristate "TI/National Semiconductor LP3943 MFD Driver"
982	depends on I2C
983	select MFD_CORE
984	select REGMAP_I2C
985	help
986	  Support for the TI/National Semiconductor LP3943.
987	  This driver consists of GPIO and PWM drivers.
988	  With these functionalities, it can be used for LED string control or
989	  general usage such like a GPIO controller and a PWM controller.
990
991config MFD_LP8788
992	bool "TI LP8788 Power Management Unit Driver"
993	depends on I2C=y
994	select MFD_CORE
995	select REGMAP_I2C
996	select IRQ_DOMAIN
997	help
998	  TI LP8788 PMU supports regulators, battery charger, RTC,
999	  ADC, backlight driver and current sinks.
1000
1001config MFD_OMAP_USB_HOST
1002	bool "TI OMAP USBHS core and TLL driver"
1003	depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1004	default y
1005	help
1006	  This is the core driver for the OAMP EHCI and OHCI drivers.
1007	  This MFD driver does the required setup functionalities for
1008	  OMAP USB Host drivers.
1009
1010config MFD_PALMAS
1011	bool "TI Palmas series chips"
1012	select MFD_CORE
1013	select REGMAP_I2C
1014	select REGMAP_IRQ
1015	depends on I2C=y
1016	help
1017	  If you say yes here you get support for the Palmas
1018	  series of PMIC chips from Texas Instruments.
1019
1020config TPS6105X
1021	tristate "TI TPS61050/61052 Boost Converters"
1022	depends on I2C
1023	select REGULATOR
1024	select MFD_CORE
1025	select REGULATOR_FIXED_VOLTAGE
1026	help
1027	  This option enables a driver for the TP61050/TPS61052
1028	  high-power "white LED driver". This boost converter is
1029	  sometimes used for other things than white LEDs, and
1030	  also contains a GPIO pin.
1031
1032config TPS65010
1033	tristate "TI TPS6501x Power Management chips"
1034	depends on I2C && GPIOLIB
1035	default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1036	help
1037	  If you say yes here you get support for the TPS6501x series of
1038	  Power Management chips.  These include voltage regulators,
1039	  lithium ion/polymer battery charging, and other features that
1040	  are often used in portable devices like cell phones and cameras.
1041
1042	  This driver can also be built as a module.  If so, the module
1043	  will be called tps65010.
1044
1045config TPS6507X
1046	tristate "TI TPS6507x Power Management / Touch Screen chips"
1047	select MFD_CORE
1048	depends on I2C
1049	help
1050	  If you say yes here you get support for the TPS6507x series of
1051	  Power Management / Touch Screen chips.  These include voltage
1052	  regulators, lithium ion/polymer battery charging, touch screen
1053	  and other features that are often used in portable devices.
1054	  This driver can also be built as a module.  If so, the module
1055	  will be called tps6507x.
1056
1057config TPS65911_COMPARATOR
1058	tristate
1059
1060config MFD_TPS65090
1061	bool "TI TPS65090 Power Management chips"
1062	depends on I2C=y
1063	select MFD_CORE
1064	select REGMAP_I2C
1065	select REGMAP_IRQ
1066	help
1067	  If you say yes here you get support for the TPS65090 series of
1068	  Power Management chips.
1069	  This driver provides common support for accessing the device,
1070	  additional drivers must be enabled in order to use the
1071	  functionality of the device.
1072
1073config MFD_TPS65217
1074	tristate "TI TPS65217 Power Management / White LED chips"
1075	depends on I2C
1076	select MFD_CORE
1077	select REGMAP_I2C
1078	help
1079	  If you say yes here you get support for the TPS65217 series of
1080	  Power Management / White LED chips.
1081	  These include voltage regulators, lithium ion/polymer battery
1082	  charger, wled and other features that are often used in portable
1083	  devices.
1084
1085	  This driver can also be built as a module.  If so, the module
1086	  will be called tps65217.
1087
1088config MFD_TPS65218
1089	tristate "TI TPS65218 Power Management chips"
1090	depends on I2C
1091	select MFD_CORE
1092	select REGMAP_I2C
1093	select REGMAP_IRQ
1094	help
1095	  If you say yes here you get support for the TPS65218 series of
1096	  Power Management chips.
1097	  These include voltage regulators, gpio and other features
1098	  that are often used in portable devices. Only regulator
1099	  component is currently supported.
1100
1101	  This driver can also be built as a module.  If so, the module
1102	  will be called tps65218.
1103
1104config MFD_TPS6586X
1105	bool "TI TPS6586x Power Management chips"
1106	depends on I2C=y
1107	select MFD_CORE
1108	select REGMAP_I2C
1109	help
1110	  If you say yes here you get support for the TPS6586X series of
1111	  Power Management chips.
1112	  This driver provides common support for accessing the device,
1113	  additional drivers must be enabled in order to use the
1114	  functionality of the device.
1115
1116	  This driver can also be built as a module.  If so, the module
1117	  will be called tps6586x.
1118
1119config MFD_TPS65910
1120	bool "TI TPS65910 Power Management chip"
1121	depends on I2C=y
1122	depends on GPIOLIB || COMPILE_TEST
1123	select MFD_CORE
1124	select REGMAP_I2C
1125	select REGMAP_IRQ
1126	select IRQ_DOMAIN
1127	help
1128	  if you say yes here you get support for the TPS65910 series of
1129	  Power Management chips.
1130
1131config MFD_TPS65912
1132	bool "TI TPS65912 Power Management chip"
1133	depends on GPIOLIB
1134	select MFD_CORE
1135	help
1136	  If you say yes here you get support for the TPS65912 series of
1137	  PM chips.
1138
1139config MFD_TPS65912_I2C
1140	bool "TI TPS65912 Power Management chip with I2C"
1141	select MFD_CORE
1142	select MFD_TPS65912
1143	depends on I2C=y && GPIOLIB
1144	help
1145	  If you say yes here you get support for the TPS65912 series of
1146	  PM chips with I2C interface.
1147
1148config MFD_TPS65912_SPI
1149	bool "TI TPS65912 Power Management chip with SPI"
1150	select MFD_CORE
1151	select MFD_TPS65912
1152	depends on SPI_MASTER && GPIOLIB
1153	help
1154	  If you say yes here you get support for the TPS65912 series of
1155	  PM chips with SPI interface.
1156
1157config MFD_TPS80031
1158	bool "TI TPS80031/TPS80032 Power Management chips"
1159	depends on I2C=y
1160	select MFD_CORE
1161	select REGMAP_I2C
1162	select REGMAP_IRQ
1163	help
1164	  If you say yes here you get support for the Texas Instruments
1165	  TPS80031/ TPS80032 Fully Integrated Power Management with Power
1166	  Path and Battery Charger. The device provides five configurable
1167	  step-down converters, 11 general purpose LDOs, USB OTG Module,
1168	  ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1169	  Power Path from USB, 32K clock generator.
1170
1171config TWL4030_CORE
1172	bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1173	depends on I2C=y
1174	select IRQ_DOMAIN
1175	select REGMAP_I2C
1176	help
1177	  Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1178	  This core driver provides register access and IRQ handling
1179	  facilities, and registers devices for the various functions
1180	  so that function-specific drivers can bind to them.
1181
1182	  These multi-function chips are found on many OMAP2 and OMAP3
1183	  boards, providing power management, RTC, GPIO, keypad, a
1184	  high speed USB OTG transceiver, an audio codec (on most
1185	  versions) and many other features.
1186
1187config TWL4030_POWER
1188	bool "TI TWL4030 power resources"
1189	depends on TWL4030_CORE && ARM
1190	help
1191	  Say yes here if you want to use the power resources on the
1192	  TWL4030 family chips.  Most of these resources are regulators,
1193	  which have a separate driver; some are control signals, such
1194	  as clock request handshaking.
1195
1196	  This driver uses board-specific data to initialize the resources
1197	  and load scripts controlling which resources are switched off/on
1198	  or reset when a sleep, wakeup or warm reset event occurs.
1199
1200config MFD_TWL4030_AUDIO
1201	bool "TI TWL4030 Audio"
1202	depends on TWL4030_CORE
1203	select MFD_CORE
1204	default n
1205
1206config TWL6040_CORE
1207	bool "TI TWL6040 audio codec"
1208	depends on I2C=y
1209	select MFD_CORE
1210	select REGMAP_I2C
1211	select REGMAP_IRQ
1212	default n
1213	help
1214	  Say yes here if you want support for Texas Instruments TWL6040 audio
1215	  codec.
1216	  This driver provides common support for accessing the device,
1217	  additional drivers must be enabled in order to use the
1218	  functionality of the device (audio, vibra).
1219
1220config MENELAUS
1221	bool "TI TWL92330/Menelaus PM chip"
1222	depends on I2C=y && ARCH_OMAP2
1223	help
1224	  If you say yes here you get support for the Texas Instruments
1225	  TWL92330/Menelaus Power Management chip. This include voltage
1226	  regulators, Dual slot memory card transceivers, real-time clock
1227	  and other features that are often used in portable devices like
1228	  cell phones and PDAs.
1229
1230config MFD_WL1273_CORE
1231	tristate "TI WL1273 FM radio"
1232	depends on I2C
1233	select MFD_CORE
1234	default n
1235	help
1236	  This is the core driver for the TI WL1273 FM radio. This MFD
1237	  driver connects the radio-wl1273 V4L2 module and the wl1273
1238	  audio codec.
1239
1240config MFD_LM3533
1241	tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1242	depends on I2C
1243	select MFD_CORE
1244	select REGMAP_I2C
1245	help
1246	  Say yes here to enable support for National Semiconductor / TI
1247	  LM3533 Lighting Power chips.
1248
1249	  This driver provides common support for accessing the device;
1250	  additional drivers must be enabled in order to use the LED,
1251	  backlight or ambient-light-sensor functionality of the device.
1252
1253config MFD_TIMBERDALE
1254	tristate "Timberdale FPGA"
1255	select MFD_CORE
1256	depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1257	---help---
1258	This is the core driver for the timberdale FPGA. This device is a
1259	multifunction device which exposes numerous platform devices.
1260
1261	The timberdale FPGA can be found on the Intel Atom development board
1262	for in-vehicle infontainment, called Russellville.
1263
1264config MFD_TC3589X
1265	bool "Toshiba TC35892 and variants"
1266	depends on I2C=y
1267	depends on OF
1268	select MFD_CORE
1269	help
1270	  Support for the Toshiba TC35892 and variants I/O Expander.
1271
1272	  This driver provides common support for accessing the device,
1273	  additional drivers must be enabled in order to use the
1274	  functionality of the device.
1275
1276config MFD_TMIO
1277	bool
1278	default n
1279
1280config MFD_T7L66XB
1281	bool "Toshiba T7L66XB"
1282	depends on ARM && HAVE_CLK
1283	select MFD_CORE
1284	select MFD_TMIO
1285	help
1286	  Support for Toshiba Mobile IO Controller T7L66XB
1287
1288config MFD_TC6387XB
1289	bool "Toshiba TC6387XB"
1290	depends on ARM && HAVE_CLK
1291	select MFD_CORE
1292	select MFD_TMIO
1293	help
1294	  Support for Toshiba Mobile IO Controller TC6387XB
1295
1296config MFD_TC6393XB
1297	bool "Toshiba TC6393XB"
1298	depends on ARM && HAVE_CLK
1299	select GPIOLIB
1300	select MFD_CORE
1301	select MFD_TMIO
1302	help
1303	  Support for Toshiba Mobile IO Controller TC6393XB
1304
1305config MFD_VX855
1306	tristate "VIA VX855/VX875 integrated south bridge"
1307	depends on PCI
1308	select MFD_CORE
1309	help
1310	  Say yes here to enable support for various functions of the
1311	  VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1312	  and/or vx855_gpio drivers for this to do anything useful.
1313
1314config MFD_ARIZONA
1315	select REGMAP
1316	select REGMAP_IRQ
1317	select MFD_CORE
1318	bool
1319
1320config MFD_ARIZONA_I2C
1321	tristate "Wolfson Microelectronics Arizona platform with I2C"
1322	select MFD_ARIZONA
1323	select MFD_CORE
1324	select REGMAP_I2C
1325	depends on I2C
1326	help
1327	  Support for the Wolfson Microelectronics Arizona platform audio SoC
1328	  core functionality controlled via I2C.
1329
1330config MFD_ARIZONA_SPI
1331	tristate "Wolfson Microelectronics Arizona platform with SPI"
1332	select MFD_ARIZONA
1333	select MFD_CORE
1334	select REGMAP_SPI
1335	depends on SPI_MASTER
1336	help
1337	  Support for the Wolfson Microelectronics Arizona platform audio SoC
1338	  core functionality controlled via I2C.
1339
1340config MFD_WM5102
1341	bool "Wolfson Microelectronics WM5102"
1342	depends on MFD_ARIZONA
1343	help
1344	  Support for Wolfson Microelectronics WM5102 low power audio SoC
1345
1346config MFD_WM5110
1347	bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1348	depends on MFD_ARIZONA
1349	help
1350	  Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1351	  low power audio SoC
1352
1353config MFD_WM8997
1354	bool "Wolfson Microelectronics WM8997"
1355	depends on MFD_ARIZONA
1356	help
1357	  Support for Wolfson Microelectronics WM8997 low power audio SoC
1358
1359config MFD_WM8400
1360	bool "Wolfson Microelectronics WM8400"
1361	select MFD_CORE
1362	depends on I2C=y
1363	select REGMAP_I2C
1364	help
1365	  Support for the Wolfson Microelecronics WM8400 PMIC and audio
1366	  CODEC.  This driver provides common support for accessing
1367	  the device, additional drivers must be enabled in order to use
1368	  the functionality of the device.
1369
1370config MFD_WM831X
1371	bool
1372
1373config MFD_WM831X_I2C
1374	bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1375	select MFD_CORE
1376	select MFD_WM831X
1377	select REGMAP_I2C
1378	select IRQ_DOMAIN
1379	depends on I2C=y
1380	help
1381	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1382	  when controlled using I2C.  This driver provides common support
1383	  for accessing the device, additional drivers must be enabled in
1384	  order to use the functionality of the device.
1385
1386config MFD_WM831X_SPI
1387	bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1388	select MFD_CORE
1389	select MFD_WM831X
1390	select REGMAP_SPI
1391	select IRQ_DOMAIN
1392	depends on SPI_MASTER
1393	help
1394	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1395	  when controlled using SPI.  This driver provides common support
1396	  for accessing the device, additional drivers must be enabled in
1397	  order to use the functionality of the device.
1398
1399config MFD_WM8350
1400	bool
1401
1402config MFD_WM8350_I2C
1403	bool "Wolfson Microelectronics WM8350 with I2C"
1404	select MFD_WM8350
1405	depends on I2C=y
1406	help
1407	  The WM8350 is an integrated audio and power management
1408	  subsystem with watchdog and RTC functionality for embedded
1409	  systems.  This option enables core support for the WM8350 with
1410	  I2C as the control interface.  Additional options must be
1411	  selected to enable support for the functionality of the chip.
1412
1413config MFD_WM8994
1414	tristate "Wolfson Microelectronics WM8994"
1415	select MFD_CORE
1416	select REGMAP_I2C
1417	select REGMAP_IRQ
1418	depends on I2C
1419	help
1420	  The WM8994 is a highly integrated hi-fi CODEC designed for
1421	  smartphone applications.  As well as audio functionality it
1422	  has on board GPIO and regulator functionality which is
1423	  supported via the relevant subsystems.  This driver provides
1424	  core support for the WM8994, in order to use the actual
1425	  functionaltiy of the device other drivers must be enabled.
1426
1427config MFD_STW481X
1428	tristate "Support for ST Microelectronics STw481x"
1429	depends on I2C && ARCH_NOMADIK
1430	select REGMAP_I2C
1431	select MFD_CORE
1432	help
1433	  Select this option to enable the STw481x chip driver used
1434	  in various ST Microelectronics and ST-Ericsson embedded
1435	  Nomadik series.
1436
1437menu "Multimedia Capabilities Port drivers"
1438	depends on ARCH_SA1100
1439
1440config MCP
1441	tristate
1442
1443# Interface drivers
1444config MCP_SA11X0
1445	tristate "Support SA11x0 MCP interface"
1446	depends on ARCH_SA1100
1447	select MCP
1448
1449# Chip drivers
1450config MCP_UCB1200
1451	tristate "Support for UCB1200 / UCB1300"
1452	depends on MCP_SA11X0
1453	select MCP
1454
1455config MCP_UCB1200_TS
1456	tristate "Touchscreen interface support"
1457	depends on MCP_UCB1200 && INPUT
1458
1459endmenu
1460
1461config MFD_VEXPRESS_SYSREG
1462	bool "Versatile Express System Registers"
1463	depends on VEXPRESS_CONFIG && GPIOLIB
1464	default y
1465	select CLKSRC_MMIO
1466	select GPIO_GENERIC_PLATFORM
1467	select MFD_CORE
1468	select MFD_SYSCON
1469	help
1470	  System Registers are the platform configuration block
1471	  on the ARM Ltd. Versatile Express board.
1472
1473endmenu
1474endif
1475