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