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	depends on I2C=y && GENERIC_HARDIRQS
 
 
408	help
409	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
410	  when controlled using I2C.  This driver provides common support
411	  for accessing the device, additional drivers must be enabled in
412	  order to use the functionality of the device.
413
414config MFD_WM831X_SPI
415	bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
416	select MFD_CORE
417	select MFD_WM831X
418	depends on SPI_MASTER && GENERIC_HARDIRQS
 
 
419	help
420	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
421	  when controlled using SPI.  This driver provides common support
422	  for accessing the device, additional drivers must be enabled in
423	  order to use the functionality of the device.
424
425config MFD_WM8350
426	bool
427	depends on GENERIC_HARDIRQS
428
429config MFD_WM8350_CONFIG_MODE_0
430	bool
431	depends on MFD_WM8350
432
433config MFD_WM8350_CONFIG_MODE_1
434	bool
435	depends on MFD_WM8350
436
437config MFD_WM8350_CONFIG_MODE_2
438	bool
439	depends on MFD_WM8350
440
441config MFD_WM8350_CONFIG_MODE_3
442	bool
443	depends on MFD_WM8350
444
445config MFD_WM8351_CONFIG_MODE_0
446	bool
447	depends on MFD_WM8350
448
449config MFD_WM8351_CONFIG_MODE_1
450	bool
451	depends on MFD_WM8350
452
453config MFD_WM8351_CONFIG_MODE_2
454	bool
455	depends on MFD_WM8350
456
457config MFD_WM8351_CONFIG_MODE_3
458	bool
459	depends on MFD_WM8350
460
461config MFD_WM8352_CONFIG_MODE_0
462	bool
463	depends on MFD_WM8350
464
465config MFD_WM8352_CONFIG_MODE_1
466	bool
467	depends on MFD_WM8350
468
469config MFD_WM8352_CONFIG_MODE_2
470	bool
471	depends on MFD_WM8350
472
473config MFD_WM8352_CONFIG_MODE_3
474	bool
475	depends on MFD_WM8350
476
477config MFD_WM8350_I2C
478	bool "Support Wolfson Microelectronics WM8350 with I2C"
479	select MFD_WM8350
480	depends on I2C=y && GENERIC_HARDIRQS
 
481	help
482	  The WM8350 is an integrated audio and power management
483	  subsystem with watchdog and RTC functionality for embedded
484	  systems.  This option enables core support for the WM8350 with
485	  I2C as the control interface.  Additional options must be
486	  selected to enable support for the functionality of the chip.
487
488config MFD_WM8994
489	bool "Support Wolfson Microelectronics WM8994"
490	select MFD_CORE
491	depends on I2C=y && GENERIC_HARDIRQS
 
 
492	help
493	  The WM8994 is a highly integrated hi-fi CODEC designed for
494	  smartphone applicatiosn.  As well as audio functionality it
495	  has on board GPIO and regulator functionality which is
496	  supported via the relevant subsystems.  This driver provides
497	  core support for the WM8994, in order to use the actual
498	  functionaltiy of the device other drivers must be enabled.
499
500config MFD_PCF50633
501	tristate "Support for NXP PCF50633"
502	depends on I2C
503	help
504	  Say yes here if you have NXP PCF50633 chip on your board.
505	  This core driver provides register access and IRQ handling
506	  facilities, and registers devices for the various functions
507	  so that function-specific drivers can bind to them.
508
509config PCF50633_ADC
510	tristate "Support for NXP PCF50633 ADC"
511	depends on MFD_PCF50633
512	help
513	 Say yes here if you want to include support for ADC in the
514	 NXP PCF50633 chip.
515
516config PCF50633_GPIO
517	tristate "Support for NXP PCF50633 GPIO"
518	depends on MFD_PCF50633
519	help
520	 Say yes here if you want to include support GPIO for pins on
521	 the PCF50633 chip.
522
523config MFD_MC13783
524	tristate
525
526config MFD_MC13XXX
527	tristate "Support Freescale MC13783 and MC13892"
528	depends on SPI_MASTER
529	select MFD_CORE
530	select MFD_MC13783
531	help
532	  Support for the Freescale (Atlas) PMIC and audio CODECs
533	  MC13783 and MC13892.
534	  This driver provides common support for accessing  the device,
535	  additional drivers must be enabled in order to use the
536	  functionality of the device.
537
538config ABX500_CORE
539	bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
540	default y if ARCH_U300 || ARCH_U8500
541	help
542	  Say yes here if you have the ABX500 Mixed Signal IC family
543	  chips. This core driver expose register access functions.
544	  Functionality specific drivers using these functions can
545	  remain unchanged when IC changes. Binding of the functions to
546	  actual register access is done by the IC core driver.
547
548config AB3100_CORE
549	bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
550	depends on I2C=y && ABX500_CORE
551	select MFD_CORE
552	default y if ARCH_U300
553	help
554	  Select this to enable the AB3100 Mixed Signal IC core
555	  functionality. This connects to a AB3100 on the I2C bus
556	  and expose a number of symbols needed for dependent devices
557	  to read and write registers and subscribe to events from
558	  this multi-functional IC. This is needed to use other features
559	  of the AB3100 such as battery-backed RTC, charging control,
560	  LEDs, vibrator, system power and temperature, power management
561	  and ALSA sound.
562
563config AB3100_OTP
564	tristate "ST-Ericsson AB3100 OTP functions"
565	depends on AB3100_CORE
566	default y if AB3100_CORE
567	help
568	  Select this to enable the AB3100 Mixed Signal IC OTP (one-time
569	  programmable memory) support. This exposes a sysfs file to read
570	  out OTP values.
571
572config EZX_PCAP
573	bool "PCAP Support"
574	depends on GENERIC_HARDIRQS && SPI_MASTER
575	help
576	  This enables the PCAP ASIC present on EZX Phones. This is
577	  needed for MMC, TouchScreen, Sound, USB, etc..
578
579config AB8500_CORE
580	bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
581	depends on GENERIC_HARDIRQS && ABX500_CORE
 
 
 
582	select MFD_CORE
583	help
584	  Select this option to enable access to AB8500 power management
585	  chip. This connects to U8500 either on the SSP/SPI bus (deprecated
586	  since hardware version v1.0) or the I2C bus via PRCMU. It also adds
587	  the irq_chip parts for handling the Mixed Signal chip events.
588	  This chip embeds various other multimedia funtionalities as well.
589
590config AB8500_I2C_CORE
591	bool "AB8500 register access via PRCMU I2C"
592	depends on AB8500_CORE && MFD_DB8500_PRCMU
593	default y
594	help
595	  This enables register access to the AB8500 chip via PRCMU I2C.
596	  The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
597	  the I2C bus is connected to the Power Reset
598	  and Mangagement Unit, PRCMU.
599
600config AB8500_DEBUG
601       bool "Enable debug info via debugfs"
602       depends on AB8500_CORE && DEBUG_FS
603       default y if DEBUG_FS
604       help
605         Select this option if you want debug information using the debug
606         filesystem, debugfs.
607
608config AB8500_GPADC
609	bool "AB8500 GPADC driver"
610	depends on AB8500_CORE && REGULATOR_AB8500
611	default y
612	help
613	  AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
 
 
614
615config AB3550_CORE
616        bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
 
 
 
 
617	select MFD_CORE
618	depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
619	help
620	  Select this to enable the AB3550 Mixed Signal IC core
621	  functionality. This connects to a AB3550 on the I2C bus
622	  and expose a number of symbols needed for dependent devices
623	  to read and write registers and subscribe to events from
624	  this multi-functional IC. This is needed to use other features
625	  of the AB3550 such as battery-backed RTC, charging control,
626	  LEDs, vibrator, system power and temperature, power management
627	  and ALSA sound.
628
629config MFD_DB8500_PRCMU
630	bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
631	depends on UX500_SOC_DB8500
 
 
632	select MFD_CORE
633	help
634	  Select this option to enable support for the DB8500 Power Reset
635	  and Control Management Unit. This is basically an autonomous
636	  system controller running an XP70 microprocessor, which is accessed
637	  through a register map.
638
639config MFD_DB5500_PRCMU
640	bool "ST-Ericsson DB5500 Power Reset Control Management Unit"
641	depends on UX500_SOC_DB5500
642	select MFD_CORE
 
 
643	help
644	  Select this option to enable support for the DB5500 Power Reset
645	  and Control Management Unit. This is basically an autonomous
646	  system controller running an XP70 microprocessor, which is accessed
647	  through a register map.
648
649config MFD_CS5535
650	tristate "Support for CS5535 and CS5536 southbridge core functions"
651	select MFD_CORE
652	depends on PCI && X86
653	---help---
654	  This is the core driver for CS5535/CS5536 MFD functions.  This is
655          necessary for using the board's GPIO and MFGPT functionality.
656
657config MFD_TIMBERDALE
658	tristate "Support for the Timberdale FPGA"
659	select MFD_CORE
660	depends on PCI && GPIOLIB
661	---help---
662	This is the core driver for the timberdale FPGA. This device is a
663	multifunction device which exposes numerous platform devices.
664
665	The timberdale FPGA can be found on the Intel Atom development board
666	for in-vehicle infontainment, called Russellville.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
667
668config LPC_SCH
669	tristate "Intel SCH LPC"
670	depends on PCI
671	select MFD_CORE
672	help
673	  LPC bridge function of the Intel SCH provides support for
674	  System Management Bus and General Purpose I/O.
675
676config MFD_RDC321X
677	tristate "Support for RDC-R321x southbridge"
 
 
678	select MFD_CORE
679	depends on PCI
680	help
681	  Say yes here if you want to have support for the RDC R-321x SoC
682	  southbridge which provides access to GPIOs and Watchdog using the
683	  southbridge PCI device configuration space.
684
685config MFD_JANZ_CMODIO
686	tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
687	select MFD_CORE
688	depends on PCI
689	help
690	  This is the core driver for the Janz CMOD-IO PCI MODULbus
691	  carrier board. This device is a PCI to MODULbus bridge which may
692	  host many different types of MODULbus daughterboards, including
693	  CAN and GPIO controllers.
694
695config MFD_JZ4740_ADC
696	bool "Support for the JZ4740 SoC ADC core"
 
 
 
 
697	select MFD_CORE
698	select GENERIC_IRQ_CHIP
699	depends on MACH_JZ4740
700	help
701	  Say yes here if you want support for the ADC unit in the JZ4740 SoC.
702	  This driver is necessary for jz4740-battery and jz4740-hwmon driver.
 
703
704config MFD_VX855
705	tristate "Support for VIA VX855/VX875 integrated south bridge"
706	depends on PCI
707	select MFD_CORE
708	help
709	  Say yes here to enable support for various functions of the
710	  VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
711	  and/or vx855_gpio drivers for this to do anything useful.
712
713config MFD_WL1273_CORE
714	tristate "Support for TI WL1273 FM radio."
 
 
715	depends on I2C
716	select MFD_CORE
717	default n
718	help
719	  This is the core driver for the TI WL1273 FM radio. This MFD
720	  driver connects the radio-wl1273 V4L2 module and the wl1273
721	  audio codec.
722
723config MFD_OMAP_USB_HOST
724	bool "Support OMAP USBHS core driver"
725	depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
726	default y
727	help
728	  This is the core driver for the OAMP EHCI and OHCI drivers.
729	  This MFD driver does the required setup functionalities for
730	  OMAP USB Host drivers.
731
732config MFD_PM8XXX
733	tristate
734
735config MFD_PM8921_CORE
736	tristate "Qualcomm PM8921 PMIC chip"
737	depends on MSM_SSBI
738	select MFD_CORE
739	select MFD_PM8XXX
740	help
741	  If you say yes to this option, support will be included for the
742	  built-in PM8921 PMIC chip.
743
744	  This is required if your board has a PM8921 and uses its features,
745	  such as: MPPs, GPIOs, regulators, interrupts, and PWM.
746
747	  Say M here if you want to include support for PM8921 chip as a module.
748	  This will build a module called "pm8921-core".
749
750config MFD_PM8XXX_IRQ
751	bool "Support for Qualcomm PM8xxx IRQ features"
752	depends on MFD_PM8XXX
753	default y if MFD_PM8XXX
754	help
755	  This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
756
757	  This is required to use certain other PM 8xxx features, such as GPIO
758	  and MPP.
 
