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