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_88PM860X 14 bool "Support Marvell 88PM8606/88PM8607" 15 depends on I2C=y && GENERIC_HARDIRQS 16 select REGMAP_I2C 17 select MFD_CORE 18 help 19 This supports for Marvell 88PM8606/88PM8607 Power Management IC. 20 This includes the I2C driver and the core APIs _only_, you have to 21 select individual components like voltage regulators, RTC and 22 battery-charger under the corresponding menus. 23 24config MFD_88PM800 25 tristate "Support Marvell 88PM800" 26 depends on I2C=y && GENERIC_HARDIRQS 27 select REGMAP_I2C 28 select REGMAP_IRQ 29 select MFD_CORE 30 help 31 This supports for Marvell 88PM800 Power Management IC. 32 This includes the I2C driver and the core APIs _only_, you have to 33 select individual components like voltage regulators, RTC and 34 battery-charger under the corresponding menus. 35 36config MFD_88PM805 37 tristate "Support Marvell 88PM805" 38 depends on I2C=y && GENERIC_HARDIRQS 39 select REGMAP_I2C 40 select REGMAP_IRQ 41 select MFD_CORE 42 help 43 This supports for Marvell 88PM805 Power Management IC. This includes 44 the I2C driver and the core APIs _only_, you have to select individual 45 components like codec device, headset/Mic device under the 46 corresponding menus. 47 48config MFD_SM501 49 tristate "Support for Silicon Motion SM501" 50 ---help--- 51 This is the core driver for the Silicon Motion SM501 multimedia 52 companion chip. This device is a multifunction device which may 53 provide numerous interfaces including USB host controller, USB gadget, 54 asynchronous serial ports, audio functions, and a dual display video 55 interface. The device may be connected by PCI or local bus with 56 varying functions enabled. 57 58config MFD_SM501_GPIO 59 bool "Export GPIO via GPIO layer" 60 depends on MFD_SM501 && GPIOLIB 61 ---help--- 62 This option uses the gpio library layer to export the 64 GPIO 63 lines on the SM501. The platform data is used to supply the 64 base number for the first GPIO line to register. 65 66config MFD_RTSX_PCI 67 tristate "Support for Realtek PCI-E card reader" 68 depends on PCI 69 select MFD_CORE 70 help 71 This supports for Realtek PCI-Express card reader including rts5209, 72 rts5229, rtl8411, etc. Realtek card reader supports access to many 73 types of memory cards, such as Memory Stick, Memory Stick Pro, 74 Secure Digital and MultiMediaCard. 75 76config MFD_ASIC3 77 bool "Support for Compaq ASIC3" 78 depends on GENERIC_HARDIRQS && GPIOLIB && ARM 79 select MFD_CORE 80 ---help--- 81 This driver supports the ASIC3 multifunction chip found on many 82 PDAs (mainly iPAQ and HTC based ones) 83 84config MFD_DAVINCI_VOICECODEC 85 tristate 86 select MFD_CORE 87 88config MFD_DM355EVM_MSP 89 bool "DaVinci DM355 EVM microcontroller" 90 depends on I2C=y && MACH_DAVINCI_DM355_EVM 91 help 92 This driver supports the MSP430 microcontroller used on these 93 boards. MSP430 firmware manages resets and power sequencing, 94 inputs from buttons and the IR remote, LEDs, an RTC, and more. 95 96config MFD_TI_SSP 97 tristate "TI Sequencer Serial Port support" 98 depends on ARCH_DAVINCI_TNETV107X 99 select MFD_CORE 100 ---help--- 101 Say Y here if you want support for the Sequencer Serial Port 102 in a Texas Instruments TNETV107X SoC. 103 104 To compile this driver as a module, choose M here: the 105 module will be called ti-ssp. 106 107config HTC_EGPIO 108 bool "HTC EGPIO support" 109 depends on GENERIC_HARDIRQS && GPIOLIB && ARM 110 help 111 This driver supports the CPLD egpio chip present on 112 several HTC phones. It provides basic support for input 113 pins, output pins, and irqs. 114 115config HTC_PASIC3 116 tristate "HTC PASIC3 LED/DS1WM chip support" 117 select MFD_CORE 118 help 119 This core driver provides register access for the LED/DS1WM 120 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and 121 HTC Magician devices, respectively. Actual functionality is 122 handled by the leds-pasic3 and ds1wm drivers. 123 124config HTC_I2CPLD 125 bool "HTC I2C PLD chip support" 126 depends on I2C=y && GPIOLIB 127 help 128 If you say yes here you get support for the supposed CPLD 129 found on omap850 HTC devices like the HTC Wizard and HTC Herald. 130 This device provides input and output GPIOs through an I2C 131 interface to one or more sub-chips. 132 133config UCB1400_CORE 134 tristate "Philips UCB1400 Core driver" 135 depends on AC97_BUS 136 depends on GPIOLIB 137 help 138 This enables support for the Philips UCB1400 core functions. 139 The UCB1400 is an AC97 audio codec. 140 141 To compile this driver as a module, choose M here: the 142 module will be called ucb1400_core. 143 144config MFD_LM3533 145 tristate "LM3533 Lighting Power chip" 146 depends on I2C 147 select MFD_CORE 148 select REGMAP_I2C 149 help 150 Say yes here to enable support for National Semiconductor / TI 151 LM3533 Lighting Power chips. 152 153 This driver provides common support for accessing the device; 154 additional drivers must be enabled in order to use the LED, 155 backlight or ambient-light-sensor functionality of the device. 156 157config TPS6105X 158 tristate "TPS61050/61052 Boost Converters" 159 depends on I2C 160 select REGULATOR 161 select MFD_CORE 162 select REGULATOR_FIXED_VOLTAGE 163 help 164 This option enables a driver for the TP61050/TPS61052 165 high-power "white LED driver". This boost converter is 166 sometimes used for other things than white LEDs, and 167 also contains a GPIO pin. 168 169config TPS65010 170 tristate "TPS6501x Power Management chips" 171 depends on I2C && GPIOLIB 172 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK 173 help 174 If you say yes here you get support for the TPS6501x series of 175 Power Management chips. These include voltage regulators, 176 lithium ion/polymer battery charging, and other features that 177 are often used in portable devices like cell phones and cameras. 178 179 This driver can also be built as a module. If so, the module 180 will be called tps65010. 181 182config TPS6507X 183 tristate "TPS6507x Power Management / Touch Screen chips" 184 select MFD_CORE 185 depends on I2C 186 help 187 If you say yes here you get support for the TPS6507x series of 188 Power Management / Touch Screen chips. These include voltage 189 regulators, lithium ion/polymer battery charging, touch screen 190 and other features that are often used in portable devices. 191 This driver can also be built as a module. If so, the module 192 will be called tps6507x. 193 194config MFD_TPS65217 195 tristate "TPS65217 Power Management / White LED chips" 196 depends on I2C 197 select MFD_CORE 198 select REGMAP_I2C 199 help 200 If you say yes here you get support for the TPS65217 series of 201 Power Management / White LED chips. 202 These include voltage regulators, lithium ion/polymer battery 203 charger, wled and other features that are often used in portable 204 devices. 205 206 This driver can also be built as a module. If so, the module 207 will be called tps65217. 208 209config MFD_TPS6586X 210 bool "TPS6586x Power Management chips" 211 depends on I2C=y && GENERIC_HARDIRQS 212 select MFD_CORE 213 select REGMAP_I2C 214 depends on REGULATOR 215 help 216 If you say yes here you get support for the TPS6586X series of 217 Power Management chips. 218 This driver provides common support for accessing the device, 219 additional drivers must be enabled in order to use the 220 functionality of the device. 221 222 This driver can also be built as a module. If so, the module 223 will be called tps6586x. 224 225config MFD_TPS65910 226 bool "TPS65910 Power Management chip" 227 depends on I2C=y && GPIOLIB 228 select MFD_CORE 229 select REGMAP_I2C 230 select IRQ_DOMAIN 231 help 232 if you say yes here you get support for the TPS65910 series of 233 Power Management chips. 234 235config MFD_TPS65912 236 bool 237 depends on GPIOLIB 238 239config MFD_TPS65912_I2C 240 bool "TPS65912 Power Management chip with I2C" 241 select MFD_CORE 242 select MFD_TPS65912 243 depends on I2C=y && GPIOLIB 244 help 245 If you say yes here you get support for the TPS65912 series of 246 PM chips with I2C interface. 247 248config MFD_TPS65912_SPI 249 bool "TPS65912 Power Management chip with SPI" 250 select MFD_CORE 251 select MFD_TPS65912 252 depends on SPI_MASTER && GPIOLIB 253 help 254 If you say yes here you get support for the TPS65912 series of 255 PM chips with SPI interface. 256 257config MENELAUS 258 bool "Texas Instruments TWL92330/Menelaus PM chip" 259 depends on I2C=y && ARCH_OMAP2 260 help 261 If you say yes here you get support for the Texas Instruments 262 TWL92330/Menelaus Power Management chip. This include voltage 263 regulators, Dual slot memory card transceivers, real-time clock 264 and other features that are often used in portable devices like 265 cell phones and PDAs. 266 267config TWL4030_CORE 268 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support" 269 depends on I2C=y && GENERIC_HARDIRQS 270 select IRQ_DOMAIN 271 help 272 Say yes here if you have TWL4030 / TWL6030 family chip on your board. 273 This core driver provides register access and IRQ handling 274 facilities, and registers devices for the various functions 275 so that function-specific drivers can bind to them. 276 277 These multi-function chips are found on many OMAP2 and OMAP3 278 boards, providing power management, RTC, GPIO, keypad, a 279 high speed USB OTG transceiver, an audio codec (on most 280 versions) and many other features. 281 282config TWL4030_MADC 283 tristate "Texas Instruments TWL4030 MADC" 284 depends on TWL4030_CORE 285 help 286 This driver provides support for triton TWL4030-MADC. The 287 driver supports both RT and SW conversion methods. 288 289 This driver can be built as a module. If so it will be 290 named twl4030-madc 291 292config TWL4030_POWER 293 bool "Support power resources on TWL4030 family chips" 294 depends on TWL4030_CORE && ARM 295 help 296 Say yes here if you want to use the power resources on the 297 TWL4030 family chips. Most of these resources are regulators, 298 which have a separate driver; some are control signals, such 299 as clock request handshaking. 300 301 This driver uses board-specific data to initialize the resources 302 and load scripts controlling which resources are switched off/on 303 or reset when a sleep, wakeup or warm reset event occurs. 304 305config MFD_TWL4030_AUDIO 306 bool 307 depends on TWL4030_CORE 308 select MFD_CORE 309 default n 310 311config TWL6040_CORE 312 bool "Support for TWL6040 audio codec" 313 depends on I2C=y && GENERIC_HARDIRQS 314 select MFD_CORE 315 select REGMAP_I2C 316 select IRQ_DOMAIN 317 default n 318 help 319 Say yes here if you want support for Texas Instruments TWL6040 audio 320 codec. 321 This driver provides common support for accessing the device, 322 additional drivers must be enabled in order to use the 323 functionality of the device (audio, vibra). 324 325config MFD_STMPE 326 bool "Support STMicroelectronics STMPE" 327 depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS 328 select MFD_CORE 329 help 330 Support for the STMPE family of I/O Expanders from 331 STMicroelectronics. 332 333 Currently supported devices are: 334 335 STMPE811: GPIO, Touchscreen 336 STMPE1601: GPIO, Keypad 337 STMPE2401: GPIO, Keypad 338 STMPE2403: GPIO, Keypad 339 340 This driver provides common support for accessing the device, 341 additional drivers must be enabled in order to use the functionality 342 of the device. Currently available sub drivers are: 343 344 GPIO: stmpe-gpio 345 Keypad: stmpe-keypad 346 Touchscreen: stmpe-ts 347 348menu "STMPE Interface Drivers" 349depends on MFD_STMPE 350 351config STMPE_I2C 352 bool "STMPE I2C Inteface" 353 depends on I2C=y 354 default y 355 help 356 This is used to enable I2C interface of STMPE 357 358config STMPE_SPI 359 bool "STMPE SPI Inteface" 360 depends on SPI_MASTER 361 help 362 This is used to enable SPI interface of STMPE 363endmenu 364 365config MFD_TC3589X 366 bool "Support Toshiba TC35892 and variants" 367 depends on I2C=y && GENERIC_HARDIRQS 368 select MFD_CORE 369 help 370 Support for the Toshiba TC35892 and variants I/O Expander. 371 372 This driver provides common support for accessing the device, 373 additional drivers must be enabled in order to use the 374 functionality of the device. 375 376config MFD_TMIO 377 bool 378 default n 379 380config MFD_T7L66XB 381 bool "Support Toshiba T7L66XB" 382 depends on ARM && HAVE_CLK 383 select MFD_CORE 384 select MFD_TMIO 385 help 386 Support for Toshiba Mobile IO Controller T7L66XB 387 388config MFD_SMSC 389 bool "Support for the SMSC ECE1099 series chips" 390 depends on I2C=y 391 select MFD_CORE 392 select REGMAP_I2C 393 help 394 If you say yes here you get support for the 395 ece1099 chips from SMSC. 396 397 To compile this driver as a module, choose M here: the 398 module will be called smsc. 399 400config MFD_TC6387XB 401 bool "Support Toshiba TC6387XB" 402 depends on ARM && HAVE_CLK 403 select MFD_CORE 404 select MFD_TMIO 405 help 406 Support for Toshiba Mobile IO Controller TC6387XB 407 408config MFD_TC6393XB 409 bool "Support Toshiba TC6393XB" 410 depends on ARM && HAVE_CLK 411 select GPIOLIB 412 select MFD_CORE 413 select MFD_TMIO 414 help 415 Support for Toshiba Mobile IO Controller TC6393XB 416 417config PMIC_DA903X 418 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" 419 depends on I2C=y 420 help 421 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a 422 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC 423 usually found on PXA processors-based platforms. This includes 424 the I2C driver and the core APIs _only_, you have to select 425 individual components like LCD backlight, voltage regulators, 426 LEDs and battery-charger under the corresponding menus. 427 428config PMIC_DA9052 429 bool 430 select MFD_CORE 431 432config MFD_DA9052_SPI 433 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI" 434 select REGMAP_SPI 435 select REGMAP_IRQ 436 select PMIC_DA9052 437 depends on SPI_MASTER=y 438 help 439 Support for the Dialog Semiconductor DA9052 PMIC 440 when controlled using SPI. This driver provides common support 441 for accessing the device, additional drivers must be enabled in 442 order to use the functionality of the device. 443 444config MFD_DA9052_I2C 445 bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C" 446 select REGMAP_I2C 447 select REGMAP_IRQ 448 select PMIC_DA9052 449 depends on I2C=y 450 help 451 Support for the Dialog Semiconductor DA9052 PMIC 452 when controlled using I2C. This driver provides common support 453 for accessing the device, additional drivers must be enabled in 454 order to use the functionality of the device. 455 456config MFD_DA9055 457 bool "Dialog Semiconductor DA9055 PMIC Support" 458 select REGMAP_I2C 459 select REGMAP_IRQ 460 select PMIC_DA9055 461 select MFD_CORE 462 depends on I2C=y 463 help 464 Say yes here for support of Dialog Semiconductor DA9055. This is 465 a Power Management IC. This driver provides common support for 466 accessing the device as well as the I2C interface to the chip itself. 467 Additional drivers must be enabled in order to use the functionality 468 of the device. 469 470 This driver can be built as a module. If built as a module it will be 471 called "da9055" 472 473config PMIC_ADP5520 474 bool "Analog Devices ADP5520/01 MFD PMIC Core Support" 475 depends on I2C=y 476 help 477 Say yes here to add support for Analog Devices AD5520 and ADP5501, 478 Multifunction Power Management IC. This includes 479 the I2C driver and the core APIs _only_, you have to select 480 individual components like LCD backlight, LEDs, GPIOs and Kepad 481 under the corresponding menus. 482 483config MFD_LP8788 484 bool "Texas Instruments LP8788 Power Management Unit Driver" 485 depends on I2C=y 486 select MFD_CORE 487 select REGMAP_I2C 488 select IRQ_DOMAIN 489 help 490 TI LP8788 PMU supports regulators, battery charger, RTC, 491 ADC, backlight driver and current sinks. 492 493config MFD_MAX77686 494 bool "Maxim Semiconductor MAX77686 PMIC Support" 495 depends on I2C=y && GENERIC_HARDIRQS 496 select MFD_CORE 497 select REGMAP_I2C 498 select IRQ_DOMAIN 499 help 500 Say yes here to support for Maxim Semiconductor MAX77686. 501 This is a Power Management IC with RTC on chip. 502 This driver provides common support for accessing the device; 503 additional drivers must be enabled in order to use the functionality 504 of the device. 505 506config MFD_MAX77693 507 bool "Maxim Semiconductor MAX77693 PMIC Support" 508 depends on I2C=y && GENERIC_HARDIRQS 509 select MFD_CORE 510 select REGMAP_I2C 511 help 512 Say yes here to support for Maxim Semiconductor MAX77693. 513 This is a companion Power Management IC with Flash, Haptic, Charger, 514 and MUIC(Micro USB Interface Controller) controls on chip. 515 This driver provides common support for accessing the device; 516 additional drivers must be enabled in order to use the functionality 517 of the device. 518 519config MFD_MAX8907 520 tristate "Maxim Semiconductor MAX8907 PMIC Support" 521 select MFD_CORE 522 depends on I2C=y && GENERIC_HARDIRQS 523 select REGMAP_I2C 524 select REGMAP_IRQ 525 help 526 Say yes here to support for Maxim Semiconductor MAX8907. This is 527 a Power Management IC. This driver provides common support for 528 accessing the device; additional drivers must be enabled in order 529 to use the functionality of the device. 530 531config MFD_MAX8925 532 bool "Maxim Semiconductor MAX8925 PMIC Support" 533 depends on I2C=y && GENERIC_HARDIRQS 534 select MFD_CORE 535 help 536 Say yes here to support for Maxim Semiconductor MAX8925. This is 537 a Power Management IC. This driver provides common support for 538 accessing the device, additional drivers must be enabled in order 539 to use the functionality of the device. 540 541config MFD_MAX8997 542 bool "Maxim Semiconductor MAX8997/8966 PMIC Support" 543 depends on I2C=y && GENERIC_HARDIRQS 544 select MFD_CORE 545 select IRQ_DOMAIN 546 help 547 Say yes here to support for Maxim Semiconductor MAX8997/8966. 548 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic, 549 MUIC controls on chip. 550 This driver provides common support for accessing the device; 551 additional drivers must be enabled in order to use the functionality 552 of the device. 553 554config MFD_MAX8998 555 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support" 556 depends on I2C=y && GENERIC_HARDIRQS 557 select MFD_CORE 558 help 559 Say yes here to support for Maxim Semiconductor MAX8998 and 560 National Semiconductor LP3974. This is a Power Management IC. 561 This driver provides common support for accessing the device, 562 additional drivers must be enabled in order to use the functionality 563 of the device. 564 565config MFD_SEC_CORE 566 bool "SAMSUNG Electronics PMIC Series Support" 567 depends on I2C=y && GENERIC_HARDIRQS 568 select MFD_CORE 569 select REGMAP_I2C 570 select REGMAP_IRQ 571 help 572 Support for the Samsung Electronics MFD series. 573 This driver provides common support for accessing the device, 574 additional drivers must be enabled in order to use the functionality 575 of the device 576 577config MFD_ARIZONA 578 select REGMAP 579 select REGMAP_IRQ 580 select MFD_CORE 581 bool 582 583config MFD_ARIZONA_I2C 584 tristate "Support Wolfson Microelectronics Arizona platform with I2C" 585 select MFD_ARIZONA 586 select MFD_CORE 587 select REGMAP_I2C 588 depends on I2C 589 help 590 Support for the Wolfson Microelectronics Arizona platform audio SoC 591 core functionality controlled via I2C. 592 593config MFD_ARIZONA_SPI 594 tristate "Support Wolfson Microelectronics Arizona platform with SPI" 595 select MFD_ARIZONA 596 select MFD_CORE 597 select REGMAP_SPI 598 depends on SPI_MASTER 599 help 600 Support for the Wolfson Microelectronics Arizona platform audio SoC 601 core functionality controlled via I2C. 602 603config MFD_WM5102 604 bool "Support Wolfson Microelectronics WM5102" 605 depends on MFD_ARIZONA 606 help 607 Support for Wolfson Microelectronics WM5102 low power audio SoC 608 609config MFD_WM5110 610 bool "Support Wolfson Microelectronics WM5110" 611 depends on MFD_ARIZONA 612 help 613 Support for Wolfson Microelectronics WM5110 low power audio SoC 614 615config MFD_WM8400 616 bool "Support Wolfson Microelectronics WM8400" 617 select MFD_CORE 618 depends on I2C=y 619 select REGMAP_I2C 620 help 621 Support for the Wolfson Microelecronics WM8400 PMIC and audio 622 CODEC. This driver provides common support for accessing 623 the device, additional drivers must be enabled in order to use 624 the functionality of the device. 625 626config MFD_WM831X 627 bool 628 depends on GENERIC_HARDIRQS 629 630config MFD_WM831X_I2C 631 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C" 632 select MFD_CORE 633 select MFD_WM831X 634 select REGMAP_I2C 635 select IRQ_DOMAIN 636 depends on I2C=y && GENERIC_HARDIRQS 637 help 638 Support for the Wolfson Microelecronics WM831x and WM832x PMICs 639 when controlled using I2C. This driver provides common support 640 for accessing the device, additional drivers must be enabled in 641 order to use the functionality of the device. 642 643config MFD_WM831X_SPI 644 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI" 645 select MFD_CORE 646 select MFD_WM831X 647 select REGMAP_SPI 648 select IRQ_DOMAIN 649 depends on SPI_MASTER && GENERIC_HARDIRQS 650 help 651 Support for the Wolfson Microelecronics WM831x and WM832x PMICs 652 when controlled using SPI. This driver provides common support 653 for accessing the device, additional drivers must be enabled in 654 order to use the functionality of the device. 655 656config MFD_WM8350 657 bool 658 depends on GENERIC_HARDIRQS 659 660config MFD_WM8350_CONFIG_MODE_0 661 bool 662 depends on MFD_WM8350 663 664config MFD_WM8350_CONFIG_MODE_1 665 bool 666 depends on MFD_WM8350 667 668config MFD_WM8350_CONFIG_MODE_2 669 bool 670 depends on MFD_WM8350 671 672config MFD_WM8350_CONFIG_MODE_3 673 bool 674 depends on MFD_WM8350 675 676config MFD_WM8351_CONFIG_MODE_0 677 bool 678 depends on MFD_WM8350 679 680config MFD_WM8351_CONFIG_MODE_1 681 bool 682 depends on MFD_WM8350 683 684config MFD_WM8351_CONFIG_MODE_2 685 bool 686 depends on MFD_WM8350 687 688config MFD_WM8351_CONFIG_MODE_3 689 bool 690 depends on MFD_WM8350 691 692config MFD_WM8352_CONFIG_MODE_0 693 bool 694 depends on MFD_WM8350 695 696config MFD_WM8352_CONFIG_MODE_1 697 bool 698 depends on MFD_WM8350 699 700config MFD_WM8352_CONFIG_MODE_2 701 bool 702 depends on MFD_WM8350 703 704config MFD_WM8352_CONFIG_MODE_3 705 bool 706 depends on MFD_WM8350 707 708config MFD_WM8350_I2C 709 bool "Support Wolfson Microelectronics WM8350 with I2C" 710 select MFD_WM8350 711 depends on I2C=y && GENERIC_HARDIRQS 712 help 713 The WM8350 is an integrated audio and power management 714 subsystem with watchdog and RTC functionality for embedded 715 systems. This option enables core support for the WM8350 with 716 I2C as the control interface. Additional options must be 717 selected to enable support for the functionality of the chip. 718 719config MFD_WM8994 720 bool "Support Wolfson Microelectronics WM8994" 721 select MFD_CORE 722 select REGMAP_I2C 723 select REGMAP_IRQ 724 depends on I2C=y && GENERIC_HARDIRQS 725 help 726 The WM8994 is a highly integrated hi-fi CODEC designed for 727 smartphone applicatiosn. As well as audio functionality it 728 has on board GPIO and regulator functionality which is 729 supported via the relevant subsystems. This driver provides 730 core support for the WM8994, in order to use the actual 731 functionaltiy of the device other drivers must be enabled. 732 733config MFD_PCF50633 734 tristate "Support for NXP PCF50633" 735 depends on I2C 736 select REGMAP_I2C 737 help 738 Say yes here if you have NXP PCF50633 chip on your board. 739 This core driver provides register access and IRQ handling 740 facilities, and registers devices for the various functions 741 so that function-specific drivers can bind to them. 742 743config PCF50633_ADC 744 tristate "Support for NXP PCF50633 ADC" 745 depends on MFD_PCF50633 746 help 747 Say yes here if you want to include support for ADC in the 748 NXP PCF50633 chip. 749 750config PCF50633_GPIO 751 tristate "Support for NXP PCF50633 GPIO" 752 depends on MFD_PCF50633 753 help 754 Say yes here if you want to include support GPIO for pins on 755 the PCF50633 chip. 756 757config MFD_MC13783 758 tristate 759 760config MFD_MC13XXX 761 tristate 762 depends on SPI_MASTER || I2C 763 select MFD_CORE 764 select MFD_MC13783 765 help 766 Enable support for the Freescale MC13783 and MC13892 PMICs. 767 This driver provides common support for accessing the device, 768 additional drivers must be enabled in order to use the 769 functionality of the device. 770 771config MFD_MC13XXX_SPI 772 tristate "Freescale MC13783 and MC13892 SPI interface" 773 depends on SPI_MASTER 774 select REGMAP_SPI 775 select MFD_MC13XXX 776 help 777 Select this if your MC13xxx is connected via an SPI bus. 778 779config MFD_MC13XXX_I2C 780 tristate "Freescale MC13892 I2C interface" 781 depends on I2C 782 select REGMAP_I2C 783 select MFD_MC13XXX 784 help 785 Select this if your MC13xxx is connected via an I2C bus. 786 787config ABX500_CORE 788 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" 789 default y if ARCH_U300 || ARCH_U8500 790 help 791 Say yes here if you have the ABX500 Mixed Signal IC family 792 chips. This core driver expose register access functions. 793 Functionality specific drivers using these functions can 794 remain unchanged when IC changes. Binding of the functions to 795 actual register access is done by the IC core driver. 796 797config AB3100_CORE 798 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" 799 depends on I2C=y && ABX500_CORE 800 select MFD_CORE 801 default y if ARCH_U300 802 help 803 Select this to enable the AB3100 Mixed Signal IC core 804 functionality. This connects to a AB3100 on the I2C bus 805 and expose a number of symbols needed for dependent devices 806 to read and write registers and subscribe to events from 807 this multi-functional IC. This is needed to use other features 808 of the AB3100 such as battery-backed RTC, charging control, 809 LEDs, vibrator, system power and temperature, power management 810 and ALSA sound. 811 812config AB3100_OTP 813 tristate "ST-Ericsson AB3100 OTP functions" 814 depends on AB3100_CORE 815 default y if AB3100_CORE 816 help 817 Select this to enable the AB3100 Mixed Signal IC OTP (one-time 818 programmable memory) support. This exposes a sysfs file to read 819 out OTP values. 820 821config EZX_PCAP 822 bool "PCAP Support" 823 depends on GENERIC_HARDIRQS && SPI_MASTER 824 help 825 This enables the PCAP ASIC present on EZX Phones. This is 826 needed for MMC, TouchScreen, Sound, USB, etc.. 827 828config AB8500_CORE 829 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" 830 depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU 831 select MFD_CORE 832 select IRQ_DOMAIN 833 help 834 Select this option to enable access to AB8500 power management 835 chip. This connects to U8500 either on the SSP/SPI bus (deprecated 836 since hardware version v1.0) or the I2C bus via PRCMU. It also adds 837 the irq_chip parts for handling the Mixed Signal chip events. 838 This chip embeds various other multimedia funtionalities as well. 839 840config AB8500_DEBUG 841 bool "Enable debug info via debugfs" 842 depends on AB8500_CORE && DEBUG_FS 843 default y if DEBUG_FS 844 help 845 Select this option if you want debug information using the debug 846 filesystem, debugfs. 847 848config AB8500_GPADC 849 bool "AB8500 GPADC driver" 850 depends on AB8500_CORE && REGULATOR_AB8500 851 default y 852 help 853 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage 854 855config MFD_DB8500_PRCMU 856 bool "ST-Ericsson DB8500 Power Reset Control Management Unit" 857 depends on UX500_SOC_DB8500 858 select MFD_CORE 859 help 860 Select this option to enable support for the DB8500 Power Reset 861 and Control Management Unit. This is basically an autonomous 862 system controller running an XP70 microprocessor, which is accessed 863 through a register map. 864 865config MFD_CS5535 866 tristate "Support for CS5535 and CS5536 southbridge core functions" 867 select MFD_CORE 868 depends on PCI && X86 869 ---help--- 870 This is the core driver for CS5535/CS5536 MFD functions. This is 871 necessary for using the board's GPIO and MFGPT functionality. 872 873config MFD_TIMBERDALE 874 tristate "Support for the Timberdale FPGA" 875 select MFD_CORE 876 depends on PCI && GPIOLIB 877 ---help--- 878 This is the core driver for the timberdale FPGA. This device is a 879 multifunction device which exposes numerous platform devices. 880 881 The timberdale FPGA can be found on the Intel Atom development board 882 for in-vehicle infontainment, called Russellville. 883 884config LPC_SCH 885 tristate "Intel SCH LPC" 886 depends on PCI 887 select MFD_CORE 888 help 889 LPC bridge function of the Intel SCH provides support for 890 System Management Bus and General Purpose I/O. 891 892config LPC_ICH 893 tristate "Intel ICH LPC" 894 depends on PCI 895 select MFD_CORE 896 help 897 The LPC bridge function of the Intel ICH provides support for 898 many functional units. This driver provides needed support for 899 other drivers to control these functions, currently GPIO and 900 watchdog. 901 902config MFD_RDC321X 903 tristate "Support for RDC-R321x southbridge" 904 select MFD_CORE 905 depends on PCI 906 help 907 Say yes here if you want to have support for the RDC R-321x SoC 908 southbridge which provides access to GPIOs and Watchdog using the 909 southbridge PCI device configuration space. 910 911config MFD_JANZ_CMODIO 912 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board" 913 select MFD_CORE 914 depends on PCI 915 help 916 This is the core driver for the Janz CMOD-IO PCI MODULbus 917 carrier board. This device is a PCI to MODULbus bridge which may 918 host many different types of MODULbus daughterboards, including 919 CAN and GPIO controllers. 920 921config MFD_JZ4740_ADC 922 bool "Support for the JZ4740 SoC ADC core" 923 select MFD_CORE 924 select GENERIC_IRQ_CHIP 925 depends on MACH_JZ4740 926 help 927 Say yes here if you want support for the ADC unit in the JZ4740 SoC. 928 This driver is necessary for jz4740-battery and jz4740-hwmon driver. 929 930config MFD_VX855 931 tristate "Support for VIA VX855/VX875 integrated south bridge" 932 depends on PCI 933 select MFD_CORE 934 help 935 Say yes here to enable support for various functions of the 936 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi 937 and/or vx855_gpio drivers for this to do anything useful. 938 939config MFD_WL1273_CORE 940 tristate "Support for TI WL1273 FM radio." 941 depends on I2C 942 select MFD_CORE 943 default n 944 help 945 This is the core driver for the TI WL1273 FM radio. This MFD 946 driver connects the radio-wl1273 V4L2 module and the wl1273 947 audio codec. 948 949config MFD_OMAP_USB_HOST 950 bool "Support OMAP USBHS core and TLL driver" 951 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3 952 default y 953 help 954 This is the core driver for the OAMP EHCI and OHCI drivers. 955 This MFD driver does the required setup functionalities for 956 OMAP USB Host drivers. 957 958config MFD_PM8XXX 959 tristate 960 961config MFD_PM8921_CORE 962 tristate "Qualcomm PM8921 PMIC chip" 963 depends on MSM_SSBI 964 select MFD_CORE 965 select MFD_PM8XXX 966 help 967 If you say yes to this option, support will be included for the 968 built-in PM8921 PMIC chip. 969 970 This is required if your board has a PM8921 and uses its features, 971 such as: MPPs, GPIOs, regulators, interrupts, and PWM. 972 973 Say M here if you want to include support for PM8921 chip as a module. 974 This will build a module called "pm8921-core". 975 976config MFD_PM8XXX_IRQ 977 bool "Support for Qualcomm PM8xxx IRQ features" 978 depends on MFD_PM8XXX 979 default y if MFD_PM8XXX 980 help 981 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips. 982 983 This is required to use certain other PM 8xxx features, such as GPIO 984 and MPP. 985 986config TPS65911_COMPARATOR 987 tristate 988 989config MFD_TPS65090 990 bool "TPS65090 Power Management chips" 991 depends on I2C=y && GENERIC_HARDIRQS 992 select MFD_CORE 993 select REGMAP_I2C 994 help 995 If you say yes here you get support for the TPS65090 series of 996 Power Management chips. 997 This driver provides common support for accessing the device, 998 additional drivers must be enabled in order to use the 999 functionality of the device. 1000 1001config MFD_AAT2870_CORE 1002 bool "Support for the AnalogicTech AAT2870" 1003 select MFD_CORE 1004 depends on I2C=y && GPIOLIB 1005 help 1006 If you say yes here you get support for the AAT2870. 1007 This driver provides common support for accessing the device, 1008 additional drivers must be enabled in order to use the 1009 functionality of the device. 1010 1011config MFD_INTEL_MSIC 1012 bool "Support for Intel MSIC" 1013 depends on INTEL_SCU_IPC 1014 select MFD_CORE 1015 help 1016 Select this option to enable access to Intel MSIC (Avatele 1017 Passage) chip. This chip embeds audio, battery, GPIO, etc. 1018 devices used in Intel Medfield platforms. 1019 1020config MFD_RC5T583 1021 bool "Ricoh RC5T583 Power Management system device" 1022 depends on I2C=y && GENERIC_HARDIRQS 1023 select MFD_CORE 1024 select REGMAP_I2C 1025 help 1026 Select this option to get support for the RICOH583 Power 1027 Management system device. 1028 This driver provides common support for accessing the device 1029 through i2c interface. The device supports multiple sub-devices 1030 like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey. 1031 Additional drivers must be enabled in order to use the 1032 different functionality of the device. 1033 1034config MFD_STA2X11 1035 bool "STA2X11 multi function device support" 1036 depends on STA2X11 1037 select MFD_CORE 1038 1039config MFD_SYSCON 1040 bool "System Controller Register R/W Based on Regmap" 1041 depends on OF 1042 select REGMAP_MMIO 1043 help 1044 Select this option to enable accessing system control registers 1045 via regmap. 1046 1047config MFD_PALMAS 1048 bool "Support for the TI Palmas series chips" 1049 select MFD_CORE 1050 select REGMAP_I2C 1051 select REGMAP_IRQ 1052 depends on I2C=y 1053 help 1054 If you say yes here you get support for the Palmas 1055 series of PMIC chips from Texas Instruments. 1056 1057endmenu 1058endif 1059 1060menu "Multimedia Capabilities Port drivers" 1061 depends on ARCH_SA1100 1062 1063config MCP 1064 tristate 1065 1066# Interface drivers 1067config MCP_SA11X0 1068 tristate "Support SA11x0 MCP interface" 1069 depends on ARCH_SA1100 1070 select MCP 1071 1072# Chip drivers 1073config MCP_UCB1200 1074 bool "Support for UCB1200 / UCB1300" 1075 depends on MCP_SA11X0 1076 select MCP 1077 1078config MCP_UCB1200_TS 1079 tristate "Touchscreen interface support" 1080 depends on MCP_UCB1200 && INPUT 1081 1082endmenu 1083