759
760config TPS65911_COMPARATOR
761	tristate
 
762
763config MFD_AAT2870_CORE
764	bool "Support for the AnalogicTech AAT2870"
 
 
765	select MFD_CORE
766	depends on I2C=y && GPIOLIB
767	help
768	  If you say yes here you get support for the AAT2870.
769	  This driver provides common support for accessing the device,
770	  additional drivers must be enabled in order to use the
771	  functionality of the device.
772
773endif # MFD_SUPPORT
 
 
 
 
 
 
 
 
 
 
 
774
775menu "Multimedia Capabilities Port drivers"
776	depends on ARCH_SA1100
777
778config MCP
779	tristate
780
781# Interface drivers
782config MCP_SA11X0
783	tristate "Support SA11x0 MCP interface"
784	depends on ARCH_SA1100
785	select MCP
786
787# Chip drivers
788config MCP_UCB1200
789	tristate "Support for UCB1200 / UCB1300"
790	depends on MCP
 
791
792config MCP_UCB1200_TS
793	tristate "Touchscreen interface support"
794	depends on MCP_UCB1200 && INPUT
795
796endmenu

   1# SPDX-License-Identifier: GPL-2.0-only
   2#
   3# Multifunction miscellaneous devices
   4#
   5
   6if HAS_IOMEM
   7menu "Multifunction device drivers"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
   8
   9config MFD_CORE
  10	tristate
  11	select IRQ_DOMAIN
  12	default n
  13
  14config MFD_CS5535
  15	tristate "AMD CS5535 and CS5536 southbridge core functions"
 
  16	select MFD_CORE
  17	depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
  18	help
  19	  This is the core driver for CS5535/CS5536 MFD functions.  This is
  20	  necessary for using the board's GPIO and MFGPT functionality.
 
 
  21
  22config MFD_ALTERA_A10SR
  23	bool "Altera Arria10 DevKit System Resource chip"
  24	depends on ARCH_INTEL_SOCFPGA && SPI_MASTER=y && OF
  25	select REGMAP_SPI
  26	select MFD_CORE
  27	help
  28	  Support for the Altera Arria10 DevKit MAX5 System Resource chip
  29	  using the SPI interface. This driver provides common support for
  30	  accessing the external gpio extender (LEDs & buttons) and
  31	  power supply alarms (hwmon).
  32
  33config MFD_ALTERA_SYSMGR
  34	bool "Altera SOCFPGA System Manager"
  35	depends on ARCH_INTEL_SOCFPGA && OF
  36	select MFD_SYSCON
  37	help
  38	  Select this to get System Manager support for all Altera branded
  39	  SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by
  40	  using regmap_mmio accesses for ARM32 parts and SMC calls to
  41	  EL3 for ARM64 parts.
  42
  43config MFD_ACT8945A
  44	tristate "Active-semi ACT8945A"
  45	select MFD_CORE
  46	select REGMAP_I2C
  47	depends on I2C && OF
  48	help
  49	  Support for the ACT8945A PMIC from Active-semi. This device
  50	  features three step-down DC/DC converters and four low-dropout
  51	  linear regulators, along with a complete ActivePath battery
  52	  charger.
  53
  54config MFD_SUN4I_GPADC
  55	tristate "Allwinner sunxi platforms' GPADC MFD driver"
  56	select MFD_CORE
  57	select REGMAP_MMIO
  58	select REGMAP_IRQ
  59	depends on ARCH_SUNXI || COMPILE_TEST
  60	depends on !TOUCHSCREEN_SUN4I
  61	help
  62	  Select this to get support for Allwinner SoCs (A10, A13 and A31) ADC.
  63	  This driver will only map the hardware interrupt and registers, you
  64	  have to select individual drivers based on this MFD to be able to use
  65	  the ADC or the thermal sensor. This will try to probe the ADC driver
  66	  sun4i-gpadc-iio and the hwmon driver iio_hwmon.
  67
  68	  To compile this driver as a module, choose M here: the module will be
  69	  called sun4i-gpadc.
  70
  71config MFD_AS3711
  72	bool "AMS AS3711"
  73	select MFD_CORE
  74	select REGMAP_I2C
  75	select REGMAP_IRQ
  76	depends on I2C=y
  77	help
  78	  Support for the AS3711 PMIC from AMS
  79
  80config MFD_AS3722
  81	tristate "ams AS3722 Power Management IC"
  82	select MFD_CORE
  83	select REGMAP_I2C
  84	select REGMAP_IRQ
  85	depends on I2C=y && OF
  86	help
  87	  The ams AS3722 is a compact system PMU suitable for mobile phones,
  88	  tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
  89	  controllers, 11 LDOs, RTC, automatic battery, temperature and
  90	  over current monitoring, GPIOs, ADC and a watchdog.
  91
  92config PMIC_ADP5520
  93	bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  94	depends on I2C=y
  95	help
  96	  Say yes here to add support for Analog Devices AD5520 and ADP5501,
  97	  Multifunction Power Management IC. This includes
  98	  the I2C driver and the core APIs _only_, you have to select
  99	  individual components like LCD backlight, LEDs, GPIOs and Kepad
 100	  under the corresponding menus.
 101
 102config MFD_AAT2870_CORE
 103	bool "AnalogicTech AAT2870"
 104	select MFD_CORE
 105	depends on I2C=y
 106	depends on GPIOLIB || COMPILE_TEST
 107	help
 108	  If you say yes here you get support for the AAT2870.
 109	  This driver provides common support for accessing the device,
 110	  additional drivers must be enabled in order to use the
 111	  functionality of the device.
 112
 113config MFD_AT91_USART
 114	tristate "AT91 USART Driver"
 115	select MFD_CORE
 116	depends on ARCH_AT91 || COMPILE_TEST
 117	help
 118	  Select this to get support for AT91 USART IP. This is a wrapper
 119	  over at91-usart-serial driver and usart-spi-driver. Only one function
 120	  can be used at a time. The choice is done at boot time by the probe
 121	  function of this MFD driver according to a device tree property.
 122
 123config MFD_ATMEL_FLEXCOM
 124	tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
 125	select MFD_CORE
 126	depends on OF
 127	help
 128	  Select this to get support for Atmel Flexcom. This is a wrapper
 129	  which embeds a SPI controller, a I2C controller and a USART. Only
 130	  one function can be used at a time. The choice is done at boot time
 131	  by the probe function of this MFD driver according to a device tree
 132	  property.
 133
 134config MFD_ATMEL_HLCDC
 135	tristate "Atmel HLCDC (High-end LCD Controller)"
 136	select MFD_CORE
 137	select REGMAP_MMIO
 138	depends on OF
 139	help
 140	  If you say yes here you get support for the HLCDC block.
 141	  This driver provides common support for accessing the device,
 142	  additional drivers must be enabled in order to use the
 143	  functionality of the device.
 144
 145config MFD_ATMEL_SMC
 146	bool
 147	select MFD_SYSCON
 148
 149config MFD_BCM590XX
 150	tristate "Broadcom BCM590xx PMUs"
 151	select MFD_CORE
 152	select REGMAP_I2C
 153	depends on I2C
 154	help
 155	  Support for the BCM590xx PMUs from Broadcom
 156
 157config MFD_BD9571MWV
 158	tristate "ROHM BD9571MWV PMIC"
 159	select MFD_CORE
 160	select REGMAP_I2C
 161	select REGMAP_IRQ
 162	depends on I2C
 163	help
 164	  Support for the ROHM BD9571MWV PMIC, which contains single
 165	  voltage regulator, voltage sampling units, GPIO block and
 166	  watchdog block.
 167
 168	  This driver can also be built as a module. If so, the module
 169	  will be called bd9571mwv.
 170
 171config MFD_AC100
 172	tristate "X-Powers AC100"
 173	select MFD_CORE
 174	depends on SUNXI_RSB
 175	help
 176	  If you say Y here you get support for the X-Powers AC100 audio codec
 177	  IC.
 178	  This driver include only the core APIs. You have to select individual
 179	  components like codecs or RTC under the corresponding menus.
 180
 181config MFD_AXP20X
 182	tristate
 183	select MFD_CORE
 184	select REGMAP_IRQ
 185
 186config MFD_AXP20X_I2C
 187	tristate "X-Powers AXP series PMICs with I2C"
 188	select MFD_AXP20X
 189	select REGMAP_I2C
 190	depends on I2C
 191	help
 192	  If you say Y here you get support for the X-Powers AXP series power
 193	  management ICs (PMICs) controlled with I2C.
 194	  This driver include only the core APIs. You have to select individual
 195	  components like regulators or the PEK (Power Enable Key) under the
 196	  corresponding menus.
 197
 198	  Note on x86 this provides an ACPI OpRegion, so this must be 'y'
 199	  (builtin) and not a module, as the OpRegion must be available as
 200	  soon as possible. For the same reason the I2C bus driver options
 201	  I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too.
 202
 203config MFD_AXP20X_RSB
 204	tristate "X-Powers AXP series PMICs with RSB"
 205	select MFD_AXP20X
 206	depends on SUNXI_RSB
 207	help
 208	  If you say Y here you get support for the X-Powers AXP series power
 209	  management ICs (PMICs) controlled with RSB.
 210	  This driver include only the core APIs. You have to select individual
 211	  components like regulators or the PEK (Power Enable Key) under the
 212	  corresponding menus.
 213
 214config MFD_CROS_EC_DEV
 215	tristate "ChromeOS Embedded Controller multifunction device"
 216	select MFD_CORE
 217	depends on CROS_EC
 218	default CROS_EC
 219	help
 220	  Select this to get support for ChromeOS Embedded Controller
 221	  sub-devices. This driver will instantiate additional drivers such
 222	  as RTC, USBPD, etc. but you have to select the individual drivers.
 223
 224	  To compile this driver as a module, choose M here: the module will be
 225	  called cros-ec-dev.
 226
 227config MFD_MADERA
 228	tristate "Cirrus Logic Madera codecs"
 229	select MFD_CORE
 230	select REGMAP
 231	select REGMAP_IRQ
 232	select MADERA_IRQ
 233	select PINCTRL
 234	select PINCTRL_MADERA
 235	help
 236	  Support for the Cirrus Logic Madera platform audio codecs
 237
 238config MFD_MADERA_I2C
 239	tristate "Cirrus Logic Madera codecs with I2C"
 240	depends on MFD_MADERA
 241	depends on I2C
 242	select REGMAP_I2C
 243	help
 244	  Support for the Cirrus Logic Madera platform audio SoC
 245	  core functionality controlled via I2C.
 246
 247config MFD_MADERA_SPI
 248	tristate "Cirrus Logic Madera codecs with SPI"
 249	depends on MFD_MADERA
 250	depends on SPI_MASTER
 251	select REGMAP_SPI
 252	help
 253	  Support for the Cirrus Logic Madera platform audio SoC
 254	  core functionality controlled via SPI.
 255
 256config MFD_CS47L15
 257	bool "Cirrus Logic CS47L15"
 258	select PINCTRL_CS47L15
 259	depends on MFD_MADERA
 260	help
 261	  Support for Cirrus Logic CS47L15 Smart Codec
 262
 263config MFD_CS47L35
 264	bool "Cirrus Logic CS47L35"
 265	select PINCTRL_CS47L35
 266	depends on MFD_MADERA
 267	help
 268	  Support for Cirrus Logic CS47L35 Smart Codec
 269
 270config MFD_CS47L85
 271	bool "Cirrus Logic CS47L85"
 272	select PINCTRL_CS47L85
 273	depends on MFD_MADERA
 274	help
 275	  Support for Cirrus Logic CS47L85 Smart Codec
 276
 277config MFD_CS47L90
 278	bool "Cirrus Logic CS47L90/91"
 279	select PINCTRL_CS47L90
 280	depends on MFD_MADERA
 281	help
 282	  Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs
 283
 284config MFD_CS47L92
 285	bool "Cirrus Logic CS47L92/93"
 286	select PINCTRL_CS47L92
 287	depends on MFD_MADERA
 288	help
 289	  Support for Cirrus Logic CS42L92, CS47L92 and CS47L93 Smart Codecs
 290
 291config MFD_ASIC3
 292	bool "Compaq ASIC3"
 293	depends on GPIOLIB
 294	depends on ARM || COMPILE_TEST
 295	select MFD_CORE
 296	help
 297	  This driver supports the ASIC3 multifunction chip found on many
 298	  PDAs (mainly iPAQ and HTC based ones)
 299
 300config PMIC_DA903X
 301	bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
 302	depends on I2C=y
 303	help
 304	  Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
 305	  ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
 306	  usually found on PXA processors-based platforms. This includes
 307	  the I2C driver and the core APIs _only_, you have to select
 308	  individual components like LCD backlight, voltage regulators,
 309	  LEDs and battery-charger under the corresponding menus.
 310
 311config PMIC_DA9052
 312	bool
 313	select MFD_CORE
 314
 315config MFD_DA9052_SPI
 316	bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
 317	select REGMAP_SPI
 318	select REGMAP_IRQ
 319	select PMIC_DA9052
 320	depends on SPI_MASTER=y
 321	help
 322	  Support for the Dialog Semiconductor DA9052 PMIC
 323	  when controlled using SPI. This driver provides common support
 324	  for accessing the device, additional drivers must be enabled in
 325	  order to use the functionality of the device.
 326
 327config MFD_DA9052_I2C
 328	bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
 329	select REGMAP_I2C
 330	select REGMAP_IRQ
 331	select PMIC_DA9052
 332	depends on I2C=y
 333	help
 334	  Support for the Dialog Semiconductor DA9052 PMIC
 335	  when controlled using I2C. This driver provides common support
 336	  for accessing the device, additional drivers must be enabled in
 337	  order to use the functionality of the device.
 338
 339config MFD_DA9055
 340	bool "Dialog Semiconductor DA9055 PMIC Support"
 341	select REGMAP_I2C
 342	select REGMAP_IRQ
 343	select MFD_CORE
 344	depends on I2C=y
 345	help
 346	  Say yes here for support of Dialog Semiconductor DA9055. This is
 347	  a Power Management IC. This driver provides common support for
 348	  accessing the device as well as the I2C interface to the chip itself.
 349	  Additional drivers must be enabled in order to use the functionality
 350	  of the device.
 351
 352	  This driver can be built as a module. If built as a module it will be
 353	  called "da9055"
 354
 355config MFD_DA9062
 356	tristate "Dialog Semiconductor DA9062/61 PMIC Support"
 357	select MFD_CORE
 358	select REGMAP_I2C
 359	select REGMAP_IRQ
 360	depends on I2C
 361	help
 362	  Say yes here for support for the Dialog Semiconductor DA9061 and
 363	  DA9062 PMICs.
 364	  This includes the I2C driver and core APIs.
 365	  Additional drivers must be enabled in order to use the functionality
 366	  of the device.
 367
 368config MFD_DA9063
 369	tristate "Dialog Semiconductor DA9063 PMIC Support"
 370	select MFD_CORE
 371	select REGMAP_I2C
 372	select REGMAP_IRQ
 373	depends on I2C
 374	help
 375	  Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
 376	  This includes the I2C driver and core APIs.
 377	  Additional drivers must be enabled in order to use the functionality
 378	  of the device.
 379
 380config MFD_DA9150
 381	tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
 382	depends on I2C
 383	select MFD_CORE
 384	select REGMAP_I2C
 385	select REGMAP_IRQ
 386	help
 387	  This adds support for the DA9150 integrated charger and fuel-gauge
 388	  chip. This driver provides common support for accessing the device.
 389	  Additional drivers must be enabled in order to use the specific
 390	  features of the device.
 391
 392config MFD_DLN2
 393	tristate "Diolan DLN2 support"
 394	select MFD_CORE
 395	depends on USB
 396	help
 397	  This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
 398	  DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
 399	  etc. must be enabled in order to use the functionality of
 400	  the device.
 401
 402config MFD_ENE_KB3930
 403	tristate "ENE KB3930 Embedded Controller support"
 404	depends on I2C
 405	depends on MACH_MMP3_DT || COMPILE_TEST
 406	select MFD_CORE
 407	help
 408	  This adds support for the power-off functionality and access to
 409	  the registers that control LEDS and USB port power on ENE KB3930
 410	  Embedded Controller. To use the LED functionality LEDS_ARIEL must
 411	  be enabled.
 412
 413config MFD_EXYNOS_LPASS
 414	tristate "Samsung Exynos SoC Low Power Audio Subsystem"
 415	depends on ARCH_EXYNOS || COMPILE_TEST
 416	select MFD_CORE
 417	select REGMAP_MMIO
 418	help
 419	  Select this option to enable support for Samsung Exynos Low Power
 420	  Audio Subsystem.
 421
 422config MFD_GATEWORKS_GSC
 423	tristate "Gateworks System Controller"
 424	depends on (I2C && OF)
 425	select MFD_CORE
 426	select REGMAP_I2C
 427	select REGMAP_IRQ
 428	help
 429	  Enable support for the Gateworks System Controller (GSC) found
 430	  on Gateworks Single Board Computers supporting system functions
 431	  such as push-button monitor, multiple ADC's for voltage and
 432	  temperature monitoring, fan controller and watchdog monitor.
 433	  This driver provides common support for accessing the device.
 434	  Additional drivers must be enabled in order to use the
 435	  functionality of the device.
 436
 437config MFD_MC13XXX
 438	tristate
 439	depends on (SPI_MASTER || I2C)
 440	select MFD_CORE
 441	select REGMAP_IRQ
 442	help
 443	  Enable support for the Freescale MC13783 and MC13892 PMICs.
 444	  This driver provides common support for accessing the device,
 445	  additional drivers must be enabled in order to use the
 446	  functionality of the device.
 447
 448config MFD_MC13XXX_SPI
 449	tristate "Freescale MC13783 and MC13892 SPI interface"
 450	depends on SPI_MASTER
 451	select REGMAP_SPI
 452	select MFD_MC13XXX
 453	help
 454	  Select this if your MC13xxx is connected via an SPI bus.
 
 
 455
 456config MFD_MC13XXX_I2C
 457	tristate "Freescale MC13892 I2C interface"
 458	depends on I2C
 459	select REGMAP_I2C
 460	select MFD_MC13XXX
 461	help
 462	  Select this if your MC13xxx is connected via an I2C bus.
 463
 464config MFD_MP2629
 465	tristate "Monolithic Power Systems MP2629 ADC and Battery charger"
 466	depends on I2C
 467	select REGMAP_I2C
 468	select MFD_CORE
 469	help
 470	  Select this option to enable support for Monolithic Power Systems
 471	  battery charger. This provides ADC, thermal and battery charger power
 472	  management functions.
 473
 474config MFD_MXS_LRADC
 475	tristate "Freescale i.MX23/i.MX28 LRADC"
 476	depends on ARCH_MXS || COMPILE_TEST
 477	select MFD_CORE
 478	select STMP_DEVICE
 479	help
 480	  Say yes here to build support for the Low Resolution
 481	  Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
 482	  processors. This driver provides common support for accessing the
 483	  device, additional drivers must be enabled in order to use the
 484	  functionality of the device:
 485		mxs-lradc-adc for ADC readings
 486		mxs-lradc-ts  for touchscreen support
 487
 488	  This driver can also be built as a module. If so, the module will be
 489	  called mxs-lradc.
 490
 491config MFD_MX25_TSADC
 492	tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
 493	select REGMAP_MMIO
 494	depends on (SOC_IMX25 && OF) || COMPILE_TEST
 495	help
 496	  Enable support for the integrated Touchscreen and ADC unit of the
 497	  i.MX25 processors. They consist of a conversion queue for general
 498	  purpose ADC and a queue for Touchscreens.
 499
 500config MFD_HI6421_PMIC
 501	tristate "HiSilicon Hi6421 PMU/Codec IC"
 502	depends on OF
 503	select MFD_CORE
 504	select REGMAP_MMIO
 505	help
 506	  Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
 507	  functions, such as regulators, RTC, codec, Coulomb counter, etc.
 508	  This driver includes core APIs _only_. You have to select
 509	  individual components like voltage regulators under corresponding
 510	  menus in order to enable them.
 511	  We communicate with the Hi6421 via memory-mapped I/O.
 512
 513config MFD_HI655X_PMIC
 514	tristate "HiSilicon Hi655X series PMU/Codec IC"
 515	depends on ARCH_HISI || COMPILE_TEST
 516	depends on OF
 517	select MFD_CORE
 518	select REGMAP_MMIO
 519	select REGMAP_IRQ
 520	help
 521	  Select this option to enable Hisilicon hi655x series pmic driver.
 522
 523config HTC_PASIC3
 524	tristate "HTC PASIC3 LED/DS1WM chip support"
 525	select MFD_CORE
 526	help
 527	  This core driver provides register access for the LED/DS1WM
 528	  chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
 529	  HTC Magician devices, respectively. Actual functionality is
 530	  handled by the leds-pasic3 and ds1wm drivers.
 531
 532config HTC_I2CPLD
 533	bool "HTC I2C PLD chip support"
 534	depends on I2C=y && GPIOLIB
 535	help
 536	  If you say yes here you get support for the supposed CPLD
 537	  found on omap850 HTC devices like the HTC Wizard and HTC Herald.
 538	  This device provides input and output GPIOs through an I2C
 539	  interface to one or more sub-chips.
 540
 541config MFD_INTEL_QUARK_I2C_GPIO
 542	tristate "Intel Quark MFD I2C GPIO"
 543	depends on PCI
 544	depends on X86
 545	depends on COMMON_CLK
 546	select MFD_CORE
 547	help
 548	  This MFD provides support for I2C and GPIO that exist only
 549	  in a single PCI device. It splits the 2 IO devices to
 550	  their respective IO driver.
 551	  The GPIO exports a total amount of 8 interrupt-capable GPIOs.
 552
 553config LPC_ICH
 554	tristate "Intel ICH LPC"
 555	depends on PCI
 556	select MFD_CORE
 557	help
 558	  The LPC bridge function of the Intel ICH provides support for
 559	  many functional units. This driver provides needed support for
 560	  other drivers to control these functions, currently GPIO and
 561	  watchdog.
 562
 563config LPC_SCH
 564	tristate "Intel SCH LPC"
 565	depends on PCI
 566	select MFD_CORE
 567	help
 568	  LPC bridge function of the Intel SCH provides support for
 569	  System Management Bus and General Purpose I/O.
 570
 571config INTEL_SOC_PMIC
 572	bool "Support for Crystal Cove PMIC"
 573	depends on ACPI && HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
 574	depends on X86 || COMPILE_TEST
 575	depends on I2C_DESIGNWARE_PLATFORM=y
 576	select MFD_CORE
 577	select REGMAP_I2C
 578	select REGMAP_IRQ
 579	help
 580	  Select this option to enable support for Crystal Cove PMIC
 581	  on some Intel SoC systems. The PMIC provides ADC, GPIO,
 582	  thermal, charger and related power management functions
 583	  on these systems.
 584
 585	  This option is a bool as it provides an ACPI OpRegion which must be
 586	  available before any devices using it are probed. This option also
 587	  causes the designware-i2c driver to be builtin for the same reason.
 588
 589config INTEL_SOC_PMIC_BXTWC
 590	tristate "Support for Intel Broxton Whiskey Cove PMIC"
 591	depends on MFD_INTEL_PMC_BXT
 592	select MFD_CORE
 593	select REGMAP_IRQ
 594	help
 595	  Select this option to enable support for Whiskey Cove PMIC
 596	  on Intel Broxton systems. The PMIC provides ADC, GPIO,
 597	  thermal, charger and related power management functions
 598	  on these systems.
 599
 600config INTEL_SOC_PMIC_CHTWC
 601	bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
 602	depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
 603	depends on X86 || COMPILE_TEST
 604	depends on I2C_DESIGNWARE_PLATFORM=y
 605	select MFD_CORE
 606	select REGMAP_I2C
 607	select REGMAP_IRQ
 608	help
 609	  Select this option to enable support for the Intel Cherry Trail
 610	  Whiskey Cove PMIC found on some Intel Cherry Trail systems.
 611
 612	  This option is a bool as it provides an ACPI OpRegion which must be
 613	  available before any devices using it are probed. This option also
 614	  causes the designware-i2c driver to be builtin for the same reason.
 615
 616config INTEL_SOC_PMIC_CHTDC_TI
 617	tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC"
 618	depends on GPIOLIB
 619	depends on I2C
 620	depends on ACPI
 621	depends on X86
 622	select MFD_CORE
 623	select REGMAP_I2C
 624	select REGMAP_IRQ
 625	help
 626	  Select this option for supporting Dollar Cove (TI version) PMIC
 627	  device that is found on some Intel Cherry Trail systems.
 628
 629config INTEL_SOC_PMIC_MRFLD
 630	tristate "Support for Intel Merrifield Basin Cove PMIC"
 631	depends on GPIOLIB
 632	depends on ACPI
 633	depends on INTEL_SCU
 634	select MFD_CORE
 635	select REGMAP_IRQ
 636	help
 637	  Select this option for supporting Basin Cove PMIC device
 638	  that is found on Intel Merrifield systems.
 639
 640config MFD_INTEL_LPSS
 641	tristate
 642	select COMMON_CLK
 643	select MFD_CORE
 644
 645config MFD_INTEL_LPSS_ACPI
 646	tristate "Intel Low Power Subsystem support in ACPI mode"
 647	select MFD_INTEL_LPSS
 648	depends on X86 && ACPI
 649	help
 650	  This driver supports Intel Low Power Subsystem (LPSS) devices such as
 651	  I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
 652	  PCH) in ACPI mode.
 653
 654config MFD_INTEL_LPSS_PCI
 655	tristate "Intel Low Power Subsystem support in PCI mode"
 656	select MFD_INTEL_LPSS
 657	depends on X86 && PCI
 658	help
 659	  This driver supports Intel Low Power Subsystem (LPSS) devices such as
 660	  I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
 661	  PCH) in PCI mode.
 662
 663config MFD_INTEL_PMC_BXT
 664	tristate "Intel PMC Driver for Broxton"
 665	depends on X86
 666	depends on X86_PLATFORM_DEVICES
 667	depends on ACPI
 668	select INTEL_SCU_IPC
 669	select MFD_CORE
 670	help
 671	  This driver provides support for the PMC (Power Management
 672	  Controller) on Intel Broxton and Apollo Lake. The PMC is a
 673	  multi-function device that exposes IPC, General Control
 674	  Register and P-unit access. In addition this creates devices
 675	  for iTCO watchdog and telemetry that are part of the PMC.
 676
 677config MFD_INTEL_PMT
 678	tristate "Intel Platform Monitoring Technology (PMT) support"
 679	depends on PCI
 680	select MFD_CORE
 681	help
 682	  The Intel Platform Monitoring Technology (PMT) is an interface that
 683	  provides access to hardware monitor registers. This driver supports
 684	  Telemetry, Watcher, and Crashlog PMT capabilities/devices for
 685	  platforms starting from Tiger Lake.
 686
 687config MFD_IPAQ_MICRO
 688	bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
 689	depends on SA1100_H3100 || SA1100_H3600
 690	select MFD_CORE
 691	help
 692	  Select this to get support for the Microcontroller found in
 693	  the Compaq iPAQ handheld computers. This is an Atmel
 694	  AT90LS8535 microcontroller flashed with a special iPAQ
 695	  firmware using the custom protocol implemented in this driver.
 696
 697config MFD_IQS62X
 698	tristate "Azoteq IQS620A/621/622/624/625 core support"
 699	depends on I2C
 700	select MFD_CORE
 701	select REGMAP_I2C
 702	help
 703	  Say Y here if you want to build core support for the Azoteq IQS620A,
 704	  IQS621, IQS622, IQS624 and IQS625 multi-function sensors. Additional
 705	  options must be selected to enable device-specific functions.
 706
 707	  To compile this driver as a module, choose M here: the module will
 708	  be called iqs62x.
 709
 710config MFD_JANZ_CMODIO
 711	tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
 712	select MFD_CORE
 713	depends on PCI
 714	help
 715	  This is the core driver for the Janz CMOD-IO PCI MODULbus
 716	  carrier board. This device is a PCI to MODULbus bridge which may
 717	  host many different types of MODULbus daughterboards, including
 718	  CAN and GPIO controllers.
 719
 720config MFD_KEMPLD
 721	tristate "Kontron module PLD device"
 722	select MFD_CORE
 723	help
 724	  This is the core driver for the PLD (Programmable Logic Device) found
 725	  on some Kontron ETX and nearly all COMexpress (ETXexpress) modules as
 726	  well as on some other Kontron products. The PLD device may provide
 727	  functions like watchdog, GPIO, UART and I2C bus.
 728
 729	  This driver can also be built as a module. If so, the module
 730	  will be called kempld-core.
 731
 732config MFD_88PM800
 733	tristate "Marvell 88PM800"
 734	depends on I2C
 735	select REGMAP_I2C
 736	select REGMAP_IRQ
 737	select MFD_CORE
 738	help
 739	  This supports for Marvell 88PM800 Power Management IC.
 740	  This includes the I2C driver and the core APIs _only_, you have to
 741	  select individual components like voltage regulators, RTC and
 742	  battery-charger under the corresponding menus.
 743
 744config MFD_88PM805
 745	tristate "Marvell 88PM805"
 746	depends on I2C
 747	select REGMAP_I2C
 748	select REGMAP_IRQ
 749	select MFD_CORE
 750	help
 751	  This supports for Marvell 88PM805 Power Management IC. This includes
 752	  the I2C driver and the core APIs _only_, you have to select individual
 753	  components like codec device, headset/Mic device under the
 754	  corresponding menus.
 755
 756config MFD_88PM860X
 757	bool "Marvell 88PM8606/88PM8607"
 758	depends on I2C=y
 759	select REGMAP_I2C
 760	select MFD_CORE
 761	help
 762	  This supports for Marvell 88PM8606/88PM8607 Power Management IC.
 763	  This includes the I2C driver and the core APIs _only_, you have to
 764	  select individual components like voltage regulators, RTC and
 765	  battery-charger under the corresponding menus.
 766
 767config MFD_MAX14577
 768	tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
 769	depends on I2C
 770	select MFD_CORE
 771	select REGMAP_I2C
 772	select REGMAP_IRQ
 773	select IRQ_DOMAIN
 774	help
 775	  Say yes here to add support for Maxim Semiconductor MAX14577 and
 776	  MAX77836 Micro-USB ICs with battery charger.
 777	  This driver provides common support for accessing the device;
 778	  additional drivers must be enabled in order to use the functionality
 779	  of the device.
 780
 781config MFD_MAX77620
 782	bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
 783	depends on I2C=y
 784	depends on OF || COMPILE_TEST
 785	select MFD_CORE
 786	select REGMAP_I2C
 787	select REGMAP_IRQ
 788	select IRQ_DOMAIN
 789	help
 790	  Say yes here to add support for Maxim Semiconductor MAX77620 and
 791	  MAX20024 which are Power Management IC with General purpose pins,
 792	  RTC, regulators, clock generator, watchdog etc. This driver
 793	  provides common support for accessing the device; additional drivers
 794	  must be enabled in order to use the functionality of the device.
 795
 796config MFD_MAX77650
 797	tristate "Maxim MAX77650/77651 PMIC Support"
 798	depends on I2C
 799	depends on OF || COMPILE_TEST
 800	select MFD_CORE
 801	select REGMAP_I2C
 802	select REGMAP_IRQ
 803	help
 804	  Say Y here to add support for Maxim Semiconductor MAX77650 and
 805	  MAX77651 Power Management ICs. This is the core multifunction
 806	  driver for interacting with the device. The module name is
 807	  'max77650'. Additional drivers can be enabled in order to use
 808	  the following functionalities of the device: GPIO, regulator,
 809	  charger, LED, onkey.
 810
 811config MFD_MAX77686
 812	tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
 813	depends on I2C
 814	depends on OF || COMPILE_TEST
 815	select MFD_CORE
 816	select REGMAP_I2C
 817	select REGMAP_IRQ
 818	select IRQ_DOMAIN
 819	help
 820	  Say yes here to add support for Maxim Semiconductor MAX77686 and
 821	  MAX77802 which are Power Management IC with an RTC on chip.
 822	  This driver provides common support for accessing the device;
 823	  additional drivers must be enabled in order to use the functionality
 824	  of the device.
 825
 826config MFD_MAX77693
 827	tristate "Maxim Semiconductor MAX77693 PMIC Support"
 828	depends on I2C
 829	select MFD_CORE
 830	select REGMAP_I2C
 831	select REGMAP_IRQ
 832	help
 833	  Say yes here to add support for Maxim Semiconductor MAX77693.
 834	  This is a companion Power Management IC with Flash, Haptic, Charger,
 835	  and MUIC(Micro USB Interface Controller) controls on chip.
 836	  This driver provides common support for accessing the device;
 837	  additional drivers must be enabled in order to use the functionality
 838	  of the device.
 839
 840config MFD_MAX77843
 841	bool "Maxim Semiconductor MAX77843 PMIC Support"
 842	depends on I2C=y
 843	select MFD_CORE
 844	select REGMAP_I2C
 845	select REGMAP_IRQ
 846	help
 847	  Say yes here to add support for Maxim Semiconductor MAX77843.
 848	  This is companion Power Management IC with LEDs, Haptic, Charger,
 849	  Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
 850	  This driver provides common support for accessing the device;
 851	  additional drivers must be enabled in order to use the functionality
 852	  of the device.
 853
 854config MFD_MAX8907
 855	tristate "Maxim Semiconductor MAX8907 PMIC Support"
 856	select MFD_CORE
 857	depends on I2C
 858	select REGMAP_I2C
 859	select REGMAP_IRQ
 860	help
 861	  Say yes here to add support for Maxim Semiconductor MAX8907. This is
 862	  a Power Management IC. This driver provides common support for
 863	  accessing the device; additional drivers must be enabled in order
 864	  to use the functionality of the device.
 865
 866config MFD_MAX8925
 867	bool "Maxim Semiconductor MAX8925 PMIC Support"
 868	depends on I2C=y
 869	select MFD_CORE
 870	help
 871	  Say yes here to add support for Maxim Semiconductor MAX8925. This is
 872	  a Power Management IC. This driver provides common support for
 873	  accessing the device, additional drivers must be enabled in order
 874	  to use the functionality of the device.
 875
 876config MFD_MAX8997
 877	bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
 878	depends on I2C=y
 879	select MFD_CORE
 880	select IRQ_DOMAIN
 881	help
 882	  Say yes here to add support for Maxim Semiconductor MAX8997/8966.
 883	  This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
 884	  MUIC controls on chip.
 885	  This driver provides common support for accessing the device;
 886	  additional drivers must be enabled in order to use the functionality
 887	  of the device.
 888
 889config MFD_MAX8998
 890	bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
 891	depends on I2C=y
 892	select MFD_CORE
 893	select IRQ_DOMAIN
 894	help
 895	  Say yes here to add support for Maxim Semiconductor MAX8998 and
 896	  National Semiconductor LP3974. This is a Power Management IC.
 897	  This driver provides common support for accessing the device,
 898	  additional drivers must be enabled in order to use the functionality
 899	  of the device.
 900
 901config MFD_MT6360
 902	tristate "Mediatek MT6360 SubPMIC"
 903	select MFD_CORE
 904	select REGMAP_I2C
 905	select REGMAP_IRQ
 906	select CRC8
 907	depends on I2C
 908	help
 909	  Say Y here to enable MT6360 PMU/PMIC/LDO functional support.
 910	  PMU part includes Charger, Flashlight, RGB LED
 911	  PMIC part includes 2-channel BUCKs and 2-channel LDOs
 912	  LDO part includes 4-channel LDOs
 913
 914config MFD_MT6397
 915	tristate "MediaTek MT6397 PMIC Support"
 916	select MFD_CORE
 917	select IRQ_DOMAIN
 918	help
 919	  Say yes here to add support for MediaTek MT6397 PMIC. This is
 920	  a Power Management IC. This driver provides common support for
 921	  accessing the device; additional drivers must be enabled in order
 922	  to use the functionality of the device.
 923
 924config MFD_MENF21BMC
 925	tristate "MEN 14F021P00 Board Management Controller Support"
 926	depends on I2C
 927	select MFD_CORE
 928	help
 929	  Say yes here to add support for the MEN 14F021P00 BMC
 930	  which is a Board Management Controller connected to the I2C bus.
 931	  The device supports multiple sub-devices like LED, HWMON and WDT.
 932	  This driver provides common support for accessing the devices;
 933	  additional drivers must be enabled in order to use the
 934	  functionality of the BMC device.
 935
 936	  This driver can also be built as a module. If so the module
 937	  will be called menf21bmc.
 938
 939config EZX_PCAP
 940	bool "Motorola EZXPCAP Support"
 941	depends on SPI_MASTER
 942	help
 943	  This enables the PCAP ASIC present on EZX Phones. This is
 944	  needed for MMC, TouchScreen, Sound, USB, etc..
 945
 946config MFD_CPCAP
 947	tristate "Support for Motorola CPCAP"
 948	depends on SPI
 949	depends on OF || COMPILE_TEST
 950	select MFD_CORE
 951	select REGMAP_SPI
 952	select REGMAP_IRQ
 953	help
 954	  Say yes here if you want to include driver for CPCAP.
 955	  It is used on many Motorola phones and tablets as a PMIC.
 956	  At least Motorola Droid 4 is known to use CPCAP.
 957
 958config MFD_VIPERBOARD
 959	tristate "Nano River Technologies Viperboard"
 960	select MFD_CORE
 961	depends on USB
 962	default n
 963	help
 964	  Say yes here if you want support for Nano River Technologies
 965	  Viperboard.
 966	  There are mfd cell drivers available for i2c master, adc and
 967	  both gpios found on the board. The spi part does not yet
 968	  have a driver.
 969	  You need to select the mfd cell drivers separately.
 970	  The drivers do not support all features the board exposes.
 971
 972config MFD_NTXEC
 973	tristate "Netronix embedded controller (EC)"
 974	depends on OF || COMPILE_TEST
 975	depends on I2C
 976	select REGMAP_I2C
 977	select MFD_CORE
 978	help
 979	  Say yes here if you want to support the embedded controller found in
 980	  certain e-book readers designed by the original design manufacturer
 981	  Netronix.
 982
 983config MFD_RETU
 984	tristate "Nokia Retu and Tahvo multi-function device"
 985	select MFD_CORE
 986	depends on I2C
 987	select REGMAP_IRQ
 988	help
 989	  Retu and Tahvo are a multi-function devices found on Nokia
 990	  Internet Tablets (770, N800 and N810).
 991
 992config MFD_PCF50633
 993	tristate "NXP PCF50633"
 994	depends on I2C
 995	select REGMAP_I2C
 996	help
 997	  Say yes here if you have NXP PCF50633 chip on your board.
 998	  This core driver provides register access and IRQ handling
 999	  facilities, and registers devices for the various functions
