blob: b67a7cd209956d7cd028c4f13db26dc6201bf8db [file] [log] [blame]
rjw1f884582022-01-06 17:20:42 +08001#
2# Multifunction miscellaneous devices
3#
4
5if HAS_IOMEM
6menu "Multifunction device drivers"
7
8config MFD_CORE
9 tristate
10 select IRQ_DOMAIN
11 default n
12
13config MFD_CS5535
14 tristate "AMD CS5535 and CS5536 southbridge core functions"
15 select MFD_CORE
16 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
17 ---help---
18 This is the core driver for CS5535/CS5536 MFD functions. This is
19 necessary for using the board's GPIO and MFGPT functionality.
20
21config MFD_ALTERA_A10SR
22 bool "Altera Arria10 DevKit System Resource chip"
23 depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
24 select REGMAP_SPI
25 select MFD_CORE
26 help
27 Support for the Altera Arria10 DevKit MAX5 System Resource chip
28 using the SPI interface. This driver provides common support for
29 accessing the external gpio extender (LEDs & buttons) and
30 power supply alarms (hwmon).
31
32config MFD_ACT8945A
33 tristate "Active-semi ACT8945A"
34 select MFD_CORE
35 select REGMAP_I2C
36 depends on I2C && OF
37 help
38 Support for the ACT8945A PMIC from Active-semi. This device
39 features three step-down DC/DC converters and four low-dropout
40 linear regulators, along with a complete ActivePath battery
41 charger.
42
43config MFD_SUN4I_GPADC
44 tristate "Allwinner sunxi platforms' GPADC MFD driver"
45 select MFD_CORE
46 select REGMAP_MMIO
47 select REGMAP_IRQ
48 depends on ARCH_SUNXI || COMPILE_TEST
49 depends on !TOUCHSCREEN_SUN4I
50 help
51 Select this to get support for Allwinner SoCs (A10, A13 and A31) ADC.
52 This driver will only map the hardware interrupt and registers, you
53 have to select individual drivers based on this MFD to be able to use
54 the ADC or the thermal sensor. This will try to probe the ADC driver
55 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
56
57 To compile this driver as a module, choose M here: the module will be
58 called sun4i-gpadc.
59
60config MFD_AS3711
61 bool "AMS AS3711"
62 select MFD_CORE
63 select REGMAP_I2C
64 select REGMAP_IRQ
65 depends on I2C=y
66 help
67 Support for the AS3711 PMIC from AMS
68
69config MFD_AS3722
70 tristate "ams AS3722 Power Management IC"
71 select MFD_CORE
72 select REGMAP_I2C
73 select REGMAP_IRQ
74 depends on I2C=y && OF
75 help
76 The ams AS3722 is a compact system PMU suitable for mobile phones,
77 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
78 controllers, 11 LDOs, RTC, automatic battery, temperature and
79 over current monitoring, GPIOs, ADC and a watchdog.
80
81config PMIC_ADP5520
82 bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
83 depends on I2C=y
84 help
85 Say yes here to add support for Analog Devices AD5520 and ADP5501,
86 Multifunction Power Management IC. This includes
87 the I2C driver and the core APIs _only_, you have to select
88 individual components like LCD backlight, LEDs, GPIOs and Kepad
89 under the corresponding menus.
90
91config MFD_AAT2870_CORE
92 bool "AnalogicTech AAT2870"
93 select MFD_CORE
94 depends on I2C=y
95 depends on GPIOLIB || COMPILE_TEST
96 help
97 If you say yes here you get support for the AAT2870.
98 This driver provides common support for accessing the device,
99 additional drivers must be enabled in order to use the
100 functionality of the device.
101
102config MFD_ATMEL_FLEXCOM
103 tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
104 select MFD_CORE
105 depends on OF
106 help
107 Select this to get support for Atmel Flexcom. This is a wrapper
108 which embeds a SPI controller, a I2C controller and a USART. Only
109 one function can be used at a time. The choice is done at boot time
110 by the probe function of this MFD driver according to a device tree
111 property.
112
113config MFD_ATMEL_HLCDC
114 tristate "Atmel HLCDC (High-end LCD Controller)"
115 select MFD_CORE
116 select REGMAP_MMIO
117 depends on OF
118 help
119 If you say yes here you get support for the HLCDC block.
120 This driver provides common support for accessing the device,
121 additional drivers must be enabled in order to use the
122 functionality of the device.
123
124config MFD_ATMEL_SMC
125 bool
126 select MFD_SYSCON
127
128config MFD_BCM590XX
129 tristate "Broadcom BCM590xx PMUs"
130 select MFD_CORE
131 select REGMAP_I2C
132 depends on I2C
133 help
134 Support for the BCM590xx PMUs from Broadcom
135
136config MFD_BD9571MWV
137 tristate "ROHM BD9571MWV PMIC"
138 select MFD_CORE
139 select REGMAP_I2C
140 select REGMAP_IRQ
141 depends on I2C
142 help
143 Support for the ROHM BD9571MWV PMIC, which contains single
144 voltage regulator, voltage sampling units, GPIO block and
145 watchdog block.
146
147 This driver can also be built as a module. If so, the module
148 will be called bd9571mwv.
149
150config MFD_AC100
151 tristate "X-Powers AC100"
152 select MFD_CORE
153 depends on SUNXI_RSB
154 help
155 If you say Y here you get support for the X-Powers AC100 audio codec
156 IC.
157 This driver include only the core APIs. You have to select individual
158 components like codecs or RTC under the corresponding menus.
159
160config MFD_AXP20X
161 tristate
162 select MFD_CORE
163 select REGMAP_IRQ
164
165config MFD_AXP20X_I2C
166 tristate "X-Powers AXP series PMICs with I2C"
167 select MFD_AXP20X
168 select REGMAP_I2C
169 depends on I2C
170 help
171 If you say Y here you get support for the X-Powers AXP series power
172 management ICs (PMICs) controlled with I2C.
173 This driver include only the core APIs. You have to select individual
174 components like regulators or the PEK (Power Enable Key) under the
175 corresponding menus.
176
177 Note on x86 this provides an ACPI OpRegion, so this must be 'y'
178 (builtin) and not a module, as the OpRegion must be available as
179 soon as possible. For the same reason the I2C bus driver options
180 I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too.
181
182config MFD_AXP20X_RSB
183 tristate "X-Powers AXP series PMICs with RSB"
184 select MFD_AXP20X
185 depends on SUNXI_RSB
186 help
187 If you say Y here you get support for the X-Powers AXP series power
188 management ICs (PMICs) controlled with RSB.
189 This driver include only the core APIs. You have to select individual
190 components like regulators or the PEK (Power Enable Key) under the
191 corresponding menus.
192
193config MFD_CROS_EC
194 tristate "ChromeOS Embedded Controller"
195 select MFD_CORE
196 select CHROME_PLATFORMS
197 select CROS_EC_PROTO
198 depends on X86 || ARM || ARM64 || COMPILE_TEST
199 help
200 If you say Y here you get support for the ChromeOS Embedded
201 Controller (EC) providing keyboard, battery and power services.
202 You also need to enable the driver for the bus you are using. The
203 protocol for talking to the EC is defined by the bus driver.
204
205config MFD_CROS_EC_I2C
206 tristate "ChromeOS Embedded Controller (I2C)"
207 depends on MFD_CROS_EC && I2C
208
209 help
210 If you say Y here, you get support for talking to the ChromeOS
211 EC through an I2C bus. This uses a simple byte-level protocol with
212 a checksum. Failing accesses will be retried three times to
213 improve reliability.
214
215config MFD_CROS_EC_SPI
216 tristate "ChromeOS Embedded Controller (SPI)"
217 depends on MFD_CROS_EC && SPI
218
219 ---help---
220 If you say Y here, you get support for talking to the ChromeOS EC
221 through a SPI bus, using a byte-level protocol. Since the EC's
222 response time cannot be guaranteed, we support ignoring
223 'pre-amble' bytes before the response actually starts.
224
225config MFD_ASIC3
226 bool "Compaq ASIC3"
227 depends on GPIOLIB && ARM
228 select MFD_CORE
229 ---help---
230 This driver supports the ASIC3 multifunction chip found on many
231 PDAs (mainly iPAQ and HTC based ones)
232
233config PMIC_DA903X
234 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
235 depends on I2C=y
236 help
237 Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
238 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
239 usually found on PXA processors-based platforms. This includes
240 the I2C driver and the core APIs _only_, you have to select
241 individual components like LCD backlight, voltage regulators,
242 LEDs and battery-charger under the corresponding menus.
243
244config PMIC_DA9052
245 bool
246 select MFD_CORE
247
248config MFD_DA9052_SPI
249 bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
250 select REGMAP_SPI
251 select REGMAP_IRQ
252 select PMIC_DA9052
253 depends on SPI_MASTER=y
254 help
255 Support for the Dialog Semiconductor DA9052 PMIC
256 when controlled using SPI. This driver provides common support
257 for accessing the device, additional drivers must be enabled in
258 order to use the functionality of the device.
259
260config MFD_DA9052_I2C
261 bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
262 select REGMAP_I2C
263 select REGMAP_IRQ
264 select PMIC_DA9052
265 depends on I2C=y
266 help
267 Support for the Dialog Semiconductor DA9052 PMIC
268 when controlled using I2C. This driver provides common support
269 for accessing the device, additional drivers must be enabled in
270 order to use the functionality of the device.
271
272config MFD_DA9055
273 bool "Dialog Semiconductor DA9055 PMIC Support"
274 select REGMAP_I2C
275 select REGMAP_IRQ
276 select MFD_CORE
277 depends on I2C=y
278 help
279 Say yes here for support of Dialog Semiconductor DA9055. This is
280 a Power Management IC. This driver provides common support for
281 accessing the device as well as the I2C interface to the chip itself.
282 Additional drivers must be enabled in order to use the functionality
283 of the device.
284
285 This driver can be built as a module. If built as a module it will be
286 called "da9055"
287
288config MFD_DA9062
289 tristate "Dialog Semiconductor DA9062/61 PMIC Support"
290 select MFD_CORE
291 select REGMAP_I2C
292 select REGMAP_IRQ
293 depends on I2C
294 help
295 Say yes here for support for the Dialog Semiconductor DA9061 and
296 DA9062 PMICs.
297 This includes the I2C driver and core APIs.
298 Additional drivers must be enabled in order to use the functionality
299 of the device.
300
301config MFD_DA9063
302 tristate "Dialog Semiconductor DA9063 PMIC Support"
303 select MFD_CORE
304 select REGMAP_I2C
305 select REGMAP_IRQ
306 depends on I2C
307 help
308 Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
309 This includes the I2C driver and core APIs.
310 Additional drivers must be enabled in order to use the functionality
311 of the device.
312
313config MFD_DA9150
314 tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
315 depends on I2C
316 select MFD_CORE
317 select REGMAP_I2C
318 select REGMAP_IRQ
319 help
320 This adds support for the DA9150 integrated charger and fuel-gauge
321 chip. This driver provides common support for accessing the device.
322 Additional drivers must be enabled in order to use the specific
323 features of the device.
324
325config MFD_DLN2
326 tristate "Diolan DLN2 support"
327 select MFD_CORE
328 depends on USB
329 help
330 This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
331 DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
332 etc. must be enabled in order to use the functionality of
333 the device.
334
335config MFD_EXYNOS_LPASS
336 tristate "Samsung Exynos SoC Low Power Audio Subsystem"
337 depends on ARCH_EXYNOS || COMPILE_TEST
338 select MFD_CORE
339 select REGMAP_MMIO
340 help
341 Select this option to enable support for Samsung Exynos Low Power
342 Audio Subsystem.
343
344config MFD_MC13XXX
345 tristate
346 depends on (SPI_MASTER || I2C)
347 select MFD_CORE
348 select REGMAP_IRQ
349 help
350 Enable support for the Freescale MC13783 and MC13892 PMICs.
351 This driver provides common support for accessing the device,
352 additional drivers must be enabled in order to use the
353 functionality of the device.
354
355config MFD_MC13XXX_SPI
356 tristate "Freescale MC13783 and MC13892 SPI interface"
357 depends on SPI_MASTER
358 select REGMAP_SPI
359 select MFD_MC13XXX
360 help
361 Select this if your MC13xxx is connected via an SPI bus.
362
363config MFD_MC13XXX_I2C
364 tristate "Freescale MC13892 I2C interface"
365 depends on I2C
366 select REGMAP_I2C
367 select MFD_MC13XXX
368 help
369 Select this if your MC13xxx is connected via an I2C bus.
370
371config MFD_MXS_LRADC
372 tristate "Freescale i.MX23/i.MX28 LRADC"
373 depends on ARCH_MXS || COMPILE_TEST
374 select MFD_CORE
375 select STMP_DEVICE
376 help
377 Say yes here to build support for the Low Resolution
378 Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28
379 processors. This driver provides common support for accessing the
380 device, additional drivers must be enabled in order to use the
381 functionality of the device:
382 mxs-lradc-adc for ADC readings
383 mxs-lradc-ts for touchscreen support
384
385 This driver can also be built as a module. If so, the module will be
386 called mxs-lradc.
387
388config MFD_MX25_TSADC
389 tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
390 select REGMAP_MMIO
391 depends on (SOC_IMX25 && OF) || COMPILE_TEST
392 help
393 Enable support for the integrated Touchscreen and ADC unit of the
394 i.MX25 processors. They consist of a conversion queue for general
395 purpose ADC and a queue for Touchscreens.
396
397config MFD_HI6421_PMIC
398 tristate "HiSilicon Hi6421 PMU/Codec IC"
399 depends on OF
400 select MFD_CORE
401 select REGMAP_MMIO
402 help
403 Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
404 functions, such as regulators, RTC, codec, Coulomb counter, etc.
405 This driver includes core APIs _only_. You have to select
406 individul components like voltage regulators under corresponding
407 menus in order to enable them.
408 We communicate with the Hi6421 via memory-mapped I/O.
409
410config MFD_HI655X_PMIC
411 tristate "HiSilicon Hi655X series PMU/Codec IC"
412 depends on ARCH_HISI || COMPILE_TEST
413 depends on OF
414 select MFD_CORE
415 select REGMAP_MMIO
416 select REGMAP_IRQ
417 help
418 Select this option to enable Hisilicon hi655x series pmic driver.
419
420config HTC_PASIC3
421 tristate "HTC PASIC3 LED/DS1WM chip support"
422 select MFD_CORE
423 help
424 This core driver provides register access for the LED/DS1WM
425 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
426 HTC Magician devices, respectively. Actual functionality is
427 handled by the leds-pasic3 and ds1wm drivers.
428
429config HTC_I2CPLD
430 bool "HTC I2C PLD chip support"
431 depends on I2C=y && GPIOLIB
432 help
433 If you say yes here you get support for the supposed CPLD
434 found on omap850 HTC devices like the HTC Wizard and HTC Herald.
435 This device provides input and output GPIOs through an I2C
436 interface to one or more sub-chips.
437
438config MFD_INTEL_QUARK_I2C_GPIO
439 tristate "Intel Quark MFD I2C GPIO"
440 depends on PCI
441 depends on X86
442 depends on COMMON_CLK
443 select MFD_CORE
444 help
445 This MFD provides support for I2C and GPIO that exist only
446 in a single PCI device. It splits the 2 IO devices to
447 their respective IO driver.
448 The GPIO exports a total amount of 8 interrupt-capable GPIOs.
449
450config LPC_ICH
451 tristate "Intel ICH LPC"
452 depends on PCI
453 select MFD_CORE
454 help
455 The LPC bridge function of the Intel ICH provides support for
456 many functional units. This driver provides needed support for
457 other drivers to control these functions, currently GPIO and
458 watchdog.
459
460config LPC_SCH
461 tristate "Intel SCH LPC"
462 depends on PCI
463 select MFD_CORE
464 help
465 LPC bridge function of the Intel SCH provides support for
466 System Management Bus and General Purpose I/O.
467
468config INTEL_SOC_PMIC
469 bool "Support for Crystal Cove PMIC"
470 depends on ACPI && HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK
471 depends on X86 || COMPILE_TEST
472 select MFD_CORE
473 select REGMAP_I2C
474 select REGMAP_IRQ
475 select I2C_DESIGNWARE_PLATFORM
476 help
477 Select this option to enable support for Crystal Cove PMIC
478 on some Intel SoC systems. The PMIC provides ADC, GPIO,
479 thermal, charger and related power management functions
480 on these systems.
481
482 This option is a bool as it provides an ACPI OpRegion which must be
483 available before any devices using it are probed. This option also
484 causes the designware-i2c driver to be builtin for the same reason.
485
486config INTEL_SOC_PMIC_BXTWC
487 tristate "Support for Intel Broxton Whiskey Cove PMIC"
488 depends on INTEL_PMC_IPC
489 select MFD_CORE
490 select REGMAP_IRQ
491 help
492 Select this option to enable support for Whiskey Cove PMIC
493 on Intel Broxton systems. The PMIC provides ADC, GPIO,
494 thermal, charger and related power management functions
495 on these systems.
496
497config INTEL_SOC_PMIC_CHTWC
498 bool "Support for Intel Cherry Trail Whiskey Cove PMIC"
499 depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK
500 depends on X86 || COMPILE_TEST
501 select MFD_CORE
502 select REGMAP_I2C
503 select REGMAP_IRQ
504 select I2C_DESIGNWARE_PLATFORM
505 help
506 Select this option to enable support for the Intel Cherry Trail
507 Whiskey Cove PMIC found on some Intel Cherry Trail systems.
508
509 This option is a bool as it provides an ACPI OpRegion which must be
510 available before any devices using it are probed. This option also
511 causes the designware-i2c driver to be builtin for the same reason.
512
513config MFD_INTEL_LPSS
514 tristate
515 select COMMON_CLK
516 select MFD_CORE
517
518config MFD_INTEL_LPSS_ACPI
519 tristate "Intel Low Power Subsystem support in ACPI mode"
520 select MFD_INTEL_LPSS
521 depends on X86 && ACPI
522 help
523 This driver supports Intel Low Power Subsystem (LPSS) devices such as
524 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
525 PCH) in ACPI mode.
526
527config MFD_INTEL_LPSS_PCI
528 tristate "Intel Low Power Subsystem support in PCI mode"
529 select MFD_INTEL_LPSS
530 depends on X86 && PCI
531 help
532 This driver supports Intel Low Power Subsystem (LPSS) devices such as
533 I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
534 PCH) in PCI mode.
535
536config MFD_INTEL_MSIC
537 bool "Intel MSIC"
538 depends on INTEL_SCU_IPC
539 select MFD_CORE
540 help
541 Select this option to enable access to Intel MSIC (Avatele
542 Passage) chip. This chip embeds audio, battery, GPIO, etc.
543 devices used in Intel Medfield platforms.
544
545config MFD_IPAQ_MICRO
546 bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
547 depends on SA1100_H3100 || SA1100_H3600
548 select MFD_CORE
549 help
550 Select this to get support for the Microcontroller found in
551 the Compaq iPAQ handheld computers. This is an Atmel
552 AT90LS8535 microcontroller flashed with a special iPAQ
553 firmware using the custom protocol implemented in this driver.
554
555config MFD_JANZ_CMODIO
556 tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
557 select MFD_CORE
558 depends on PCI
559 help
560 This is the core driver for the Janz CMOD-IO PCI MODULbus
561 carrier board. This device is a PCI to MODULbus bridge which may
562 host many different types of MODULbus daughterboards, including
563 CAN and GPIO controllers.
564
565config MFD_JZ4740_ADC
566 bool "Janz JZ4740 ADC core"
567 select MFD_CORE
568 select GENERIC_IRQ_CHIP
569 depends on MACH_JZ4740
570 help
571 Say yes here if you want support for the ADC unit in the JZ4740 SoC.
572 This driver is necessary for jz4740-battery and jz4740-hwmon driver.
573
574config MFD_KEMPLD
575 tristate "Kontron module PLD device"
576 select MFD_CORE
577 help
578 This is the core driver for the PLD (Programmable Logic Device) found
579 on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
580 device may provide functions like watchdog, GPIO, UART and I2C bus.
581
582 The following modules are supported:
583 * COMe-bBD#
584 * COMe-bBL6
585 * COMe-bHL6
586 * COMe-bSL6
587 * COMe-bIP#
588 * COMe-bKL6
589 * COMe-bPC2 (ETXexpress-PC)
590 * COMe-bSC# (ETXexpress-SC T#)
591 * COMe-cAL6
592 * COMe-cBL6
593 * COMe-cBT6
594 * COMe-cBW6
595 * COMe-cCT6
596 * COMe-cDC2 (microETXexpress-DC)
597 * COMe-cHL6
598 * COMe-cKL6
599 * COMe-cPC2 (microETXexpress-PC)
600 * COMe-cSL6
601 * COMe-mAL10
602 * COMe-mBT10
603 * COMe-mCT10
604 * COMe-mTT10 (nanoETXexpress-TT)
605 * ETX-OH
606
607 This driver can also be built as a module. If so, the module
608 will be called kempld-core.
609
610config MFD_88PM800
611 tristate "Marvell 88PM800"
612 depends on I2C
613 select REGMAP_I2C
614 select REGMAP_IRQ
615 select MFD_CORE
616 help
617 This supports for Marvell 88PM800 Power Management IC.
618 This includes the I2C driver and the core APIs _only_, you have to
619 select individual components like voltage regulators, RTC and
620 battery-charger under the corresponding menus.
621
622config MFD_88PM805
623 tristate "Marvell 88PM805"
624 depends on I2C
625 select REGMAP_I2C
626 select REGMAP_IRQ
627 select MFD_CORE
628 help
629 This supports for Marvell 88PM805 Power Management IC. This includes
630 the I2C driver and the core APIs _only_, you have to select individual
631 components like codec device, headset/Mic device under the
632 corresponding menus.
633
634config MFD_88PM860X
635 bool "Marvell 88PM8606/88PM8607"
636 depends on I2C=y
637 select REGMAP_I2C
638 select MFD_CORE
639 help
640 This supports for Marvell 88PM8606/88PM8607 Power Management IC.
641 This includes the I2C driver and the core APIs _only_, you have to
642 select individual components like voltage regulators, RTC and
643 battery-charger under the corresponding menus.
644
645config MFD_MAX14577
646 tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
647 depends on I2C
648 select MFD_CORE
649 select REGMAP_I2C
650 select REGMAP_IRQ
651 select IRQ_DOMAIN
652 help
653 Say yes here to add support for Maxim Semiconductor MAX14577 and
654 MAX77836 Micro-USB ICs with battery charger.
655 This driver provides common support for accessing the device;
656 additional drivers must be enabled in order to use the functionality
657 of the device.
658
659config MFD_MAX77620
660 bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
661 depends on I2C=y
662 depends on OF || COMPILE_TEST
663 select MFD_CORE
664 select REGMAP_I2C
665 select REGMAP_IRQ
666 select IRQ_DOMAIN
667 help
668 Say yes here to add support for Maxim Semiconductor MAX77620 and
669 MAX20024 which are Power Management IC with General purpose pins,
670 RTC, regulators, clock generator, watchdog etc. This driver
671 provides common support for accessing the device; additional drivers
672 must be enabled in order to use the functionality of the device.
673
674config MFD_MAX77686
675 tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
676 depends on I2C
677 depends on OF || COMPILE_TEST
678 select MFD_CORE
679 select REGMAP_I2C
680 select REGMAP_IRQ
681 select IRQ_DOMAIN
682 help
683 Say yes here to add support for Maxim Semiconductor MAX77686 and
684 MAX77802 which are Power Management IC with an RTC on chip.
685 This driver provides common support for accessing the device;
686 additional drivers must be enabled in order to use the functionality
687 of the device.
688
689config MFD_MAX77693
690 tristate "Maxim Semiconductor MAX77693 PMIC Support"
691 depends on I2C
692 select MFD_CORE
693 select REGMAP_I2C
694 select REGMAP_IRQ
695 help
696 Say yes here to add support for Maxim Semiconductor MAX77693.
697 This is a companion Power Management IC with Flash, Haptic, Charger,
698 and MUIC(Micro USB Interface Controller) controls on chip.
699 This driver provides common support for accessing the device;
700 additional drivers must be enabled in order to use the functionality
701 of the device.
702
703config MFD_MAX77843
704 bool "Maxim Semiconductor MAX77843 PMIC Support"
705 depends on I2C=y
706 select MFD_CORE
707 select REGMAP_I2C
708 select REGMAP_IRQ
709 help
710 Say yes here to add support for Maxim Semiconductor MAX77843.
711 This is companion Power Management IC with LEDs, Haptic, Charger,
712 Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
713 This driver provides common support for accessing the device;
714 additional drivers must be enabled in order to use the functionality
715 of the device.
716
717config MFD_MAX8907
718 tristate "Maxim Semiconductor MAX8907 PMIC Support"
719 select MFD_CORE
720 depends on I2C
721 select REGMAP_I2C
722 select REGMAP_IRQ
723 help
724 Say yes here to add support for Maxim Semiconductor MAX8907. This is
725 a Power Management IC. This driver provides common support for
726 accessing the device; additional drivers must be enabled in order
727 to use the functionality of the device.
728
729config MFD_MAX8925
730 bool "Maxim Semiconductor MAX8925 PMIC Support"
731 depends on I2C=y
732 select MFD_CORE
733 help
734 Say yes here to add support for Maxim Semiconductor MAX8925. This is
735 a Power Management IC. This driver provides common support for
736 accessing the device, additional drivers must be enabled in order
737 to use the functionality of the device.
738
739config MFD_MAX8997
740 bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
741 depends on I2C=y
742 select MFD_CORE
743 select IRQ_DOMAIN
744 help
745 Say yes here to add support for Maxim Semiconductor MAX8997/8966.
746 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
747 MUIC controls on chip.
748 This driver provides common support for accessing the device;
749 additional drivers must be enabled in order to use the functionality
750 of the device.
751
752config MFD_MAX8998
753 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
754 depends on I2C=y
755 select MFD_CORE
756 select IRQ_DOMAIN
757 help
758 Say yes here to add support for Maxim Semiconductor MAX8998 and
759 National Semiconductor LP3974. This is a Power Management IC.
760 This driver provides common support for accessing the device,
761 additional drivers must be enabled in order to use the functionality
762 of the device.
763
764config MFD_MT6358
765 tristate "MediaTek MT6358 PMIC Support"
766 select MFD_CORE
767 select IRQ_DOMAIN
768 help
769 Say yes here to add support for MediaTek MT6358 PMIC. This is
770 a Power Management IC. This driver provides common support for
771 accessing the device; additional drivers must be enabled in order
772 to use the functionality of the device.
773
774config MT6358_MISC
775 tristate "MediaTek MT6358 MISC FUNCTIONS Support"
776 depends on MFD_MT6358
777 help
778 Say yes here to add support for MediaTek MT6358 misc functions
779 support. And this driver only provides some additional functions
780 and depends on PMIC rtc module. it can be provide some APIs to
781 other modules and store some misc information to rtc registers.
782
783config MFD_MT6397
784 tristate "MediaTek MT6397 PMIC Support"
785 select MFD_CORE
786 select IRQ_DOMAIN
787 help
788 Say yes here to add support for MediaTek MT6397 PMIC. This is
789 a Power Management IC. This driver provides common support for
790 accessing the device; additional drivers must be enabled in order
791 to use the functionality of the device.
792
793config MFD_MENF21BMC
794 tristate "MEN 14F021P00 Board Management Controller Support"
795 depends on I2C
796 select MFD_CORE
797 help
798 Say yes here to add support for the MEN 14F021P00 BMC
799 which is a Board Management Controller connected to the I2C bus.
800 The device supports multiple sub-devices like LED, HWMON and WDT.
801 This driver provides common support for accessing the devices;
802 additional drivers must be enabled in order to use the
803 functionality of the BMC device.
804
805 This driver can also be built as a module. If so the module
806 will be called menf21bmc.
807
808config EZX_PCAP
809 bool "Motorola EZXPCAP Support"
810 depends on SPI_MASTER
811 help
812 This enables the PCAP ASIC present on EZX Phones. This is
813 needed for MMC, TouchScreen, Sound, USB, etc..
814
815config MFD_CPCAP
816 tristate "Support for Motorola CPCAP"
817 depends on SPI
818 depends on OF || COMPILE_TEST
819 select REGMAP_SPI
820 select REGMAP_IRQ
821 help
822 Say yes here if you want to include driver for CPCAP.
823 It is used on many Motorola phones and tablets as a PMIC.
824 At least Motorola Droid 4 is known to use CPCAP.
825
826config MFD_VIPERBOARD
827 tristate "Nano River Technologies Viperboard"
828 select MFD_CORE
829 depends on USB
830 default n
831 help
832 Say yes here if you want support for Nano River Technologies
833 Viperboard.
834 There are mfd cell drivers available for i2c master, adc and
835 both gpios found on the board. The spi part does not yet
836 have a driver.
837 You need to select the mfd cell drivers separately.
838 The drivers do not support all features the board exposes.
839
840config MFD_RETU
841 tristate "Nokia Retu and Tahvo multi-function device"
842 select MFD_CORE
843 depends on I2C
844 select REGMAP_IRQ
845 help
846 Retu and Tahvo are a multi-function devices found on Nokia
847 Internet Tablets (770, N800 and N810).
848
849config MFD_PCF50633
850 tristate "NXP PCF50633"
851 depends on I2C
852 select REGMAP_I2C
853 help
854 Say yes here if you have NXP PCF50633 chip on your board.
855 This core driver provides register access and IRQ handling
856 facilities, and registers devices for the various functions
857 so that function-specific drivers can bind to them.
858
859config PCF50633_ADC
860 tristate "NXP PCF50633 ADC"
861 depends on MFD_PCF50633
862 help
863 Say yes here if you want to include support for ADC in the
864 NXP PCF50633 chip.
865
866config PCF50633_GPIO
867 tristate "NXP PCF50633 GPIO"
868 depends on MFD_PCF50633
869 help
870 Say yes here if you want to include support GPIO for pins on
871 the PCF50633 chip.
872
873config UCB1400_CORE
874 tristate "Philips UCB1400 Core driver"
875 depends on AC97_BUS
876 depends on GPIOLIB
877 help
878 This enables support for the Philips UCB1400 core functions.
879 The UCB1400 is an AC97 audio codec.
880
881 To compile this driver as a module, choose M here: the
882 module will be called ucb1400_core.
883
884config MFD_PM8XXX
885 tristate "Qualcomm PM8xxx PMIC chips driver"
886 depends on (ARM || HEXAGON)
887 select IRQ_DOMAIN
888 select MFD_CORE
889 select REGMAP
890 help
891 If you say yes to this option, support will be included for the
892 built-in PM8xxx PMIC chips.
893
894 This is required if your board has a PM8xxx and uses its features,
895 such as: MPPs, GPIOs, regulators, interrupts, and PWM.
896
897 Say M here if you want to include support for PM8xxx chips as a
898 module. This will build a module called "pm8xxx-core".
899
900config MFD_QCOM_RPM
901 tristate "Qualcomm Resource Power Manager (RPM)"
902 depends on ARCH_QCOM && OF
903 help
904 If you say yes to this option, support will be included for the
905 Resource Power Manager system found in the Qualcomm 8660, 8960 and
906 8064 based devices.
907
908 This is required to access many regulators, clocks and bus
909 frequencies controlled by the RPM on these devices.
910
911 Say M here if you want to include support for the Qualcomm RPM as a
912 module. This will build a module called "qcom_rpm".
913
914config MFD_SPMI_PMIC
915 tristate "Qualcomm SPMI PMICs"
916 depends on ARCH_QCOM || COMPILE_TEST
917 depends on OF
918 depends on SPMI
919 select REGMAP_SPMI
920 help
921 This enables support for the Qualcomm SPMI PMICs.
922 These PMICs are currently used with the Snapdragon 800 series of
923 SoCs. Note, that this will only be useful paired with descriptions
924 of the independent functions as children nodes in the device tree.
925
926 Say M here if you want to include support for the SPMI PMIC
927 series as a module. The module will be called "qcom-spmi-pmic".
928
929config MFD_RDC321X
930 tristate "RDC R-321x southbridge"
931 select MFD_CORE
932 depends on PCI
933 help
934 Say yes here if you want to have support for the RDC R-321x SoC
935 southbridge which provides access to GPIOs and Watchdog using the
936 southbridge PCI device configuration space.
937
938config MFD_RTSX_PCI
939 tristate "Realtek PCI-E card reader"
940 depends on PCI
941 select MFD_CORE
942 help
943 This supports for Realtek PCI-Express card reader including rts5209,
944 rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
945 Realtek card reader supports access to many types of memory cards,
946 such as Memory Stick, Memory Stick Pro, Secure Digital and
947 MultiMediaCard.
948
949config MFD_RT5033
950 tristate "Richtek RT5033 Power Management IC"
951 depends on I2C
952 select MFD_CORE
953 select REGMAP_I2C
954 select REGMAP_IRQ
955 help
956 This driver provides for the Richtek RT5033 Power Management IC,
957 which includes the I2C driver and the Core APIs. This driver provides
958 common support for accessing the device. The device supports multiple
959 sub-devices like charger, fuel gauge, flash LED, current source,
960 LDO and Buck.
961
962config MFD_RTSX_USB
963 tristate "Realtek USB card reader"
964 depends on USB
965 select MFD_CORE
966 help
967 Select this option to get support for Realtek USB 2.0 card readers
968 including RTS5129, RTS5139, RTS5179 and RTS5170.
969 Realtek card reader supports access to many types of memory cards,
970 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
971
972config MFD_RC5T583
973 bool "Ricoh RC5T583 Power Management system device"
974 depends on I2C=y
975 select MFD_CORE
976 select REGMAP_I2C
977 help
978 Select this option to get support for the RICOH583 Power
979 Management system device.
980 This driver provides common support for accessing the device
981 through i2c interface. The device supports multiple sub-devices
982 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
983 Additional drivers must be enabled in order to use the
984 different functionality of the device.
985
986config MFD_RK808
987 tristate "Rockchip RK805/RK808/RK818 Power Management Chip"
988 depends on I2C && OF
989 select MFD_CORE
990 select REGMAP_I2C
991 select REGMAP_IRQ
992 help
993 If you say yes here you get support for the RK805, RK808 and RK818
994 Power Management chips.
995 This driver provides common support for accessing the device
996 through I2C interface. The device supports multiple sub-devices
997 including interrupts, RTC, LDO & DCDC regulators, and onkey.
998
999config MFD_RN5T618
1000 tristate "Ricoh RN5T567/618 PMIC"
1001 depends on I2C
1002 depends on OF
1003 select MFD_CORE
1004 select REGMAP_I2C
1005 help
1006 Say yes here to add support for the Ricoh RN5T567,
1007 RN5T618, RC5T619 PMIC.
1008 This driver provides common support for accessing the device,
1009 additional drivers must be enabled in order to use the
1010 functionality of the device.
1011
1012config MFD_SEC_CORE
1013 bool "SAMSUNG Electronics PMIC Series Support"
1014 depends on I2C=y
1015 select MFD_CORE
1016 select REGMAP_I2C
1017 select REGMAP_IRQ
1018 help
1019 Support for the Samsung Electronics MFD series.
1020 This driver provides common support for accessing the device,
1021 additional drivers must be enabled in order to use the functionality
1022 of the device
1023
1024config MFD_SI476X_CORE
1025 tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
1026 depends on I2C
1027 select MFD_CORE
1028 select REGMAP_I2C
1029 help
1030 This is the core driver for the SI476x series of AM/FM
1031 radio. This MFD driver connects the radio-si476x V4L2 module
1032 and the si476x audio codec.
1033
1034 To compile this driver as a module, choose M here: the
1035 module will be called si476x-core.
1036
1037config MFD_SM501
1038 tristate "Silicon Motion SM501"
1039 ---help---
1040 This is the core driver for the Silicon Motion SM501 multimedia
1041 companion chip. This device is a multifunction device which may
1042 provide numerous interfaces including USB host controller, USB gadget,
1043 asynchronous serial ports, audio functions, and a dual display video
1044 interface. The device may be connected by PCI or local bus with
1045 varying functions enabled.
1046
1047config MFD_SM501_GPIO
1048 bool "Export GPIO via GPIO layer"
1049 depends on MFD_SM501 && GPIOLIB
1050 ---help---
1051 This option uses the gpio library layer to export the 64 GPIO
1052 lines on the SM501. The platform data is used to supply the
1053 base number for the first GPIO line to register.
1054
1055config MFD_SKY81452
1056 tristate "Skyworks Solutions SKY81452"
1057 select MFD_CORE
1058 select REGMAP_I2C
1059 depends on I2C
1060 help
1061 This is the core driver for the Skyworks SKY81452 backlight and
1062 voltage regulator device.
1063
1064 This driver can also be built as a module. If so, the module
1065 will be called sky81452.
1066
1067config MFD_SMSC
1068 bool "SMSC ECE1099 series chips"
1069 depends on I2C=y
1070 select MFD_CORE
1071 select REGMAP_I2C
1072 help
1073 If you say yes here you get support for the
1074 ece1099 chips from SMSC.
1075
1076 To compile this driver as a module, choose M here: the
1077 module will be called smsc.
1078
1079config ABX500_CORE
1080 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
1081 default y if ARCH_U300 || ARCH_U8500 || COMPILE_TEST
1082 help
1083 Say yes here if you have the ABX500 Mixed Signal IC family
1084 chips. This core driver expose register access functions.
1085 Functionality specific drivers using these functions can
1086 remain unchanged when IC changes. Binding of the functions to
1087 actual register access is done by the IC core driver.
1088
1089config AB3100_CORE
1090 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
1091 depends on I2C=y && ABX500_CORE
1092 select MFD_CORE
1093 default y if ARCH_U300
1094 help
1095 Select this to enable the AB3100 Mixed Signal IC core
1096 functionality. This connects to a AB3100 on the I2C bus
1097 and expose a number of symbols needed for dependent devices
1098 to read and write registers and subscribe to events from
1099 this multi-functional IC. This is needed to use other features
1100 of the AB3100 such as battery-backed RTC, charging control,
1101 LEDs, vibrator, system power and temperature, power management
1102 and ALSA sound.
1103
1104config AB3100_OTP
1105 tristate "ST-Ericsson AB3100 OTP functions"
1106 depends on AB3100_CORE
1107 default y if AB3100_CORE
1108 help
1109 Select this to enable the AB3100 Mixed Signal IC OTP (one-time
1110 programmable memory) support. This exposes a sysfs file to read
1111 out OTP values.
1112
1113config AB8500_CORE
1114 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
1115 depends on ABX500_CORE && MFD_DB8500_PRCMU
1116 select POWER_SUPPLY
1117 select MFD_CORE
1118 select IRQ_DOMAIN
1119 help
1120 Select this option to enable access to AB8500 power management
1121 chip. This connects to U8500 either on the SSP/SPI bus (deprecated
1122 since hardware version v1.0) or the I2C bus via PRCMU. It also adds
1123 the irq_chip parts for handling the Mixed Signal chip events.
1124 This chip embeds various other multimedia funtionalities as well.
1125
1126config AB8500_DEBUG
1127 bool "Enable debug info via debugfs"
1128 depends on AB8500_GPADC && DEBUG_FS
1129 default y if DEBUG_FS
1130 help
1131 Select this option if you want debug information using the debug
1132 filesystem, debugfs.
1133
1134config AB8500_GPADC
1135 bool "ST-Ericsson AB8500 GPADC driver"
1136 depends on AB8500_CORE && REGULATOR_AB8500
1137 default y
1138 help
1139 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1140
1141config MFD_DB8500_PRCMU
1142 bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1143 depends on UX500_SOC_DB8500
1144 select MFD_CORE
1145 help
1146 Select this option to enable support for the DB8500 Power Reset
1147 and Control Management Unit. This is basically an autonomous
1148 system controller running an XP70 microprocessor, which is accessed
1149 through a register map.
1150
1151config MFD_STMPE
1152 bool "STMicroelectronics STMPE"
1153 depends on (I2C=y || SPI_MASTER=y)
1154 depends on OF
1155 select MFD_CORE
1156 help
1157 Support for the STMPE family of I/O Expanders from
1158 STMicroelectronics.
1159
1160 Currently supported devices are:
1161
1162 STMPE811: GPIO, Touchscreen
1163 STMPE1601: GPIO, Keypad
1164 STMPE1801: GPIO, Keypad
1165 STMPE2401: GPIO, Keypad
1166 STMPE2403: GPIO, Keypad
1167
1168 This driver provides common support for accessing the device,
1169 additional drivers must be enabled in order to use the functionality
1170 of the device. Currently available sub drivers are:
1171
1172 GPIO: stmpe-gpio
1173 Keypad: stmpe-keypad
1174 Touchscreen: stmpe-ts
1175
1176menu "STMicroelectronics STMPE Interface Drivers"
1177depends on MFD_STMPE
1178
1179config STMPE_I2C
1180 bool "STMicroelectronics STMPE I2C Interface"
1181 depends on I2C=y
1182 default y
1183 help
1184 This is used to enable I2C interface of STMPE
1185
1186config STMPE_SPI
1187 bool "STMicroelectronics STMPE SPI Interface"
1188 depends on SPI_MASTER
1189 help
1190 This is used to enable SPI interface of STMPE
1191endmenu
1192
1193config MFD_STA2X11
1194 bool "STMicroelectronics STA2X11"
1195 depends on STA2X11
1196 select MFD_CORE
1197 select REGMAP_MMIO
1198
1199config MFD_SUN6I_PRCM
1200 bool "Allwinner A31 PRCM controller"
1201 depends on ARCH_SUNXI
1202 select MFD_CORE
1203 help
1204 Support for the PRCM (Power/Reset/Clock Management) unit available
1205 in A31 SoC.
1206
1207config MFD_SYSCON
1208 bool "System Controller Register R/W Based on Regmap"
1209 select REGMAP_MMIO
1210 help
1211 Select this option to enable accessing system control registers
1212 via regmap.
1213
1214config MFD_DAVINCI_VOICECODEC
1215 tristate
1216 select MFD_CORE
1217 select REGMAP_MMIO
1218
1219config MFD_TI_AM335X_TSCADC
1220 tristate "TI ADC / Touch Screen chip support"
1221 select MFD_CORE
1222 select REGMAP
1223 select REGMAP_MMIO
1224 help
1225 If you say yes here you get support for Texas Instruments series
1226 of Touch Screen /ADC chips.
1227 To compile this driver as a module, choose M here: the
1228 module will be called ti_am335x_tscadc.
1229
1230config MFD_DM355EVM_MSP
1231 bool "TI DaVinci DM355 EVM microcontroller"
1232 depends on I2C=y && MACH_DAVINCI_DM355_EVM
1233 help
1234 This driver supports the MSP430 microcontroller used on these
1235 boards. MSP430 firmware manages resets and power sequencing,
1236 inputs from buttons and the IR remote, LEDs, an RTC, and more.
1237
1238config MFD_LP3943
1239 tristate "TI/National Semiconductor LP3943 MFD Driver"
1240 depends on I2C
1241 select MFD_CORE
1242 select REGMAP_I2C
1243 help
1244 Support for the TI/National Semiconductor LP3943.
1245 This driver consists of GPIO and PWM drivers.
1246 With these functionalities, it can be used for LED string control or
1247 general usage such like a GPIO controller and a PWM controller.
1248
1249config MFD_LP8788
1250 bool "TI LP8788 Power Management Unit Driver"
1251 depends on I2C=y
1252 select MFD_CORE
1253 select REGMAP_I2C
1254 select IRQ_DOMAIN
1255 help
1256 TI LP8788 PMU supports regulators, battery charger, RTC,
1257 ADC, backlight driver and current sinks.
1258
1259config MFD_TI_LMU
1260 tristate "TI Lighting Management Unit driver"
1261 depends on I2C
1262 select MFD_CORE
1263 select REGMAP_I2C
1264 help
1265 Say yes here to enable support for TI LMU chips.
1266
1267 TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
1268 It consists of backlight, LED and regulator driver.
1269 It provides consistent device controls for lighting functions.
1270
1271config MFD_OMAP_USB_HOST
1272 bool "TI OMAP USBHS core and TLL driver"
1273 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1274 default y
1275 help
1276 This is the core driver for the OAMP EHCI and OHCI drivers.
1277 This MFD driver does the required setup functionalities for
1278 OMAP USB Host drivers.
1279
1280config MFD_PALMAS
1281 bool "TI Palmas series chips"
1282 select MFD_CORE
1283 select REGMAP_I2C
1284 select REGMAP_IRQ
1285 depends on I2C=y
1286 help
1287 If you say yes here you get support for the Palmas
1288 series of PMIC chips from Texas Instruments.
1289
1290config TPS6105X
1291 tristate "TI TPS61050/61052 Boost Converters"
1292 depends on I2C
1293 select REGMAP_I2C
1294 select REGULATOR
1295 select MFD_CORE
1296 select REGULATOR_FIXED_VOLTAGE
1297 help
1298 This option enables a driver for the TP61050/TPS61052
1299 high-power "white LED driver". This boost converter is
1300 sometimes used for other things than white LEDs, and
1301 also contains a GPIO pin.
1302
1303config TPS65010
1304 tristate "TI TPS6501x Power Management chips"
1305 depends on I2C && GPIOLIB
1306 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1307 help
1308 If you say yes here you get support for the TPS6501x series of
1309 Power Management chips. These include voltage regulators,
1310 lithium ion/polymer battery charging, and other features that
1311 are often used in portable devices like cell phones and cameras.
1312
1313 This driver can also be built as a module. If so, the module
1314 will be called tps65010.
1315
1316config TPS6507X
1317 tristate "TI TPS6507x Power Management / Touch Screen chips"
1318 select MFD_CORE
1319 depends on I2C
1320 help
1321 If you say yes here you get support for the TPS6507x series of
1322 Power Management / Touch Screen chips. These include voltage
1323 regulators, lithium ion/polymer battery charging, touch screen
1324 and other features that are often used in portable devices.
1325 This driver can also be built as a module. If so, the module
1326 will be called tps6507x.
1327
1328config MFD_TPS65086
1329 tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1330 select MFD_CORE
1331 select REGMAP
1332 select REGMAP_IRQ
1333 select REGMAP_I2C
1334 depends on I2C
1335 help
1336 If you say yes here you get support for the TPS65086 series of
1337 Power Management chips.
1338 This driver provides common support for accessing the device,
1339 additional drivers must be enabled in order to use the
1340 functionality of the device.
1341
1342config TPS65911_COMPARATOR
1343 tristate
1344
1345config MFD_TPS65090
1346 bool "TI TPS65090 Power Management chips"
1347 depends on I2C=y
1348 select MFD_CORE
1349 select REGMAP_I2C
1350 select REGMAP_IRQ
1351 help
1352 If you say yes here you get support for the TPS65090 series of
1353 Power Management chips.
1354 This driver provides common support for accessing the device,
1355 additional drivers must be enabled in order to use the
1356 functionality of the device.
1357
1358config MFD_TPS65217
1359 tristate "TI TPS65217 Power Management / White LED chips"
1360 depends on I2C
1361 select MFD_CORE
1362 select REGMAP_I2C
1363 select IRQ_DOMAIN
1364 help
1365 If you say yes here you get support for the TPS65217 series of
1366 Power Management / White LED chips.
1367 These include voltage regulators, lithium ion/polymer battery
1368 charger, wled and other features that are often used in portable
1369 devices.
1370
1371 This driver can also be built as a module. If so, the module
1372 will be called tps65217.
1373
1374config MFD_TPS68470
1375 bool "TI TPS68470 Power Management / LED chips"
1376 depends on ACPI && I2C=y
1377 select MFD_CORE
1378 select REGMAP_I2C
1379 select I2C_DESIGNWARE_PLATFORM
1380 help
1381 If you say yes here you get support for the TPS68470 series of
1382 Power Management / LED chips.
1383
1384 These include voltage regulators, LEDs and other features
1385 that are often used in portable devices.
1386
1387 This option is a bool as it provides an ACPI operation
1388 region, which must be available before any of the devices
1389 using this are probed. This option also configures the
1390 designware-i2c driver to be built-in, for the same reason.
1391
1392config MFD_TI_LP873X
1393 tristate "TI LP873X Power Management IC"
1394 depends on I2C
1395 select MFD_CORE
1396 select REGMAP_I2C
1397 help
1398 If you say yes here then you get support for the LP873X series of
1399 Power Management Integrated Circuits (PMIC).
1400 These include voltage regulators, thermal protection, configurable
1401 General Purpose Outputs (GPO) that are used in portable devices.
1402
1403 This driver can also be built as a module. If so, the module
1404 will be called lp873x.
1405
1406config MFD_TI_LP87565
1407 tristate "TI LP87565 Power Management IC"
1408 depends on I2C && OF
1409 select MFD_CORE
1410 select REGMAP_I2C
1411 help
1412 If you say yes here then you get support for the LP87565 series of
1413 Power Management Integrated Circuits (PMIC).
1414 These include voltage regulators, thermal protection, configurable
1415 General Purpose Outputs (GPO) that are used in portable devices.
1416
1417 This driver can also be built as a module. If so, the module
1418 will be called lp87565.
1419
1420config MFD_TPS65218
1421 tristate "TI TPS65218 Power Management chips"
1422 depends on I2C
1423 select MFD_CORE
1424 select REGMAP_I2C
1425 select REGMAP_IRQ
1426 help
1427 If you say yes here you get support for the TPS65218 series of
1428 Power Management chips.
1429 These include voltage regulators, gpio and other features
1430 that are often used in portable devices. Only regulator
1431 component is currently supported.
1432
1433 This driver can also be built as a module. If so, the module
1434 will be called tps65218.
1435
1436config MFD_TPS6586X
1437 bool "TI TPS6586x Power Management chips"
1438 depends on I2C=y
1439 select MFD_CORE
1440 select REGMAP_I2C
1441 help
1442 If you say yes here you get support for the TPS6586X series of
1443 Power Management chips.
1444 This driver provides common support for accessing the device,
1445 additional drivers must be enabled in order to use the
1446 functionality of the device.
1447
1448 This driver can also be built as a module. If so, the module
1449 will be called tps6586x.
1450
1451config MFD_TPS65910
1452 bool "TI TPS65910 Power Management chip"
1453 depends on I2C=y
1454 depends on GPIOLIB || COMPILE_TEST
1455 select MFD_CORE
1456 select REGMAP_I2C
1457 select REGMAP_IRQ
1458 select IRQ_DOMAIN
1459 help
1460 if you say yes here you get support for the TPS65910 series of
1461 Power Management chips.
1462
1463config MFD_TPS65912
1464 tristate
1465 select MFD_CORE
1466 select REGMAP
1467 select REGMAP_IRQ
1468
1469config MFD_TPS65912_I2C
1470 tristate "TI TPS65912 Power Management chip with I2C"
1471 select MFD_TPS65912
1472 select REGMAP_I2C
1473 depends on I2C
1474 help
1475 If you say yes here you get support for the TPS65912 series of
1476 PM chips with I2C interface.
1477
1478config MFD_TPS65912_SPI
1479 tristate "TI TPS65912 Power Management chip with SPI"
1480 select MFD_TPS65912
1481 select REGMAP_SPI
1482 depends on SPI_MASTER
1483 help
1484 If you say yes here you get support for the TPS65912 series of
1485 PM chips with SPI interface.
1486
1487config MFD_TPS80031
1488 bool "TI TPS80031/TPS80032 Power Management chips"
1489 depends on I2C=y
1490 select MFD_CORE
1491 select REGMAP_I2C
1492 select REGMAP_IRQ
1493 help
1494 If you say yes here you get support for the Texas Instruments
1495 TPS80031/ TPS80032 Fully Integrated Power Management with Power
1496 Path and Battery Charger. The device provides five configurable
1497 step-down converters, 11 general purpose LDOs, USB OTG Module,
1498 ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1499 Power Path from USB, 32K clock generator.
1500
1501config TWL4030_CORE
1502 bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1503 depends on I2C=y
1504 select IRQ_DOMAIN
1505 select REGMAP_I2C
1506 help
1507 Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1508 This core driver provides register access and IRQ handling
1509 facilities, and registers devices for the various functions
1510 so that function-specific drivers can bind to them.
1511
1512 These multi-function chips are found on many OMAP2 and OMAP3
1513 boards, providing power management, RTC, GPIO, keypad, a
1514 high speed USB OTG transceiver, an audio codec (on most
1515 versions) and many other features.
1516
1517config TWL4030_POWER
1518 bool "TI TWL4030 power resources"
1519 depends on TWL4030_CORE && ARM
1520 help
1521 Say yes here if you want to use the power resources on the
1522 TWL4030 family chips. Most of these resources are regulators,
1523 which have a separate driver; some are control signals, such
1524 as clock request handshaking.
1525
1526 This driver uses board-specific data to initialize the resources
1527 and load scripts controlling which resources are switched off/on
1528 or reset when a sleep, wakeup or warm reset event occurs.
1529
1530config MFD_TWL4030_AUDIO
1531 bool "TI TWL4030 Audio"
1532 depends on TWL4030_CORE
1533 select MFD_CORE
1534 default n
1535
1536config TWL6040_CORE
1537 bool "TI TWL6040 audio codec"
1538 depends on I2C=y
1539 select MFD_CORE
1540 select REGMAP_I2C
1541 select REGMAP_IRQ
1542 default n
1543 help
1544 Say yes here if you want support for Texas Instruments TWL6040 audio
1545 codec.
1546 This driver provides common support for accessing the device,
1547 additional drivers must be enabled in order to use the
1548 functionality of the device (audio, vibra).
1549
1550config MENELAUS
1551 bool "TI TWL92330/Menelaus PM chip"
1552 depends on I2C=y && ARCH_OMAP2
1553 help
1554 If you say yes here you get support for the Texas Instruments
1555 TWL92330/Menelaus Power Management chip. This include voltage
1556 regulators, Dual slot memory card transceivers, real-time clock
1557 and other features that are often used in portable devices like
1558 cell phones and PDAs.
1559
1560config MFD_WL1273_CORE
1561 tristate "TI WL1273 FM radio"
1562 depends on I2C
1563 select MFD_CORE
1564 default n
1565 help
1566 This is the core driver for the TI WL1273 FM radio. This MFD
1567 driver connects the radio-wl1273 V4L2 module and the wl1273
1568 audio codec.
1569
1570config MFD_LM3533
1571 tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1572 depends on I2C
1573 select MFD_CORE
1574 select REGMAP_I2C
1575 help
1576 Say yes here to enable support for National Semiconductor / TI
1577 LM3533 Lighting Power chips.
1578
1579 This driver provides common support for accessing the device;
1580 additional drivers must be enabled in order to use the LED,
1581 backlight or ambient-light-sensor functionality of the device.
1582
1583config MFD_TIMBERDALE
1584 tristate "Timberdale FPGA"
1585 select MFD_CORE
1586 depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1587 ---help---
1588 This is the core driver for the timberdale FPGA. This device is a
1589 multifunction device which exposes numerous platform devices.
1590
1591 The timberdale FPGA can be found on the Intel Atom development board
1592 for in-vehicle infontainment, called Russellville.
1593
1594config MFD_TC3589X
1595 bool "Toshiba TC35892 and variants"
1596 depends on I2C=y
1597 depends on OF
1598 select MFD_CORE
1599 help
1600 Support for the Toshiba TC35892 and variants I/O Expander.
1601
1602 This driver provides common support for accessing the device,
1603 additional drivers must be enabled in order to use the
1604 functionality of the device.
1605
1606config MFD_TMIO
1607 bool
1608 default n
1609
1610config MFD_T7L66XB
1611 bool "Toshiba T7L66XB"
1612 depends on ARM && HAVE_CLK
1613 select MFD_CORE
1614 select MFD_TMIO
1615 help
1616 Support for Toshiba Mobile IO Controller T7L66XB
1617
1618config MFD_TC6387XB
1619 bool "Toshiba TC6387XB"
1620 depends on ARM && HAVE_CLK
1621 select MFD_CORE
1622 select MFD_TMIO
1623 help
1624 Support for Toshiba Mobile IO Controller TC6387XB
1625
1626config MFD_TC6393XB
1627 bool "Toshiba TC6393XB"
1628 depends on ARM && HAVE_CLK
1629 select GPIOLIB
1630 select MFD_CORE
1631 select MFD_TMIO
1632 help
1633 Support for Toshiba Mobile IO Controller TC6393XB
1634
1635config MFD_VX855
1636 tristate "VIA VX855/VX875 integrated south bridge"
1637 depends on PCI
1638 select MFD_CORE
1639 help
1640 Say yes here to enable support for various functions of the
1641 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1642 and/or vx855_gpio drivers for this to do anything useful.
1643
1644config MFD_ARIZONA
1645 select REGMAP
1646 select REGMAP_IRQ
1647 select MFD_CORE
1648 bool
1649
1650config MFD_ARIZONA_I2C
1651 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1652 select MFD_ARIZONA
1653 select REGMAP_I2C
1654 depends on I2C
1655 help
1656 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1657 audio SoC core functionality controlled via I2C.
1658
1659config MFD_ARIZONA_SPI
1660 tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1661 select MFD_ARIZONA
1662 select REGMAP_SPI
1663 depends on SPI_MASTER
1664 help
1665 Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1666 audio SoC core functionality controlled via SPI.
1667
1668config MFD_CS47L24
1669 bool "Cirrus Logic CS47L24 and WM1831"
1670 depends on MFD_ARIZONA
1671 help
1672 Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1673
1674config MFD_WM5102
1675 bool "Wolfson Microelectronics WM5102"
1676 depends on MFD_ARIZONA
1677 help
1678 Support for Wolfson Microelectronics WM5102 low power audio SoC
1679
1680config MFD_WM5110
1681 bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1682 depends on MFD_ARIZONA
1683 help
1684 Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1685 low power audio SoC
1686
1687config MFD_WM8997
1688 bool "Wolfson Microelectronics WM8997"
1689 depends on MFD_ARIZONA
1690 help
1691 Support for Wolfson Microelectronics WM8997 low power audio SoC
1692
1693config MFD_WM8998
1694 bool "Wolfson Microelectronics WM8998"
1695 depends on MFD_ARIZONA
1696 help
1697 Support for Wolfson Microelectronics WM8998 low power audio SoC
1698
1699config MFD_WM8400
1700 bool "Wolfson Microelectronics WM8400"
1701 select MFD_CORE
1702 depends on I2C=y
1703 select REGMAP_I2C
1704 help
1705 Support for the Wolfson Microelecronics WM8400 PMIC and audio
1706 CODEC. This driver provides common support for accessing
1707 the device, additional drivers must be enabled in order to use
1708 the functionality of the device.
1709
1710config MFD_WM831X
1711 bool
1712
1713config MFD_WM831X_I2C
1714 bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1715 select MFD_CORE
1716 select MFD_WM831X
1717 select REGMAP_I2C
1718 select IRQ_DOMAIN
1719 depends on I2C=y
1720 help
1721 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1722 when controlled using I2C. This driver provides common support
1723 for accessing the device, additional drivers must be enabled in
1724 order to use the functionality of the device.
1725
1726config MFD_WM831X_SPI
1727 bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1728 select MFD_CORE
1729 select MFD_WM831X
1730 select REGMAP_SPI
1731 select IRQ_DOMAIN
1732 depends on SPI_MASTER
1733 help
1734 Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1735 when controlled using SPI. This driver provides common support
1736 for accessing the device, additional drivers must be enabled in
1737 order to use the functionality of the device.
1738
1739config MFD_WM8350
1740 bool
1741
1742config MFD_WM8350_I2C
1743 bool "Wolfson Microelectronics WM8350 with I2C"
1744 select MFD_WM8350
1745 select REGMAP_I2C
1746 depends on I2C=y
1747 help
1748 The WM8350 is an integrated audio and power management
1749 subsystem with watchdog and RTC functionality for embedded
1750 systems. This option enables core support for the WM8350 with
1751 I2C as the control interface. Additional options must be
1752 selected to enable support for the functionality of the chip.
1753
1754config MFD_WM8994
1755 tristate "Wolfson Microelectronics WM8994"
1756 select MFD_CORE
1757 select REGMAP_I2C
1758 select REGMAP_IRQ
1759 depends on I2C
1760 help
1761 The WM8994 is a highly integrated hi-fi CODEC designed for
1762 smartphone applications. As well as audio functionality it
1763 has on board GPIO and regulator functionality which is
1764 supported via the relevant subsystems. This driver provides
1765 core support for the WM8994, in order to use the actual
1766 functionaltiy of the device other drivers must be enabled.
1767
1768config MFD_STW481X
1769 tristate "Support for ST Microelectronics STw481x"
1770 depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1771 select REGMAP_I2C
1772 select MFD_CORE
1773 help
1774 Select this option to enable the STw481x chip driver used
1775 in various ST Microelectronics and ST-Ericsson embedded
1776 Nomadik series.
1777
1778config MFD_STM32_LPTIMER
1779 tristate "Support for STM32 Low-Power Timer"
1780 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1781 select MFD_CORE
1782 select REGMAP
1783 select REGMAP_MMIO
1784 help
1785 Select this option to enable STM32 Low-Power Timer driver
1786 used for PWM, IIO Trigger, IIO Encoder and Counter. Shared
1787 resources are also dealt with here.
1788
1789 To compile this driver as a module, choose M here: the
1790 module will be called stm32-lptimer.
1791
1792config MFD_STM32_TIMERS
1793 tristate "Support for STM32 Timers"
1794 depends on (ARCH_STM32 && OF) || COMPILE_TEST
1795 select MFD_CORE
1796 select REGMAP
1797 select REGMAP_MMIO
1798 help
1799 Select this option to enable STM32 timers driver used
1800 for PWM and IIO Timer. This driver allow to share the
1801 registers between the others drivers.
1802
1803menu "Multimedia Capabilities Port drivers"
1804 depends on ARCH_SA1100
1805
1806config MCP
1807 tristate
1808
1809# Interface drivers
1810config MCP_SA11X0
1811 tristate "Support SA11x0 MCP interface"
1812 depends on ARCH_SA1100
1813 select MCP
1814
1815# Chip drivers
1816config MCP_UCB1200
1817 tristate "Support for UCB1200 / UCB1300"
1818 depends on MCP_SA11X0
1819 select MCP
1820
1821config MCP_UCB1200_TS
1822 tristate "Touchscreen interface support"
1823 depends on MCP_UCB1200 && INPUT
1824
1825endmenu
1826
1827config MFD_VEXPRESS_SYSREG
1828 bool "Versatile Express System Registers"
1829 depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1830 default y
1831 select CLKSRC_MMIO
1832 select GPIO_GENERIC_PLATFORM
1833 select MFD_CORE
1834 select MFD_SYSCON
1835 help
1836 System Registers are the platform configuration block
1837 on the ARM Ltd. Versatile Express board.
1838
1839endmenu
1840endif