drivers/mfd/Kconfig

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