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