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