drivers/mfd/Kconfig

   1 #
   2 # Multifunction miscellaneous devices
   3 #
   4
   5 if HAS_IOMEM
   6 menu "Multifunction device drivers"
   7
   8 config MFD_CORE
   9         tristate
  10         select IRQ_DOMAIN
  11         default n
  12
  13 config MFD_88PM860X
  14         bool "Support Marvell 88PM8606/88PM8607"
  15         depends on I2C=y && GENERIC_HARDIRQS
  16         select REGMAP_I2C
  17         select MFD_CORE
  18         help
  19           This supports for Marvell 88PM8606/88PM8607 Power Management IC.
  20           This includes the I2C driver and the core APIs _only_, you have to
  21           select individual components like voltage regulators, RTC and
  22           battery-charger under the corresponding menus.
  23
  24 config MFD_CROS_EC
  25         tristate "Support ChromeOS Embedded Controller"
  26         select MFD_CORE
  27         help
  28           If you say Y here you get support for the ChromeOS Embedded
  29           Controller (EC) providing keyboard, battery and power services.
  30           You also ned to enable the driver for the bus you are using. The
  31           protocol for talking to the EC is defined by the bus driver.
  32
  33 config MFD_CROS_EC_I2C
  34         tristate "ChromeOS Embedded Controller (I2C)"
  35         depends on MFD_CROS_EC && I2C
  36
  37         help
  38           If you say Y here, you get support for talking to the ChromeOS
  39           EC through an I2C bus. This uses a simple byte-level protocol with
  40           a checksum. Failing accesses will be retried three times to
  41           improve reliability.
  42
  43 config MFD_CROS_EC_SPI
  44         tristate "ChromeOS Embedded Controller (SPI)"
  45         depends on MFD_CROS_EC && SPI
  46
  47         ---help---
  48           If you say Y here, you get support for talking to the ChromeOS EC
  49           through a SPI bus, using a byte-level protocol. Since the EC's
  50           response time cannot be guaranteed, we support ignoring
  51           'pre-amble' bytes before the response actually starts.
  52
  53 config MFD_88PM800
  54         tristate "Support Marvell 88PM800"
  55         depends on I2C=y && GENERIC_HARDIRQS
  56         select REGMAP_I2C
  57         select REGMAP_IRQ
  58         select MFD_CORE
  59         help
  60           This supports for Marvell 88PM800 Power Management IC.
  61           This includes the I2C driver and the core APIs _only_, you have to
  62           select individual components like voltage regulators, RTC and
  63           battery-charger under the corresponding menus.
  64
  65 config MFD_88PM805
  66         tristate "Support Marvell 88PM805"
  67         depends on I2C=y && GENERIC_HARDIRQS
  68         select REGMAP_I2C
  69         select REGMAP_IRQ
  70         select MFD_CORE
  71         help
  72           This supports for Marvell 88PM805 Power Management IC. This includes
  73           the I2C driver and the core APIs _only_, you have to select individual
  74           components like codec device, headset/Mic device under the
  75           corresponding menus.
  76
  77 config MFD_SM501
  78         tristate "Support for Silicon Motion SM501"
  79          ---help---
  80           This is the core driver for the Silicon Motion SM501 multimedia
  81           companion chip. This device is a multifunction device which may
  82           provide numerous interfaces including USB host controller, USB gadget,
  83           asynchronous serial ports, audio functions, and a dual display video
  84           interface. The device may be connected by PCI or local bus with
  85           varying functions enabled.
  86
  87 config MFD_SM501_GPIO
  88         bool "Export GPIO via GPIO layer"
  89         depends on MFD_SM501 && GPIOLIB
  90          ---help---
  91          This option uses the gpio library layer to export the 64 GPIO
  92          lines on the SM501. The platform data is used to supply the
  93          base number for the first GPIO line to register.
  94
  95 config MFD_RTSX_PCI
  96         tristate "Support for Realtek PCI-E card reader"
  97         depends on PCI && GENERIC_HARDIRQS
  98         select MFD_CORE
  99         help
 100           This supports for Realtek PCI-Express card reader including rts5209,
 101           rts5229, rtl8411, etc. Realtek card reader supports access to many
 102           types of memory cards, such as Memory Stick, Memory Stick Pro,
 103           Secure Digital and MultiMediaCard.
 104
 105 config MFD_ASIC3
 106         bool "Support for Compaq ASIC3"
 107         depends on GENERIC_HARDIRQS && GPIOLIB && ARM
 108         select MFD_CORE
 109          ---help---
 110           This driver supports the ASIC3 multifunction chip found on many
 111           PDAs (mainly iPAQ and HTC based ones)
 112
 113 config MFD_DAVINCI_VOICECODEC
 114         tristate
 115         select MFD_CORE
 116
 117 config MFD_DM355EVM_MSP
 118         bool "DaVinci DM355 EVM microcontroller"
 119         depends on I2C=y && MACH_DAVINCI_DM355_EVM
 120         help
 121           This driver supports the MSP430 microcontroller used on these
 122           boards.  MSP430 firmware manages resets and power sequencing,
 123           inputs from buttons and the IR remote, LEDs, an RTC, and more.
 124
 125 config MFD_TI_SSP
 126         tristate "TI Sequencer Serial Port support"
 127         depends on ARCH_DAVINCI_TNETV107X && GENERIC_HARDIRQS
 128         select MFD_CORE
 129         ---help---
 130           Say Y here if you want support for the Sequencer Serial Port
 131           in a Texas Instruments TNETV107X SoC.
 132
 133           To compile this driver as a module, choose M here: the
 134           module will be called ti-ssp.
 135
 136 config MFD_TI_AM335X_TSCADC
 137         tristate "TI ADC / Touch Screen chip support"
 138         select MFD_CORE
 139         select REGMAP
 140         select REGMAP_MMIO
 141         depends on GENERIC_HARDIRQS
 142         help
 143           If you say yes here you get support for Texas Instruments series
 144           of Touch Screen /ADC chips.
 145           To compile this driver as a module, choose M here: the
 146           module will be called ti_am335x_tscadc.
 147
 148 config HTC_EGPIO
 149         bool "HTC EGPIO support"
 150         depends on GENERIC_HARDIRQS && GPIOLIB && ARM
 151         help
 152             This driver supports the CPLD egpio chip present on
 153             several HTC phones.  It provides basic support for input
 154             pins, output pins, and irqs.
 155
 156 config HTC_PASIC3
 157         tristate "HTC PASIC3 LED/DS1WM chip support"
 158         select MFD_CORE
 159         depends on GENERIC_HARDIRQS
 160         help
 161           This core driver provides register access for the LED/DS1WM
 162           chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
 163           HTC Magician devices, respectively. Actual functionality is
 164           handled by the leds-pasic3 and ds1wm drivers.
 165
 166 config HTC_I2CPLD
 167         bool "HTC I2C PLD chip support"
 168         depends on I2C=y && GPIOLIB
 169         help
 170           If you say yes here you get support for the supposed CPLD
 171           found on omap850 HTC devices like the HTC Wizard and HTC Herald.
 172           This device provides input and output GPIOs through an I2C
 173           interface to one or more sub-chips.
 174
 175 config UCB1400_CORE
 176         tristate "Philips UCB1400 Core driver"
 177         depends on AC97_BUS
 178         depends on GPIOLIB
 179         help
 180           This enables support for the Philips UCB1400 core functions.
 181           The UCB1400 is an AC97 audio codec.
 182
 183           To compile this driver as a module, choose M here: the
 184           module will be called ucb1400_core.
 185
 186 config MFD_LM3533
 187         tristate "LM3533 Lighting Power chip"
 188         depends on I2C
 189         select MFD_CORE
 190         select REGMAP_I2C
 191         depends on GENERIC_HARDIRQS
 192         help
 193           Say yes here to enable support for National Semiconductor / TI
 194           LM3533 Lighting Power chips.
 195
 196           This driver provides common support for accessing the device;
 197           additional drivers must be enabled in order to use the LED,
 198           backlight or ambient-light-sensor functionality of the device.
 199
 200 config TPS6105X
 201         tristate "TPS61050/61052 Boost Converters"
 202         depends on I2C
 203         select REGULATOR
 204         select MFD_CORE
 205         select REGULATOR_FIXED_VOLTAGE
 206         depends on GENERIC_HARDIRQS
 207         help
 208           This option enables a driver for the TP61050/TPS61052
 209           high-power "white LED driver". This boost converter is
 210           sometimes used for other things than white LEDs, and
 211           also contains a GPIO pin.
 212
 213 config TPS65010
 214         tristate "TPS6501x Power Management chips"
 215         depends on I2C && GPIOLIB
 216         default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
 217         help
 218           If you say yes here you get support for the TPS6501x series of
 219           Power Management chips.  These include voltage regulators,
 220           lithium ion/polymer battery charging, and other features that
 221           are often used in portable devices like cell phones and cameras.
 222
 223           This driver can also be built as a module.  If so, the module
 224           will be called tps65010.
 225
 226 config TPS6507X
 227         tristate "TPS6507x Power Management / Touch Screen chips"
 228         select MFD_CORE
 229         depends on I2C && GENERIC_HARDIRQS
 230         help
 231           If you say yes here you get support for the TPS6507x series of
 232           Power Management / Touch Screen chips.  These include voltage
 233           regulators, lithium ion/polymer battery charging, touch screen
 234           and other features that are often used in portable devices.
 235           This driver can also be built as a module.  If so, the module
 236           will be called tps6507x.
 237
 238 config MFD_TPS65217
 239         tristate "TPS65217 Power Management / White LED chips"
 240         depends on I2C && GENERIC_HARDIRQS
 241         select MFD_CORE
 242         select REGMAP_I2C
 243         help
 244           If you say yes here you get support for the TPS65217 series of
 245           Power Management / White LED chips.
 246           These include voltage regulators, lithium ion/polymer battery
 247           charger, wled and other features that are often used in portable
 248           devices.
 249
 250           This driver can also be built as a module.  If so, the module
 251           will be called tps65217.
 252
 253 config MFD_TPS6586X
 254         bool "TPS6586x Power Management chips"
 255         depends on I2C=y && GENERIC_HARDIRQS
 256         select MFD_CORE
 257         select REGMAP_I2C
 258         help
 259           If you say yes here you get support for the TPS6586X series of
 260           Power Management chips.
 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           This driver can also be built as a module.  If so, the module
 266           will be called tps6586x.
 267
 268 config MFD_TPS65910
 269         bool "TPS65910 Power Management chip"
 270         depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
 271         select MFD_CORE
 272         select REGMAP_I2C
 273         select REGMAP_IRQ
 274         select IRQ_DOMAIN
 275         help
 276           if you say yes here you get support for the TPS65910 series of
 277           Power Management chips.
 278
 279 config MFD_TPS65912
 280         bool
 281         depends on GPIOLIB
 282
 283 config MFD_TPS65912_I2C
 284         bool "TPS65912 Power Management chip with I2C"
 285         select MFD_CORE
 286         select MFD_TPS65912
 287         depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
 288         help
 289           If you say yes here you get support for the TPS65912 series of
 290           PM chips with I2C interface.
 291
 292 config MFD_TPS65912_SPI
 293         bool "TPS65912 Power Management chip with SPI"
 294         select MFD_CORE
 295         select MFD_TPS65912
 296         depends on SPI_MASTER && GPIOLIB && GENERIC_HARDIRQS
 297         help
 298           If you say yes here you get support for the TPS65912 series of
 299           PM chips with SPI interface.
 300
 301 config MFD_TPS80031
 302         bool "TI TPS80031/TPS80032 Power Management chips"
 303         depends on I2C=y && GENERIC_HARDIRQS
 304         select MFD_CORE
 305         select REGMAP_I2C
 306         select REGMAP_IRQ
 307         help
 308           If you say yes here you get support for the Texas Instruments
 309           TPS80031/ TPS80032 Fully Integrated Power Management with Power
 310           Path and Battery Charger. The device provides five configurable
 311           step-down converters, 11 general purpose LDOs, USB OTG Module,
 312           ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
 313           Power Path from USB, 32K clock generator.
 314
 315 config MENELAUS
 316         bool "Texas Instruments TWL92330/Menelaus PM chip"
 317         depends on I2C=y && ARCH_OMAP2
 318         help
 319           If you say yes here you get support for the Texas Instruments
 320           TWL92330/Menelaus Power Management chip. This include voltage
 321           regulators, Dual slot memory card transceivers, real-time clock
 322           and other features that are often used in portable devices like
 323           cell phones and PDAs.
 324
 325 config TWL4030_CORE
 326         bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
 327         depends on I2C=y && GENERIC_HARDIRQS
 328         select IRQ_DOMAIN
 329         select REGMAP_I2C
 330         help
 331           Say yes here if you have TWL4030 / TWL6030 family chip on your board.
 332           This core driver provides register access and IRQ handling
 333           facilities, and registers devices for the various functions
 334           so that function-specific drivers can bind to them.
 335
 336           These multi-function chips are found on many OMAP2 and OMAP3
 337           boards, providing power management, RTC, GPIO, keypad, a
 338           high speed USB OTG transceiver, an audio codec (on most
 339           versions) and many other features.
 340
 341 config TWL4030_MADC
 342         tristate "Texas Instruments TWL4030 MADC"
 343         depends on TWL4030_CORE
 344         help
 345         This driver provides support for triton TWL4030-MADC. The
 346         driver supports both RT and SW conversion methods.
 347
 348         This driver can be built as a module. If so it will be
 349         named twl4030-madc
 350
 351 config TWL4030_POWER
 352         bool "Support power resources on TWL4030 family chips"
 353         depends on TWL4030_CORE && ARM
 354         help
 355           Say yes here if you want to use the power resources on the
 356           TWL4030 family chips.  Most of these resources are regulators,
 357           which have a separate driver; some are control signals, such
 358           as clock request handshaking.
 359
 360           This driver uses board-specific data to initialize the resources
 361           and load scripts controlling which resources are switched off/on
 362           or reset when a sleep, wakeup or warm reset event occurs.
 363
 364 config MFD_TWL4030_AUDIO
 365         bool
 366         depends on TWL4030_CORE && GENERIC_HARDIRQS
 367         select MFD_CORE
 368         default n
 369
 370 config TWL6040_CORE
 371         bool "Support for TWL6040 audio codec"
 372         depends on I2C=y && GENERIC_HARDIRQS
 373         select MFD_CORE
 374         select REGMAP_I2C
 375         select REGMAP_IRQ
 376         default n
 377         help
 378           Say yes here if you want support for Texas Instruments TWL6040 audio
 379           codec.
 380           This driver provides common support for accessing the device,
 381           additional drivers must be enabled in order to use the
 382           functionality of the device (audio, vibra).
 383
 384 config MFD_STMPE
 385         bool "Support STMicroelectronics STMPE"
 386         depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
 387         select MFD_CORE
 388         help
 389           Support for the STMPE family of I/O Expanders from
 390           STMicroelectronics.
 391
 392           Currently supported devices are:
 393
 394                 STMPE811: GPIO, Touchscreen
 395                 STMPE1601: GPIO, Keypad
 396                 STMPE2401: GPIO, Keypad
 397                 STMPE2403: GPIO, Keypad
 398
 399           This driver provides common support for accessing the device,
 400           additional drivers must be enabled in order to use the functionality
 401           of the device.  Currently available sub drivers are:
 402
 403                 GPIO: stmpe-gpio
 404                 Keypad: stmpe-keypad
 405                 Touchscreen: stmpe-ts
 406
 407 menu "STMPE Interface Drivers"
 408 depends on MFD_STMPE
 409
 410 config STMPE_I2C
 411         bool "STMPE I2C Inteface"
 412         depends on I2C=y
 413         default y
 414         help
 415           This is used to enable I2C interface of STMPE
 416
 417 config STMPE_SPI
 418         bool "STMPE SPI Inteface"
 419         depends on SPI_MASTER
 420         help
 421           This is used to enable SPI interface of STMPE
 422 endmenu
 423
 424 config MFD_TC3589X
 425         bool "Support Toshiba TC35892 and variants"
 426         depends on I2C=y && GENERIC_HARDIRQS
 427         select MFD_CORE
 428         help
 429           Support for the Toshiba TC35892 and variants I/O Expander.
 430
 431           This driver provides common support for accessing the device,
 432           additional drivers must be enabled in order to use the
 433           functionality of the device.
 434
 435 config MFD_TMIO
 436         bool
 437         default n
 438
 439 config MFD_T7L66XB
 440         bool "Support Toshiba T7L66XB"
 441         depends on ARM && HAVE_CLK && GENERIC_HARDIRQS
 442         select MFD_CORE
 443         select MFD_TMIO
 444         help
 445           Support for Toshiba Mobile IO Controller T7L66XB
 446
 447 config MFD_SMSC
 448        bool "Support for the SMSC ECE1099 series chips"
 449        depends on I2C=y && GENERIC_HARDIRQS
 450        select MFD_CORE
 451        select REGMAP_I2C
 452        help
 453         If you say yes here you get support for the
 454         ece1099 chips from SMSC.
 455
 456         To compile this driver as a module, choose M here: the
 457         module will be called smsc.
 458
 459 config MFD_TC6387XB
 460         bool "Support Toshiba TC6387XB"
 461         depends on ARM && HAVE_CLK
 462         select MFD_CORE
 463         select MFD_TMIO
 464         help
 465           Support for Toshiba Mobile IO Controller TC6387XB
 466
 467 config MFD_TC6393XB
 468         bool "Support Toshiba TC6393XB"
 469         depends on ARM && HAVE_CLK
 470         select GPIOLIB
 471         select MFD_CORE
 472         select MFD_TMIO
 473         help
 474           Support for Toshiba Mobile IO Controller TC6393XB
 475
 476 config PMIC_DA903X
 477         bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
 478         depends on I2C=y
 479         help
 480           Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
 481           ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
 482           usually found on PXA processors-based platforms. This includes
 483           the I2C driver and the core APIs _only_, you have to select
 484           individual components like LCD backlight, voltage regulators,
 485           LEDs and battery-charger under the corresponding menus.
 486
 487 config PMIC_DA9052
 488         bool
 489         select MFD_CORE
 490
 491 config MFD_DA9052_SPI
 492         bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI"
 493         select REGMAP_SPI
 494         select REGMAP_IRQ
 495         select PMIC_DA9052
 496         depends on SPI_MASTER=y && GENERIC_HARDIRQS
 497         help
 498           Support for the Dialog Semiconductor DA9052 PMIC
 499           when controlled using SPI. This driver provides common support
 500           for accessing the device, additional drivers must be enabled in
 501           order to use the functionality of the device.
 502
 503 config MFD_DA9052_I2C
 504         bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C"
 505         select REGMAP_I2C
 506         select REGMAP_IRQ
 507         select PMIC_DA9052
 508         depends on I2C=y && GENERIC_HARDIRQS
 509         help
 510           Support for the Dialog Semiconductor DA9052 PMIC
 511           when controlled using I2C. This driver provides common support
 512           for accessing the device, additional drivers must be enabled in
 513           order to use the functionality of the device.
 514
 515 config MFD_DA9055
 516         bool "Dialog Semiconductor DA9055 PMIC Support"
 517         select REGMAP_I2C
 518         select REGMAP_IRQ
 519         select PMIC_DA9055
 520         select MFD_CORE
 521         depends on I2C=y && GENERIC_HARDIRQS
 522         help
 523           Say yes here for support of Dialog Semiconductor DA9055. This is
 524           a Power Management IC. This driver provides common support for
 525           accessing the device as well as the I2C interface to the chip itself.
 526           Additional drivers must be enabled in order to use the functionality
 527           of the device.
 528
 529           This driver can be built as a module. If built as a module it will be
 530           called "da9055"
 531
 532 config PMIC_ADP5520
 533         bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
 534         depends on I2C=y
 535         help
 536           Say yes here to add support for Analog Devices AD5520 and ADP5501,
 537           Multifunction Power Management IC. This includes
 538           the I2C driver and the core APIs _only_, you have to select
 539           individual components like LCD backlight, LEDs, GPIOs and Kepad
 540           under the corresponding menus.
 541
 542 config MFD_LP8788
 543         bool "Texas Instruments LP8788 Power Management Unit Driver"
 544         depends on I2C=y && GENERIC_HARDIRQS
 545         select MFD_CORE
 546         select REGMAP_I2C
 547         select IRQ_DOMAIN
 548         help
 549           TI LP8788 PMU supports regulators, battery charger, RTC,
 550           ADC, backlight driver and current sinks.
 551
 552 config MFD_MAX77686
 553         bool "Maxim Semiconductor MAX77686 PMIC Support"
 554         depends on I2C=y && GENERIC_HARDIRQS
 555         select MFD_CORE
 556         select REGMAP_I2C
 557         select IRQ_DOMAIN
 558         help
 559           Say yes here to support for Maxim Semiconductor MAX77686.
 560           This is a Power Management IC with RTC on chip.
 561           This driver provides common support for accessing the device;
 562           additional drivers must be enabled in order to use the functionality
 563           of the device.
 564
 565 config MFD_MAX77693
 566         bool "Maxim Semiconductor MAX77693 PMIC Support"
 567         depends on I2C=y && GENERIC_HARDIRQS
 568         select MFD_CORE
 569         select REGMAP_I2C
 570         help
 571           Say yes here to support for Maxim Semiconductor MAX77693.
 572           This is a companion Power Management IC with Flash, Haptic, Charger,
 573           and MUIC(Micro USB Interface Controller) controls on chip.
 574           This driver provides common support for accessing the device;
 575           additional drivers must be enabled in order to use the functionality
 576           of the device.
 577
 578 config MFD_MAX8907
 579         tristate "Maxim Semiconductor MAX8907 PMIC Support"
 580         select MFD_CORE
 581         depends on I2C=y && GENERIC_HARDIRQS
 582         select REGMAP_I2C
 583         select REGMAP_IRQ
 584         help
 585           Say yes here to support for Maxim Semiconductor MAX8907. This is
 586           a Power Management IC. This driver provides common support for
 587           accessing the device; additional drivers must be enabled in order
 588           to use the functionality of the device.
 589
 590 config MFD_MAX8925
 591         bool "Maxim Semiconductor MAX8925 PMIC Support"
 592         depends on I2C=y && GENERIC_HARDIRQS
 593         select MFD_CORE
 594         help
 595           Say yes here to support for Maxim Semiconductor MAX8925. This is
 596           a Power Management IC. This driver provides common support for
 597           accessing the device, additional drivers must be enabled in order
 598           to use the functionality of the device.
 599
 600 config MFD_MAX8997
 601         bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
 602         depends on I2C=y && GENERIC_HARDIRQS
 603         select MFD_CORE
 604         select IRQ_DOMAIN
 605         help
 606           Say yes here to support for Maxim Semiconductor MAX8997/8966.
 607           This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
 608           MUIC controls on chip.
 609           This driver provides common support for accessing the device;
 610           additional drivers must be enabled in order to use the functionality
 611           of the device.
 612
 613 config MFD_MAX8998
 614         bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
 615         depends on I2C=y && GENERIC_HARDIRQS
 616         select MFD_CORE
 617         help
 618           Say yes here to support for Maxim Semiconductor MAX8998 and
 619           National Semiconductor LP3974. This is a Power Management IC.
 620           This driver provides common support for accessing the device,
 621           additional drivers must be enabled in order to use the functionality
 622           of the device.
 623
 624 config MFD_SEC_CORE
 625         bool "SAMSUNG Electronics PMIC Series Support"
 626         depends on I2C=y && GENERIC_HARDIRQS
 627         select MFD_CORE
 628         select REGMAP_I2C
 629         select REGMAP_IRQ
 630         help
 631          Support for the Samsung Electronics MFD series.
 632          This driver provides common support for accessing the device,
 633          additional drivers must be enabled in order to use the functionality
 634          of the device
 635
 636 config MFD_ARIZONA
 637         select REGMAP
 638         select REGMAP_IRQ
 639         select MFD_CORE
 640         bool
 641
 642 config MFD_ARIZONA_I2C
 643         tristate "Support Wolfson Microelectronics Arizona platform with I2C"
 644         select MFD_ARIZONA
 645         select MFD_CORE
 646         select REGMAP_I2C
 647         depends on I2C && GENERIC_HARDIRQS
 648         help
 649           Support for the Wolfson Microelectronics Arizona platform audio SoC
 650           core functionality controlled via I2C.
 651
 652 config MFD_ARIZONA_SPI
 653         tristate "Support Wolfson Microelectronics Arizona platform with SPI"
 654         select MFD_ARIZONA
 655         select MFD_CORE
 656         select REGMAP_SPI
 657         depends on SPI_MASTER && GENERIC_HARDIRQS
 658         help
 659           Support for the Wolfson Microelectronics Arizona platform audio SoC
 660           core functionality controlled via I2C.
 661
 662 config MFD_WM5102
 663         bool "Support Wolfson Microelectronics WM5102"
 664         depends on MFD_ARIZONA
 665         help
 666           Support for Wolfson Microelectronics WM5102 low power audio SoC
 667
 668 config MFD_WM5110
 669         bool "Support Wolfson Microelectronics WM5110"
 670         depends on MFD_ARIZONA
 671         help
 672           Support for Wolfson Microelectronics WM5110 low power audio SoC
 673
 674 config MFD_WM8400
 675         bool "Support Wolfson Microelectronics WM8400"
 676         select MFD_CORE
 677         depends on I2C=y && GENERIC_HARDIRQS
 678         select REGMAP_I2C
 679         help
 680           Support for the Wolfson Microelecronics WM8400 PMIC and audio
 681           CODEC.  This driver provides common support for accessing
 682           the device, additional drivers must be enabled in order to use
 683           the functionality of the device.
 684
 685 config MFD_WM831X
 686         bool
 687         depends on GENERIC_HARDIRQS
 688
 689 config MFD_WM831X_I2C
 690         bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C"
 691         select MFD_CORE
 692         select MFD_WM831X
 693         select REGMAP_I2C
 694         select IRQ_DOMAIN
 695         depends on I2C=y && GENERIC_HARDIRQS
 696         help
 697           Support for the Wolfson Microelecronics WM831x and WM832x PMICs
 698           when controlled using I2C.  This driver provides common support
 699           for accessing the device, additional drivers must be enabled in
 700           order to use the functionality of the device.
 701
 702 config MFD_WM831X_SPI
 703         bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI"
 704         select MFD_CORE
 705         select MFD_WM831X
 706         select REGMAP_SPI
 707         select IRQ_DOMAIN
 708         depends on SPI_MASTER && GENERIC_HARDIRQS
 709         help
 710           Support for the Wolfson Microelecronics WM831x and WM832x PMICs
 711           when controlled using SPI.  This driver provides common support
 712           for accessing the device, additional drivers must be enabled in
 713           order to use the functionality of the device.
 714
 715 config MFD_WM8350
 716         bool
 717         depends on GENERIC_HARDIRQS
 718
 719 config MFD_WM8350_CONFIG_MODE_0
 720         bool
 721         depends on MFD_WM8350
 722
 723 config MFD_WM8350_CONFIG_MODE_1
 724         bool
 725         depends on MFD_WM8350
 726
 727 config MFD_WM8350_CONFIG_MODE_2
 728         bool
 729         depends on MFD_WM8350
 730
 731 config MFD_WM8350_CONFIG_MODE_3
 732         bool
 733         depends on MFD_WM8350
 734
 735 config MFD_WM8351_CONFIG_MODE_0
 736         bool
 737         depends on MFD_WM8350
 738
 739 config MFD_WM8351_CONFIG_MODE_1
 740         bool
 741         depends on MFD_WM8350
 742
 743 config MFD_WM8351_CONFIG_MODE_2
 744         bool
 745         depends on MFD_WM8350
 746
 747 config MFD_WM8351_CONFIG_MODE_3
 748         bool
 749         depends on MFD_WM8350
 750
 751 config MFD_WM8352_CONFIG_MODE_0
 752         bool
 753         depends on MFD_WM8350
 754
 755 config MFD_WM8352_CONFIG_MODE_1
 756         bool
 757         depends on MFD_WM8350
 758
 759 config MFD_WM8352_CONFIG_MODE_2
 760         bool
 761         depends on MFD_WM8350
 762
 763 config MFD_WM8352_CONFIG_MODE_3
 764         bool
 765         depends on MFD_WM8350
 766
 767 config MFD_WM8350_I2C
 768         bool "Support Wolfson Microelectronics WM8350 with I2C"
 769         select MFD_WM8350
 770         depends on I2C=y && GENERIC_HARDIRQS
 771         help
 772           The WM8350 is an integrated audio and power management
 773           subsystem with watchdog and RTC functionality for embedded
 774           systems.  This option enables core support for the WM8350 with
 775           I2C as the control interface.  Additional options must be
 776           selected to enable support for the functionality of the chip.
 777
 778 config MFD_WM8994
 779         bool "Support Wolfson Microelectronics WM8994"
 780         select MFD_CORE
 781         select REGMAP_I2C
 782         select REGMAP_IRQ
 783         depends on I2C=y && GENERIC_HARDIRQS
 784         help
 785           The WM8994 is a highly integrated hi-fi CODEC designed for
 786           smartphone applicatiosn.  As well as audio functionality it
 787           has on board GPIO and regulator functionality which is
 788           supported via the relevant subsystems.  This driver provides
 789           core support for the WM8994, in order to use the actual
 790           functionaltiy of the device other drivers must be enabled.
 791
 792 config MFD_PCF50633
 793         tristate "Support for NXP PCF50633"
 794         depends on I2C
 795         select REGMAP_I2C
 796         help
 797           Say yes here if you have NXP PCF50633 chip on your board.
 798           This core driver provides register access and IRQ handling
 799           facilities, and registers devices for the various functions
 800           so that function-specific drivers can bind to them.
 801
 802 config PCF50633_ADC
 803         tristate "Support for NXP PCF50633 ADC"
 804         depends on MFD_PCF50633
 805         help
 806          Say yes here if you want to include support for ADC in the
 807          NXP PCF50633 chip.
 808
 809 config PCF50633_GPIO
 810         tristate "Support for NXP PCF50633 GPIO"
 811         depends on MFD_PCF50633
 812         help
 813          Say yes here if you want to include support GPIO for pins on
 814          the PCF50633 chip.
 815
 816 config MFD_MC13783
 817         tristate
 818
 819 config MFD_MC13XXX
 820         tristate
 821         depends on (SPI_MASTER || I2C) && GENERIC_HARDIRQS
 822         select MFD_CORE
 823         select MFD_MC13783
 824         help
 825           Enable support for the Freescale MC13783 and MC13892 PMICs.
 826           This driver provides common support for accessing the device,
 827           additional drivers must be enabled in order to use the
 828           functionality of the device.
 829
 830 config MFD_MC13XXX_SPI
 831         tristate "Freescale MC13783 and MC13892 SPI interface"
 832         depends on SPI_MASTER && GENERIC_HARDIRQS
 833         select REGMAP_SPI
 834         select MFD_MC13XXX
 835         help
 836           Select this if your MC13xxx is connected via an SPI bus.
 837
 838 config MFD_MC13XXX_I2C
 839         tristate "Freescale MC13892 I2C interface"
 840         depends on I2C && GENERIC_HARDIRQS
 841         select REGMAP_I2C
 842         select MFD_MC13XXX
 843         help
 844           Select this if your MC13xxx is connected via an I2C bus.
 845
 846 config ABX500_CORE
 847         bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
 848         default y if ARCH_U300 || ARCH_U8500
 849         help
 850           Say yes here if you have the ABX500 Mixed Signal IC family
 851           chips. This core driver expose register access functions.
 852           Functionality specific drivers using these functions can
 853           remain unchanged when IC changes. Binding of the functions to
 854           actual register access is done by the IC core driver.
 855
 856 config AB3100_CORE
 857         bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
 858         depends on I2C=y && ABX500_CORE && GENERIC_HARDIRQS
 859         select MFD_CORE
 860         default y if ARCH_U300
 861         help
 862           Select this to enable the AB3100 Mixed Signal IC core
 863           functionality. This connects to a AB3100 on the I2C bus
 864           and expose a number of symbols needed for dependent devices
 865           to read and write registers and subscribe to events from
 866           this multi-functional IC. This is needed to use other features
 867           of the AB3100 such as battery-backed RTC, charging control,
 868           LEDs, vibrator, system power and temperature, power management
 869           and ALSA sound.
 870
 871 config AB3100_OTP
 872         tristate "ST-Ericsson AB3100 OTP functions"
 873         depends on AB3100_CORE
 874         default y if AB3100_CORE
 875         help
 876           Select this to enable the AB3100 Mixed Signal IC OTP (one-time
 877           programmable memory) support. This exposes a sysfs file to read
 878           out OTP values.
 879
 880 config EZX_PCAP
 881         bool "PCAP Support"
 882         depends on GENERIC_HARDIRQS && SPI_MASTER
 883         help
 884           This enables the PCAP ASIC present on EZX Phones. This is
 885           needed for MMC, TouchScreen, Sound, USB, etc..
 886
 887 config AB8500_CORE
 888         bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
 889         depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
 890         select POWER_SUPPLY
 891         select MFD_CORE
 892         select IRQ_DOMAIN
 893         help
 894           Select this option to enable access to AB8500 power management
 895           chip. This connects to U8500 either on the SSP/SPI bus (deprecated
 896           since hardware version v1.0) or the I2C bus via PRCMU. It also adds
 897           the irq_chip parts for handling the Mixed Signal chip events.
 898           This chip embeds various other multimedia funtionalities as well.
 899
 900 config AB8500_DEBUG
 901        bool "Enable debug info via debugfs"
 902        depends on AB8500_CORE && DEBUG_FS
 903        default y if DEBUG_FS
 904        help
 905          Select this option if you want debug information using the debug
 906          filesystem, debugfs.
 907
 908 config AB8500_GPADC
 909         bool "AB8500 GPADC driver"
 910         depends on AB8500_CORE && REGULATOR_AB8500
 911         default y
 912         help
 913           AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
 914
 915 config MFD_DB8500_PRCMU
 916         bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
 917         depends on UX500_SOC_DB8500
 918         select MFD_CORE
 919         help
 920           Select this option to enable support for the DB8500 Power Reset
 921           and Control Management Unit. This is basically an autonomous
 922           system controller running an XP70 microprocessor, which is accessed
 923           through a register map.
 924
 925 config MFD_CS5535
 926         tristate "Support for CS5535 and CS5536 southbridge core functions"
 927         select MFD_CORE
 928         depends on PCI && X86
 929         ---help---
 930           This is the core driver for CS5535/CS5536 MFD functions.  This is
 931           necessary for using the board's GPIO and MFGPT functionality.
 932
 933 config MFD_TIMBERDALE
 934         tristate "Support for the Timberdale FPGA"
 935         select MFD_CORE
 936         depends on PCI && GPIOLIB
 937         ---help---
 938         This is the core driver for the timberdale FPGA. This device is a
 939         multifunction device which exposes numerous platform devices.
 940
 941         The timberdale FPGA can be found on the Intel Atom development board
 942         for in-vehicle infontainment, called Russellville.
 943
 944 config LPC_SCH
 945         tristate "Intel SCH LPC"
 946         depends on PCI && GENERIC_HARDIRQS
 947         select MFD_CORE
 948         help
 949           LPC bridge function of the Intel SCH provides support for
 950           System Management Bus and General Purpose I/O.
 951
 952 config LPC_ICH
 953         tristate "Intel ICH LPC"
 954         depends on PCI && GENERIC_HARDIRQS
 955         select MFD_CORE
 956         help
 957           The LPC bridge function of the Intel ICH provides support for
 958           many functional units. This driver provides needed support for
 959           other drivers to control these functions, currently GPIO and
 960           watchdog.
 961
 962 config MFD_RDC321X
 963         tristate "Support for RDC-R321x southbridge"
 964         select MFD_CORE
 965         depends on PCI && GENERIC_HARDIRQS
 966         help
 967           Say yes here if you want to have support for the RDC R-321x SoC
 968           southbridge which provides access to GPIOs and Watchdog using the
 969           southbridge PCI device configuration space.
 970
 971 config MFD_JANZ_CMODIO
 972         tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
 973         select MFD_CORE
 974         depends on PCI && GENERIC_HARDIRQS
 975         help
 976           This is the core driver for the Janz CMOD-IO PCI MODULbus
 977           carrier board. This device is a PCI to MODULbus bridge which may
 978           host many different types of MODULbus daughterboards, including
 979           CAN and GPIO controllers.
 980
 981 config MFD_JZ4740_ADC
 982         bool "Support for the JZ4740 SoC ADC core"
 983         select MFD_CORE
 984         select GENERIC_IRQ_CHIP
 985         depends on MACH_JZ4740
 986         help
 987           Say yes here if you want support for the ADC unit in the JZ4740 SoC.
 988           This driver is necessary for jz4740-battery and jz4740-hwmon driver.
 989
 990 config MFD_VX855
 991         tristate "Support for VIA VX855/VX875 integrated south bridge"
 992         depends on PCI && GENERIC_HARDIRQS
 993         select MFD_CORE
 994         help
 995           Say yes here to enable support for various functions of the
 996           VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
 997           and/or vx855_gpio drivers for this to do anything useful.
 998
 999 config MFD_WL1273_CORE