1000	  so that function-specific drivers can bind to them.
1001
1002config PCF50633_ADC
1003	tristate "NXP PCF50633 ADC"
1004	depends on MFD_PCF50633
1005	help
1006	  Say yes here if you want to include support for ADC in the
1007	  NXP PCF50633 chip.
1008
1009config PCF50633_GPIO
1010	tristate "NXP PCF50633 GPIO"
1011	depends on MFD_PCF50633
1012	help
1013	  Say yes here if you want to include support GPIO for pins on
1014	  the PCF50633 chip.
1015
1016config UCB1400_CORE
1017	tristate "Philips UCB1400 Core driver"
1018	depends on AC97_BUS
1019	depends on GPIOLIB
1020	help
1021	  This enables support for the Philips UCB1400 core functions.
1022	  The UCB1400 is an AC97 audio codec.
1023
1024	  To compile this driver as a module, choose M here: the
1025	  module will be called ucb1400_core.
1026
1027config MFD_PM8XXX
1028	tristate "Qualcomm PM8xxx PMIC chips driver"
1029	depends on (ARM || HEXAGON || COMPILE_TEST)
1030	select IRQ_DOMAIN_HIERARCHY
1031	select MFD_CORE
1032	select REGMAP
1033	help
1034	  If you say yes to this option, support will be included for the
1035	  built-in PM8xxx PMIC chips.
1036
1037	  This is required if your board has a PM8xxx and uses its features,
1038	  such as: MPPs, GPIOs, regulators, interrupts, and PWM.
1039
1040	  Say M here if you want to include support for PM8xxx chips as a
1041	  module. This will build a module called "pm8xxx-core".
1042
1043config MFD_QCOM_RPM
1044	tristate "Qualcomm Resource Power Manager (RPM)"
1045	depends on ARCH_QCOM && OF
1046	help
1047	  If you say yes to this option, support will be included for the
1048	  Resource Power Manager system found in the Qualcomm 8660, 8960 and
1049	  8064 based devices.
1050
1051	  This is required to access many regulators, clocks and bus
1052	  frequencies controlled by the RPM on these devices.
1053
1054	  Say M here if you want to include support for the Qualcomm RPM as a
1055	  module. This will build a module called "qcom_rpm".
1056
1057config MFD_SPMI_PMIC
1058	tristate "Qualcomm SPMI PMICs"
1059	depends on ARCH_QCOM || COMPILE_TEST
1060	depends on OF
1061	depends on SPMI
1062	select REGMAP_SPMI
1063	help
1064	  This enables support for the Qualcomm SPMI PMICs.
1065	  These PMICs are currently used with the Snapdragon 800 series of
1066	  SoCs.  Note, that this will only be useful paired with descriptions
1067	  of the independent functions as children nodes in the device tree.
1068
1069	  Say M here if you want to include support for the SPMI PMIC
1070	  series as a module.  The module will be called "qcom-spmi-pmic".
1071
1072config MFD_RDC321X
1073	tristate "RDC R-321x southbridge"
1074	select MFD_CORE
1075	depends on PCI
1076	help
1077	  Say yes here if you want to have support for the RDC R-321x SoC
1078	  southbridge which provides access to GPIOs and Watchdog using the
1079	  southbridge PCI device configuration space.
1080
1081config MFD_RT4831
1082	tristate "Richtek RT4831 four channel WLED and Display Bias Voltage"
1083	depends on I2C
1084	select MFD_CORE
1085	select REGMAP_I2C
1086	help
1087	  This enables support for the Richtek RT4831 that includes 4 channel
1088	  WLED driving and Display Bias Voltage. It's commonly used to provide
1089	  power to the LCD display and LCD backlight.
1090
1091config MFD_RT5033
1092	tristate "Richtek RT5033 Power Management IC"
1093	depends on I2C
1094	select MFD_CORE
1095	select REGMAP_I2C
1096	select REGMAP_IRQ
1097	help
1098	  This driver provides for the Richtek RT5033 Power Management IC,
1099	  which includes the I2C driver and the Core APIs. This driver provides
1100	  common support for accessing the device. The device supports multiple
1101	  sub-devices like charger, fuel gauge, flash LED, current source,
1102	  LDO and Buck.
1103
1104config MFD_RC5T583
1105	bool "Ricoh RC5T583 Power Management system device"
1106	depends on I2C=y
1107	select MFD_CORE
1108	select REGMAP_I2C
1109	help
1110	  Select this option to get support for the RICOH583 Power
1111	  Management system device.
1112	  This driver provides common support for accessing the device
1113	  through i2c interface. The device supports multiple sub-devices
1114	  like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1115	  Additional drivers must be enabled in order to use the
1116	  different functionality of the device.
1117
1118config MFD_RK808
1119	tristate "Rockchip RK805/RK808/RK809/RK817/RK818 Power Management Chip"
1120	depends on I2C && OF
1121	select MFD_CORE
1122	select REGMAP_I2C
1123	select REGMAP_IRQ
1124	help
1125	  If you say yes here you get support for the RK805, RK808, RK809,
1126	  RK817 and RK818 Power Management chips.
1127	  This driver provides common support for accessing the device
1128	  through I2C interface. The device supports multiple sub-devices
1129	  including interrupts, RTC, LDO & DCDC regulators, and onkey.
1130
1131config MFD_RN5T618
1132	tristate "Ricoh RN5T567/618 PMIC"
1133	depends on I2C
1134	depends on OF
1135	select MFD_CORE
1136	select REGMAP_I2C
1137	select REGMAP_IRQ
1138	help
1139	  Say yes here to add support for the Ricoh RN5T567,
1140	  RN5T618, RC5T619 PMIC.
1141	  This driver provides common support for accessing the device,
1142	  additional drivers must be enabled in order to use the
1143	  functionality of the device.
1144
1145config MFD_SEC_CORE
1146	tristate "Samsung Electronics PMIC Series Support"
1147	depends on I2C=y
1148	depends on OF || COMPILE_TEST
1149	select MFD_CORE
1150	select REGMAP_I2C
1151	select REGMAP_IRQ
1152	help
1153	  Support for the Samsung Electronics PMIC devices coming
1154	  usually along with Samsung Exynos SoC chipset.
1155	  This driver provides common support for accessing the device,
1156	  additional drivers must be enabled in order to use the functionality
1157	  of the device
1158
1159	  To compile this driver as a module, choose M here: the
1160	  module will be called sec-core.
1161	  Have in mind that important core drivers (like regulators) depend
1162	  on this driver so building this as a module might require proper
1163	  initial ramdisk or might not boot up as well in certain scenarios.
1164
1165config MFD_SI476X_CORE
1166	tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1167	depends on I2C
1168	select MFD_CORE
1169	select REGMAP_I2C
1170	help
1171	  This is the core driver for the SI476x series of AM/FM
1172	  radio. This MFD driver connects the radio-si476x V4L2 module
1173	  and the si476x audio codec.
1174
1175	  To compile this driver as a module, choose M here: the
1176	  module will be called si476x-core.
1177
1178config MFD_SIMPLE_MFD_I2C
1179	tristate
1180	depends on I2C
1181	select REGMAP_I2C
1182	help
1183	  This driver creates a single register map with the intention for it
1184	  to be shared by all sub-devices.
1185
1186	  Once the register map has been successfully initialised, any
1187	  sub-devices represented by child nodes in Device Tree will be
1188	  subsequently registered.
1189
1190config MFD_SL28CPLD
1191	tristate "Kontron sl28cpld Board Management Controller"
1192	depends on I2C
1193	depends on ARCH_LAYERSCAPE || COMPILE_TEST
1194	select MFD_SIMPLE_MFD_I2C
1195	help
1196	  Say yes here to enable support for the Kontron sl28cpld board
1197	  management controller.
1198
1199	  It can be found on the following boards:
1200		* SMARC-sAL28
1201
1202config MFD_SM501
1203	tristate "Silicon Motion SM501"
1204	depends on HAS_DMA
1205	help
1206	  This is the core driver for the Silicon Motion SM501 multimedia
1207	  companion chip. This device is a multifunction device which may
1208	  provide numerous interfaces including USB host controller, USB gadget,
1209	  asynchronous serial ports, audio functions, and a dual display video
1210	  interface. The device may be connected by PCI or local bus with
1211	  varying functions enabled.
1212
1213config MFD_SM501_GPIO
1214	bool "Export GPIO via GPIO layer"
1215	depends on MFD_SM501 && GPIOLIB
1216	help
1217	  This option uses the gpio library layer to export the 64 GPIO
1218	  lines on the SM501. The platform data is used to supply the
1219	  base number for the first GPIO line to register.
1220
1221config MFD_SKY81452
1222	tristate "Skyworks Solutions SKY81452"
1223	select MFD_CORE
1224	select REGMAP_I2C
1225	depends on I2C
1226	help
1227	  This is the core driver for the Skyworks SKY81452 backlight and
1228	  voltage regulator device.
1229
1230	  This driver can also be built as a module.  If so, the module
1231	  will be called sky81452.
1232
1233config MFD_SC27XX_PMIC
1234	tristate "Spreadtrum SC27xx PMICs"
1235	depends on ARCH_SPRD || COMPILE_TEST
1236	depends on SPI_MASTER
1237	select MFD_CORE
1238	select REGMAP_SPI
1239	select REGMAP_IRQ
1240	help
1241	  This enables support for the Spreadtrum SC27xx PMICs with SPI
1242	  interface. The SC27xx series PMICs integrate power management,
1243	  audio codec, battery management and user interface support
1244	  function (such as RTC, Typec, indicator and so on) in a single chip.
1245
1246	  This driver provides common support for accessing the SC27xx PMICs,
1247	  and it also adds the irq_chip parts for handling the PMIC chip events.
1248
1249config ABX500_CORE
1250	bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1251	depends on ARCH_U8500 || COMPILE_TEST
1252	default y if ARCH_U8500
1253	help
1254	  Say yes here if you have the ABX500 Mixed Signal IC family
1255	  chips. This core driver expose register access functions.
1256	  Functionality specific drivers using these functions can
1257	  remain unchanged when IC changes. Binding of the functions to
1258	  actual register access is done by the IC core driver.
1259
1260config AB8500_CORE
1261	bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1262	depends on ABX500_CORE && MFD_DB8500_PRCMU
1263	select POWER_SUPPLY
1264	select MFD_CORE
1265	select IRQ_DOMAIN
1266	help
1267	  Select this option to enable access to AB8500 power management
1268	  chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1269	  since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1270	  the irq_chip parts for handling the Mixed Signal chip events.
1271	  This chip embeds various other multimedia functionalities as well.
1272
1273config AB8500_DEBUG
1274	bool "Enable debug info via debugfs"
1275	depends on AB8500_GPADC && DEBUG_FS
1276	default y if DEBUG_FS
1277	help
1278	  Select this option if you want debug information using the debug
1279	  filesystem, debugfs.
1280
1281config MFD_DB8500_PRCMU
1282	bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1283	depends on UX500_SOC_DB8500
1284	select MFD_CORE
1285	help
1286	  Select this option to enable support for the DB8500 Power Reset
1287	  and Control Management Unit. This is basically an autonomous
1288	  system controller running an XP70 microprocessor, which is accessed
1289	  through a register map.
1290
1291config MFD_STMPE
1292	bool "STMicroelectronics STMPE"
1293	depends on (I2C=y || SPI_MASTER=y)
1294	depends on OF
1295	select MFD_CORE
1296	help
1297	  Support for the STMPE family of I/O Expanders from
1298	  STMicroelectronics.
1299
1300	  Currently supported devices are:
1301
1302		STMPE811: GPIO, Touchscreen, ADC
1303		STMPE1601: GPIO, Keypad
1304		STMPE1801: GPIO, Keypad
1305		STMPE2401: GPIO, Keypad
1306		STMPE2403: GPIO, Keypad
1307
1308	  This driver provides common support for accessing the device,
1309	  additional drivers must be enabled in order to use the functionality
1310	  of the device.  Currently available sub drivers are:
1311
1312		GPIO: stmpe-gpio
1313		Keypad: stmpe-keypad
1314		Touchscreen: stmpe-ts
1315		ADC: stmpe-adc
1316
1317menu "STMicroelectronics STMPE Interface Drivers"
1318depends on MFD_STMPE
1319
1320config STMPE_I2C
1321	bool "STMicroelectronics STMPE I2C Interface"
1322	depends on I2C=y
1323	default y
1324	help
1325	  This is used to enable I2C interface of STMPE
1326
1327config STMPE_SPI
1328	bool "STMicroelectronics STMPE SPI Interface"
1329	depends on SPI_MASTER
1330	help
1331	  This is used to enable SPI interface of STMPE
1332endmenu
1333
1334config MFD_STA2X11
1335	bool "STMicroelectronics STA2X11"
1336	depends on STA2X11
1337	select MFD_CORE
1338	select REGMAP_MMIO
1339
1340config MFD_SUN6I_PRCM
1341	bool "Allwinner A31 PRCM controller"
1342	depends on ARCH_SUNXI || COMPILE_TEST
1343	select MFD_CORE
1344	help
1345	  Support for the PRCM (Power/Reset/Clock Management) unit available
1346	  in A31 SoC.
1347
1348config MFD_SYSCON
1349	bool "System Controller Register R/W Based on Regmap"
1350	select REGMAP_MMIO
1351	help
1352	  Select this option to enable accessing system control registers
1353	  via regmap.
1354
1355config MFD_DAVINCI_VOICECODEC
1356	tristate
1357	select MFD_CORE
1358	select REGMAP_MMIO
1359
1360config MFD_TI_AM335X_TSCADC
1361	tristate "TI ADC / Touch Screen chip support"
1362	select MFD_CORE
1363	select REGMAP
1364	select REGMAP_MMIO
1365	help
1366	  If you say yes here you get support for Texas Instruments series
1367	  of Touch Screen /ADC chips.
1368	  To compile this driver as a module, choose M here: the
1369	  module will be called ti_am335x_tscadc.
1370
1371config MFD_DM355EVM_MSP
1372	bool "TI DaVinci DM355 EVM microcontroller"
1373	depends on I2C=y && MACH_DAVINCI_DM355_EVM
1374	help
1375	  This driver supports the MSP430 microcontroller used on these
1376	  boards.  MSP430 firmware manages resets and power sequencing,
1377	  inputs from buttons and the IR remote, LEDs, an RTC, and more.
1378
1379config MFD_LP3943
1380	tristate "TI/National Semiconductor LP3943 MFD Driver"
1381	depends on I2C
1382	select MFD_CORE
1383	select REGMAP_I2C
1384	help
1385	  Support for the TI/National Semiconductor LP3943.
1386	  This driver consists of GPIO and PWM drivers.
1387	  With these functionalities, it can be used for LED string control or
1388	  general usage such like a GPIO controller and a PWM controller.
1389
1390config MFD_LP8788
1391	bool "TI LP8788 Power Management Unit Driver"
1392	depends on I2C=y
1393	select MFD_CORE
1394	select REGMAP_I2C
1395	select IRQ_DOMAIN
1396	help
1397	  TI LP8788 PMU supports regulators, battery charger, RTC,
1398	  ADC, backlight driver and current sinks.
1399
1400config MFD_TI_LMU
1401	tristate "TI Lighting Management Unit driver"
1402	depends on I2C
1403	select MFD_CORE
1404	select REGMAP_I2C
1405	help
1406	  Say yes here to enable support for TI LMU chips.
1407	  TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and
1408	  LM36274.  It consists of backlight, LED and regulator driver.
1409	  It provides consistent device controls for lighting functions.
1410
1411config MFD_OMAP_USB_HOST
1412	bool "TI OMAP USBHS core and TLL driver"
1413	depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1414	depends on COMMON_CLK
1415	default y
1416	help
1417	  This is the core driver for the OAMP EHCI and OHCI drivers.
1418	  This MFD driver does the required setup functionalities for
1419	  OMAP USB Host drivers.
1420
1421config MFD_PALMAS
1422	bool "TI Palmas series chips"
1423	select MFD_CORE
1424	select REGMAP_I2C
1425	select REGMAP_IRQ
1426	depends on I2C=y
1427	help
1428	  If you say yes here you get support for the Palmas
1429	  series of PMIC chips from Texas Instruments.
1430
1431config TPS6105X
1432	tristate "TI TPS61050/61052 Boost Converters"
1433	depends on I2C
1434	select REGMAP_I2C
1435	select REGULATOR
1436	select MFD_CORE
1437	select REGULATOR_FIXED_VOLTAGE
1438	help
1439	  This option enables a driver for the TP61050/TPS61052
1440	  high-power "white LED driver". This boost converter is
1441	  sometimes used for other things than white LEDs, and
1442	  also contains a GPIO pin.
1443
1444config TPS65010
1445	tristate "TI TPS6501x Power Management chips"
1446	depends on I2C && GPIOLIB
1447	default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1448	help
1449	  If you say yes here you get support for the TPS6501x series of
1450	  Power Management chips.  These include voltage regulators,
1451	  lithium ion/polymer battery charging, and other features that
1452	  are often used in portable devices like cell phones and cameras.
1453
1454	  This driver can also be built as a module.  If so, the module
1455	  will be called tps65010.
1456
1457config TPS6507X
1458	tristate "TI TPS6507x Power Management / Touch Screen chips"
1459	select MFD_CORE
1460	depends on I2C
1461	help
1462	  If you say yes here you get support for the TPS6507x series of
1463	  Power Management / Touch Screen chips.  These include voltage
1464	  regulators, lithium ion/polymer battery charging, touch screen
1465	  and other features that are often used in portable devices.
1466	  This driver can also be built as a module.  If so, the module
1467	  will be called tps6507x.
1468
1469config MFD_TPS65086
1470	tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1471	select MFD_CORE
1472	select REGMAP
1473	select REGMAP_IRQ
1474	select REGMAP_I2C
1475	depends on I2C
1476	help
1477	  If you say yes here you get support for the TPS65086 series of
1478	  Power Management chips.
1479	  This driver provides common support for accessing the device,
1480	  additional drivers must be enabled in order to use the
1481	  functionality of the device.
1482
1483config TPS65911_COMPARATOR
1484	tristate
1485
1486config MFD_TPS65090
1487	bool "TI TPS65090 Power Management chips"
1488	depends on I2C=y
1489	select MFD_CORE
1490	select REGMAP_I2C
1491	select REGMAP_IRQ
1492	help
1493	  If you say yes here you get support for the TPS65090 series of
1494	  Power Management chips.
1495	  This driver provides common support for accessing the device,
1496	  additional drivers must be enabled in order to use the
1497	  functionality of the device.
1498
1499config MFD_TPS65217
1500	tristate "TI TPS65217 Power Management / White LED chips"
1501	depends on I2C && OF
1502	select MFD_CORE
1503	select REGMAP_I2C
1504	select IRQ_DOMAIN
1505	help
1506	  If you say yes here you get support for the TPS65217 series of
1507	  Power Management / White LED chips.
1508	  These include voltage regulators, lithium ion/polymer battery
1509	  charger, wled and other features that are often used in portable
1510	  devices.
1511
1512	  This driver can also be built as a module.  If so, the module
1513	  will be called tps65217.
1514
1515config MFD_TI_LP873X
1516	tristate "TI LP873X Power Management IC"
1517	depends on I2C
1518	select MFD_CORE
1519	select REGMAP_I2C
1520	help
1521	  If you say yes here then you get support for the LP873X series of
1522	  Power Management Integrated Circuits (PMIC).
1523	  These include voltage regulators, thermal protection, configurable
1524	  General Purpose Outputs (GPO) that are used in portable devices.
1525
1526	  This driver can also be built as a module. If so, the module
1527	  will be called lp873x.
1528
1529config MFD_TI_LP87565
1530	tristate "TI LP87565 Power Management IC"
1531	depends on I2C && OF
1532	select MFD_CORE
1533	select REGMAP_I2C
1534	help
1535	  If you say yes here then you get support for the LP87565 series of
1536	  Power Management Integrated Circuits (PMIC).
1537	  These include voltage regulators, thermal protection, configurable
1538	  General Purpose Outputs (GPO) that are used in portable devices.
1539
1540	  This driver can also be built as a module. If so, the module
1541	  will be called lp87565.
1542
1543config MFD_TPS65218
1544	tristate "TI TPS65218 Power Management chips"
1545	depends on I2C && OF
1546	select MFD_CORE
1547	select REGMAP_I2C
1548	select REGMAP_IRQ
1549	help
1550	  If you say yes here you get support for the TPS65218 series of
1551	  Power Management chips.
1552	  These include voltage regulators, gpio and other features
1553	  that are often used in portable devices.
1554
1555	  This driver can also be built as a module.  If so, the module
1556	  will be called tps65218.
1557
1558config MFD_TPS6586X
1559	bool "TI TPS6586x Power Management chips"
1560	depends on I2C=y
1561	select MFD_CORE
1562	select REGMAP_I2C
1563	help
1564	  If you say yes here you get support for the TPS6586X series of
1565	  Power Management chips.
1566	  This driver provides common support for accessing the device,
1567	  additional drivers must be enabled in order to use the
1568	  functionality of the device.
1569
1570	  This driver can also be built as a module.  If so, the module
1571	  will be called tps6586x.
1572
1573config MFD_TPS65910
1574	bool "TI TPS65910 Power Management chip"
1575	depends on I2C=y
1576	depends on GPIOLIB || COMPILE_TEST
1577	select MFD_CORE
1578	select REGMAP_I2C
1579	select REGMAP_IRQ
1580	select IRQ_DOMAIN
1581	help
1582	  if you say yes here you get support for the TPS65910 series of
1583	  Power Management chips.
1584
1585config MFD_TPS65912
1586	tristate
1587	select MFD_CORE
1588	select REGMAP
1589	select REGMAP_IRQ
1590
1591config MFD_TPS65912_I2C
1592	tristate "TI TPS65912 Power Management chip with I2C"
 
