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