PageRenderTime 47ms CodeModel.GetById 32ms app.highlight 6ms RepoModel.GetById 2ms app.codeStats 0ms

/drivers/mfd/Kconfig

http://github.com/mirrors/linux
#! | 1621 lines | 1433 code | 188 blank | 0 comment | 0 complexity | 381fd414db97a3cae21e25e031908b57 MD5 | raw file
   1#
   2# Multifunction miscellaneous devices
   3#
   4
   5if HAS_IOMEM
   6menu "Multifunction device drivers"
   7
   8config MFD_CORE
   9	tristate
  10	select IRQ_DOMAIN
  11	default n
  12
  13config MFD_CS5535
  14	tristate "AMD CS5535 and CS5536 southbridge core functions"
  15	select MFD_CORE
  16	depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
  17	---help---
  18	  This is the core driver for CS5535/CS5536 MFD functions.  This is
  19          necessary for using the board's GPIO and MFGPT functionality.
  20
  21config MFD_ALTERA_A10SR
  22	bool "Altera Arria10 DevKit System Resource chip"
  23	depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
  24	select REGMAP_SPI
  25	select MFD_CORE
  26	help
  27	  Support for the Altera Arria10 DevKit MAX5 System Resource chip
  28	  using the SPI interface. This driver provides common support for
  29	  accessing the external gpio extender (LEDs & buttons) and
  30	  power supply alarms (hwmon).
  31
  32config MFD_ACT8945A
  33	tristate "Active-semi ACT8945A"
  34	select MFD_CORE
  35	select REGMAP_I2C
  36	depends on I2C && OF
  37	help
  38	  Support for the ACT8945A PMIC from Active-semi. This device
  39	  features three step-down DC/DC converters and four low-dropout
  40	  linear regulators, along with a complete ActivePath battery
  41	  charger.
  42
  43config MFD_AS3711
  44	bool "AMS AS3711"
  45	select MFD_CORE
  46	select REGMAP_I2C
  47	select REGMAP_IRQ
  48	depends on I2C=y
  49	help
  50	  Support for the AS3711 PMIC from AMS
  51
  52config MFD_AS3722
  53	bool "ams AS3722 Power Management IC"
  54	select MFD_CORE
  55	select REGMAP_I2C
  56	select REGMAP_IRQ
  57	depends on I2C=y && OF
  58	help
  59	  The ams AS3722 is a compact system PMU suitable for mobile phones,
  60	  tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
  61	  controllers, 11 LDOs, RTC, automatic battery, temperature and
  62	  over current monitoring, GPIOs, ADC and a watchdog.
  63
  64config PMIC_ADP5520
  65	bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
  66	depends on I2C=y
  67	help
  68	  Say yes here to add support for Analog Devices AD5520 and ADP5501,
  69	  Multifunction Power Management IC. This includes
  70	  the I2C driver and the core APIs _only_, you have to select
  71	  individual components like LCD backlight, LEDs, GPIOs and Kepad
  72	  under the corresponding menus.
  73
  74config MFD_AAT2870_CORE
  75	bool "AnalogicTech AAT2870"
  76	select MFD_CORE
  77	depends on I2C=y
  78	depends on GPIOLIB || COMPILE_TEST
  79	help
  80	  If you say yes here you get support for the AAT2870.
  81	  This driver provides common support for accessing the device,
  82	  additional drivers must be enabled in order to use the
  83	  functionality of the device.
  84
  85config MFD_ATMEL_FLEXCOM
  86	tristate "Atmel Flexcom (Flexible Serial Communication Unit)"
  87	select MFD_CORE
  88	depends on OF
  89	help
  90	  Select this to get support for Atmel Flexcom. This is a wrapper
  91	  which embeds a SPI controller, a I2C controller and a USART. Only
  92	  one function can be used at a time. The choice is done at boot time
  93	  by the probe function of this MFD driver according to a device tree
  94	  property.
  95
  96config MFD_ATMEL_HLCDC
  97	tristate "Atmel HLCDC (High-end LCD Controller)"
  98	select MFD_CORE
  99	select REGMAP_MMIO
 100	depends on OF
 101	help
 102	  If you say yes here you get support for the HLCDC block.
 103	  This driver provides common support for accessing the device,
 104	  additional drivers must be enabled in order to use the
 105	  functionality of the device.
 106
 107config MFD_BCM590XX
 108	tristate "Broadcom BCM590xx PMUs"
 109	select MFD_CORE
 110	select REGMAP_I2C
 111	depends on I2C
 112	help
 113	  Support for the BCM590xx PMUs from Broadcom
 114
 115config MFD_AXP20X
 116	tristate
 117	select MFD_CORE
 118	select REGMAP_IRQ
 119
 120config MFD_AXP20X_I2C
 121	tristate "X-Powers AXP series PMICs with I2C"
 122	select MFD_AXP20X
 123	select REGMAP_I2C
 124	depends on I2C
 125	help
 126	  If you say Y here you get support for the X-Powers AXP series power
 127	  management ICs (PMICs) controlled with I2C.
 128	  This driver include only the core APIs. You have to select individual
 129	  components like regulators or the PEK (Power Enable Key) under the
 130	  corresponding menus.
 131
 132config MFD_AXP20X_RSB
 133	tristate "X-Powers AXP series PMICs with RSB"
 134	select MFD_AXP20X
 135	depends on SUNXI_RSB
 136	help
 137	  If you say Y here you get support for the X-Powers AXP series power
 138	  management ICs (PMICs) controlled with RSB.
 139	  This driver include only the core APIs. You have to select individual
 140	  components like regulators or the PEK (Power Enable Key) under the
 141	  corresponding menus.
 142
 143config MFD_CROS_EC
 144	tristate "ChromeOS Embedded Controller"
 145	select MFD_CORE
 146	select CHROME_PLATFORMS
 147	select CROS_EC_PROTO
 148	depends on X86 || ARM || ARM64 || COMPILE_TEST
 149	help
 150	  If you say Y here you get support for the ChromeOS Embedded
 151	  Controller (EC) providing keyboard, battery and power services.
 152	  You also need to enable the driver for the bus you are using. The
 153	  protocol for talking to the EC is defined by the bus driver.
 154
 155config MFD_CROS_EC_I2C
 156	tristate "ChromeOS Embedded Controller (I2C)"
 157	depends on MFD_CROS_EC && I2C
 158
 159	help
 160	  If you say Y here, you get support for talking to the ChromeOS
 161	  EC through an I2C bus. This uses a simple byte-level protocol with
 162	  a checksum. Failing accesses will be retried three times to
 163	  improve reliability.
 164
 165config MFD_CROS_EC_SPI
 166	tristate "ChromeOS Embedded Controller (SPI)"
 167	depends on MFD_CROS_EC && SPI
 168
 169	---help---
 170	  If you say Y here, you get support for talking to the ChromeOS EC
 171	  through a SPI bus, using a byte-level protocol. Since the EC's
 172	  response time cannot be guaranteed, we support ignoring
 173	  'pre-amble' bytes before the response actually starts.
 174
 175config MFD_ASIC3
 176	bool "Compaq ASIC3"
 177	depends on GPIOLIB && ARM
 178	select MFD_CORE
 179	 ---help---
 180	  This driver supports the ASIC3 multifunction chip found on many
 181	  PDAs (mainly iPAQ and HTC based ones)
 182
 183config PMIC_DA903X
 184	bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
 185	depends on I2C=y
 186	help
 187	  Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
 188	  ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
 189	  usually found on PXA processors-based platforms. This includes
 190	  the I2C driver and the core APIs _only_, you have to select
 191	  individual components like LCD backlight, voltage regulators,
 192	  LEDs and battery-charger under the corresponding menus.
 193
 194config PMIC_DA9052
 195	bool
 196	select MFD_CORE
 197
 198config MFD_DA9052_SPI
 199	bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
 200	select REGMAP_SPI
 201	select REGMAP_IRQ
 202	select PMIC_DA9052
 203	depends on SPI_MASTER=y
 204	help
 205	  Support for the Dialog Semiconductor DA9052 PMIC
 206	  when controlled using SPI. This driver provides common support
 207	  for accessing the device, additional drivers must be enabled in
 208	  order to use the functionality of the device.
 209
 210config MFD_DA9052_I2C
 211	bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
 212	select REGMAP_I2C
 213	select REGMAP_IRQ
 214	select PMIC_DA9052
 215	depends on I2C=y
 216	help
 217	  Support for the Dialog Semiconductor DA9052 PMIC
 218	  when controlled using I2C. This driver provides common support
 219	  for accessing the device, additional drivers must be enabled in
 220	  order to use the functionality of the device.
 221
 222config MFD_DA9055
 223	bool "Dialog Semiconductor DA9055 PMIC Support"
 224	select REGMAP_I2C
 225	select REGMAP_IRQ
 226	select MFD_CORE
 227	depends on I2C=y
 228	help
 229	  Say yes here for support of Dialog Semiconductor DA9055. This is
 230	  a Power Management IC. This driver provides common support for
 231	  accessing the device as well as the I2C interface to the chip itself.
 232	  Additional drivers must be enabled in order to use the functionality
 233	  of the device.
 234
 235	  This driver can be built as a module. If built as a module it will be
 236	  called "da9055"
 237
 238config MFD_DA9062
 239	tristate "Dialog Semiconductor DA9062 PMIC Support"
 240	select MFD_CORE
 241	select REGMAP_I2C
 242	select REGMAP_IRQ
 243	depends on I2C
 244	help
 245	  Say yes here for support for the Dialog Semiconductor DA9062 PMIC.
 246	  This includes the I2C driver and core APIs.
 247	  Additional drivers must be enabled in order to use the functionality
 248	  of the device.
 249
 250config MFD_DA9063
 251	tristate "Dialog Semiconductor DA9063 PMIC Support"
 252	select MFD_CORE
 253	select REGMAP_I2C
 254	select REGMAP_IRQ
 255	depends on I2C
 256	help
 257	  Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
 258	  This includes the I2C driver and core APIs.
 259	  Additional drivers must be enabled in order to use the functionality
 260	  of the device.
 261
 262config MFD_DA9150
 263	tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip"
 264	depends on I2C
 265	select MFD_CORE
 266	select REGMAP_I2C
 267	select REGMAP_IRQ
 268	help
 269	  This adds support for the DA9150 integrated charger and fuel-gauge
 270	  chip. This driver provides common support for accessing the device.
 271	  Additional drivers must be enabled in order to use the specific
 272	  features of the device.
 273
 274config MFD_DLN2
 275	tristate "Diolan DLN2 support"
 276	select MFD_CORE
 277	depends on USB
 278	help
 279	  This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter
 280	  DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2,
 281	  etc. must be enabled in order to use the functionality of
 282	  the device.
 283
 284config MFD_MC13XXX
 285	tristate
 286	depends on (SPI_MASTER || I2C)
 287	select MFD_CORE
 288	select REGMAP_IRQ
 289	help
 290	  Enable support for the Freescale MC13783 and MC13892 PMICs.
 291	  This driver provides common support for accessing the device,
 292	  additional drivers must be enabled in order to use the
 293	  functionality of the device.
 294
 295config MFD_MC13XXX_SPI
 296	tristate "Freescale MC13783 and MC13892 SPI interface"
 297	depends on SPI_MASTER
 298	select REGMAP_SPI
 299	select MFD_MC13XXX
 300	help
 301	  Select this if your MC13xxx is connected via an SPI bus.
 302
 303config MFD_MC13XXX_I2C
 304	tristate "Freescale MC13892 I2C interface"
 305	depends on I2C
 306	select REGMAP_I2C
 307	select MFD_MC13XXX
 308	help
 309	  Select this if your MC13xxx is connected via an I2C bus.
 310
 311config MFD_MX25_TSADC
 312	tristate "Freescale i.MX25 integrated Touchscreen and ADC unit"
 313	select REGMAP_MMIO
 314	depends on (SOC_IMX25 && OF) || COMPILE_TEST
 315	help
 316	  Enable support for the integrated Touchscreen and ADC unit of the
 317	  i.MX25 processors. They consist of a conversion queue for general
 318	  purpose ADC and a queue for Touchscreens.
 319
 320config MFD_HI6421_PMIC
 321	tristate "HiSilicon Hi6421 PMU/Codec IC"
 322	depends on OF
 323	select MFD_CORE
 324	select REGMAP_MMIO
 325	help
 326	  Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi-
 327	  functions, such as regulators, RTC, codec, Coulomb counter, etc.
 328	  This driver includes core APIs _only_. You have to select
 329	  individul components like voltage regulators under corresponding
 330	  menus in order to enable them.
 331	  We communicate with the Hi6421 via memory-mapped I/O.
 332
 333config MFD_HI655X_PMIC
 334	tristate "HiSilicon Hi655X series PMU/Codec IC"
 335	depends on ARCH_HISI || COMPILE_TEST
 336	depends on OF
 337	select MFD_CORE
 338	select REGMAP_MMIO
 339	select REGMAP_IRQ
 340	help
 341	  Select this option to enable Hisilicon hi655x series pmic driver.
 342
 343config HTC_EGPIO
 344	bool "HTC EGPIO support"
 345	depends on GPIOLIB && ARM
 346	help
 347	    This driver supports the CPLD egpio chip present on
 348	    several HTC phones.  It provides basic support for input
 349	    pins, output pins, and irqs.
 350
 351config HTC_PASIC3
 352	tristate "HTC PASIC3 LED/DS1WM chip support"
 353	select MFD_CORE
 354	help
 355	  This core driver provides register access for the LED/DS1WM
 356	  chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
 357	  HTC Magician devices, respectively. Actual functionality is
 358	  handled by the leds-pasic3 and ds1wm drivers.
 359
 360config HTC_I2CPLD
 361	bool "HTC I2C PLD chip support"
 362	depends on I2C=y && GPIOLIB
 363	help
 364	  If you say yes here you get support for the supposed CPLD
 365	  found on omap850 HTC devices like the HTC Wizard and HTC Herald.
 366	  This device provides input and output GPIOs through an I2C
 367	  interface to one or more sub-chips.
 368
 369config MFD_INTEL_QUARK_I2C_GPIO
 370	tristate "Intel Quark MFD I2C GPIO"
 371	depends on PCI
 372	depends on X86
 373	depends on COMMON_CLK
 374	select MFD_CORE
 375	help
 376	  This MFD provides support for I2C and GPIO that exist only
 377	  in a single PCI device. It splits the 2 IO devices to
 378	  their respective IO driver.
 379	  The GPIO exports a total amount of 8 interrupt-capable GPIOs.
 380
 381config LPC_ICH
 382	tristate "Intel ICH LPC"
 383	depends on PCI
 384	select MFD_CORE
 385	help
 386	  The LPC bridge function of the Intel ICH provides support for
 387	  many functional units. This driver provides needed support for
 388	  other drivers to control these functions, currently GPIO and
 389	  watchdog.
 390
 391config LPC_SCH
 392	tristate "Intel SCH LPC"
 393	depends on PCI
 394	select MFD_CORE
 395	help
 396	  LPC bridge function of the Intel SCH provides support for
 397	  System Management Bus and General Purpose I/O.
 398
 399config INTEL_SOC_PMIC
 400	bool "Support for Intel Atom SoC PMIC"
 401	depends on GPIOLIB
 402	depends on I2C=y
 403	select MFD_CORE
 404	select REGMAP_I2C
 405	select REGMAP_IRQ
 406	help
 407	  Select this option to enable support for the PMIC device
 408	  on some Intel SoC systems. The PMIC provides ADC, GPIO,
 409	  thermal, charger and related power management functions
 410	  on these systems.
 411
 412config MFD_INTEL_LPSS
 413	tristate
 414	select COMMON_CLK
 415	select MFD_CORE
 416
 417config MFD_INTEL_LPSS_ACPI
 418	tristate "Intel Low Power Subsystem support in ACPI mode"
 419	select MFD_INTEL_LPSS
 420	depends on X86 && ACPI
 421	help
 422	  This driver supports Intel Low Power Subsystem (LPSS) devices such as
 423	  I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
 424	  PCH) in ACPI mode.
 425
 426config MFD_INTEL_LPSS_PCI
 427	tristate "Intel Low Power Subsystem support in PCI mode"
 428	select MFD_INTEL_LPSS
 429	depends on X86 && PCI
 430	help
 431	  This driver supports Intel Low Power Subsystem (LPSS) devices such as
 432	  I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake
 433	  PCH) in PCI mode.
 434
 435config MFD_INTEL_MSIC
 436	bool "Intel MSIC"
 437	depends on INTEL_SCU_IPC
 438	select MFD_CORE
 439	help
 440	  Select this option to enable access to Intel MSIC (Avatele
 441	  Passage) chip. This chip embeds audio, battery, GPIO, etc.
 442	  devices used in Intel Medfield platforms.
 443
 444config MFD_IPAQ_MICRO
 445	bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
 446	depends on SA1100_H3100 || SA1100_H3600
 447	select MFD_CORE
 448	help
 449	  Select this to get support for the Microcontroller found in
 450	  the Compaq iPAQ handheld computers. This is an Atmel
 451	  AT90LS8535 microcontroller flashed with a special iPAQ
 452	  firmware using the custom protocol implemented in this driver.
 453
 454config MFD_JANZ_CMODIO
 455	tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
 456	select MFD_CORE
 457	depends on PCI
 458	help
 459	  This is the core driver for the Janz CMOD-IO PCI MODULbus
 460	  carrier board. This device is a PCI to MODULbus bridge which may
 461	  host many different types of MODULbus daughterboards, including
 462	  CAN and GPIO controllers.
 463
 464config MFD_JZ4740_ADC
 465	bool "Janz JZ4740 ADC core"
 466	select MFD_CORE
 467	select GENERIC_IRQ_CHIP
 468	depends on MACH_JZ4740
 469	help
 470	  Say yes here if you want support for the ADC unit in the JZ4740 SoC.
 471	  This driver is necessary for jz4740-battery and jz4740-hwmon driver.
 472
 473config MFD_KEMPLD
 474	tristate "Kontron module PLD device"
 475	select MFD_CORE
 476	help
 477	  This is the core driver for the PLD (Programmable Logic Device) found
 478	  on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
 479	  device may provide functions like watchdog, GPIO, UART and I2C bus.
 480
 481	  The following modules are supported:
 482		* COMe-bBL6
 483		* COMe-bHL6
 484		* COMe-bIP#
 485		* COMe-bPC2 (ETXexpress-PC)
 486		* COMe-bSC# (ETXexpress-SC T#)
 487		* COMe-cBL6
 488		* COMe-cBT6
 489		* COMe-cBW6
 490		* COMe-cCT6
 491		* COMe-cDC2 (microETXexpress-DC)
 492		* COMe-cHL6
 493		* COMe-cPC2 (microETXexpress-PC)
 494		* COMe-cSL6
 495		* COMe-mAL10
 496		* COMe-mBT10
 497		* COMe-mCT10
 498		* COMe-mTT10 (nanoETXexpress-TT)
 499		* ETX-OH
 500
 501	  This driver can also be built as a module. If so, the module
 502	  will be called kempld-core.
 503
 504config MFD_88PM800
 505	tristate "Marvell 88PM800"
 506	depends on I2C
 507	select REGMAP_I2C
 508	select REGMAP_IRQ
 509	select MFD_CORE
 510	help
 511	  This supports for Marvell 88PM800 Power Management IC.
 512	  This includes the I2C driver and the core APIs _only_, you have to
 513	  select individual components like voltage regulators, RTC and
 514	  battery-charger under the corresponding menus.
 515
 516config MFD_88PM805
 517	tristate "Marvell 88PM805"
 518	depends on I2C
 519	select REGMAP_I2C
 520	select REGMAP_IRQ
 521	select MFD_CORE
 522	help
 523	  This supports for Marvell 88PM805 Power Management IC. This includes
 524	  the I2C driver and the core APIs _only_, you have to select individual
 525	  components like codec device, headset/Mic device under the
 526	  corresponding menus.
 527
 528config MFD_88PM860X
 529	bool "Marvell 88PM8606/88PM8607"
 530	depends on I2C=y
 531	select REGMAP_I2C
 532	select MFD_CORE
 533	help
 534	  This supports for Marvell 88PM8606/88PM8607 Power Management IC.
 535	  This includes the I2C driver and the core APIs _only_, you have to
 536	  select individual components like voltage regulators, RTC and
 537	  battery-charger under the corresponding menus.
 538
 539config MFD_MAX14577
 540	tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
 541	depends on I2C
 542	select MFD_CORE
 543	select REGMAP_I2C
 544	select REGMAP_IRQ
 545	select IRQ_DOMAIN
 546	help
 547	  Say yes here to add support for Maxim Semiconductor MAX14577 and
 548	  MAX77836 Micro-USB ICs with battery charger.
 549	  This driver provides common support for accessing the device;
 550	  additional drivers must be enabled in order to use the functionality
 551	  of the device.
 552
 553config MFD_MAX77620
 554	bool "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support"
 555	depends on I2C=y
 556	depends on OF
 557	select MFD_CORE
 558	select REGMAP_I2C
 559	select REGMAP_IRQ
 560	select IRQ_DOMAIN
 561	help
 562	  Say yes here to add support for Maxim Semiconductor MAX77620 and
 563	  MAX20024 which are Power Management IC with General purpose pins,
 564	  RTC, regulators, clock generator, watchdog etc. This driver
 565	  provides common support for accessing the device; additional drivers
 566	  must be enabled in order to use the functionality of the device.
 567
 568config MFD_MAX77686
 569	tristate "Maxim Semiconductor MAX77686/802 PMIC Support"
 570	depends on I2C
 571	depends on OF
 572	select MFD_CORE
 573	select REGMAP_I2C
 574	select REGMAP_IRQ
 575	select IRQ_DOMAIN
 576	help
 577	  Say yes here to add support for Maxim Semiconductor MAX77686 and
 578	  MAX77802 which are Power Management IC with an RTC on chip.
 579	  This driver provides common support for accessing the device;
 580	  additional drivers must be enabled in order to use the functionality
 581	  of the device.
 582
 583config MFD_MAX77693
 584	tristate "Maxim Semiconductor MAX77693 PMIC Support"
 585	depends on I2C
 586	select MFD_CORE
 587	select REGMAP_I2C
 588	select REGMAP_IRQ
 589	help
 590	  Say yes here to add support for Maxim Semiconductor MAX77693.
 591	  This is a companion Power Management IC with Flash, Haptic, Charger,
 592	  and MUIC(Micro USB Interface Controller) controls on chip.
 593	  This driver provides common support for accessing the device;
 594	  additional drivers must be enabled in order to use the functionality
 595	  of the device.
 596
 597config MFD_MAX77843
 598	bool "Maxim Semiconductor MAX77843 PMIC Support"
 599	depends on I2C=y
 600	select MFD_CORE
 601	select REGMAP_I2C
 602	select REGMAP_IRQ
 603	help
 604	  Say yes here to add support for Maxim Semiconductor MAX77843.
 605	  This is companion Power Management IC with LEDs, Haptic, Charger,
 606	  Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip.
 607	  This driver provides common support for accessing the device;
 608	  additional drivers must be enabled in order to use the functionality
 609	  of the device.
 610
 611config MFD_MAX8907
 612	tristate "Maxim Semiconductor MAX8907 PMIC Support"
 613	select MFD_CORE
 614	depends on I2C
 615	select REGMAP_I2C
 616	select REGMAP_IRQ
 617	help
 618	  Say yes here to add support for Maxim Semiconductor MAX8907. This is
 619	  a Power Management IC. This driver provides common support for
 620	  accessing the device; additional drivers must be enabled in order
 621	  to use the functionality of the device.
 622
 623config MFD_MAX8925
 624	bool "Maxim Semiconductor MAX8925 PMIC Support"
 625	depends on I2C=y
 626	select MFD_CORE
 627	help
 628	  Say yes here to add support for Maxim Semiconductor MAX8925. This is
 629	  a Power Management IC. This driver provides common support for
 630	  accessing the device, additional drivers must be enabled in order
 631	  to use the functionality of the device.
 632
 633config MFD_MAX8997
 634	bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
 635	depends on I2C=y
 636	select MFD_CORE
 637	select IRQ_DOMAIN
 638	help
 639	  Say yes here to add support for Maxim Semiconductor MAX8997/8966.
 640	  This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
 641	  MUIC controls on chip.
 642	  This driver provides common support for accessing the device;
 643	  additional drivers must be enabled in order to use the functionality
 644	  of the device.
 645
 646config MFD_MAX8998
 647	bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
 648	depends on I2C=y
 649	select MFD_CORE
 650	select IRQ_DOMAIN
 651	help
 652	  Say yes here to add support for Maxim Semiconductor MAX8998 and
 653	  National Semiconductor LP3974. This is a Power Management IC.
 654	  This driver provides common support for accessing the device,
 655	  additional drivers must be enabled in order to use the functionality
 656	  of the device.
 657
 658config MFD_MT6397
 659	tristate "MediaTek MT6397 PMIC Support"
 660	select MFD_CORE
 661	select IRQ_DOMAIN
 662	help
 663	  Say yes here to add support for MediaTek MT6397 PMIC. This is
 664	  a Power Management IC. This driver provides common support for
 665	  accessing the device; additional drivers must be enabled in order
 666	  to use the functionality of the device.
 667
 668config MFD_MENF21BMC
 669	tristate "MEN 14F021P00 Board Management Controller Support"
 670	depends on I2C
 671	select MFD_CORE
 672	help
 673	  Say yes here to add support for the MEN 14F021P00 BMC
 674	  which is a Board Management Controller connected to the I2C bus.
 675	  The device supports multiple sub-devices like LED, HWMON and WDT.
 676	  This driver provides common support for accessing the devices;
 677	  additional drivers must be enabled in order to use the
 678	  functionality of the BMC device.
 679
 680	  This driver can also be built as a module. If so the module
 681	  will be called menf21bmc.
 682
 683config EZX_PCAP
 684	bool "Motorola EZXPCAP Support"
 685	depends on SPI_MASTER
 686	help
 687	  This enables the PCAP ASIC present on EZX Phones. This is
 688	  needed for MMC, TouchScreen, Sound, USB, etc..
 689
 690config MFD_VIPERBOARD
 691        tristate "Nano River Technologies Viperboard"
 692	select MFD_CORE
 693	depends on USB
 694	default n
 695	help
 696	  Say yes here if you want support for Nano River Technologies
 697	  Viperboard.
 698	  There are mfd cell drivers available for i2c master, adc and
 699	  both gpios found on the board. The spi part does not yet
 700	  have a driver.
 701	  You need to select the mfd cell drivers separately.
 702	  The drivers do not support all features the board exposes.
 703
 704config MFD_RETU
 705	tristate "Nokia Retu and Tahvo multi-function device"
 706	select MFD_CORE
 707	depends on I2C
 708	select REGMAP_IRQ
 709	help
 710	  Retu and Tahvo are a multi-function devices found on Nokia
 711	  Internet Tablets (770, N800 and N810).
 712
 713config MFD_PCF50633
 714	tristate "NXP PCF50633"
 715	depends on I2C
 716	select REGMAP_I2C
 717	help
 718	  Say yes here if you have NXP PCF50633 chip on your board.
 719	  This core driver provides register access and IRQ handling
 720	  facilities, and registers devices for the various functions
 721	  so that function-specific drivers can bind to them.
 722
 723config PCF50633_ADC
 724	tristate "NXP PCF50633 ADC"
 725	depends on MFD_PCF50633
 726	help
 727	 Say yes here if you want to include support for ADC in the
 728	 NXP PCF50633 chip.
 729
 730config PCF50633_GPIO
 731	tristate "NXP PCF50633 GPIO"
 732	depends on MFD_PCF50633
 733	help
 734	 Say yes here if you want to include support GPIO for pins on
 735	 the PCF50633 chip.
 736
 737config UCB1400_CORE
 738	tristate "Philips UCB1400 Core driver"
 739	depends on AC97_BUS
 740	depends on GPIOLIB
 741	help
 742	  This enables support for the Philips UCB1400 core functions.
 743	  The UCB1400 is an AC97 audio codec.
 744
 745	  To compile this driver as a module, choose M here: the
 746	  module will be called ucb1400_core.
 747
 748config MFD_PM8XXX
 749	tristate
 750
 751config MFD_PM8921_CORE
 752	tristate "Qualcomm PM8921 PMIC chip"
 753	depends on (ARM || HEXAGON)
 754	select IRQ_DOMAIN
 755	select MFD_CORE
 756	select MFD_PM8XXX
 757	select REGMAP
 758	help
 759	  If you say yes to this option, support will be included for the
 760	  built-in PM8921 PMIC chip.
 761
 762	  This is required if your board has a PM8921 and uses its features,
 763	  such as: MPPs, GPIOs, regulators, interrupts, and PWM.
 764
 765	  Say M here if you want to include support for PM8921 chip as a module.
 766	  This will build a module called "pm8921-core".
 767
 768config MFD_QCOM_RPM
 769	tristate "Qualcomm Resource Power Manager (RPM)"
 770	depends on ARCH_QCOM && OF
 771	help
 772	  If you say yes to this option, support will be included for the
 773	  Resource Power Manager system found in the Qualcomm 8660, 8960 and
 774	  8064 based devices.
 775
 776	  This is required to access many regulators, clocks and bus
 777	  frequencies controlled by the RPM on these devices.
 778
 779	  Say M here if you want to include support for the Qualcomm RPM as a
 780	  module. This will build a module called "qcom_rpm".
 781
 782config MFD_SPMI_PMIC
 783	tristate "Qualcomm SPMI PMICs"
 784	depends on ARCH_QCOM || COMPILE_TEST
 785	depends on OF
 786	depends on SPMI
 787	select REGMAP_SPMI
 788	help
 789	  This enables support for the Qualcomm SPMI PMICs.
 790	  These PMICs are currently used with the Snapdragon 800 series of
 791	  SoCs.  Note, that this will only be useful paired with descriptions
 792	  of the independent functions as children nodes in the device tree.
 793
 794	  Say M here if you want to include support for the SPMI PMIC
 795	  series as a module.  The module will be called "qcom-spmi-pmic".
 796
 797config MFD_RDC321X
 798	tristate "RDC R-321x southbridge"
 799	select MFD_CORE
 800	depends on PCI
 801	help
 802	  Say yes here if you want to have support for the RDC R-321x SoC
 803	  southbridge which provides access to GPIOs and Watchdog using the
 804	  southbridge PCI device configuration space.
 805
 806config MFD_RTSX_PCI
 807	tristate "Realtek PCI-E card reader"
 808	depends on PCI
 809	select MFD_CORE
 810	help
 811	  This supports for Realtek PCI-Express card reader including rts5209,
 812	  rts5227, rts522A, rts5229, rts5249, rts524A, rts525A, rtl8411, etc.
 813	  Realtek card reader supports access to many types of memory cards,
 814	  such as Memory Stick, Memory Stick Pro, Secure Digital and
 815	  MultiMediaCard.
 816
 817config MFD_RT5033
 818	tristate "Richtek RT5033 Power Management IC"
 819	depends on I2C
 820	select MFD_CORE
 821	select REGMAP_I2C
 822	select REGMAP_IRQ
 823	help
 824	  This driver provides for the Richtek RT5033 Power Management IC,
 825	  which includes the I2C driver and the Core APIs. This driver provides
 826	  common support for accessing the device. The device supports multiple
 827	  sub-devices like charger, fuel gauge, flash LED, current source,
 828	  LDO and Buck.
 829
 830config MFD_RTSX_USB
 831	tristate "Realtek USB card reader"
 832	depends on USB
 833	select MFD_CORE
 834	help
 835	  Select this option to get support for Realtek USB 2.0 card readers
 836	  including RTS5129, RTS5139, RTS5179 and RTS5170.
 837	  Realtek card reader supports access to many types of memory cards,
 838	  such as Memory Stick Pro, Secure Digital and MultiMediaCard.
 839
 840config MFD_RC5T583
 841	bool "Ricoh RC5T583 Power Management system device"
 842	depends on I2C=y
 843	select MFD_CORE
 844	select REGMAP_I2C
 845	help
 846	  Select this option to get support for the RICOH583 Power
 847	  Management system device.
 848	  This driver provides common support for accessing the device
 849	  through i2c interface. The device supports multiple sub-devices
 850	  like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
 851	  Additional drivers must be enabled in order to use the
 852	  different functionality of the device.
 853
 854config MFD_RK808
 855	tristate "Rockchip RK808 Power Management chip"
 856	depends on I2C && OF
 857	select MFD_CORE
 858	select REGMAP_I2C
 859	select REGMAP_IRQ
 860	help
 861	  If you say yes here you get support for the RK808
 862	  Power Management chips.
 863	  This driver provides common support for accessing the device
 864	  through I2C interface. The device supports multiple sub-devices
 865	  including interrupts, RTC, LDO & DCDC regulators, and onkey.
 866
 867config MFD_RN5T618
 868	tristate "Ricoh RN5T567/618 PMIC"
 869	depends on I2C
 870	depends on OF
 871	select MFD_CORE
 872	select REGMAP_I2C
 873	help
 874	  Say yes here to add support for the Ricoh RN5T567 or R5T618 PMIC.
 875	  This driver provides common support for accessing the device,
 876	  additional drivers must be enabled in order to use the
 877	  functionality of the device.
 878
 879config MFD_SEC_CORE
 880	bool "SAMSUNG Electronics PMIC Series Support"
 881	depends on I2C=y
 882	select MFD_CORE
 883	select REGMAP_I2C
 884	select REGMAP_IRQ
 885	help
 886	 Support for the Samsung Electronics MFD series.
 887	 This driver provides common support for accessing the device,
 888	 additional drivers must be enabled in order to use the functionality
 889	 of the device
 890
 891config MFD_SI476X_CORE
 892	tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
 893	depends on I2C
 894	select MFD_CORE
 895	select REGMAP_I2C
 896	help
 897	  This is the core driver for the SI476x series of AM/FM
 898	  radio. This MFD driver connects the radio-si476x V4L2 module
 899	  and the si476x audio codec.
 900
 901	  To compile this driver as a module, choose M here: the
 902	  module will be called si476x-core.
 903
 904config MFD_SM501
 905	tristate "Silicon Motion SM501"
 906	 ---help---
 907	  This is the core driver for the Silicon Motion SM501 multimedia
 908	  companion chip. This device is a multifunction device which may
 909	  provide numerous interfaces including USB host controller, USB gadget,
 910	  asynchronous serial ports, audio functions, and a dual display video
 911	  interface. The device may be connected by PCI or local bus with
 912	  varying functions enabled.
 913
 914config MFD_SM501_GPIO
 915	bool "Export GPIO via GPIO layer"
 916	depends on MFD_SM501 && GPIOLIB
 917	 ---help---
 918	 This option uses the gpio library layer to export the 64 GPIO
 919	 lines on the SM501. The platform data is used to supply the
 920	 base number for the first GPIO line to register.
 921
 922config MFD_SKY81452
 923	tristate "Skyworks Solutions SKY81452"
 924	select MFD_CORE
 925	select REGMAP_I2C
 926	depends on I2C
 927	help
 928	  This is the core driver for the Skyworks SKY81452 backlight and
 929	  voltage regulator device.
 930
 931	  This driver can also be built as a module.  If so, the module
 932	  will be called sky81452.
 933
 934config MFD_SMSC
 935       bool "SMSC ECE1099 series chips"
 936       depends on I2C=y
 937       select MFD_CORE
 938       select REGMAP_I2C
 939       help
 940        If you say yes here you get support for the
 941        ece1099 chips from SMSC.
 942
 943        To compile this driver as a module, choose M here: the
 944        module will be called smsc.
 945
 946config ABX500_CORE
 947	bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
 948	default y if ARCH_U300 || ARCH_U8500
 949	help
 950	  Say yes here if you have the ABX500 Mixed Signal IC family
 951	  chips. This core driver expose register access functions.
 952	  Functionality specific drivers using these functions can
 953	  remain unchanged when IC changes. Binding of the functions to
 954	  actual register access is done by the IC core driver.
 955
 956config AB3100_CORE
 957	bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
 958	depends on I2C=y && ABX500_CORE
 959	select MFD_CORE
 960	default y if ARCH_U300
 961	help
 962	  Select this to enable the AB3100 Mixed Signal IC core
 963	  functionality. This connects to a AB3100 on the I2C bus
 964	  and expose a number of symbols needed for dependent devices
 965	  to read and write registers and subscribe to events from
 966	  this multi-functional IC. This is needed to use other features
 967	  of the AB3100 such as battery-backed RTC, charging control,
 968	  LEDs, vibrator, system power and temperature, power management
 969	  and ALSA sound.
 970
 971config AB3100_OTP
 972	tristate "ST-Ericsson AB3100 OTP functions"
 973	depends on AB3100_CORE
 974	default y if AB3100_CORE
 975	help
 976	  Select this to enable the AB3100 Mixed Signal IC OTP (one-time
 977	  programmable memory) support. This exposes a sysfs file to read
 978	  out OTP values.
 979
 980config AB8500_CORE
 981	bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
 982	depends on ABX500_CORE && MFD_DB8500_PRCMU
 983	select POWER_SUPPLY
 984	select MFD_CORE
 985	select IRQ_DOMAIN
 986	help
 987	  Select this option to enable access to AB8500 power management
 988	  chip. This connects to U8500 either on the SSP/SPI bus (deprecated
 989	  since hardware version v1.0) or the I2C bus via PRCMU. It also adds
 990	  the irq_chip parts for handling the Mixed Signal chip events.
 991	  This chip embeds various other multimedia funtionalities as well.
 992
 993config AB8500_DEBUG
 994       bool "Enable debug info via debugfs"
 995       depends on AB8500_GPADC && DEBUG_FS
 996       default y if DEBUG_FS
 997       help
 998         Select this option if you want debug information using the debug
 999         filesystem, debugfs.
