xref: /linux/drivers/mfd/Kconfig (revision 5148fa52a12fa1b97c730b2fe321f2aad7ea041c)
1#
2# Multifunction miscellaneous devices
3#
4
5if HAS_IOMEM
6menu "Multifunction device drivers"
7
8config MFD_CORE
9	tristate
10	default n
11
12config MFD_88PM860X
13	bool "Support Marvell 88PM8606/88PM8607"
14	depends on I2C=y && GENERIC_HARDIRQS
15	select REGMAP_I2C
16	select MFD_CORE
17	help
18	  This supports for Marvell 88PM8606/88PM8607 Power Management IC.
19	  This includes the I2C driver and the core APIs _only_, you have to
20	  select individual components like voltage regulators, RTC and
21	  battery-charger under the corresponding menus.
22
23config MFD_SM501
24	tristate "Support for Silicon Motion SM501"
25	 ---help---
26	  This is the core driver for the Silicon Motion SM501 multimedia
27	  companion chip. This device is a multifunction device which may
28	  provide numerous interfaces including USB host controller, USB gadget,
29	  asynchronous serial ports, audio functions, and a dual display video
30	  interface. The device may be connected by PCI or local bus with
31	  varying functions enabled.
32
33config MFD_SM501_GPIO
34	bool "Export GPIO via GPIO layer"
35	depends on MFD_SM501 && GPIOLIB
36	 ---help---
37	 This option uses the gpio library layer to export the 64 GPIO
38	 lines on the SM501. The platform data is used to supply the
39	 base number for the first GPIO line to register.
40
41config MFD_ASIC3
42	bool "Support for Compaq ASIC3"
43	depends on GENERIC_HARDIRQS && GPIOLIB && ARM
44	select MFD_CORE
45	 ---help---
46	  This driver supports the ASIC3 multifunction chip found on many
47	  PDAs (mainly iPAQ and HTC based ones)
48
49config MFD_DAVINCI_VOICECODEC
50	tristate
51	select MFD_CORE
52
53config MFD_DM355EVM_MSP
54	bool "DaVinci DM355 EVM microcontroller"
55	depends on I2C=y && MACH_DAVINCI_DM355_EVM
56	help
57	  This driver supports the MSP430 microcontroller used on these
58	  boards.  MSP430 firmware manages resets and power sequencing,
59	  inputs from buttons and the IR remote, LEDs, an RTC, and more.
60
61config MFD_TI_SSP
62	tristate "TI Sequencer Serial Port support"
63	depends on ARCH_DAVINCI_TNETV107X
64	select MFD_CORE
65	---help---
66	  Say Y here if you want support for the Sequencer Serial Port
67	  in a Texas Instruments TNETV107X SoC.
68
69	  To compile this driver as a module, choose M here: the
70	  module will be called ti-ssp.
71
72config HTC_EGPIO
73	bool "HTC EGPIO support"
74	depends on GENERIC_HARDIRQS && GPIOLIB && ARM
75	help
76	    This driver supports the CPLD egpio chip present on
77	    several HTC phones.  It provides basic support for input
78	    pins, output pins, and irqs.
79
80config HTC_PASIC3
81	tristate "HTC PASIC3 LED/DS1WM chip support"
82	select MFD_CORE
83	help
84	  This core driver provides register access for the LED/DS1WM
85	  chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
86	  HTC Magician devices, respectively. Actual functionality is
87	  handled by the leds-pasic3 and ds1wm drivers.
88
89config HTC_I2CPLD
90	bool "HTC I2C PLD chip support"
91	depends on I2C=y && GPIOLIB
92	help
93	  If you say yes here you get support for the supposed CPLD
94	  found on omap850 HTC devices like the HTC Wizard and HTC Herald.
95	  This device provides input and output GPIOs through an I2C
96	  interface to one or more sub-chips.
97
98config UCB1400_CORE
99	tristate "Philips UCB1400 Core driver"
100	depends on AC97_BUS
101	depends on GPIOLIB
102	help
103	  This enables support for the Philips UCB1400 core functions.
104	  The UCB1400 is an AC97 audio codec.
105
106	  To compile this driver as a module, choose M here: the
107	  module will be called ucb1400_core.
108
109config TPS6105X
110	tristate "TPS61050/61052 Boost Converters"
111	depends on I2C
112	select REGULATOR
113	select MFD_CORE
114	select REGULATOR_FIXED_VOLTAGE
115	help
116	  This option enables a driver for the TP61050/TPS61052
117	  high-power "white LED driver". This boost converter is
118	  sometimes used for other things than white LEDs, and
119	  also contains a GPIO pin.
120
121config TPS65010
122	tristate "TPS6501x Power Management chips"
123	depends on I2C && GPIOLIB
124	default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
125	help
126	  If you say yes here you get support for the TPS6501x series of
127	  Power Management chips.  These include voltage regulators,
128	  lithium ion/polymer battery charging, and other features that
129	  are often used in portable devices like cell phones and cameras.
130
131	  This driver can also be built as a module.  If so, the module
132	  will be called tps65010.
133
134config TPS6507X
135	tristate "TPS6507x Power Management / Touch Screen chips"
136	select MFD_CORE
137	depends on I2C
138	help
139	  If you say yes here you get support for the TPS6507x series of
140	  Power Management / Touch Screen chips.  These include voltage
141	  regulators, lithium ion/polymer battery charging, touch screen
142	  and other features that are often used in portable devices.
143	  This driver can also be built as a module.  If so, the module
144	  will be called tps6507x.
145
146config MFD_TPS65217
147	tristate "TPS65217 Power Management / White LED chips"
148	depends on I2C
149	select MFD_CORE
150	select REGMAP_I2C
151	help
152	  If you say yes here you get support for the TPS65217 series of
153	  Power Management / White LED chips.
154	  These include voltage regulators, lithium ion/polymer battery
155	  charger, wled and other features that are often used in portable
156	  devices.
157
158	  This driver can also be built as a module.  If so, the module
159	  will be called tps65217.
160
161config MFD_TPS6586X
162	bool "TPS6586x Power Management chips"
163	depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
164	select MFD_CORE
165	depends on REGULATOR
166	help
167	  If you say yes here you get support for the TPS6586X series of
168	  Power Management chips.
169	  This driver provides common support for accessing the device,
170	  additional drivers must be enabled in order to use the
171	  functionality of the device.
172
173	  This driver can also be built as a module.  If so, the module
174	  will be called tps6586x.
175
176config MFD_TPS65910
177	bool "TPS65910 Power Management chip"
178	depends on I2C=y && GPIOLIB
179	select MFD_CORE
180	select GPIO_TPS65910
181	select REGMAP_I2C
182	help
183	  if you say yes here you get support for the TPS65910 series of
184	  Power Management chips.
185
186config MFD_TPS65912
187	bool
188	depends on GPIOLIB
189
190config MFD_TPS65912_I2C
191	bool "TPS65912 Power Management chip with I2C"
192	select MFD_CORE
193	select MFD_TPS65912
194	depends on I2C=y && GPIOLIB
195	help
196	  If you say yes here you get support for the TPS65912 series of
197	  PM chips with I2C interface.
198
199config MFD_TPS65912_SPI
200	bool "TPS65912 Power Management chip with SPI"
201	select MFD_CORE
202	select MFD_TPS65912
203	depends on SPI_MASTER && GPIOLIB
204	help
205	  If you say yes here you get support for the TPS65912 series of
206	  PM chips with SPI interface.
207
208config MENELAUS
209	bool "Texas Instruments TWL92330/Menelaus PM chip"
210	depends on I2C=y && ARCH_OMAP2
211	help
212	  If you say yes here you get support for the Texas Instruments
213	  TWL92330/Menelaus Power Management chip. This include voltage
214	  regulators, Dual slot memory card transceivers, real-time clock
215	  and other features that are often used in portable devices like
216	  cell phones and PDAs.
217
218config TWL4030_CORE
219	bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
220	depends on I2C=y && GENERIC_HARDIRQS
221	select IRQ_DOMAIN
222	help
223	  Say yes here if you have TWL4030 / TWL6030 family chip on your board.
224	  This core driver provides register access and IRQ handling
225	  facilities, and registers devices for the various functions
226	  so that function-specific drivers can bind to them.
227
228	  These multi-function chips are found on many OMAP2 and OMAP3
229	  boards, providing power management, RTC, GPIO, keypad, a
230	  high speed USB OTG transceiver, an audio codec (on most
231	  versions) and many other features.
232
233config TWL4030_MADC
234	tristate "Texas Instruments TWL4030 MADC"
235	depends on TWL4030_CORE
236	help
237	This driver provides support for triton TWL4030-MADC. The
238	driver supports both RT and SW conversion methods.
239
240	This driver can be built as a module. If so it will be
241	named twl4030-madc
242
243config TWL4030_POWER
244	bool "Support power resources on TWL4030 family chips"
245	depends on TWL4030_CORE && ARM
246	help
247	  Say yes here if you want to use the power resources on the
248	  TWL4030 family chips.  Most of these resources are regulators,
249	  which have a separate driver; some are control signals, such
250	  as clock request handshaking.
251
252	  This driver uses board-specific data to initialize the resources
253	  and load scripts controlling which resources are switched off/on
254	  or reset when a sleep, wakeup or warm reset event occurs.
255
256config MFD_TWL4030_AUDIO
257	bool
258	depends on TWL4030_CORE
259	select MFD_CORE
260	default n
261
262config TWL6030_PWM
263	tristate "TWL6030 PWM (Pulse Width Modulator) Support"
264	depends on TWL4030_CORE
265	select HAVE_PWM
266	default n
267	help
268	  Say yes here if you want support for TWL6030 PWM.
269	  This is used to control charging LED brightness.
270
271config TWL6040_CORE
272	bool "Support for TWL6040 audio codec"
273	depends on I2C=y && GENERIC_HARDIRQS
274	select MFD_CORE
275	select REGMAP_I2C
276	default n
277	help
278	  Say yes here if you want support for Texas Instruments TWL6040 audio
279	  codec.
280	  This driver provides common support for accessing the device,
281	  additional drivers must be enabled in order to use the
282	  functionality of the device (audio, vibra).
283
284config MFD_STMPE
285	bool "Support STMicroelectronics STMPE"
286	depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
287	select MFD_CORE
288	help
289	  Support for the STMPE family of I/O Expanders from
290	  STMicroelectronics.
291
292	  Currently supported devices are:
293
294		STMPE811: GPIO, Touchscreen
295		STMPE1601: GPIO, Keypad
296		STMPE2401: GPIO, Keypad
297		STMPE2403: GPIO, Keypad
298
299	  This driver provides common support for accessing the device,
300	  additional drivers must be enabled in order to use the functionality
301	  of the device.  Currently available sub drivers are:
302
303		GPIO: stmpe-gpio
304		Keypad: stmpe-keypad
305		Touchscreen: stmpe-ts
306
307menu "STMPE Interface Drivers"
308depends on MFD_STMPE
309
310config STMPE_I2C
311	bool "STMPE I2C Inteface"
312	depends on I2C=y
313	default y
314	help
315	  This is used to enable I2C interface of STMPE
316
317config STMPE_SPI
318	bool "STMPE SPI Inteface"
319	depends on SPI_MASTER
320	help
321	  This is used to enable SPI interface of STMPE
322endmenu
323
324config MFD_TC3589X
325	bool "Support Toshiba TC35892 and variants"
326	depends on I2C=y && GENERIC_HARDIRQS
327	select MFD_CORE
328	help
329	  Support for the Toshiba TC35892 and variants I/O Expander.
330
331	  This driver provides common support for accessing the device,
332	  additional drivers must be enabled in order to use the
333	  functionality of the device.
334
335config MFD_TMIO
336	bool
337	default n
338
339config MFD_T7L66XB
340	bool "Support Toshiba T7L66XB"
341	depends on ARM && HAVE_CLK
342	select MFD_CORE
343	select MFD_TMIO
344	help
345	  Support for Toshiba Mobile IO Controller T7L66XB
346
347config MFD_TC6387XB
348	bool "Support Toshiba TC6387XB"
349	depends on ARM && HAVE_CLK
350	select MFD_CORE
351	select MFD_TMIO
352	help
353	  Support for Toshiba Mobile IO Controller TC6387XB
354
355config MFD_TC6393XB
356	bool "Support Toshiba TC6393XB"
357	depends on GPIOLIB && ARM && HAVE_CLK
358	select MFD_CORE
359	select MFD_TMIO
360	help
361	  Support for Toshiba Mobile IO Controller TC6393XB
362
363config PMIC_DA903X
364	bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
365	depends on I2C=y
366	help
367	  Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
368	  ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
369	  usually found on PXA processors-based platforms. This includes
370	  the I2C driver and the core APIs _only_, you have to select
371	  individual components like LCD backlight, voltage regulators,
372	  LEDs and battery-charger under the corresponding menus.
373
374config PMIC_DA9052
375	bool
376	select MFD_CORE
377
378config MFD_DA9052_SPI
379	bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
380	select IRQ_DOMAIN
381	select REGMAP_SPI
382	select REGMAP_IRQ
383	select PMIC_DA9052
384	depends on SPI_MASTER=y
385	help
386	  Support for the Dialog Semiconductor DA9052 PMIC
387	  when controlled using SPI. This driver provides common support
388	  for accessing the device, additional drivers must be enabled in
389	  order to use the functionality of the device.
390
391config MFD_DA9052_I2C
392	bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
393	select IRQ_DOMAIN
394	select REGMAP_I2C
395	select REGMAP_IRQ
396	select PMIC_DA9052
397	depends on I2C=y
398	help
399	  Support for the Dialog Semiconductor DA9052 PMIC
400	  when controlled using I2C. This driver provides common support
401	  for accessing the device, additional drivers must be enabled in
402	  order to use the functionality of the device.
403
404config PMIC_ADP5520
405	bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
406	depends on I2C=y
407	help
408	  Say yes here to add support for Analog Devices AD5520 and ADP5501,
409	  Multifunction Power Management IC. This includes
410	  the I2C driver and the core APIs _only_, you have to select
411	  individual components like LCD backlight, LEDs, GPIOs and Kepad
412	  under the corresponding menus.
413
414config MFD_MAX8925
415	bool "Maxim Semiconductor MAX8925 PMIC Support"
416	depends on I2C=y && GENERIC_HARDIRQS
417	select MFD_CORE
418	help
419	  Say yes here to support for Maxim Semiconductor MAX8925. This is
420	  a Power Management IC. This driver provies common support for
421	  accessing the device, additional drivers must be enabled in order
422	  to use the functionality of the device.
423
424config MFD_MAX8997
425	bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
426	depends on I2C=y && GENERIC_HARDIRQS
427	select MFD_CORE
428	help
429	  Say yes here to support for Maxim Semiconductor MAX8997/8966.
430	  This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
431	  MUIC controls on chip.
432	  This driver provides common support for accessing the device;
433	  additional drivers must be enabled in order to use the functionality
434	  of the device.
435
436config MFD_MAX8998
437	bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
438	depends on I2C=y && GENERIC_HARDIRQS
439	select MFD_CORE
440	help
441	  Say yes here to support for Maxim Semiconductor MAX8998 and
442	  National Semiconductor LP3974. This is a Power Management IC.
443	  This driver provies common support for accessing the device,
444	  additional drivers must be enabled in order to use the functionality
445	  of the device.
446
447config MFD_S5M_CORE
448	bool "SAMSUNG S5M Series Support"
449	depends on I2C=y && GENERIC_HARDIRQS
450	select MFD_CORE
451	select REGMAP_I2C
452	help
453	 Support for the Samsung Electronics S5M MFD series.
454	 This driver provies common support for accessing the device,
455	 additional drivers must be enabled in order to use the functionality
456	 of the device
457
458config MFD_WM8400
459	tristate "Support Wolfson Microelectronics WM8400"
460	select MFD_CORE
461	depends on I2C
462	select REGMAP_I2C
463	help
464	  Support for the Wolfson Microelecronics WM8400 PMIC and audio
465	  CODEC.  This driver provides common support for accessing
466	  the device, additional drivers must be enabled in order to use
467	  the functionality of the device.
468
469config MFD_WM831X
470	bool
471	depends on GENERIC_HARDIRQS
472
473config MFD_WM831X_I2C
474	bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
475	select MFD_CORE
476	select MFD_WM831X
477	select REGMAP_I2C
478	depends on I2C=y && GENERIC_HARDIRQS
479	help
480	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
481	  when controlled using I2C.  This driver provides common support
482	  for accessing the device, additional drivers must be enabled in
483	  order to use the functionality of the device.
484
485config MFD_WM831X_SPI
486	bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
487	select MFD_CORE
488	select MFD_WM831X
489	select REGMAP_SPI
490	depends on SPI_MASTER && GENERIC_HARDIRQS
491	help
492	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
493	  when controlled using SPI.  This driver provides common support
494	  for accessing the device, additional drivers must be enabled in
495	  order to use the functionality of the device.
496
497config MFD_WM8350
498	bool
499	depends on GENERIC_HARDIRQS
500
501config MFD_WM8350_CONFIG_MODE_0
502	bool
503	depends on MFD_WM8350
504
505config MFD_WM8350_CONFIG_MODE_1
506	bool
507	depends on MFD_WM8350
508
509config MFD_WM8350_CONFIG_MODE_2
510	bool
511	depends on MFD_WM8350
512
513config MFD_WM8350_CONFIG_MODE_3
514	bool
515	depends on MFD_WM8350
516
517config MFD_WM8351_CONFIG_MODE_0
518	bool
519	depends on MFD_WM8350
520
521config MFD_WM8351_CONFIG_MODE_1
522	bool
523	depends on MFD_WM8350
524
525config MFD_WM8351_CONFIG_MODE_2
526	bool
527	depends on MFD_WM8350
528
529config MFD_WM8351_CONFIG_MODE_3
530	bool
531	depends on MFD_WM8350
532
533config MFD_WM8352_CONFIG_MODE_0
534	bool
535	depends on MFD_WM8350
536
537config MFD_WM8352_CONFIG_MODE_1
538	bool
539	depends on MFD_WM8350
540
541config MFD_WM8352_CONFIG_MODE_2
542	bool
543	depends on MFD_WM8350
544
545config MFD_WM8352_CONFIG_MODE_3
546	bool
547	depends on MFD_WM8350
548
549config MFD_WM8350_I2C
550	bool "Support Wolfson Microelectronics WM8350 with I2C"
551	select MFD_WM8350
552	depends on I2C=y && GENERIC_HARDIRQS
553	help
554	  The WM8350 is an integrated audio and power management
555	  subsystem with watchdog and RTC functionality for embedded
556	  systems.  This option enables core support for the WM8350 with
557	  I2C as the control interface.  Additional options must be
558	  selected to enable support for the functionality of the chip.
559
560config MFD_WM8994
561	bool "Support Wolfson Microelectronics WM8994"
562	select MFD_CORE
563	select REGMAP_I2C
564	select IRQ_DOMAIN
565	select REGMAP_IRQ
566	depends on I2C=y && GENERIC_HARDIRQS
567	help
568	  The WM8994 is a highly integrated hi-fi CODEC designed for
569	  smartphone applicatiosn.  As well as audio functionality it
570	  has on board GPIO and regulator functionality which is
571	  supported via the relevant subsystems.  This driver provides
572	  core support for the WM8994, in order to use the actual
573	  functionaltiy of the device other drivers must be enabled.
574
575config MFD_PCF50633
576	tristate "Support for NXP PCF50633"
577	depends on I2C
578	select REGMAP_I2C
579	help
580	  Say yes here if you have NXP PCF50633 chip on your board.
581	  This core driver provides register access and IRQ handling
582	  facilities, and registers devices for the various functions
583	  so that function-specific drivers can bind to them.
584
585config PCF50633_ADC
586	tristate "Support for NXP PCF50633 ADC"
587	depends on MFD_PCF50633
588	help
589	 Say yes here if you want to include support for ADC in the
590	 NXP PCF50633 chip.
591
592config PCF50633_GPIO
593	tristate "Support for NXP PCF50633 GPIO"
594	depends on MFD_PCF50633
595	help
596	 Say yes here if you want to include support GPIO for pins on
597	 the PCF50633 chip.
598
599config MFD_MC13783
600	tristate
601
602config MFD_MC13XXX
603	tristate "Support Freescale MC13783 and MC13892"
604	depends on SPI_MASTER
605	select MFD_CORE
606	select MFD_MC13783
607	help
608	  Support for the Freescale (Atlas) PMIC and audio CODECs
609	  MC13783 and MC13892.
610	  This driver provides common support for accessing  the device,
611	  additional drivers must be enabled in order to use the
612	  functionality of the device.
613
614config ABX500_CORE
615	bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
616	default y if ARCH_U300 || ARCH_U8500
617	help
618	  Say yes here if you have the ABX500 Mixed Signal IC family
619	  chips. This core driver expose register access functions.
620	  Functionality specific drivers using these functions can
621	  remain unchanged when IC changes. Binding of the functions to
622	  actual register access is done by the IC core driver.
623
624config AB3100_CORE
625	bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
626	depends on I2C=y && ABX500_CORE
627	select MFD_CORE
628	default y if ARCH_U300
629	help
630	  Select this to enable the AB3100 Mixed Signal IC core
631	  functionality. This connects to a AB3100 on the I2C bus
632	  and expose a number of symbols needed for dependent devices
633	  to read and write registers and subscribe to events from
634	  this multi-functional IC. This is needed to use other features
635	  of the AB3100 such as battery-backed RTC, charging control,
636	  LEDs, vibrator, system power and temperature, power management
637	  and ALSA sound.
638
639config AB3100_OTP
640	tristate "ST-Ericsson AB3100 OTP functions"
641	depends on AB3100_CORE
642	default y if AB3100_CORE
643	help
644	  Select this to enable the AB3100 Mixed Signal IC OTP (one-time
645	  programmable memory) support. This exposes a sysfs file to read
646	  out OTP values.
647
648config EZX_PCAP
649	bool "PCAP Support"
650	depends on GENERIC_HARDIRQS && SPI_MASTER
651	help
652	  This enables the PCAP ASIC present on EZX Phones. This is
653	  needed for MMC, TouchScreen, Sound, USB, etc..
654
655config AB8500_CORE
656	bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
657	depends on GENERIC_HARDIRQS && ABX500_CORE
658	select MFD_CORE
659	help
660	  Select this option to enable access to AB8500 power management
661	  chip. This connects to U8500 either on the SSP/SPI bus (deprecated
662	  since hardware version v1.0) or the I2C bus via PRCMU. It also adds
663	  the irq_chip parts for handling the Mixed Signal chip events.
664	  This chip embeds various other multimedia funtionalities as well.
665
666config AB8500_I2C_CORE
667	bool "AB8500 register access via PRCMU I2C"
668	depends on AB8500_CORE && MFD_DB8500_PRCMU
669	default y
670	help
671	  This enables register access to the AB8500 chip via PRCMU I2C.
672	  The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
673	  the I2C bus is connected to the Power Reset
674	  and Mangagement Unit, PRCMU.
675
676config AB8500_DEBUG
677       bool "Enable debug info via debugfs"
678       depends on AB8500_CORE && DEBUG_FS
679       default y if DEBUG_FS
680       help
681         Select this option if you want debug information using the debug
682         filesystem, debugfs.
683
684config AB8500_GPADC
685	bool "AB8500 GPADC driver"
686	depends on AB8500_CORE && REGULATOR_AB8500
687	default y
688	help
689	  AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
690
691config MFD_DB8500_PRCMU
692	bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
693	depends on UX500_SOC_DB8500
694	select MFD_CORE
695	help
696	  Select this option to enable support for the DB8500 Power Reset
697	  and Control Management Unit. This is basically an autonomous
698	  system controller running an XP70 microprocessor, which is accessed
699	  through a register map.
700
701config MFD_CS5535
702	tristate "Support for CS5535 and CS5536 southbridge core functions"
703	select MFD_CORE
704	depends on PCI && X86
705	---help---
706	  This is the core driver for CS5535/CS5536 MFD functions.  This is
707          necessary for using the board's GPIO and MFGPT functionality.
708
709config MFD_TIMBERDALE
710	tristate "Support for the Timberdale FPGA"
711	select MFD_CORE
712	depends on PCI && GPIOLIB
713	---help---
714	This is the core driver for the timberdale FPGA. This device is a
715	multifunction device which exposes numerous platform devices.
716
717	The timberdale FPGA can be found on the Intel Atom development board
718	for in-vehicle infontainment, called Russellville.
719
720config LPC_SCH
721	tristate "Intel SCH LPC"
722	depends on PCI
723	select MFD_CORE
724	help
725	  LPC bridge function of the Intel SCH provides support for
726	  System Management Bus and General Purpose I/O.
727
728config MFD_RDC321X
729	tristate "Support for RDC-R321x southbridge"
730	select MFD_CORE
731	depends on PCI
732	help
733	  Say yes here if you want to have support for the RDC R-321x SoC
734	  southbridge which provides access to GPIOs and Watchdog using the
735	  southbridge PCI device configuration space.
736
737config MFD_JANZ_CMODIO
738	tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
739	select MFD_CORE
740	depends on PCI
741	help
742	  This is the core driver for the Janz CMOD-IO PCI MODULbus
743	  carrier board. This device is a PCI to MODULbus bridge which may
744	  host many different types of MODULbus daughterboards, including
745	  CAN and GPIO controllers.
746
747config MFD_JZ4740_ADC
748	bool "Support for the JZ4740 SoC ADC core"
749	select MFD_CORE
750	select GENERIC_IRQ_CHIP
751	depends on MACH_JZ4740
752	help
753	  Say yes here if you want support for the ADC unit in the JZ4740 SoC.
754	  This driver is necessary for jz4740-battery and jz4740-hwmon driver.
755
756config MFD_VX855
757	tristate "Support for VIA VX855/VX875 integrated south bridge"
758	depends on PCI
759	select MFD_CORE
760	help
761	  Say yes here to enable support for various functions of the
762	  VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
763	  and/or vx855_gpio drivers for this to do anything useful.
764
765config MFD_WL1273_CORE
766	tristate "Support for TI WL1273 FM radio."
767	depends on I2C
768	select MFD_CORE
769	default n
770	help
771	  This is the core driver for the TI WL1273 FM radio. This MFD
772	  driver connects the radio-wl1273 V4L2 module and the wl1273
773	  audio codec.
774
775config MFD_OMAP_USB_HOST
776	bool "Support OMAP USBHS core driver"
777	depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
778	default y
779	help
780	  This is the core driver for the OAMP EHCI and OHCI drivers.
781	  This MFD driver does the required setup functionalities for
782	  OMAP USB Host drivers.
783
784config MFD_PM8XXX
785	tristate
786
787config MFD_PM8921_CORE
788	tristate "Qualcomm PM8921 PMIC chip"
789	depends on MSM_SSBI
790	select MFD_CORE
791	select MFD_PM8XXX
792	help
793	  If you say yes to this option, support will be included for the
794	  built-in PM8921 PMIC chip.
795
796	  This is required if your board has a PM8921 and uses its features,
797	  such as: MPPs, GPIOs, regulators, interrupts, and PWM.
798
799	  Say M here if you want to include support for PM8921 chip as a module.
800	  This will build a module called "pm8921-core".
801
802config MFD_PM8XXX_IRQ
803	bool "Support for Qualcomm PM8xxx IRQ features"
804	depends on MFD_PM8XXX
805	default y if MFD_PM8XXX
806	help
807	  This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
808
809	  This is required to use certain other PM 8xxx features, such as GPIO
810	  and MPP.
811
812config TPS65911_COMPARATOR
813	tristate
814
815config MFD_TPS65090
816	bool "TPS65090 Power Management chips"
817	depends on I2C=y && GENERIC_HARDIRQS
818	select MFD_CORE
819	select REGMAP_I2C
820	help
821	  If you say yes here you get support for the TPS65090 series of
822	  Power Management chips.
823	  This driver provides common support for accessing the device,
824	  additional drivers must be enabled in order to use the
825	  functionality of the device.
826
827config MFD_AAT2870_CORE
828	bool "Support for the AnalogicTech AAT2870"
829	select MFD_CORE
830	depends on I2C=y && GPIOLIB
831	help
832	  If you say yes here you get support for the AAT2870.
833	  This driver provides common support for accessing the device,
834	  additional drivers must be enabled in order to use the
835	  functionality of the device.
836
837config MFD_INTEL_MSIC
838	bool "Support for Intel MSIC"
839	depends on INTEL_SCU_IPC
840	select MFD_CORE
841	help
842	  Select this option to enable access to Intel MSIC (Avatele
843	  Passage) chip. This chip embeds audio, battery, GPIO, etc.
844	  devices used in Intel Medfield platforms.
845
846config MFD_RC5T583
847	bool "Ricoh RC5T583 Power Management system device"
848	depends on I2C=y && GENERIC_HARDIRQS
849	select MFD_CORE
850	select REGMAP_I2C
851	help
852	  Select this option to get support for the RICOH583 Power
853	  Management system device.
854	  This driver provides common support for accessing the device
855	  through i2c interface. The device supports multiple sub-devices
856	  like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
857	  Additional drivers must be enabled in order to use the
858	  different functionality of the device.
859
860config MFD_ANATOP
861	bool "Support for Freescale i.MX on-chip ANATOP controller"
862	depends on SOC_IMX6Q
863	help
864	  Select this option to enable Freescale i.MX on-chip ANATOP
865	  MFD controller. This controller embeds regulator and
866	  thermal devices for Freescale i.MX platforms.
867
868config MFD_PALMAS
869	bool "Support for the TI Palmas series chips"
870	select MFD_CORE
871	select REGMAP_I2C
872	select REGMAP_IRQ
873	depends on I2C=y
874	help
875	  If you say yes here you get support for the Palmas
876	  series of PMIC chips from Texas Instruments.
877
878endmenu
879endif
880
881menu "Multimedia Capabilities Port drivers"
882	depends on ARCH_SA1100
883
884config MCP
885	tristate
886
887# Interface drivers
888config MCP_SA11X0
889	tristate "Support SA11x0 MCP interface"
890	depends on ARCH_SA1100
891	select MCP
892
893# Chip drivers
894config MCP_UCB1200
895	bool "Support for UCB1200 / UCB1300"
896	depends on MCP_SA11X0
897	select MCP
898
899config MCP_UCB1200_TS
900	tristate "Touchscreen interface support"
901	depends on MCP_UCB1200 && INPUT
902
903endmenu
904