1000         tristate "Support for TI WL1273 FM radio."
1001         depends on I2C && GENERIC_HARDIRQS
1002         select MFD_CORE
1003         default n
1004         help
1005           This is the core driver for the TI WL1273 FM radio. This MFD
1006           driver connects the radio-wl1273 V4L2 module and the wl1273
1007           audio codec.
1008
1009 config MFD_OMAP_USB_HOST
1010         bool "Support OMAP USBHS core and TLL driver"
1011         depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1012         default y
1013         help
1014           This is the core driver for the OAMP EHCI and OHCI drivers.
1015           This MFD driver does the required setup functionalities for
1016           OMAP USB Host drivers.
1017
1018 config MFD_PM8XXX
1019         tristate
1020
1021 config MFD_PM8921_CORE
1022         tristate "Qualcomm PM8921 PMIC chip"
1023         depends on MSM_SSBI
1024         select MFD_CORE
1025         select MFD_PM8XXX
1026         help
1027           If you say yes to this option, support will be included for the
1028           built-in PM8921 PMIC chip.
1029
1030           This is required if your board has a PM8921 and uses its features,
1031           such as: MPPs, GPIOs, regulators, interrupts, and PWM.
1032
1033           Say M here if you want to include support for PM8921 chip as a module.
1034           This will build a module called "pm8921-core".
1035
1036 config MFD_PM8XXX_IRQ
1037         bool "Support for Qualcomm PM8xxx IRQ features"
1038         depends on MFD_PM8XXX
1039         default y if MFD_PM8XXX
1040         help
1041           This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
1042
1043           This is required to use certain other PM 8xxx features, such as GPIO
1044           and MPP.
1045
1046 config TPS65911_COMPARATOR
1047         tristate
1048
1049 config MFD_TPS65090
1050         bool "TPS65090 Power Management chips"
1051         depends on I2C=y && GENERIC_HARDIRQS
1052         select MFD_CORE
1053         select REGMAP_I2C
1054         select REGMAP_IRQ
1055         help
1056           If you say yes here you get support for the TPS65090 series of
1057           Power Management chips.
1058           This driver provides common support for accessing the device,
1059           additional drivers must be enabled in order to use the
1060           functionality of the device.
1061
1062 config MFD_AAT2870_CORE
1063         bool "Support for the AnalogicTech AAT2870"
1064         select MFD_CORE
1065         depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
1066         help
1067           If you say yes here you get support for the AAT2870.
1068           This driver provides common support for accessing the device,
1069           additional drivers must be enabled in order to use the
1070           functionality of the device.
1071
1072 config MFD_INTEL_MSIC
1073         bool "Support for Intel MSIC"
1074         depends on INTEL_SCU_IPC
1075         select MFD_CORE
1076         help
1077           Select this option to enable access to Intel MSIC (Avatele
1078           Passage) chip. This chip embeds audio, battery, GPIO, etc.
1079           devices used in Intel Medfield platforms.
1080
1081 config MFD_RC5T583
1082         bool "Ricoh RC5T583 Power Management system device"
1083         depends on I2C=y && GENERIC_HARDIRQS
1084         select MFD_CORE
1085         select REGMAP_I2C
1086         help
1087           Select this option to get support for the RICOH583 Power
1088           Management system device.
1089           This driver provides common support for accessing the device
1090           through i2c interface. The device supports multiple sub-devices
1091           like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
1092           Additional drivers must be enabled in order to use the
1093           different functionality of the device.
1094
1095 config MFD_STA2X11
1096         bool "STA2X11 multi function device support"
1097         depends on STA2X11 && GENERIC_HARDIRQS
1098         select MFD_CORE
1099         select REGMAP_MMIO
1100
1101 config MFD_SYSCON
1102         bool "System Controller Register R/W Based on Regmap"
1103         select REGMAP_MMIO
1104         help
1105           Select this option to enable accessing system control registers
1106           via regmap.
1107
1108 config MFD_PALMAS
1109         bool "Support for the TI Palmas series chips"
1110         select MFD_CORE
1111         select REGMAP_I2C
1112         select REGMAP_IRQ
1113         depends on I2C=y && GENERIC_HARDIRQS
1114         help
1115           If you say yes here you get support for the Palmas
1116           series of PMIC chips from Texas Instruments.
1117
1118 config MFD_VIPERBOARD
1119         tristate "Support for Nano River Technologies Viperboard"
1120         select MFD_CORE
1121         depends on USB && GENERIC_HARDIRQS
1122         default n
1123         help
1124           Say yes here if you want support for Nano River Technologies
1125           Viperboard.
1126           There are mfd cell drivers available for i2c master, adc and
1127           both gpios found on the board. The spi part does not yet
1128           have a driver.
1129           You need to select the mfd cell drivers separately.
1130           The drivers do not support all features the board exposes.
1131
1132 config MFD_RETU
1133         tristate "Support for Retu multi-function device"
1134         select MFD_CORE
1135         depends on I2C && GENERIC_HARDIRQS
1136         select REGMAP_IRQ
1137         help
1138           Retu is a multi-function device found on Nokia Internet Tablets
1139           (770, N800 and N810).
1140
1141 config MFD_AS3711
1142         bool "Support for AS3711"
1143         select MFD_CORE
1144         select REGMAP_I2C
1145         select REGMAP_IRQ
1146         depends on I2C=y && GENERIC_HARDIRQS
1147         help
1148           Support for the AS3711 PMIC from AMS
1149
1150 endmenu
1151 endif
1152
1153 menu "Multimedia Capabilities Port drivers"
1154         depends on ARCH_SA1100
1155
1156 config MCP
1157         tristate
1158
1159 # Interface drivers
1160 config MCP_SA11X0
1161         tristate "Support SA11x0 MCP interface"
1162         depends on ARCH_SA1100
1163         select MCP
1164
1165 # Chip drivers
1166 config MCP_UCB1200
1167         bool "Support for UCB1200 / UCB1300"
1168         depends on MCP_SA11X0
1169         select MCP
1170
1171 config MCP_UCB1200_TS
1172         tristate "Touchscreen interface support"
1173         depends on MCP_UCB1200 && INPUT
1174
1175 endmenu
1176
1177 config VEXPRESS_CONFIG
1178         bool
1179         help
1180           Platform configuration infrastructure for the ARM Ltd.
1181           Versatile Express.