1593	select MFD_TPS65912
1594	select REGMAP_I2C
1595	depends on I2C
1596	help
1597	  If you say yes here you get support for the TPS65912 series of
1598	  PM chips with I2C interface.
1599
1600config MFD_TPS65912_SPI
1601	tristate "TI TPS65912 Power Management chip with SPI"
 
1602	select MFD_TPS65912
1603	select REGMAP_SPI
1604	depends on SPI_MASTER
1605	help
1606	  If you say yes here you get support for the TPS65912 series of
1607	  PM chips with SPI interface.
1608
1609config MFD_TPS80031
1610	bool "TI TPS80031/TPS80032 Power Management chips"
1611	depends on I2C=y
1612	select MFD_CORE
1613	select REGMAP_I2C
1614	select REGMAP_IRQ
1615	help
1616	  If you say yes here you get support for the Texas Instruments
1617	  TPS80031/ TPS80032 Fully Integrated Power Management with Power
1618	  Path and Battery Charger. The device provides five configurable
1619	  step-down converters, 11 general purpose LDOs, USB OTG Module,
1620	  ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1621	  Power Path from USB, 32K clock generator.
1622
1623config TWL4030_CORE
1624	bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1625	depends on I2C=y
1626	select IRQ_DOMAIN
1627	select REGMAP_I2C
1628	help
1629	  Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1630	  This core driver provides register access and IRQ handling
1631	  facilities, and registers devices for the various functions
1632	  so that function-specific drivers can bind to them.
1633
1634	  These multi-function chips are found on many OMAP2 and OMAP3
1635	  boards, providing power management, RTC, GPIO, keypad, a
1636	  high speed USB OTG transceiver, an audio codec (on most
1637	  versions) and many other features.
1638
 
 
 
 
 
 
 
 
 
 
1639config TWL4030_POWER
1640	bool "TI TWL4030 power resources"
1641	depends on TWL4030_CORE && ARM
1642	help
1643	  Say yes here if you want to use the power resources on the
1644	  TWL4030 family chips.  Most of these resources are regulators,
1645	  which have a separate driver; some are control signals, such
1646	  as clock request handshaking.
1647
1648	  This driver uses board-specific data to initialize the resources
1649	  and load scripts controlling which resources are switched off/on
1650	  or reset when a sleep, wakeup or warm reset event occurs.
1651
1652config MFD_TWL4030_AUDIO
1653	bool "TI TWL4030 Audio"
1654	depends on TWL4030_CORE
1655	select MFD_CORE
1656	default n
1657
1658config TWL6040_CORE
1659	bool "TI TWL6040 audio codec"
1660	depends on I2C=y
1661	select MFD_CORE
1662	select REGMAP_I2C
1663	select REGMAP_IRQ
1664	default n
1665	help
1666	  Say yes here if you want support for Texas Instruments TWL6040 audio
1667	  codec.
1668	  This driver provides common support for accessing the device,
1669	  additional drivers must be enabled in order to use the
1670	  functionality of the device (audio, vibra).
1671
1672config MENELAUS
1673	bool "TI TWL92330/Menelaus PM chip"
1674	depends on I2C=y && ARCH_OMAP2
1675	help
1676	  If you say yes here you get support for the Texas Instruments
1677	  TWL92330/Menelaus Power Management chip. This include voltage
1678	  regulators, Dual slot memory card transceivers, real-time clock
1679	  and other features that are often used in portable devices like
1680	  cell phones and PDAs.
1681
1682config MFD_WL1273_CORE
1683	tristate "TI WL1273 FM radio"
1684	depends on I2C
1685	select MFD_CORE
1686	default n
1687	help
1688	  This is the core driver for the TI WL1273 FM radio. This MFD
1689	  driver connects the radio-wl1273 V4L2 module and the wl1273
1690	  audio codec.
1691
1692config MFD_LM3533
1693	tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1694	depends on I2C
1695	select MFD_CORE
1696	select REGMAP_I2C
1697	help
1698	  Say yes here to enable support for National Semiconductor / TI
1699	  LM3533 Lighting Power chips.
 
 
1700
1701	  This driver provides common support for accessing the device;
1702	  additional drivers must be enabled in order to use the LED,
1703	  backlight or ambient-light-sensor functionality of the device.
 
