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