Advertisement
Guest User

Kconfig

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