1704
1705config MFD_TIMBERDALE
1706	tristate "Timberdale FPGA"
1707	select MFD_CORE
1708	depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1709	help
1710	This is the core driver for the timberdale FPGA. This device is a
1711	multifunction device which exposes numerous platform devices.
1712
1713	The timberdale FPGA can be found on the Intel Atom development board
1714	for in-vehicle infontainment, called Russellville.
 
1715
1716config MFD_TC3589X
1717	bool "Toshiba TC35892 and variants"
1718	depends on I2C=y
1719	depends on OF
1720	select MFD_CORE
1721	help
1722	  Support for the Toshiba TC35892 and variants I/O Expander.
1723
1724	  This driver provides common support for accessing the device,
1725	  additional drivers must be enabled in order to use the
1726	  functionality of the device.
1727
1728config MFD_TMIO
1729	bool
1730	default n
1731
1732config MFD_T7L66XB
1733	bool "Toshiba T7L66XB"
1734	depends on ARM && HAVE_CLK
1735	select MFD_CORE
1736	select MFD_TMIO
1737	help
1738	  Support for Toshiba Mobile IO Controller T7L66XB
1739
1740config MFD_TC6387XB
1741	bool "Toshiba TC6387XB"
1742	depends on ARM && HAVE_CLK
1743	select MFD_CORE
1744	select MFD_TMIO
1745	help
1746	  Support for Toshiba Mobile IO Controller TC6387XB
1747
1748config MFD_TC6393XB
1749	bool "Toshiba TC6393XB"
1750	depends on ARM && HAVE_CLK
1751	select GPIOLIB
1752	select MFD_CORE
1753	select MFD_TMIO
1754	help
1755	  Support for Toshiba Mobile IO Controller TC6393XB
1756
1757config MFD_TQMX86
1758	tristate "TQ-Systems IO controller TQMX86"
1759	select MFD_CORE
1760	help
1761	  Say yes here to enable support for various functions of the
1762	  TQ-Systems IO controller and watchdog device, found on their
1763	  ComExpress CPU modules.
 
 
 
