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 MFD_CORE
 137         select REGULATOR_FIXED_VOLTAGE
 138         help
 139           This option enables a driver for the TP61050/TPS61052
 140           high-power "white LED driver". This boost converter is
 141           sometimes used for other things than white LEDs, and
 142           also contains a GPIO pin.
 143
 144 config TPS65010
 145         tristate "TPS6501x Power Management chips"
 146         depends on I2C && GPIOLIB
 147         default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
 148         help
 149           If you say yes here you get support for the TPS6501x series of
 150           Power Management chips.  These include voltage regulators,
 151           lithium ion/polymer battery charging, and other features that
 152           are often used in portable devices like cell phones and cameras.
 153
 154           This driver can also be built as a module.  If so, the module
 155           will be called tps65010.
 156
 157 config TPS6507X
 158         tristate "TPS6507x Power Management / Touch Screen chips"
 159         select MFD_CORE
 160         depends on I2C
 161         help
 162           If you say yes here you get support for the TPS6507x series of
 163           Power Management / Touch Screen chips.  These include voltage
 164           regulators, lithium ion/polymer battery charging, touch screen
 165           and other features that are often used in portable devices.
 166           This driver can also be built as a module.  If so, the module
 167           will be called tps6507x.
 168
 169 config MENELAUS
 170         bool "Texas Instruments TWL92330/Menelaus PM chip"
 171         depends on I2C=y && ARCH_OMAP2
 172         help
 173           If you say yes here you get support for the Texas Instruments
 174           TWL92330/Menelaus Power Management chip. This include voltage
 175           regulators, Dual slot memory card transceivers, real-time clock
 176           and other features that are often used in portable devices like
 177           cell phones and PDAs.
 178
 179 config TWL4030_CORE
 180         bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
 181         depends on I2C=y && GENERIC_HARDIRQS
 182         help
 183           Say yes here if you have TWL4030 / TWL6030 family chip on your board.
 184           This core driver provides register access and IRQ handling
 185           facilities, and registers devices for the various functions
 186           so that function-specific drivers can bind to them.
 187
 188           These multi-function chips are found on many OMAP2 and OMAP3
 189           boards, providing power management, RTC, GPIO, keypad, a
 190           high speed USB OTG transceiver, an audio codec (on most
 191           versions) and many other features.
 192
 193 config TWL4030_MADC
 194         tristate "Texas Instruments TWL4030 MADC"
 195         depends on TWL4030_CORE
 196         help
 197         This driver provides support for triton TWL4030-MADC. The
 198         driver supports both RT and SW conversion methods.
 199
 200         This driver can be built as a module. If so it will be
 201         named twl4030-madc
 202
 203 config TWL4030_POWER
 204         bool "Support power resources on TWL4030 family chips"
 205         depends on TWL4030_CORE && ARM
 206         help
 207           Say yes here if you want to use the power resources on the
 208           TWL4030 family chips.  Most of these resources are regulators,
 209           which have a separate driver; some are control signals, such
 210           as clock request handshaking.
 211
 212           This driver uses board-specific data to initialize the resources
 213           and load scripts controling which resources are switched off/on
 214           or reset when a sleep, wakeup or warm reset event occurs.
 215
 216 config TWL4030_CODEC
 217         bool
 218         depends on TWL4030_CORE
 219         select MFD_CORE
 220         default n
 221
 222 config TWL6030_PWM
 223         tristate "TWL6030 PWM (Pulse Width Modulator) Support"
 224         depends on TWL4030_CORE
 225         select HAVE_PWM
 226         default n
 227         help
 228           Say yes here if you want support for TWL6030 PWM.
 229           This is used to control charging LED brightness.
 230
 231 config MFD_STMPE
 232         bool "Support STMicroelectronics STMPE"
 233         depends on I2C=y && GENERIC_HARDIRQS
 234         select MFD_CORE
 235         help
 236           Support for the STMPE family of I/O Expanders from
 237           STMicroelectronics.
 238
 239           Currently supported devices are:
 240
 241                 STMPE811: GPIO, Touchscreen
 242                 STMPE1601: GPIO, Keypad
 243                 STMPE2401: GPIO, Keypad
 244                 STMPE2403: GPIO, Keypad
 245
 246           This driver provides common support for accessing the device,
 247           additional drivers must be enabled in order to use the functionality
 248           of the device.  Currently available sub drivers are:
 249
 250                 GPIO: stmpe-gpio
 251                 Keypad: stmpe-keypad
 252                 Touchscreen: stmpe-ts
 253
 254 config MFD_TC3589X
 255         bool "Support Toshiba TC35892 and variants"
 256         depends on I2C=y && GENERIC_HARDIRQS
 257         select MFD_CORE
 258         help
 259           Support for the Toshiba TC35892 and variants I/O Expander.
 260
 261           This driver provides common support for accessing the device,
 262           additional drivers must be enabled in order to use the
 263           functionality of the device.
 264
 265 config MFD_TMIO
 266         bool
 267         default n
 268
 269 config TMIO_MMC_DMA
 270         bool
 271         select DMA_ENGINE
 272         select DMADEVICES
 273
 274 config 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
 282 config 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
 290 config 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
 298 config 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
 309 config 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
 319 config 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
 329 config 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
 341 config 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
 352 config 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
 362 config MFD_WM831X
 363         bool
 364         depends on GENERIC_HARDIRQS
 365
 366 config 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
 377 config 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
 388 config MFD_WM8350
 389         bool
 390         depends on GENERIC_HARDIRQS
 391
 392 config MFD_WM8350_CONFIG_MODE_0
 393         bool
 394         depends on MFD_WM8350
 395
 396 config MFD_WM8350_CONFIG_MODE_1
 397         bool
 398         depends on MFD_WM8350
 399
 400 config MFD_WM8350_CONFIG_MODE_2
 401         bool
 402         depends on MFD_WM8350
 403
 404 config MFD_WM8350_CONFIG_MODE_3
 405         bool
 406         depends on MFD_WM8350
 407
 408 config MFD_WM8351_CONFIG_MODE_0
 409         bool
 410         depends on MFD_WM8350
 411
 412 config MFD_WM8351_CONFIG_MODE_1
 413         bool
 414         depends on MFD_WM8350
 415
 416 config MFD_WM8351_CONFIG_MODE_2
 417         bool
 418         depends on MFD_WM8350
 419
 420 config MFD_WM8351_CONFIG_MODE_3
 421         bool
 422         depends on MFD_WM8350
 423
 424 config MFD_WM8352_CONFIG_MODE_0
 425         bool
 426         depends on MFD_WM8350
 427
 428 config MFD_WM8352_CONFIG_MODE_1
 429         bool
 430         depends on MFD_WM8350
 431
 432 config MFD_WM8352_CONFIG_MODE_2
 433         bool
 434         depends on MFD_WM8350
 435
 436 config MFD_WM8352_CONFIG_MODE_3
 437         bool
 438         depends on MFD_WM8350
 439
 440 config 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
 451 config 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
 463 config 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
 472 config MFD_MC13783
 473         tristate
 474
 475 config MFD_MC13XXX
 476         tristate "Support Freescale MC13783 and MC13892"
 477         depends on SPI_MASTER
 478         select MFD_CORE
 479         select MFD_MC13783
 480         help
 481           Support for the Freescale (Atlas) PMIC and audio CODECs
 482           MC13783 and MC13892.
 483           This driver provides common support for accessing  the device,
 484           additional drivers must be enabled in order to use the
 485           functionality of the device.
 486
 487 config PCF50633_ADC
 488         tristate "Support for NXP PCF50633 ADC"
 489         depends on MFD_PCF50633
 490         help
 491          Say yes here if you want to include support for ADC in the
 492          NXP PCF50633 chip.
 493
 494 config PCF50633_GPIO
 495         tristate "Support for NXP PCF50633 GPIO"
 496         depends on MFD_PCF50633
 497         help
 498          Say yes here if you want to include support GPIO for pins on
 499          the PCF50633 chip.
 500
 501 config 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
 511 config 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
 526 config 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
 535 config 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
 542 config 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
 553 config AB8500_I2C_CORE
 554         bool "AB8500 register access via PRCMU I2C"
 555         depends on AB8500_CORE && UX500_SOC_DB8500
 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
 563 config 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
 571 config 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
 578 config 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
 592 config MFD_CS5535
 593         tristate "Support for CS5535 and CS5536 southbridge core functions"
 594         select MFD_CORE
 595         depends on PCI
 596         ---help---
 597           This is the core driver for CS5535/CS5536 MFD functions.  This is
 598           necessary for using the board's GPIO and MFGPT functionality.
 599
 600 config MFD_TIMBERDALE
 601         tristate "Support for the Timberdale FPGA"
 602         select MFD_CORE
 603         depends on PCI && GPIOLIB
 604         ---help---
 605         This is the core driver for the timberdale FPGA. This device is a
 606         multifunction device which exposes numerous platform devices.
 607
 608         The timberdale FPGA can be found on the Intel Atom development board
 609         for in-vehicle infontainment, called Russellville.
 610
 611 config LPC_SCH
 612         tristate "Intel SCH LPC"
 613         depends on PCI
 614         select MFD_CORE
 615         help
 616           LPC bridge function of the Intel SCH provides support for
 617           System Management Bus and General Purpose I/O.
 618
 619 config MFD_RDC321X
 620         tristate "Support for RDC-R321x southbridge"
 621         select MFD_CORE
 622         depends on PCI
 623         help
 624           Say yes here if you want to have support for the RDC R-321x SoC
 625           southbridge which provides access to GPIOs and Watchdog using the
 626           southbridge PCI device configuration space.
 627
 628 config MFD_JANZ_CMODIO
 629         tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
 630         select MFD_CORE
 631         depends on PCI
 632         help
 633           This is the core driver for the Janz CMOD-IO PCI MODULbus
 634           carrier board. This device is a PCI to MODULbus bridge which may
 635           host many different types of MODULbus daughterboards, including
 636           CAN and GPIO controllers.
 637
 638 config MFD_JZ4740_ADC
 639         tristate "Support for the JZ4740 SoC ADC core"
 640         select MFD_CORE
 641         depends on MACH_JZ4740
 642         help
 643           Say yes here if you want support for the ADC unit in the JZ4740 SoC.
 644           This driver is necessary for jz4740-battery and jz4740-hwmon driver.
 645
 646 config MFD_TPS6586X
 647         bool "TPS6586x Power Management chips"
 648         depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
 649         select MFD_CORE
 650         help
 651           If you say yes here you get support for the TPS6586X series of
 652           Power Management chips.
 653           This driver provides common support for accessing the device,
 654           additional drivers must be enabled in order to use the
 655           functionality of the device.
 656
 657           This driver can also be built as a module.  If so, the module
 658           will be called tps6586x.
 659
 660 config MFD_VX855
 661         tristate "Support for VIA VX855/VX875 integrated south bridge"
 662         depends on PCI
 663         select MFD_CORE
 664         help
 665           Say yes here to enable support for various functions of the
 666           VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
 667           and/or vx855_gpio drivers for this to do anything useful.
 668
 669 config MFD_WL1273_CORE
 670         tristate "Support for TI WL1273 FM radio."
 671         depends on I2C
 672         select MFD_CORE
 673         default n
 674         help
 675           This is the core driver for the TI WL1273 FM radio. This MFD
 676           driver connects the radio-wl1273 V4L2 module and the wl1273
 677           audio codec.
 678
 679 config MFD_OMAP_USB_HOST
 680         bool "Support OMAP USBHS core driver"
 681         depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
 682         default y
 683         help
 684           This is the core driver for the OAMP EHCI and OHCI drivers.
 685           This MFD driver does the required setup functionalities for
 686           OMAP USB Host drivers.
 687
 688 endif # MFD_SUPPORT
 689
 690 menu "Multimedia Capabilities Port drivers"
 691         depends on ARCH_SA1100
 692
 693 config MCP
 694         tristate
 695
 696 # Interface drivers
 697 config MCP_SA11X0
 698         tristate "Support SA11x0 MCP interface"
 699         depends on ARCH_SA1100
 700         select MCP
 701
 702 # Chip drivers
 703 config MCP_UCB1200
 704         tristate "Support for UCB1200 / UCB1300"
 705         depends on MCP
 706
 707 config MCP_UCB1200_TS
 708         tristate "Touchscreen interface support"
 709         depends on MCP_UCB1200 && INPUT
 710
 711 endmenu