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