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