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