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 282config MFD_TC3589X 283 bool "Support Toshiba TC35892 and variants" 284 depends on I2C=y && GENERIC_HARDIRQS 285 select MFD_CORE 286 help 287 Support for the Toshiba TC35892 and variants I/O Expander. 288 289 This driver provides common support for accessing the device, 290 additional drivers must be enabled in order to use the 291 functionality of the device. 292 293config MFD_TMIO 294 bool 295 default n 296 297config MFD_T7L66XB 298 bool "Support Toshiba T7L66XB" 299 depends on ARM && HAVE_CLK 300 select MFD_CORE 301 select MFD_TMIO 302 help 303 Support for Toshiba Mobile IO Controller T7L66XB 304 305config MFD_TC6387XB 306 bool "Support Toshiba TC6387XB" 307 depends on ARM && HAVE_CLK 308 select MFD_CORE 309 select MFD_TMIO 310 help 311 Support for Toshiba Mobile IO Controller TC6387XB 312 313config MFD_TC6393XB 314 bool "Support Toshiba TC6393XB" 315 depends on GPIOLIB && ARM && HAVE_CLK 316 select MFD_CORE 317 select MFD_TMIO 318 help 319 Support for Toshiba Mobile IO Controller TC6393XB 320 321config PMIC_DA903X 322 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" 323 depends on I2C=y 324 help 325 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a 326 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC 327 usually found on PXA processors-based platforms. This includes 328 the I2C driver and the core APIs _only_, you have to select 329 individual components like LCD backlight, voltage regulators, 330 LEDs and battery-charger under the corresponding menus. 331 332config PMIC_ADP5520 333 bool "Analog Devices ADP5520/01 MFD PMIC Core Support" 334 depends on I2C=y 335 help 336 Say yes here to add support for Analog Devices AD5520 and ADP5501, 337 Multifunction Power Management IC. This includes 338 the I2C driver and the core APIs _only_, you have to select 339 individual components like LCD backlight, LEDs, GPIOs and Kepad 340 under the corresponding menus. 341 342config MFD_MAX8925 343 bool "Maxim Semiconductor MAX8925 PMIC Support" 344 depends on I2C=y && GENERIC_HARDIRQS 345 select MFD_CORE 346 help 347 Say yes here to support for Maxim Semiconductor MAX8925. This is 348 a Power Management IC. This driver provies common support for 349 accessing the device, additional drivers must be enabled in order 350 to use the functionality of the device. 351 352config MFD_MAX8997 353 bool "Maxim Semiconductor MAX8997/8966 PMIC Support" 354 depends on I2C=y && GENERIC_HARDIRQS 355 select MFD_CORE 356 help 357 Say yes here to support for Maxim Semiconductor MAX8998/8966. 358 This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic, 359 MUIC controls on chip. 360 This driver provides common support for accessing the device; 361 additional drivers must be enabled in order to use the functionality 362 of the device. 363 364config MFD_MAX8998 365 bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support" 366 depends on I2C=y && GENERIC_HARDIRQS 367 select MFD_CORE 368 help 369 Say yes here to support for Maxim Semiconductor MAX8998 and 370 National Semiconductor LP3974. This is a Power Management IC. 371 This driver provies 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_WM8400 376 tristate "Support Wolfson Microelectronics WM8400" 377 select MFD_CORE 378 depends on I2C 379 select REGMAP_I2C 380 help 381 Support for the Wolfson Microelecronics WM8400 PMIC and audio 382 CODEC. This driver provides common support for accessing 383 the device, additional drivers must be enabled in order to use 384 the functionality of the device. 385 386config MFD_WM831X 387 bool 388 depends on GENERIC_HARDIRQS 389 390config MFD_WM831X_I2C 391 bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C" 392 select MFD_CORE 393 select MFD_WM831X 394 select REGMAP_I2C 395 depends on I2C=y && GENERIC_HARDIRQS 396 help 397 Support for the Wolfson Microelecronics WM831x and WM832x PMICs 398 when controlled using I2C. This driver provides common support 399 for accessing the device, additional drivers must be enabled in 400 order to use the functionality of the device. 401 402config MFD_WM831X_SPI 403 bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI" 404 select MFD_CORE 405 select MFD_WM831X 406 select REGMAP_SPI 407 depends on SPI_MASTER && GENERIC_HARDIRQS 408 help 409 Support for the Wolfson Microelecronics WM831x and WM832x PMICs 410 when controlled using SPI. This driver provides common support 411 for accessing the device, additional drivers must be enabled in 412 order to use the functionality of the device. 413 414config MFD_WM8350 415 bool 416 depends on GENERIC_HARDIRQS 417 418config MFD_WM8350_CONFIG_MODE_0 419 bool 420 depends on MFD_WM8350 421 422config MFD_WM8350_CONFIG_MODE_1 423 bool 424 depends on MFD_WM8350 425 426config MFD_WM8350_CONFIG_MODE_2 427 bool 428 depends on MFD_WM8350 429 430config MFD_WM8350_CONFIG_MODE_3 431 bool 432 depends on MFD_WM8350 433 434config MFD_WM8351_CONFIG_MODE_0 435 bool 436 depends on MFD_WM8350 437 438config MFD_WM8351_CONFIG_MODE_1 439 bool 440 depends on MFD_WM8350 441 442config MFD_WM8351_CONFIG_MODE_2 443 bool 444 depends on MFD_WM8350 445 446config MFD_WM8351_CONFIG_MODE_3 447 bool 448 depends on MFD_WM8350 449 450config MFD_WM8352_CONFIG_MODE_0 451 bool 452 depends on MFD_WM8350 453 454config MFD_WM8352_CONFIG_MODE_1 455 bool 456 depends on MFD_WM8350 457 458config MFD_WM8352_CONFIG_MODE_2 459 bool 460 depends on MFD_WM8350 461 462config MFD_WM8352_CONFIG_MODE_3 463 bool 464 depends on MFD_WM8350 465 466config MFD_WM8350_I2C 467 bool "Support Wolfson Microelectronics WM8350 with I2C" 468 select MFD_WM8350 469 depends on I2C=y && GENERIC_HARDIRQS 470 help 471 The WM8350 is an integrated audio and power management 472 subsystem with watchdog and RTC functionality for embedded 473 systems. This option enables core support for the WM8350 with 474 I2C as the control interface. Additional options must be 475 selected to enable support for the functionality of the chip. 476 477config MFD_WM8994 478 bool "Support Wolfson Microelectronics WM8994" 479 select MFD_CORE 480 select REGMAP_I2C 481 depends on I2C=y && GENERIC_HARDIRQS 482 help 483 The WM8994 is a highly integrated hi-fi CODEC designed for 484 smartphone applicatiosn. As well as audio functionality it 485 has on board GPIO and regulator functionality which is 486 supported via the relevant subsystems. This driver provides 487 core support for the WM8994, in order to use the actual 488 functionaltiy of the device other drivers must be enabled. 489 490config MFD_PCF50633 491 tristate "Support for NXP PCF50633" 492 depends on I2C 493 select REGMAP_I2C 494 help 495 Say yes here if you have NXP PCF50633 chip on your board. 496 This core driver provides register access and IRQ handling 497 facilities, and registers devices for the various functions 498 so that function-specific drivers can bind to them. 499 500config PCF50633_ADC 501 tristate "Support for NXP PCF50633 ADC" 502 depends on MFD_PCF50633 503 help 504 Say yes here if you want to include support for ADC in the 505 NXP PCF50633 chip. 506 507config PCF50633_GPIO 508 tristate "Support for NXP PCF50633 GPIO" 509 depends on MFD_PCF50633 510 help 511 Say yes here if you want to include support GPIO for pins on 512 the PCF50633 chip. 513 514config MFD_MC13783 515 tristate 516 517config MFD_MC13XXX 518 tristate "Support Freescale MC13783 and MC13892" 519 depends on SPI_MASTER 520 select MFD_CORE 521 select MFD_MC13783 522 help 523 Support for the Freescale (Atlas) PMIC and audio CODECs 524 MC13783 and MC13892. 525 This driver provides common support for accessing the device, 526 additional drivers must be enabled in order to use the 527 functionality of the device. 528 529config ABX500_CORE 530 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" 531 default y if ARCH_U300 || ARCH_U8500 532 help 533 Say yes here if you have the ABX500 Mixed Signal IC family 534 chips. This core driver expose register access functions. 535 Functionality specific drivers using these functions can 536 remain unchanged when IC changes. Binding of the functions to 537 actual register access is done by the IC core driver. 538 539config AB3100_CORE 540 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" 541 depends on I2C=y && ABX500_CORE 542 select MFD_CORE 543 default y if ARCH_U300 544 help 545 Select this to enable the AB3100 Mixed Signal IC core 546 functionality. This connects to a AB3100 on the I2C bus 547 and expose a number of symbols needed for dependent devices 548 to read and write registers and subscribe to events from 549 this multi-functional IC. This is needed to use other features 550 of the AB3100 such as battery-backed RTC, charging control, 551 LEDs, vibrator, system power and temperature, power management 552 and ALSA sound. 553 554config AB3100_OTP 555 tristate "ST-Ericsson AB3100 OTP functions" 556 depends on AB3100_CORE 557 default y if AB3100_CORE 558 help 559 Select this to enable the AB3100 Mixed Signal IC OTP (one-time 560 programmable memory) support. This exposes a sysfs file to read 561 out OTP values. 562 563config EZX_PCAP 564 bool "PCAP Support" 565 depends on GENERIC_HARDIRQS && SPI_MASTER 566 help 567 This enables the PCAP ASIC present on EZX Phones. This is 568 needed for MMC, TouchScreen, Sound, USB, etc.. 569 570config AB5500_CORE 571 bool "ST-Ericsson AB5500 Mixed Signal Power Management chip" 572 depends on ABX500_CORE && MFD_DB5500_PRCMU 573 select MFD_CORE 574 help 575 Select this option to enable access to AB5500 power management 576 chip. This connects to the db5500 chip via the I2C bus via PRCMU. 577 This chip embeds various other multimedia funtionalities as well. 578 579config AB5500_DEBUG 580 bool "Enable debug info via debugfs" 581 depends on AB5500_CORE && DEBUG_FS 582 default y if DEBUG_FS 583 help 584 Select this option if you want debug information from the AB5500 585 using the debug filesystem, debugfs. 586 587config AB8500_CORE 588 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" 589 depends on GENERIC_HARDIRQS && ABX500_CORE 590 select MFD_CORE 591 help 592 Select this option to enable access to AB8500 power management 593 chip. This connects to U8500 either on the SSP/SPI bus (deprecated 594 since hardware version v1.0) or the I2C bus via PRCMU. It also adds 595 the irq_chip parts for handling the Mixed Signal chip events. 596 This chip embeds various other multimedia funtionalities as well. 597 598config AB8500_I2C_CORE 599 bool "AB8500 register access via PRCMU I2C" 600 depends on AB8500_CORE && MFD_DB8500_PRCMU 601 default y 602 help 603 This enables register access to the AB8500 chip via PRCMU I2C. 604 The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware 605 the I2C bus is connected to the Power Reset 606 and Mangagement Unit, PRCMU. 607 608config AB8500_DEBUG 609 bool "Enable debug info via debugfs" 610 depends on AB8500_CORE && DEBUG_FS 611 default y if DEBUG_FS 612 help 613 Select this option if you want debug information using the debug 614 filesystem, debugfs. 615 616config AB8500_GPADC 617 bool "AB8500 GPADC driver" 618 depends on AB8500_CORE && REGULATOR_AB8500 619 default y 620 help 621 AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage 622 623config MFD_DB8500_PRCMU 624 bool "ST-Ericsson DB8500 Power Reset Control Management Unit" 625 depends on UX500_SOC_DB8500 626 select MFD_CORE 627 help 628 Select this option to enable support for the DB8500 Power Reset 629 and Control Management Unit. This is basically an autonomous 630 system controller running an XP70 microprocessor, which is accessed 631 through a register map. 632 633config MFD_DB5500_PRCMU 634 bool "ST-Ericsson DB5500 Power Reset Control Management Unit" 635 depends on UX500_SOC_DB5500 636 select MFD_CORE 637 help 638 Select this option to enable support for the DB5500 Power Reset 639 and Control Management Unit. This is basically an autonomous 640 system controller running an XP70 microprocessor, which is accessed 641 through a register map. 642 643config MFD_CS5535 644 tristate "Support for CS5535 and CS5536 southbridge core functions" 645 select MFD_CORE 646 depends on PCI && X86 647 ---help--- 648 This is the core driver for CS5535/CS5536 MFD functions. This is 649 necessary for using the board's GPIO and MFGPT functionality. 650 651config MFD_TIMBERDALE 652 tristate "Support for the Timberdale FPGA" 653 select MFD_CORE 654 depends on PCI && GPIOLIB 655 ---help--- 656 This is the core driver for the timberdale FPGA. This device is a 657 multifunction device which exposes numerous platform devices. 658 659 The timberdale FPGA can be found on the Intel Atom development board 660 for in-vehicle infontainment, called Russellville. 661 662config LPC_SCH 663 tristate "Intel SCH LPC" 664 depends on PCI 665 select MFD_CORE 666 help 667 LPC bridge function of the Intel SCH provides support for 668 System Management Bus and General Purpose I/O. 669 670config MFD_RDC321X 671 tristate "Support for RDC-R321x southbridge" 672 select MFD_CORE 673 depends on PCI 674 help 675 Say yes here if you want to have support for the RDC R-321x SoC 676 southbridge which provides access to GPIOs and Watchdog using the 677 southbridge PCI device configuration space. 678 679config MFD_JANZ_CMODIO 680 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board" 681 select MFD_CORE 682 depends on PCI 683 help 684 This is the core driver for the Janz CMOD-IO PCI MODULbus 685 carrier board. This device is a PCI to MODULbus bridge which may 686 host many different types of MODULbus daughterboards, including 687 CAN and GPIO controllers. 688 689config MFD_JZ4740_ADC 690 bool "Support for the JZ4740 SoC ADC core" 691 select MFD_CORE 692 select GENERIC_IRQ_CHIP 693 depends on MACH_JZ4740 694 help 695 Say yes here if you want support for the ADC unit in the JZ4740 SoC. 696 This driver is necessary for jz4740-battery and jz4740-hwmon driver. 697 698config MFD_VX855 699 tristate "Support for VIA VX855/VX875 integrated south bridge" 700 depends on PCI 701 select MFD_CORE 702 help 703 Say yes here to enable support for various functions of the 704 VIA VX855/VX875 south bridge. You will need to enable the vx855_spi 705 and/or vx855_gpio drivers for this to do anything useful. 706 707config MFD_WL1273_CORE 708 tristate "Support for TI WL1273 FM radio." 709 depends on I2C 710 select MFD_CORE 711 default n 712 help 713 This is the core driver for the TI WL1273 FM radio. This MFD 714 driver connects the radio-wl1273 V4L2 module and the wl1273 715 audio codec. 716 717config MFD_OMAP_USB_HOST 718 bool "Support OMAP USBHS core driver" 719 depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3 720 default y 721 help 722 This is the core driver for the OAMP EHCI and OHCI drivers. 723 This MFD driver does the required setup functionalities for 724 OMAP USB Host drivers. 725 726config MFD_PM8XXX 727 tristate 728 729config MFD_PM8921_CORE 730 tristate "Qualcomm PM8921 PMIC chip" 731 depends on MSM_SSBI 732 select MFD_CORE 733 select MFD_PM8XXX 734 help 735 If you say yes to this option, support will be included for the 736 built-in PM8921 PMIC chip. 737 738 This is required if your board has a PM8921 and uses its features, 739 such as: MPPs, GPIOs, regulators, interrupts, and PWM. 740 741 Say M here if you want to include support for PM8921 chip as a module. 742 This will build a module called "pm8921-core". 743 744config MFD_PM8XXX_IRQ 745 bool "Support for Qualcomm PM8xxx IRQ features" 746 depends on MFD_PM8XXX 747 default y if MFD_PM8XXX 748 help 749 This is the IRQ driver for Qualcomm PM 8xxx PMIC chips. 750 751 This is required to use certain other PM 8xxx features, such as GPIO 752 and MPP. 753 754config TPS65911_COMPARATOR 755 tristate 756 757config MFD_AAT2870_CORE 758 bool "Support for the AnalogicTech AAT2870" 759 select MFD_CORE 760 depends on I2C=y && GPIOLIB 761 help 762 If you say yes here you get support for the AAT2870. 763 This driver provides common support for accessing the device, 764 additional drivers must be enabled in order to use the 765 functionality of the device. 766 767config MFD_INTEL_MSIC 768 bool "Support for Intel MSIC" 769 depends on INTEL_SCU_IPC 770 select MFD_CORE 771 help 772 Select this option to enable access to Intel MSIC (Avatele 773 Passage) chip. This chip embeds audio, battery, GPIO, etc. 774 devices used in Intel Medfield platforms. 775 776endmenu 777endif 778 779menu "Multimedia Capabilities Port drivers" 780 depends on ARCH_SA1100 781 782config MCP 783 tristate 784 785# Interface drivers 786config MCP_SA11X0 787 tristate "Support SA11x0 MCP interface" 788 depends on ARCH_SA1100 789 select MCP 790 791# Chip drivers 792config MCP_UCB1200 793 tristate "Support for UCB1200 / UCB1300" 794 depends on MCP 795 796config MCP_UCB1200_TS 797 tristate "Touchscreen interface support" 798 depends on MCP_UCB1200 && INPUT 799 800endmenu 801