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