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