1# 2# Multifunction miscellaneous devices 3# 4 5if HAS_IOMEM 6menu "Multifunction device drivers" 7 8config MFD_CORE 9 tristate 10 default n 11 12config MFD_88PM860X 13 bool "Support Marvell 88PM8606/88PM8607" 14 depends on I2C=y && GENERIC_HARDIRQS 15 select REGMAP_I2C 16 select MFD_CORE 17 help 18 This supports for Marvell 88PM8606/88PM8607 Power Management IC. 19 This includes the I2C driver and the core APIs _only_, you have to 20 select individual components like voltage regulators, RTC and 21 battery-charger under the corresponding menus. 22 23config MFD_SM501 24 tristate "Support for Silicon Motion SM501" 25 ---help--- 26 This is the core driver for the Silicon Motion SM501 multimedia 27 companion chip. This device is a multifunction device which may 28 provide numerous interfaces including USB host controller, USB gadget, 29 asynchronous serial ports, audio functions, and a dual display video 30 interface. The device may be connected by PCI or local bus with 31 varying functions enabled. 32 33config MFD_SM501_GPIO 34 bool "Export GPIO via GPIO layer" 35 depends on MFD_SM501 && GPIOLIB 36 ---help--- 37 This option uses the gpio library layer to export the 64 GPIO 38 lines on the SM501. The platform data is used to supply the 39 base number for the first GPIO line to register. 40 41config MFD_ASIC3 42 bool "Support for Compaq ASIC3" 43 depends on GENERIC_HARDIRQS && GPIOLIB && ARM 44 select MFD_CORE 45 ---help--- 46 This driver supports the ASIC3 multifunction chip found on many 47 PDAs (mainly iPAQ and HTC based ones) 48 49config MFD_DAVINCI_VOICECODEC 50 tristate 51 select MFD_CORE 52 53config MFD_DM355EVM_MSP 54 bool "DaVinci DM355 EVM microcontroller" 55 depends on I2C=y && MACH_DAVINCI_DM355_EVM 56 help 57 This driver supports the MSP430 microcontroller used on these 58 boards. MSP430 firmware manages resets and power sequencing, 59 inputs from buttons and the IR remote, LEDs, an RTC, and more. 60 61config MFD_TI_SSP 62 tristate "TI Sequencer Serial Port support" 63 depends on ARCH_DAVINCI_TNETV107X 64 select MFD_CORE 65 ---help--- 66 Say Y here if you want support for the Sequencer Serial Port 67 in a Texas Instruments TNETV107X SoC. 68 69 To compile this driver as a module, choose M here: the 70 module will be called ti-ssp. 71 72config HTC_EGPIO 73 bool "HTC EGPIO support" 74 depends on GENERIC_HARDIRQS && GPIOLIB && ARM 75 help 76 This driver supports the CPLD egpio chip present on 77 several HTC phones. It provides basic support for input 78 pins, output pins, and irqs. 79 80config HTC_PASIC3 81 tristate "HTC PASIC3 LED/DS1WM chip support" 82 select MFD_CORE 83 help 84 This core driver provides register access for the LED/DS1WM 85 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and 86 HTC Magician devices, respectively. Actual functionality is 87 handled by the leds-pasic3 and ds1wm drivers. 88 89config HTC_I2CPLD 90 bool "HTC I2C PLD chip support" 91 depends on I2C=y && GPIOLIB 92 help 93 If you say yes here you get support for the supposed CPLD 94 found on omap850 HTC devices like the HTC Wizard and HTC Herald. 95 This device provides input and output GPIOs through an I2C 96 interface to one or more sub-chips. 97 98config UCB1400_CORE 99 tristate "Philips UCB1400 Core driver" 100 depends on AC97_BUS 101 depends on GPIOLIB 102 help 103 This enables support for the Philips UCB1400 core functions. 104 The UCB1400 is an AC97 audio codec. 105 106 To compile this driver as a module, choose M here: the 107 module will be called ucb1400_core. 108 109config TPS6105X 110 tristate "TPS61050/61052 Boost Converters" 111 depends on I2C 112 select REGULATOR 113 select MFD_CORE 114 select REGULATOR_FIXED_VOLTAGE 115 help 116 This option enables a driver for the TP61050/TPS61052 117 high-power "white LED driver". This boost converter is 118 sometimes used for other things than white LEDs, and 119 also contains a GPIO pin. 120 121config TPS65010 122 tristate "TPS6501x Power Management chips" 123 depends on I2C && GPIOLIB 124 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK 125 help 126 If you say yes here you get support for the TPS6501x series of 127 Power Management chips. These include voltage regulators, 128 lithium ion/polymer battery charging, and other features that 129 are often used in portable devices like cell phones and cameras. 130 131 This driver can also be built as a module. If so, the module 132 will be called tps65010. 133 134config TPS6507X 135 tristate "TPS6507x Power Management / Touch Screen chips" 136 select MFD_CORE 137 depends on I2C 138 help 139 If you say yes here you get support for the TPS6507x series of 140 Power Management / Touch Screen chips. These include voltage 141 regulators, lithium ion/polymer battery charging, touch screen 142 and other features that are often used in portable devices. 143 This driver can also be built as a module. If so, the module 144 will be called tps6507x. 145 146config MFD_TPS6586X 147 bool "TPS6586x Power Management chips" 148 depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS 149 select MFD_CORE 150 help 151 If you say yes here you get support for the TPS6586X series of 152 Power Management chips. 153 This driver provides common support for accessing the device, 154 additional drivers must be enabled in order to use the 155 functionality of the device. 156 157 This driver can also be built as a module. If so, the module 158 will be called tps6586x. 159 160config MFD_TPS65910 161 bool "TPS65910 Power Management chip" 162 depends on I2C=y && GPIOLIB 163 select MFD_CORE 164 select GPIO_TPS65910 165 help 166 if you say yes here you get support for the TPS65910 series of 167 Power Management chips. 168 169config MFD_TPS65912 170 bool 171 depends on GPIOLIB 172 173config MFD_TPS65912_I2C 174 bool "TPS95612 Power Management chip with I2C" 175 select MFD_CORE 176 select MFD_TPS65912 177 depends on I2C=y && GPIOLIB 178 help 179 If you say yes here you get support for the TPS65912 series of 180 PM chips with I2C interface. 181 182config MFD_TPS65912_SPI 183 bool "TPS65912 Power Management chip with SPI" 184 select MFD_CORE 185 select MFD_TPS65912 186 depends on SPI_MASTER && GPIOLIB 187 help 188 If you say yes here you get support for the TPS65912 series of 189 PM chips with SPI interface. 190 191config MENELAUS 192 bool "Texas Instruments TWL92330/Menelaus PM chip" 193 depends on I2C=y && ARCH_OMAP2 194 help 195 If you say yes here you get support for the Texas Instruments 196 TWL92330/Menelaus Power Management chip. This include voltage 197 regulators, Dual slot memory card transceivers, real-time clock 198 and other features that are often used in portable devices like 199 cell phones and PDAs. 200 201config TWL4030_CORE 202 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support" 203 depends on I2C=y && GENERIC_HARDIRQS && IRQ_DOMAIN 204 help 205 Say yes here if you have TWL4030 / TWL6030 family chip on your board. 206 This core driver provides register access and IRQ handling 207 facilities, and registers devices for the various functions 208 so that function-specific drivers can bind to them. 209 210 These multi-function chips are found on many OMAP2 and OMAP3 211 boards, providing power management, RTC, GPIO, keypad, a 212 high speed USB OTG transceiver, an audio codec (on most 213 versions) and many other features. 214 215config TWL4030_MADC 216 tristate "Texas Instruments TWL4030 MADC" 217 depends on TWL4030_CORE 218 help 219 This driver provides support for triton TWL4030-MADC. The 220 driver supports both RT and SW conversion methods. 221 222 This driver can be built as a module. If so it will be 223 named twl4030-madc 224 225config TWL4030_POWER 226 bool "Support power resources on TWL4030 family chips" 227 depends on TWL4030_CORE && ARM 228 help 229 Say yes here if you want to use the power resources on the 230 TWL4030 family chips. Most of these resources are regulators, 231 which have a separate driver; some are control signals, such 232 as clock request handshaking. 233 234 This driver uses board-specific data to initialize the resources 235 and load scripts controlling which resources are switched off/on 236 or reset when a sleep, wakeup or warm reset event occurs. 237 238config MFD_TWL4030_AUDIO 239 bool 240 depends on TWL4030_CORE 241 select MFD_CORE 242 default n 243 244config TWL6030_PWM 245 tristate "TWL6030 PWM (Pulse Width Modulator) Support" 246 depends on TWL4030_CORE 247 select HAVE_PWM 248 default n 249 help 250 Say yes here if you want support for TWL6030 PWM. 251 This is used to control charging LED brightness. 252 253config TWL6040_CORE 254 bool 255 depends on TWL4030_CORE && GENERIC_HARDIRQS 256 select MFD_CORE 257 default n 258 259config MFD_STMPE 260 bool "Support STMicroelectronics STMPE" 261 depends on I2C=y && GENERIC_HARDIRQS 262 select MFD_CORE 263 help 264 Support for the STMPE family of I/O Expanders from 265 STMicroelectronics. 266 267 Currently supported devices are: 268 269 STMPE811: GPIO, Touchscreen 270 STMPE1601: GPIO, Keypad 271 STMPE2401: GPIO, Keypad 272 STMPE2403: GPIO, Keypad 273 274 This driver provides common support for accessing the device, 275 additional drivers must be enabled in order to use the functionality 276 of the device. Currently available sub drivers are: 277 278 GPIO: stmpe-gpio 279 Keypad: stmpe-keypad 280 Touchscreen: stmpe-ts 281 282menu "STMPE Interface Drivers" 283depends on MFD_STMPE 284 285config STMPE_I2C 286 bool "STMPE I2C Inteface" 287 depends on I2C 288 default y 289 help 290 This is used to enable I2C interface of STMPE 291endmenu 292 293config MFD_TC3589X 294 bool "Support Toshiba TC35892 and variants" 295 depends on I2C=y && GENERIC_HARDIRQS 296 select MFD_CORE 297 help 298 Support for the Toshiba TC35892 and variants I/O Expander. 299 300 This driver provides common support for accessing the device, 301 additional drivers must be enabled in order to use the 302 functionality of the device. 303 304config MFD_TMIO 305 bool 306 default n 307 308config MFD_T7L66XB 309 bool "Support Toshiba T7L66XB" 310 depends on ARM && HAVE_CLK 311 select MFD_CORE 312 select MFD_TMIO 313 help 314 Support for Toshiba Mobile IO Controller T7L66XB 315 316config MFD_TC6387XB 317 bool "Support Toshiba TC6387XB" 318 depends on ARM && HAVE_CLK 319 select MFD_CORE 320 select MFD_TMIO 321 help 322 Support for Toshiba Mobile IO Controller TC6387XB 323 324config MFD_TC6393XB 325 bool "Support Toshiba TC6393XB" 326 depends on GPIOLIB && ARM && HAVE_CLK 327 select MFD_CORE 328 select MFD_TMIO 329 help 330 Support for Toshiba Mobile IO Controller TC6393XB 331 332config PMIC_DA903X 333 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" 334 depends on I2C=y 335 help 336 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a 337 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC 338 usually found on PXA processors-based platforms. This includes 339 the I2C driver and the core APIs _only_, you have to select 340 individual components like LCD backlight, voltage regulators, 341 LEDs and battery-charger under the corresponding menus. 342 343config PMIC_ADP5520 344 bool "Analog Devices ADP5520/01 MFD PMIC Core Support" 345 depends on I2C=y 346 help 347 Say yes here to add support for Analog Devices AD5520 and ADP5501, 348 Multifunction Power Management IC. This includes 349 the I2C driver and the core APIs _only_, you have to select 350 individual components like LCD backlight, LEDs, GPIOs and Kepad 351 under the corresponding menus. 352 353config MFD_MAX8925 354 bool "Maxim Semiconductor MAX8925 PMIC Support" 355 depends on I2C=y && GENERIC_HARDIRQS 356 select MFD_CORE 357 help 358 Say yes here to support for Maxim Semiconductor MAX8925. This is 359 a Power Management IC. This driver provies common support for 360 accessing the device, additional drivers must be enabled in order 361 to use the functionality of the device. 362 363config MFD_MAX8997 364 bool "Maxim Semiconductor MAX8997/8966 PMIC Support" 365 depends on I2C=y && GENERIC_HARDIRQS 366 select MFD_CORE 367 help 368 Say yes here to support for Maxim Semiconductor MAX8998/8966. 369 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic, 370 MUIC controls on chip. 371 This driver provides common support for accessing the device; 372 additional drivers must be enabled in order to use the functionality 373 of the device. 374 375config MFD_MAX8998 376 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support" 377 depends on I2C=y && GENERIC_HARDIRQS 378 select MFD_CORE 379 help 380 Say yes here to support for Maxim Semiconductor MAX8998 and 381 National Semiconductor LP3974. This is a Power Management IC. 382 This driver provies common support for accessing the device, 383 additional drivers must be enabled in order to use the functionality 384 of the device. 385 386config MFD_WM8400 387 tristate "Support Wolfson Microelectronics WM8400" 388 select MFD_CORE 389 depends on I2C 390 select REGMAP_I2C 391 help 392 Support for the Wolfson Microelecronics WM8400 PMIC and audio 393 CODEC. This driver provides common support for accessing 394 the device, additional drivers must be enabled in order to use 395 the functionality of the device. 396 397config MFD_WM831X 398 bool 399 depends on GENERIC_HARDIRQS 400 401config MFD_WM831X_I2C 402 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C" 403 select MFD_CORE 404 select MFD_WM831X 405 select REGMAP_I2C 406 depends on I2C=y && GENERIC_HARDIRQS 407 help 408 Support for the Wolfson Microelecronics WM831x and WM832x PMICs 409 when controlled using I2C. This driver provides common support 410 for accessing the device, additional drivers must be enabled in 411 order to use the functionality of the device. 412 413config MFD_WM831X_SPI 414 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI" 415 select MFD_CORE 416 select MFD_WM831X 417 select REGMAP_SPI 418 depends on SPI_MASTER && GENERIC_HARDIRQS 419 help 420 Support for the Wolfson Microelecronics WM831x and WM832x PMICs 421 when controlled using SPI. This driver provides common support 422 for accessing the device, additional drivers must be enabled in 423 order to use the functionality of the device. 424 425config MFD_WM8350 426 bool 427 depends on GENERIC_HARDIRQS 428 429config MFD_WM8350_CONFIG_MODE_0 430 bool 431 depends on MFD_WM8350 432 433config MFD_WM8350_CONFIG_MODE_1 434 bool 435 depends on MFD_WM8350 436 437config MFD_WM8350_CONFIG_MODE_2 438 bool 439 depends on MFD_WM8350 440 441config MFD_WM8350_CONFIG_MODE_3 442 bool 443 depends on MFD_WM8350 444 445config MFD_WM8351_CONFIG_MODE_0 446 bool 447 depends on MFD_WM8350 448 449config MFD_WM8351_CONFIG_MODE_1 450 bool 451 depends on MFD_WM8350 452 453config MFD_WM8351_CONFIG_MODE_2 454 bool 455 depends on MFD_WM8350 456 457config MFD_WM8351_CONFIG_MODE_3 458 bool 459 depends on MFD_WM8350 460 461config MFD_WM8352_CONFIG_MODE_0 462 bool 463 depends on MFD_WM8350 464 465config MFD_WM8352_CONFIG_MODE_1 466 bool 467 depends on MFD_WM8350 468 469config MFD_WM8352_CONFIG_MODE_2 470 bool 471 depends on MFD_WM8350 472 473config MFD_WM8352_CONFIG_MODE_3 474 bool 475 depends on MFD_WM8350 476 477config MFD_WM8350_I2C 478 bool "Support Wolfson Microelectronics WM8350 with I2C" 479 select MFD_WM8350 480 depends on I2C=y && GENERIC_HARDIRQS 481 help 482 The WM8350 is an integrated audio and power management 483 subsystem with watchdog and RTC functionality for embedded 484 systems. This option enables core support for the WM8350 with 485 I2C as the control interface. Additional options must be 486 selected to enable support for the functionality of the chip. 487 488config MFD_WM8994 489 bool "Support Wolfson Microelectronics WM8994" 490 select MFD_CORE 491 select REGMAP_I2C 492 depends on I2C=y && GENERIC_HARDIRQS 493 help 494 The WM8994 is a highly integrated hi-fi CODEC designed for 495 smartphone applicatiosn. As well as audio functionality it 496 has on board GPIO and regulator functionality which is 497 supported via the relevant subsystems. This driver provides 498 core support for the WM8994, in order to use the actual 499 functionaltiy of the device other drivers must be enabled. 500 501config MFD_PCF50633 502 tristate "Support for NXP PCF50633" 503 depends on I2C 504 select REGMAP_I2C 505 help 506 Say yes here if you have NXP PCF50633 chip on your board. 507 This core driver provides register access and IRQ handling 508 facilities, and registers devices for the various functions 509 so that function-specific drivers can bind to them. 510 511config PCF50633_ADC 512 tristate "Support for NXP PCF50633 ADC" 513 depends on MFD_PCF50633 514 help 515 Say yes here if you want to include support for ADC in the 516 NXP PCF50633 chip. 517 518config PCF50633_GPIO 519 tristate "Support for NXP PCF50633 GPIO" 520 depends on MFD_PCF50633 521 help 522 Say yes here if you want to include support GPIO for pins on 523 the PCF50633 chip. 524 525config MFD_MC13783 526 tristate 527 528config MFD_MC13XXX 529 tristate "Support Freescale MC13783 and MC13892" 530 depends on SPI_MASTER 531 select MFD_CORE 532 select MFD_MC13783 533 help 534 Support for the Freescale (Atlas) PMIC and audio CODECs 535 MC13783 and MC13892. 536 This driver provides common support for accessing the device, 537 additional drivers must be enabled in order to use the 538 functionality of the device. 539 540config ABX500_CORE 541 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" 542 default y if ARCH_U300 || ARCH_U8500 543 help 544 Say yes here if you have the ABX500 Mixed Signal IC family 545 chips. This core driver expose register access functions. 546 Functionality specific drivers using these functions can 547 remain unchanged when IC changes. Binding of the functions to 548 actual register access is done by the IC core driver. 549 550config AB3100_CORE 551 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" 552 depends on I2C=y && ABX500_CORE 553 select MFD_CORE 554 default y if ARCH_U300 555 help 556 Select this to enable the AB3100 Mixed Signal IC core 557 functionality. This connects to a AB3100 on the I2C bus 558 and expose a number of symbols needed for dependent devices 559 to read and write registers and subscribe to events from 560 this multi-functional IC. This is needed to use other features 561 of the AB3100 such as battery-backed RTC, charging control, 562 LEDs, vibrator, system power and temperature, power management 563 and ALSA sound. 564 565config AB3100_OTP 566 tristate "ST-Ericsson AB3100 OTP functions" 567 depends on AB3100_CORE 568 default y if AB3100_CORE 569 help 570 Select this to enable the AB3100 Mixed Signal IC OTP (one-time 571 programmable memory) support. This exposes a sysfs file to read 572 out OTP values. 573 574config EZX_PCAP 575 bool "PCAP Support" 576 depends on GENERIC_HARDIRQS && SPI_MASTER 577 help 578 This enables the PCAP ASIC present on EZX Phones. This is 579 needed for MMC, TouchScreen, Sound, USB, etc.. 580 581config AB5500_CORE 582 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip" 583 depends on ABX500_CORE && MFD_DB5500_PRCMU 584 select MFD_CORE 585 help 586 Select this option to enable access to AB5500 power management 587 chip. This connects to the db5500 chip via the I2C bus via PRCMU. 588 This chip embeds various other multimedia funtionalities as well. 589 590config AB5500_DEBUG 591 bool "Enable debug info via debugfs" 592 depends on AB5500_CORE && DEBUG_FS 593 default y if DEBUG_FS 594 help 595 Select this option if you want debug information from the AB5500 596 using the debug filesystem, debugfs. 597 598config AB8500_CORE 599 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" 600 depends on GENERIC_HARDIRQS && ABX500_CORE 601 select MFD_CORE 602 help 603 Select this option to enable access to AB8500 power management 604 chip. This connects to U8500 either on the SSP/SPI bus (deprecated 605 since hardware version v1.0) or the I2C bus via PRCMU. It also adds 606 the irq_chip parts for handling the Mixed Signal chip events. 607 This chip embeds various other multimedia funtionalities as well. 608 609config AB8500_I2C_CORE 610 bool "AB8500 register access via PRCMU I2C" 611 depends on AB8500_CORE && MFD_DB8500_PRCMU 612 default y 613 help 614 This enables register access to the AB8500 chip via PRCMU I2C. 615 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware 616 the I2C bus is connected to the Power Reset 617 and Mangagement Unit, PRCMU. 618 619config AB8500_DEBUG 620 bool "Enable debug info via debugfs" 621 depends on AB8500_CORE && DEBUG_FS 622 default y if DEBUG_FS 623 help 624 Select this option if you want debug information using the debug 625 filesystem, debugfs. 626 627config AB8500_GPADC 628 bool "AB8500 GPADC driver" 629 depends on AB8500_CORE && REGULATOR_AB8500 630 default y 631 help 632 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage 633 634config MFD_DB8500_PRCMU 635 bool "ST-Ericsson DB8500 Power Reset Control Management Unit" 636 depends on UX500_SOC_DB8500 637 select MFD_CORE 638 help 639 Select this option to enable support for the DB8500 Power Reset 640 and Control Management Unit. This is basically an autonomous 641 system controller running an XP70 microprocessor, which is accessed 642 through a register map. 643 644config MFD_DB5500_PRCMU 645 bool "ST-Ericsson DB5500 Power Reset Control Management Unit" 646 depends on UX500_SOC_DB5500 647 select MFD_CORE 648 help 649 Select this option to enable support for the DB5500 Power Reset 650 and Control Management Unit. This is basically an autonomous 651 system controller running an XP70 microprocessor, which is accessed 652 through a register map. 653 654config MFD_CS5535 655 tristate "Support for CS5535 and CS5536 southbridge core functions" 656 select MFD_CORE 657 depends on PCI && X86 658 ---help--- 659 This is the core driver for CS5535/CS5536 MFD functions. This is 660 necessary for using the board's GPIO and MFGPT functionality. 661 662config MFD_TIMBERDALE 663 tristate "Support for the Timberdale FPGA" 664 select MFD_CORE 665 depends on PCI && GPIOLIB 666 ---help--- 667 This is the core driver for the timberdale FPGA. This device is a 668 multifunction device which exposes numerous platform devices. 669 670 The timberdale FPGA can be found on the Intel Atom development board 671 for in-vehicle infontainment, called Russellville. 672 673config LPC_SCH 674 tristate "Intel SCH LPC" 675 depends on PCI 676 select MFD_CORE 677 help 678 LPC bridge function of the Intel SCH provides support for 679 System Management Bus and General Purpose I/O. 680 681config MFD_RDC321X 682 tristate "Support for RDC-R321x southbridge" 683 select MFD_CORE 684 depends on PCI 685 help 686 Say yes here if you want to have support for the RDC R-321x SoC 687 southbridge which provides access to GPIOs and Watchdog using the 688 southbridge PCI device configuration space. 689 690config MFD_JANZ_CMODIO 691 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board" 692 select MFD_CORE 693 depends on PCI 694 help 695 This is the core driver for the Janz CMOD-IO PCI MODULbus 696 carrier board. This device is a PCI to MODULbus bridge which may 697 host many different types of MODULbus daughterboards, including 698 CAN and GPIO controllers. 699 700config MFD_JZ4740_ADC 701 bool "Support for the JZ4740 SoC ADC core" 702 select MFD_CORE 703 select GENERIC_IRQ_CHIP 704 depends on MACH_JZ4740 705 help 706 Say yes here if you want support for the ADC unit in the JZ4740 SoC. 707 This driver is necessary for jz4740-battery and jz4740-hwmon driver. 708 709config MFD_VX855 710 tristate "Support for VIA VX855/VX875 integrated south bridge" 711 depends on PCI 712 select MFD_CORE 713 help 714 Say yes here to enable support for various functions of the 715 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi 716 and/or vx855_gpio drivers for this to do anything useful. 717 718config MFD_WL1273_CORE 719 tristate "Support for TI WL1273 FM radio." 720 depends on I2C 721 select MFD_CORE 722 default n 723 help 724 This is the core driver for the TI WL1273 FM radio. This MFD 725 driver connects the radio-wl1273 V4L2 module and the wl1273 726 audio codec. 727 728config MFD_OMAP_USB_HOST 729 bool "Support OMAP USBHS core driver" 730 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3 731 default y 732 help 733 This is the core driver for the OAMP EHCI and OHCI drivers. 734 This MFD driver does the required setup functionalities for 735 OMAP USB Host drivers. 736 737config MFD_PM8XXX 738 tristate 739 740config MFD_PM8921_CORE 741 tristate "Qualcomm PM8921 PMIC chip" 742 depends on MSM_SSBI 743 select MFD_CORE 744 select MFD_PM8XXX 745 help 746 If you say yes to this option, support will be included for the 747 built-in PM8921 PMIC chip. 748 749 This is required if your board has a PM8921 and uses its features, 750 such as: MPPs, GPIOs, regulators, interrupts, and PWM. 751 752 Say M here if you want to include support for PM8921 chip as a module. 753 This will build a module called "pm8921-core". 754 755config MFD_PM8XXX_IRQ 756 bool "Support for Qualcomm PM8xxx IRQ features" 757 depends on MFD_PM8XXX 758 default y if MFD_PM8XXX 759 help 760 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips. 761 762 This is required to use certain other PM 8xxx features, such as GPIO 763 and MPP. 764 765config TPS65911_COMPARATOR 766 tristate 767 768config MFD_AAT2870_CORE 769 bool "Support for the AnalogicTech AAT2870" 770 select MFD_CORE 771 depends on I2C=y && GPIOLIB 772 help 773 If you say yes here you get support for the AAT2870. 774 This driver provides common support for accessing the device, 775 additional drivers must be enabled in order to use the 776 functionality of the device. 777 778config MFD_INTEL_MSIC 779 bool "Support for Intel MSIC" 780 depends on INTEL_SCU_IPC 781 select MFD_CORE 782 help 783 Select this option to enable access to Intel MSIC (Avatele 784 Passage) chip. This chip embeds audio, battery, GPIO, etc. 785 devices used in Intel Medfield platforms. 786 787endmenu 788endif 789 790menu "Multimedia Capabilities Port drivers" 791 depends on ARCH_SA1100 792 793config MCP 794 tristate 795 796# Interface drivers 797config MCP_SA11X0 798 tristate "Support SA11x0 MCP interface" 799 depends on ARCH_SA1100 800 select MCP 801 802# Chip drivers 803config MCP_UCB1200 804 tristate "Support for UCB1200 / UCB1300" 805 depends on MCP 806 807config MCP_UCB1200_TS 808 tristate "Touchscreen interface support" 809 depends on MCP_UCB1200 && INPUT 810 811endmenu 812