1764
1765config MFD_VX855
1766	tristate "VIA VX855/VX875 integrated south bridge"
1767	depends on PCI
1768	select MFD_CORE
1769	help
1770	  Say yes here to enable support for various functions of the
1771	  VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1772	  and/or vx855_gpio drivers for this to do anything useful.
 
 
1773
1774config MFD_LOCHNAGAR
1775	bool "Cirrus Logic Lochnagar Audio Development Board"
 
1776	select MFD_CORE
1777	select REGMAP_I2C
1778	depends on I2C=y && OF
1779	help
1780	  Support for Cirrus Logic Lochnagar audio development board.
 
 
 
1781
1782config MFD_ARIZONA
1783	select REGMAP
1784	select REGMAP_IRQ
1785	select MFD_CORE
1786	tristate
1787
1788config MFD_ARIZONA_I2C
1789	tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1790	select MFD_ARIZONA
1791	select REGMAP_I2C
1792	depends on I2C
1793	help
1794	  Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1795	  audio SoC core functionality controlled via I2C.
 
 
 
 
1796
1797config MFD_ARIZONA_SPI
1798	tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1799	select MFD_ARIZONA
1800	select REGMAP_SPI
1801	depends on SPI_MASTER
1802	help
1803	  Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1804	  audio SoC core functionality controlled via SPI.
1805
1806config MFD_CS47L24
1807	bool "Cirrus Logic CS47L24 and WM1831"
1808	depends on MFD_ARIZONA
1809	help
1810	  Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1811
1812config MFD_WM5102
1813	bool "Wolfson Microelectronics WM5102"
1814	depends on MFD_ARIZONA
1815	help
1816	  Support for Wolfson Microelectronics WM5102 low power audio SoC
1817
1818config MFD_WM5110
1819	bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1820	depends on MFD_ARIZONA
1821	help
1822	  Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1823	  low power audio SoC
1824
1825config MFD_WM8997
1826	bool "Wolfson Microelectronics WM8997"
1827	depends on MFD_ARIZONA
1828	help
1829	  Support for Wolfson Microelectronics WM8997 low power audio SoC
1830
1831config MFD_WM8998
1832	bool "Wolfson Microelectronics WM8998"
1833	depends on MFD_ARIZONA
1834	help
1835	  Support for Wolfson Microelectronics WM8998 low power audio SoC
1836
1837config MFD_WM8400
1838	bool "Wolfson Microelectronics WM8400"
1839	select MFD_CORE
1840	depends on I2C=y
1841	select REGMAP_I2C
1842	help
1843	  Support for the Wolfson Microelecronics WM8400 PMIC and audio
1844	  CODEC.  This driver provides common support for accessing
1845	  the device, additional drivers must be enabled in order to use
1846	  the functionality of the device.
1847
1848config MFD_WM831X
1849	bool
 