1000
1001config AB8500_GPADC
1002	bool "ST-Ericsson AB8500 GPADC driver"
1003	depends on AB8500_CORE && REGULATOR_AB8500
1004	default y
1005	help
1006	  AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
1007
1008config MFD_DB8500_PRCMU
1009	bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
1010	depends on UX500_SOC_DB8500
1011	select MFD_CORE
1012	help
1013	  Select this option to enable support for the DB8500 Power Reset
1014	  and Control Management Unit. This is basically an autonomous
1015	  system controller running an XP70 microprocessor, which is accessed
1016	  through a register map.
1017
1018config MFD_STMPE
1019	bool "STMicroelectronics STMPE"
1020	depends on (I2C=y || SPI_MASTER=y)
1021	depends on OF
1022	select MFD_CORE
1023	help
1024	  Support for the STMPE family of I/O Expanders from
1025	  STMicroelectronics.
1026
1027	  Currently supported devices are:
1028
1029		STMPE811: GPIO, Touchscreen
1030		STMPE1601: GPIO, Keypad
1031		STMPE1801: GPIO, Keypad
1032		STMPE2401: GPIO, Keypad
1033		STMPE2403: GPIO, Keypad
1034
1035	  This driver provides common support for accessing the device,
1036	  additional drivers must be enabled in order to use the functionality
1037	  of the device.  Currently available sub drivers are:
1038
1039		GPIO: stmpe-gpio
1040		Keypad: stmpe-keypad
1041		Touchscreen: stmpe-ts
1042
1043menu "STMicroelectronics STMPE Interface Drivers"
1044depends on MFD_STMPE
1045
1046config STMPE_I2C
1047	bool "STMicroelectronics STMPE I2C Interface"
1048	depends on I2C=y
1049	default y
1050	help
1051	  This is used to enable I2C interface of STMPE
1052
1053config STMPE_SPI
1054	bool "STMicroelectronics STMPE SPI Interface"
1055	depends on SPI_MASTER
1056	help
1057	  This is used to enable SPI interface of STMPE
1058endmenu
1059
1060config MFD_STA2X11
1061	bool "STMicroelectronics STA2X11"
1062	depends on STA2X11
1063	select MFD_CORE
1064	select REGMAP_MMIO
1065
1066config MFD_SUN6I_PRCM
1067	bool "Allwinner A31 PRCM controller"
1068	depends on ARCH_SUNXI
1069	select MFD_CORE
1070	help
1071	  Support for the PRCM (Power/Reset/Clock Management) unit available
1072	  in A31 SoC.
1073
1074config MFD_SYSCON
1075	bool "System Controller Register R/W Based on Regmap"
1076	select REGMAP_MMIO
1077	help
1078	  Select this option to enable accessing system control registers
1079	  via regmap.
1080
1081config MFD_DAVINCI_VOICECODEC
1082	tristate
1083	select MFD_CORE
1084	select REGMAP_MMIO
1085
1086config MFD_TI_AM335X_TSCADC
1087	tristate "TI ADC / Touch Screen chip support"
1088	select MFD_CORE
1089	select REGMAP
1090	select REGMAP_MMIO
1091	help
1092	  If you say yes here you get support for Texas Instruments series
1093	  of Touch Screen /ADC chips.
1094	  To compile this driver as a module, choose M here: the
1095	  module will be called ti_am335x_tscadc.
1096
1097config MFD_DM355EVM_MSP
1098	bool "TI DaVinci DM355 EVM microcontroller"
1099	depends on I2C=y && MACH_DAVINCI_DM355_EVM
1100	help
1101	  This driver supports the MSP430 microcontroller used on these
1102	  boards.  MSP430 firmware manages resets and power sequencing,
1103	  inputs from buttons and the IR remote, LEDs, an RTC, and more.
1104
1105config MFD_LP3943
1106	tristate "TI/National Semiconductor LP3943 MFD Driver"
1107	depends on I2C
1108	select MFD_CORE
1109	select REGMAP_I2C
1110	help
1111	  Support for the TI/National Semiconductor LP3943.
1112	  This driver consists of GPIO and PWM drivers.
1113	  With these functionalities, it can be used for LED string control or
1114	  general usage such like a GPIO controller and a PWM controller.
1115
1116config MFD_LP8788
1117	bool "TI LP8788 Power Management Unit Driver"
1118	depends on I2C=y
1119	select MFD_CORE
1120	select REGMAP_I2C
1121	select IRQ_DOMAIN
1122	help
1123	  TI LP8788 PMU supports regulators, battery charger, RTC,
1124	  ADC, backlight driver and current sinks.
1125
1126config MFD_OMAP_USB_HOST
1127	bool "TI OMAP USBHS core and TLL driver"
1128	depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
1129	default y
1130	help
1131	  This is the core driver for the OAMP EHCI and OHCI drivers.
1132	  This MFD driver does the required setup functionalities for
1133	  OMAP USB Host drivers.
1134
1135config MFD_PALMAS
1136	bool "TI Palmas series chips"
1137	select MFD_CORE
1138	select REGMAP_I2C
1139	select REGMAP_IRQ
1140	depends on I2C=y
1141	help
1142	  If you say yes here you get support for the Palmas
1143	  series of PMIC chips from Texas Instruments.
1144
1145config TPS6105X
1146	tristate "TI TPS61050/61052 Boost Converters"
1147	depends on I2C
1148	select REGMAP_I2C
1149	select REGULATOR
1150	select MFD_CORE
1151	select REGULATOR_FIXED_VOLTAGE
1152	help
1153	  This option enables a driver for the TP61050/TPS61052
1154	  high-power "white LED driver". This boost converter is
1155	  sometimes used for other things than white LEDs, and
1156	  also contains a GPIO pin.
1157
1158config TPS65010
1159	tristate "TI TPS6501x Power Management chips"
1160	depends on I2C && GPIOLIB
1161	default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
1162	help
1163	  If you say yes here you get support for the TPS6501x series of
1164	  Power Management chips.  These include voltage regulators,
1165	  lithium ion/polymer battery charging, and other features that
1166	  are often used in portable devices like cell phones and cameras.
1167
1168	  This driver can also be built as a module.  If so, the module
1169	  will be called tps65010.
1170
1171config TPS6507X
1172	tristate "TI TPS6507x Power Management / Touch Screen chips"
1173	select MFD_CORE
1174	depends on I2C
1175	help
1176	  If you say yes here you get support for the TPS6507x series of
1177	  Power Management / Touch Screen chips.  These include voltage
1178	  regulators, lithium ion/polymer battery charging, touch screen
1179	  and other features that are often used in portable devices.
1180	  This driver can also be built as a module.  If so, the module
1181	  will be called tps6507x.
1182
1183config MFD_TPS65086
1184	tristate "TI TPS65086 Power Management Integrated Chips (PMICs)"
1185	select REGMAP
1186	select REGMAP_IRQ
1187	select REGMAP_I2C
1188	depends on I2C
1189	help
1190	  If you say yes here you get support for the TPS65086 series of
1191	  Power Management chips.
1192	  This driver provides common support for accessing the device,
1193	  additional drivers must be enabled in order to use the
1194	  functionality of the device.
1195
1196config TPS65911_COMPARATOR
1197	tristate
1198
1199config MFD_TPS65090
1200	bool "TI TPS65090 Power Management chips"
1201	depends on I2C=y
1202	select MFD_CORE
1203	select REGMAP_I2C
1204	select REGMAP_IRQ
1205	help
1206	  If you say yes here you get support for the TPS65090 series of
1207	  Power Management chips.
1208	  This driver provides common support for accessing the device,
1209	  additional drivers must be enabled in order to use the
1210	  functionality of the device.
1211
1212config MFD_TPS65217
1213	tristate "TI TPS65217 Power Management / White LED chips"
1214	depends on I2C
1215	select MFD_CORE
1216	select REGMAP_I2C
1217	help
1218	  If you say yes here you get support for the TPS65217 series of
1219	  Power Management / White LED chips.
1220	  These include voltage regulators, lithium ion/polymer battery
1221	  charger, wled and other features that are often used in portable
1222	  devices.
1223
1224	  This driver can also be built as a module.  If so, the module
1225	  will be called tps65217.
1226
1227config MFD_TPS65218
1228	tristate "TI TPS65218 Power Management chips"
1229	depends on I2C
1230	select MFD_CORE
1231	select REGMAP_I2C
1232	select REGMAP_IRQ
1233	help
1234	  If you say yes here you get support for the TPS65218 series of
1235	  Power Management chips.
1236	  These include voltage regulators, gpio and other features
1237	  that are often used in portable devices. Only regulator
1238	  component is currently supported.
1239
1240	  This driver can also be built as a module.  If so, the module
1241	  will be called tps65218.
1242
1243config MFD_TPS6586X
1244	bool "TI TPS6586x Power Management chips"
1245	depends on I2C=y
1246	select MFD_CORE
1247	select REGMAP_I2C
1248	help
1249	  If you say yes here you get support for the TPS6586X series of
1250	  Power Management chips.
1251	  This driver provides common support for accessing the device,
1252	  additional drivers must be enabled in order to use the
1253	  functionality of the device.
1254
1255	  This driver can also be built as a module.  If so, the module
1256	  will be called tps6586x.
1257
1258config MFD_TPS65910
1259	bool "TI TPS65910 Power Management chip"
1260	depends on I2C=y
1261	depends on GPIOLIB || COMPILE_TEST
1262	select MFD_CORE
1263	select REGMAP_I2C
1264	select REGMAP_IRQ
1265	select IRQ_DOMAIN
1266	help
1267	  if you say yes here you get support for the TPS65910 series of
1268	  Power Management chips.
1269
1270config MFD_TPS65912
1271	tristate
1272	select MFD_CORE
1273	select REGMAP
1274	select REGMAP_IRQ
1275
1276config MFD_TPS65912_I2C
1277	tristate "TI TPS65912 Power Management chip with I2C"
1278	select MFD_TPS65912
1279	select REGMAP_I2C
1280	depends on I2C
1281	help
1282	  If you say yes here you get support for the TPS65912 series of
1283	  PM chips with I2C interface.
1284
1285config MFD_TPS65912_SPI
1286	tristate "TI TPS65912 Power Management chip with SPI"
1287	select MFD_TPS65912
1288	select REGMAP_SPI
1289	depends on SPI_MASTER
1290	help
1291	  If you say yes here you get support for the TPS65912 series of
1292	  PM chips with SPI interface.
1293
1294config MFD_TPS80031
1295	bool "TI TPS80031/TPS80032 Power Management chips"
1296	depends on I2C=y
1297	select MFD_CORE
1298	select REGMAP_I2C
1299	select REGMAP_IRQ
1300	help
1301	  If you say yes here you get support for the Texas Instruments
1302	  TPS80031/ TPS80032 Fully Integrated Power Management with Power
1303	  Path and Battery Charger. The device provides five configurable
1304	  step-down converters, 11 general purpose LDOs, USB OTG Module,
1305	  ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
1306	  Power Path from USB, 32K clock generator.
1307
1308config TWL4030_CORE
1309	bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
1310	depends on I2C=y
1311	select IRQ_DOMAIN
1312	select REGMAP_I2C
1313	help
1314	  Say yes here if you have TWL4030 / TWL6030 family chip on your board.
1315	  This core driver provides register access and IRQ handling
1316	  facilities, and registers devices for the various functions
1317	  so that function-specific drivers can bind to them.
1318
1319	  These multi-function chips are found on many OMAP2 and OMAP3
1320	  boards, providing power management, RTC, GPIO, keypad, a
1321	  high speed USB OTG transceiver, an audio codec (on most
1322	  versions) and many other features.
1323
1324config TWL4030_POWER
1325	bool "TI TWL4030 power resources"
1326	depends on TWL4030_CORE && ARM
1327	help
1328	  Say yes here if you want to use the power resources on the
1329	  TWL4030 family chips.  Most of these resources are regulators,
1330	  which have a separate driver; some are control signals, such
1331	  as clock request handshaking.
1332
1333	  This driver uses board-specific data to initialize the resources
1334	  and load scripts controlling which resources are switched off/on
1335	  or reset when a sleep, wakeup or warm reset event occurs.
1336
1337config MFD_TWL4030_AUDIO
1338	bool "TI TWL4030 Audio"
1339	depends on TWL4030_CORE
1340	select MFD_CORE
1341	default n
1342
1343config TWL6040_CORE
1344	bool "TI TWL6040 audio codec"
1345	depends on I2C=y
1346	select MFD_CORE
1347	select REGMAP_I2C
1348	select REGMAP_IRQ
1349	default n
1350	help
1351	  Say yes here if you want support for Texas Instruments TWL6040 audio
1352	  codec.
1353	  This driver provides common support for accessing the device,
1354	  additional drivers must be enabled in order to use the
1355	  functionality of the device (audio, vibra).
1356
1357config MENELAUS
1358	bool "TI TWL92330/Menelaus PM chip"
1359	depends on I2C=y && ARCH_OMAP2
1360	help
1361	  If you say yes here you get support for the Texas Instruments
1362	  TWL92330/Menelaus Power Management chip. This include voltage
1363	  regulators, Dual slot memory card transceivers, real-time clock
1364	  and other features that are often used in portable devices like
1365	  cell phones and PDAs.
1366
1367config MFD_WL1273_CORE
1368	tristate "TI WL1273 FM radio"
1369	depends on I2C
1370	select MFD_CORE
1371	default n
1372	help
1373	  This is the core driver for the TI WL1273 FM radio. This MFD
1374	  driver connects the radio-wl1273 V4L2 module and the wl1273
1375	  audio codec.
1376
1377config MFD_LM3533
1378	tristate "TI/National Semiconductor LM3533 Lighting Power chip"
1379	depends on I2C
1380	select MFD_CORE
1381	select REGMAP_I2C
1382	help
1383	  Say yes here to enable support for National Semiconductor / TI
1384	  LM3533 Lighting Power chips.
1385
1386	  This driver provides common support for accessing the device;
1387	  additional drivers must be enabled in order to use the LED,
1388	  backlight or ambient-light-sensor functionality of the device.
1389
1390config MFD_TIMBERDALE
1391	tristate "Timberdale FPGA"
1392	select MFD_CORE
1393	depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
1394	---help---
1395	This is the core driver for the timberdale FPGA. This device is a
1396	multifunction device which exposes numerous platform devices.
1397
1398	The timberdale FPGA can be found on the Intel Atom development board
1399	for in-vehicle infontainment, called Russellville.
1400
1401config MFD_TC3589X
1402	bool "Toshiba TC35892 and variants"
1403	depends on I2C=y
1404	depends on OF
1405	select MFD_CORE
1406	help
1407	  Support for the Toshiba TC35892 and variants I/O Expander.
1408
1409	  This driver provides common support for accessing the device,
1410	  additional drivers must be enabled in order to use the
1411	  functionality of the device.
1412
1413config MFD_TMIO
1414	bool
1415	default n
1416
1417config MFD_T7L66XB
1418	bool "Toshiba T7L66XB"
1419	depends on ARM && HAVE_CLK
1420	select MFD_CORE
1421	select MFD_TMIO
1422	help
1423	  Support for Toshiba Mobile IO Controller T7L66XB
1424
1425config MFD_TC6387XB
1426	bool "Toshiba TC6387XB"
1427	depends on ARM && HAVE_CLK
1428	select MFD_CORE
1429	select MFD_TMIO
1430	help
1431	  Support for Toshiba Mobile IO Controller TC6387XB
1432
1433config MFD_TC6393XB
1434	bool "Toshiba TC6393XB"
1435	depends on ARM && HAVE_CLK
1436	select GPIOLIB
1437	select MFD_CORE
1438	select MFD_TMIO
1439	help
1440	  Support for Toshiba Mobile IO Controller TC6393XB
1441
1442config MFD_VX855
1443	tristate "VIA VX855/VX875 integrated south bridge"
1444	depends on PCI
1445	select MFD_CORE
1446	help
1447	  Say yes here to enable support for various functions of the
1448	  VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
1449	  and/or vx855_gpio drivers for this to do anything useful.
1450
1451config MFD_ARIZONA
1452	select REGMAP
1453	select REGMAP_IRQ
1454	select MFD_CORE
1455	bool
1456
1457config MFD_ARIZONA_I2C
1458	tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C"
1459	select MFD_ARIZONA
1460	select REGMAP_I2C
1461	depends on I2C
1462	help
1463	  Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1464	  audio SoC core functionality controlled via I2C.
1465
1466config MFD_ARIZONA_SPI
1467	tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI"
1468	select MFD_ARIZONA
1469	select REGMAP_SPI
1470	depends on SPI_MASTER
1471	help
1472	  Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform
1473	  audio SoC core functionality controlled via SPI.
1474
1475config MFD_CS47L24
1476	bool "Cirrus Logic CS47L24 and WM1831"
1477	depends on MFD_ARIZONA
1478	help
1479	  Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC
1480
1481config MFD_WM5102
1482	bool "Wolfson Microelectronics WM5102"
1483	depends on MFD_ARIZONA
1484	help
1485	  Support for Wolfson Microelectronics WM5102 low power audio SoC
1486
1487config MFD_WM5110
1488	bool "Wolfson Microelectronics WM5110 and WM8280/WM8281"
1489	depends on MFD_ARIZONA
1490	help
1491	  Support for Wolfson Microelectronics WM5110 and WM8280/WM8281
1492	  low power audio SoC
1493
1494config MFD_WM8997
1495	bool "Wolfson Microelectronics WM8997"
1496	depends on MFD_ARIZONA
1497	help
1498	  Support for Wolfson Microelectronics WM8997 low power audio SoC
1499
1500config MFD_WM8998
1501	bool "Wolfson Microelectronics WM8998"
1502	depends on MFD_ARIZONA
1503	help
1504	  Support for Wolfson Microelectronics WM8998 low power audio SoC
1505
1506config MFD_WM8400
1507	bool "Wolfson Microelectronics WM8400"
1508	select MFD_CORE
1509	depends on I2C=y
1510	select REGMAP_I2C
1511	help
1512	  Support for the Wolfson Microelecronics WM8400 PMIC and audio
1513	  CODEC.  This driver provides common support for accessing
1514	  the device, additional drivers must be enabled in order to use
1515	  the functionality of the device.
1516
1517config MFD_WM831X
1518	bool
1519
1520config MFD_WM831X_I2C
1521	bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
1522	select MFD_CORE
1523	select MFD_WM831X
1524	select REGMAP_I2C
1525	select IRQ_DOMAIN
1526	depends on I2C=y
1527	help
1528	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1529	  when controlled using I2C.  This driver provides common support
1530	  for accessing the device, additional drivers must be enabled in
1531	  order to use the functionality of the device.
1532
1533config MFD_WM831X_SPI
1534	bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
1535	select MFD_CORE
1536	select MFD_WM831X
1537	select REGMAP_SPI
1538	select IRQ_DOMAIN
1539	depends on SPI_MASTER
1540	help
1541	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs
1542	  when controlled using SPI.  This driver provides common support
1543	  for accessing the device, additional drivers must be enabled in
1544	  order to use the functionality of the device.
1545
1546config MFD_WM8350
1547	bool
1548
1549config MFD_WM8350_I2C
1550	bool "Wolfson Microelectronics WM8350 with I2C"
1551	select MFD_WM8350
1552	depends on I2C=y
1553	help
1554	  The WM8350 is an integrated audio and power management
1555	  subsystem with watchdog and RTC functionality for embedded
1556	  systems.  This option enables core support for the WM8350 with
1557	  I2C as the control interface.  Additional options must be
1558	  selected to enable support for the functionality of the chip.
1559
1560config MFD_WM8994
1561	tristate "Wolfson Microelectronics WM8994"
1562	select MFD_CORE
1563	select REGMAP_I2C
1564	select REGMAP_IRQ
1565	depends on I2C
1566	help
1567	  The WM8994 is a highly integrated hi-fi CODEC designed for
1568	  smartphone applications.  As well as audio functionality it
1569	  has on board GPIO and regulator functionality which is
1570	  supported via the relevant subsystems.  This driver provides
1571	  core support for the WM8994, in order to use the actual
1572	  functionaltiy of the device other drivers must be enabled.
1573
1574config MFD_STW481X
1575	tristate "Support for ST Microelectronics STw481x"
1576	depends on I2C && (ARCH_NOMADIK || COMPILE_TEST)
1577	select REGMAP_I2C
1578	select MFD_CORE
1579	help
1580	  Select this option to enable the STw481x chip driver used
1581	  in various ST Microelectronics and ST-Ericsson embedded
1582	  Nomadik series.
1583
1584menu "Multimedia Capabilities Port drivers"
1585	depends on ARCH_SA1100
1586
1587config MCP
1588	tristate
1589
1590# Interface drivers
1591config MCP_SA11X0
1592	tristate "Support SA11x0 MCP interface"
1593	depends on ARCH_SA1100
1594	select MCP
1595
1596# Chip drivers
1597config MCP_UCB1200
1598	tristate "Support for UCB1200 / UCB1300"
1599	depends on MCP_SA11X0
1600	select MCP
1601
1602config MCP_UCB1200_TS
1603	tristate "Touchscreen interface support"
1604	depends on MCP_UCB1200 && INPUT
1605
1606endmenu
1607
1608config MFD_VEXPRESS_SYSREG
1609	bool "Versatile Express System Registers"
1610	depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET
1611	default y
1612	select CLKSRC_MMIO
1613	select GPIO_GENERIC_PLATFORM
1614	select MFD_CORE
1615	select MFD_SYSCON
1616	help
1617	  System Registers are the platform configuration block
1618	  on the ARM Ltd. Versatile Express board.
1619
1620endmenu
1621endif