1850
1851config MFD_WM831X_I2C
1852	bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1853	select MFD_CORE
1854	select MFD_WM831X
1855	select REGMAP_I2C
1856	select IRQ_DOMAIN
1857	depends on I2C=y
1858	help
1859	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1860	  when controlled using I2C.  This driver provides common support
1861	  for accessing the device, additional drivers must be enabled in
1862	  order to use the functionality of the device.
1863
1864config MFD_WM831X_SPI
1865	bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1866	select MFD_CORE
1867	select MFD_WM831X
1868	select REGMAP_SPI
1869	select IRQ_DOMAIN
1870	depends on SPI_MASTER
1871	help
1872	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1873	  when controlled using SPI.  This driver provides common support
1874	  for accessing the device, additional drivers must be enabled in
1875	  order to use the functionality of the device.
1876
1877config MFD_WM8350
1878	bool
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1879
1880config MFD_WM8350_I2C
1881	bool "Wolfson Microelectronics WM8350 with I2C"
1882	select MFD_WM8350
1883	select REGMAP_I2C
1884	depends on I2C=y
1885	help
1886	  The WM8350 is an integrated audio and power management
1887	  subsystem with watchdog and RTC functionality for embedded
1888	  systems.  This option enables core support for the WM8350 with
1889	  I2C as the control interface.  Additional options must be
1890	  selected to enable support for the functionality of the chip.
1891
1892config MFD_WM8994
1893	tristate "Wolfson Microelectronics WM8994"
1894	select MFD_CORE
1895	select REGMAP_I2C
1896	select REGMAP_IRQ
1897	depends on I2C
1898	help
1899	  The WM8994 is a highly integrated hi-fi CODEC designed for
1900	  smartphone applications.  As well as audio functionality it
1901	  has on board GPIO and regulator functionality which is
1902	  supported via the relevant subsystems.  This driver provides
1903	  core support for the WM8994, in order to use the actual
1904	  functionality of the device other drivers must be enabled.
 
 
 
 
 
 
 
 
 
1905
1906config MFD_WM97xx
1907	tristate "Wolfson Microelectronics WM97xx"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1908	select MFD_CORE
1909	select REGMAP_AC97
1910	select AC97_BUS_COMPAT
1911	depends on AC97_BUS_NEW
1912	help
1913	  The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC
1914	  designed for smartphone applications.  As well as audio functionality
1915	  it has on board GPIO and a touchscreen functionality which is
1916	  supported via the relevant subsystems.  This driver provides core
1917	  support for the WM97xx, in order to use the actual functionality of
1918	  the device other drivers must be enabled.
1919
1920config MFD_STW481X
1921	tristate "Support for ST Microelectronics STw481x"
1922	depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1923	select REGMAP_I2C
1924	select MFD_CORE
1925	help
1926	  Select this option to enable the STw481x chip driver used
1927	  in various ST Microelectronics and ST-Ericsson embedded
1928	  Nomadik series.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1929
1930config MFD_ROHM_BD718XX
1931	tristate "ROHM BD71837 Power Management IC"
1932	depends on I2C=y
1933	depends on OF
1934	select REGMAP_I2C
1935	select REGMAP_IRQ
1936	select MFD_CORE
1937	help
1938	  Select this option to get support for the ROHM BD71837
1939	  Power Management ICs. BD71837 is designed to power processors like
1940	  NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring
1941	  and emergency shut down as well as 32,768KHz clock output.
 
 
 
 
 
 
 
 
 
 
 
1942
1943config MFD_ROHM_BD70528
1944	tristate "ROHM BD70528 Power Management IC"
1945	depends on I2C=y
1946	depends on OF
1947	select REGMAP_I2C
1948	select REGMAP_IRQ
1949	select MFD_CORE
1950	help
1951	  Select this option to get support for the ROHM BD70528 Power
1952	  Management IC. BD71837 is general purpose single-chip power
1953	  management IC for battery-powered portable devices. It contains
1954	  3 ultra-low current consumption buck converters, 3 LDOs and 2 LED
1955	  drivers. Also included are 4 GPIOs, a real-time clock (RTC), a 32kHz
1956	  crystal oscillator, high-accuracy VREF for use with an external ADC,
1957	  10 bits SAR ADC for battery temperature monitor and 1S battery
1958	  charger.
1959
1960config MFD_ROHM_BD71828
1961	tristate "ROHM BD71828 and BD71815 Power Management IC"
1962	depends on I2C=y
1963	depends on OF
1964	select REGMAP_I2C
1965	select REGMAP_IRQ
1966	select MFD_CORE
 
1967	help
1968	  Select this option to get support for the ROHM BD71828 and BD71815
1969	  Power Management ICs. BD71828GW and BD71815AGW are single-chip power
1970	  management ICs mainly for battery-powered portable devices.
1971	  The BD71828 integrates 7 buck converters and 7 LDOs. The BD71815
1972	  has 5 bucks, 7 LDOs, and a boost for driving LEDs. Both ICs provide
1973	  also a single-cell linear charger, a Coulomb counter, a real-time
1974	  clock (RTC), GPIOs and a 32.768 kHz clock gate.
 
1975
1976config MFD_ROHM_BD957XMUF
1977	tristate "ROHM BD9576MUF and BD9573MUF Power Management ICs"
1978	depends on I2C=y
1979	depends on OF
1980	select REGMAP_I2C
1981	select MFD_CORE
1982	help
1983	  Select this option to get support for the ROHM BD9576MUF and
1984	  BD9573MUF Power Management ICs. BD9576 and BD9573 are primarily
1985	  designed to be used to power R-Car series processors.
 
1986
1987config MFD_STM32_LPTIMER
1988	tristate "Support for STM32 Low-Power Timer"
1989	depends on (ARCH_STM32 && OF) || COMPILE_TEST
1990	select MFD_CORE
1991	select REGMAP
1992	select REGMAP_MMIO
1993	help
1994	  Select this option to enable STM32 Low-Power Timer driver
1995	  used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
1996	  resources are also dealt with here.
 
1997
1998	  To compile this driver as a module, choose M here: the
1999	  module will be called stm32-lptimer.
 
 
 
 
 
 
 
 
 
 
 
 
 
2000
2001config MFD_STM32_TIMERS
2002	tristate "Support for STM32 Timers"
2003	depends on (ARCH_STM32 && OF) || COMPILE_TEST
2004	select MFD_CORE
2005	select REGMAP
2006	select REGMAP_MMIO
2007	help
2008	  Select this option to enable STM32 timers driver used
2009	  for PWM and IIO Timer. This driver allow to share the
2010	  registers between the others drivers.
2011
2012config MFD_STPMIC1
2013	tristate "Support for STPMIC1 PMIC"
2014	depends on (I2C=y && OF)
2015	select REGMAP_I2C
2016	select REGMAP_IRQ
2017	select MFD_CORE
2018	help
2019	  Support for ST Microelectronics STPMIC1 PMIC. STPMIC1 has power on
2020	  key, watchdog and regulator functionalities which are supported via
2021	  the relevant subsystems. This driver provides core support for the
2022	  STPMIC1. In order to use the actual functionality of the device other
2023	  drivers must be enabled.
2024
2025	  To compile this driver as a module, choose M here: the
2026	  module will be called stpmic1.
 
 
 
 
 
2027
2028config MFD_STMFX
2029	tristate "Support for STMicroelectronics Multi-Function eXpander (STMFX)"
2030	depends on I2C
2031	depends on OF || COMPILE_TEST
2032	select MFD_CORE
2033	select REGMAP_I2C
2034	help
2035	  Support for the STMicroelectronics Multi-Function eXpander.
 
 
2036
2037	  This driver provides common support for accessing the device,
2038	  additional drivers must be enabled in order to use the functionality
2039	  of the device.
 
 
 
 
 
 
2040
2041config MFD_WCD934X
2042	tristate "Support for WCD9340/WCD9341 Codec"
2043	depends on SLIMBUS
2044	select REGMAP
2045	select REGMAP_SLIMBUS
2046	select REGMAP_IRQ
2047	select MFD_CORE
 
 
2048	help
2049	  Support for the Qualcomm WCD9340/WCD9341 Codec.
2050	  This driver provides common support WCD934x audio codec and its
2051	  associated Pin Controller, Soundwire Controller and Audio codec.
2052
2053config MFD_ATC260X
2054	tristate
 
2055	select MFD_CORE
2056	select REGMAP
2057	select REGMAP_IRQ
 
 
2058
2059config MFD_ATC260X_I2C
2060	tristate "Actions Semi ATC260x PMICs with I2C"
2061	select MFD_ATC260X
2062	select REGMAP_I2C
2063	depends on I2C
 
 
2064	help
2065	  Support for the Actions Semi ATC260x PMICs controlled via I2C.
 
 
2066
2067	  This driver provides common support for accessing the ATC2603C
2068	  and ATC2609A chip variants, additional drivers must be enabled
2069	  in order to use the functionality of the device.
 
 
 
 
 
2070
2071config MFD_KHADAS_MCU
2072	tristate "Support for Khadas System control Microcontroller"
2073	depends on I2C
2074	depends on ARCH_MESON || ARCH_ROCKCHIP || COMPILE_TEST
 
 
2075	select MFD_CORE
2076	select REGMAP_I2C
2077	help
2078	  Support for the Khadas System control Microcontroller interface
2079	  present on their VIM and Edge boards.
2080
2081	  This Microcontroller is present on the Khadas VIM1, VIM2, VIM3 and
2082	  Edge boards.
 
 
 
 
 
 
 
 
 
 
2083
2084	  It provides multiple boot control features like password check,
2085	  power-on options, power-off control and system FAN control on recent
2086	  boards.
2087
2088	  This driver provides common support for accessing the device,
2089	  additional drivers must be enabled in order to use the functionality
2090	  of the device.
2091
2092config MFD_ACER_A500_EC
2093	tristate "Support for Acer Iconia Tab A500 Embedded Controller"
2094	depends on I2C
2095	depends on (ARCH_TEGRA_2x_SOC && OF) || COMPILE_TEST
2096	select MFD_CORE
2097	select REGMAP
2098	help
2099	  Support for Embedded Controller found on Acer Iconia Tab A500.
2100	  The controller itself is ENE KB930, it is running firmware
2101	  customized for the specific needs of the Acer A500 hardware.
2102
2103config MFD_QCOM_PM8008
2104	tristate "QCOM PM8008 Power Management IC"
2105	depends on I2C && OF
2106	select REGMAP_I2C
2107	select REGMAP_IRQ
2108	help
2109	  Select this option to get support for the Qualcomm Technologies, Inc.
2110	  PM8008 PMIC chip. PM8008 is a dedicated camera PMIC that integrates
2111	  all the necessary power management, housekeeping, and interface
2112	  support functions into a single IC. This driver provides common
2113	  support for accessing the device by instantiating all the child nodes
2114	  under it in the device tree. Additional drivers must be enabled in
2115	  order to use the functionality of the device.
2116
2117menu "Multimedia Capabilities Port drivers"
2118	depends on ARCH_SA1100
2119
2120config MCP
2121	tristate
2122
2123# Interface drivers
2124config MCP_SA11X0
2125	tristate "Support SA11x0 MCP interface"
2126	depends on ARCH_SA1100
2127	select MCP
2128
2129# Chip drivers
2130config MCP_UCB1200
2131	tristate "Support for UCB1200 / UCB1300"
2132	depends on MCP_SA11X0
2133	select MCP
2134
2135config MCP_UCB1200_TS
2136	tristate "Touchscreen interface support"
2137	depends on MCP_UCB1200 && INPUT
2138
2139endmenu
2140
2141config MFD_VEXPRESS_SYSREG
2142	tristate "Versatile Express System Registers"
2143	depends on VEXPRESS_CONFIG && GPIOLIB
2144	default y
2145	select GPIO_GENERIC_PLATFORM
2146	select MFD_CORE
2147	select MFD_SYSCON
2148	help
2149	  System Registers are the platform configuration block
2150	  on the ARM Ltd. Versatile Express board.
2151
2152config RAVE_SP_CORE
2153	tristate "RAVE SP MCU core driver"
2154	depends on SERIAL_DEV_BUS
2155	select CRC_CCITT
2156	help
2157	  Select this to get support for the Supervisory Processor
2158	  device found on several devices in RAVE line of hardware.
2159
2160config SGI_MFD_IOC3
2161	bool "SGI IOC3 core driver"
2162	depends on PCI && MIPS && 64BIT
2163	select MFD_CORE
2164	help
2165	  This option enables basic support for the SGI IOC3-based
2166	  controller cards.  This option does not enable any specific
2167	  functions on such a card, but provides necessary infrastructure
2168	  for other drivers to utilize.
2169
2170	  If you have an SGI Origin, Octane, or a PCI IOC3 card,
2171	  then say Y. Otherwise say N.
2172
2173config MFD_INTEL_M10_BMC
2174	tristate "Intel MAX 10 Board Management Controller"
2175	depends on SPI_MASTER
2176	select REGMAP_SPI_AVMM
2177	select MFD_CORE
2178	help
2179	  Support for the Intel MAX 10 board management controller using the
2180	  SPI interface.
2181
2182	  This driver provides common support for accessing the device,
2183	  additional drivers must be enabled in order to use the functionality
2184	  of the device.
2185
2186endmenu
2187endif