| .. | .. |
|---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
|---|
| 1 | 2 | # |
|---|
| 2 | 3 | # Multifunction miscellaneous devices |
|---|
| 3 | 4 | # |
|---|
| .. | .. |
|---|
| 14 | 15 | tristate "AMD CS5535 and CS5536 southbridge core functions" |
|---|
| 15 | 16 | select MFD_CORE |
|---|
| 16 | 17 | depends on PCI && (X86_32 || (X86 && COMPILE_TEST)) |
|---|
| 17 | | - ---help--- |
|---|
| 18 | + help |
|---|
| 18 | 19 | This is the core driver for CS5535/CS5536 MFD functions. This is |
|---|
| 19 | | - necessary for using the board's GPIO and MFGPT functionality. |
|---|
| 20 | + necessary for using the board's GPIO and MFGPT functionality. |
|---|
| 20 | 21 | |
|---|
| 21 | 22 | config MFD_ALTERA_A10SR |
|---|
| 22 | 23 | bool "Altera Arria10 DevKit System Resource chip" |
|---|
| .. | .. |
|---|
| 28 | 29 | using the SPI interface. This driver provides common support for |
|---|
| 29 | 30 | accessing the external gpio extender (LEDs & buttons) and |
|---|
| 30 | 31 | power supply alarms (hwmon). |
|---|
| 32 | + |
|---|
| 33 | +config MFD_ALTERA_SYSMGR |
|---|
| 34 | + bool "Altera SOCFPGA System Manager" |
|---|
| 35 | + depends on (ARCH_SOCFPGA || ARCH_STRATIX10) && OF |
|---|
| 36 | + select MFD_SYSCON |
|---|
| 37 | + help |
|---|
| 38 | + Select this to get System Manager support for all Altera branded |
|---|
| 39 | + SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by |
|---|
| 40 | + using regmap_mmio accesses for ARM32 parts and SMC calls to |
|---|
| 41 | + EL3 for ARM64 parts. |
|---|
| 31 | 42 | |
|---|
| 32 | 43 | config MFD_ACT8945A |
|---|
| 33 | 44 | tristate "Active-semi ACT8945A" |
|---|
| .. | .. |
|---|
| 98 | 109 | This driver provides common support for accessing the device, |
|---|
| 99 | 110 | additional drivers must be enabled in order to use the |
|---|
| 100 | 111 | functionality of the device. |
|---|
| 112 | + |
|---|
| 113 | +config MFD_AT91_USART |
|---|
| 114 | + tristate "AT91 USART Driver" |
|---|
| 115 | + select MFD_CORE |
|---|
| 116 | + depends on ARCH_AT91 || COMPILE_TEST |
|---|
| 117 | + help |
|---|
| 118 | + Select this to get support for AT91 USART IP. This is a wrapper |
|---|
| 119 | + over at91-usart-serial driver and usart-spi-driver. Only one function |
|---|
| 120 | + can be used at a time. The choice is done at boot time by the probe |
|---|
| 121 | + function of this MFD driver according to a device tree property. |
|---|
| 101 | 122 | |
|---|
| 102 | 123 | config MFD_ATMEL_FLEXCOM |
|---|
| 103 | 124 | tristate "Atmel Flexcom (Flexible Serial Communication Unit)" |
|---|
| .. | .. |
|---|
| 190 | 211 | components like regulators or the PEK (Power Enable Key) under the |
|---|
| 191 | 212 | corresponding menus. |
|---|
| 192 | 213 | |
|---|
| 193 | | -config MFD_CROS_EC |
|---|
| 194 | | - tristate "ChromeOS Embedded Controller" |
|---|
| 214 | +config MFD_CROS_EC_DEV |
|---|
| 215 | + tristate "ChromeOS Embedded Controller multifunction device" |
|---|
| 195 | 216 | select MFD_CORE |
|---|
| 196 | | - select CHROME_PLATFORMS |
|---|
| 197 | | - select CROS_EC_PROTO |
|---|
| 198 | | - depends on X86 || ARM || ARM64 || COMPILE_TEST |
|---|
| 217 | + depends on CROS_EC |
|---|
| 218 | + default CROS_EC |
|---|
| 199 | 219 | 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. |
|---|
| 220 | + Select this to get support for ChromeOS Embedded Controller |
|---|
| 221 | + sub-devices. This driver will instantiate additional drivers such |
|---|
| 222 | + as RTC, USBPD, etc. but you have to select the individual drivers. |
|---|
| 204 | 223 | |
|---|
| 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. |
|---|
| 224 | + To compile this driver as a module, choose M here: the module will be |
|---|
| 225 | + called cros-ec-dev. |
|---|
| 214 | 226 | |
|---|
| 215 | 227 | config MFD_MADERA |
|---|
| 216 | 228 | tristate "Cirrus Logic Madera codecs" |
|---|
| .. | .. |
|---|
| 241 | 253 | Support for the Cirrus Logic Madera platform audio SoC |
|---|
| 242 | 254 | core functionality controlled via SPI. |
|---|
| 243 | 255 | |
|---|
| 256 | +config MFD_CS47L15 |
|---|
| 257 | + bool "Cirrus Logic CS47L15" |
|---|
| 258 | + select PINCTRL_CS47L15 |
|---|
| 259 | + depends on MFD_MADERA |
|---|
| 260 | + help |
|---|
| 261 | + Support for Cirrus Logic CS47L15 Smart Codec |
|---|
| 262 | + |
|---|
| 244 | 263 | config MFD_CS47L35 |
|---|
| 245 | 264 | bool "Cirrus Logic CS47L35" |
|---|
| 246 | 265 | select PINCTRL_CS47L35 |
|---|
| .. | .. |
|---|
| 262 | 281 | help |
|---|
| 263 | 282 | Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs |
|---|
| 264 | 283 | |
|---|
| 284 | +config MFD_CS47L92 |
|---|
| 285 | + bool "Cirrus Logic CS47L92/93" |
|---|
| 286 | + select PINCTRL_CS47L92 |
|---|
| 287 | + depends on MFD_MADERA |
|---|
| 288 | + help |
|---|
| 289 | + Support for Cirrus Logic CS42L92, CS47L92 and CS47L93 Smart Codecs |
|---|
| 290 | + |
|---|
| 265 | 291 | config MFD_ASIC3 |
|---|
| 266 | 292 | bool "Compaq ASIC3" |
|---|
| 267 | | - depends on GPIOLIB && ARM |
|---|
| 293 | + depends on GPIOLIB |
|---|
| 294 | + depends on ARM || COMPILE_TEST |
|---|
| 268 | 295 | select MFD_CORE |
|---|
| 269 | | - ---help--- |
|---|
| 296 | + help |
|---|
| 270 | 297 | This driver supports the ASIC3 multifunction chip found on many |
|---|
| 271 | 298 | PDAs (mainly iPAQ and HTC based ones) |
|---|
| 272 | 299 | |
|---|
| .. | .. |
|---|
| 372 | 399 | etc. must be enabled in order to use the functionality of |
|---|
| 373 | 400 | the device. |
|---|
| 374 | 401 | |
|---|
| 402 | +config MFD_ENE_KB3930 |
|---|
| 403 | + tristate "ENE KB3930 Embedded Controller support" |
|---|
| 404 | + depends on I2C |
|---|
| 405 | + depends on MACH_MMP3_DT || COMPILE_TEST |
|---|
| 406 | + select MFD_CORE |
|---|
| 407 | + help |
|---|
| 408 | + This adds support for the power-off functionality and access to |
|---|
| 409 | + the registers that control LEDS and USB port power on ENE KB3930 |
|---|
| 410 | + Embedded Controller. To use the LED functionality LEDS_ARIEL must |
|---|
| 411 | + be enabled. |
|---|
| 412 | + |
|---|
| 375 | 413 | config MFD_EXYNOS_LPASS |
|---|
| 376 | 414 | tristate "Samsung Exynos SoC Low Power Audio Subsystem" |
|---|
| 377 | 415 | depends on ARCH_EXYNOS || COMPILE_TEST |
|---|
| .. | .. |
|---|
| 380 | 418 | help |
|---|
| 381 | 419 | Select this option to enable support for Samsung Exynos Low Power |
|---|
| 382 | 420 | Audio Subsystem. |
|---|
| 421 | + |
|---|
| 422 | +config MFD_GATEWORKS_GSC |
|---|
| 423 | + tristate "Gateworks System Controller" |
|---|
| 424 | + depends on (I2C && OF) |
|---|
| 425 | + select MFD_CORE |
|---|
| 426 | + select REGMAP_I2C |
|---|
| 427 | + select REGMAP_IRQ |
|---|
| 428 | + help |
|---|
| 429 | + Enable support for the Gateworks System Controller (GSC) found |
|---|
| 430 | + on Gateworks Single Board Computers supporting system functions |
|---|
| 431 | + such as push-button monitor, multiple ADC's for voltage and |
|---|
| 432 | + temperature monitoring, fan controller and watchdog monitor. |
|---|
| 433 | + This driver provides common support for accessing the device. |
|---|
| 434 | + Additional drivers must be enabled in order to use the |
|---|
| 435 | + functionality of the device. |
|---|
| 383 | 436 | |
|---|
| 384 | 437 | config MFD_MC13XXX |
|---|
| 385 | 438 | tristate |
|---|
| .. | .. |
|---|
| 407 | 460 | select MFD_MC13XXX |
|---|
| 408 | 461 | help |
|---|
| 409 | 462 | Select this if your MC13xxx is connected via an I2C bus. |
|---|
| 463 | + |
|---|
| 464 | +config MFD_MP2629 |
|---|
| 465 | + tristate "Monolithic Power Systems MP2629 ADC and Battery charger" |
|---|
| 466 | + depends on I2C |
|---|
| 467 | + select REGMAP_I2C |
|---|
| 468 | + select MFD_CORE |
|---|
| 469 | + help |
|---|
| 470 | + Select this option to enable support for Monolithic Power Systems |
|---|
| 471 | + battery charger. This provides ADC, thermal and battery charger power |
|---|
| 472 | + management functions. |
|---|
| 410 | 473 | |
|---|
| 411 | 474 | config MFD_MXS_LRADC |
|---|
| 412 | 475 | tristate "Freescale i.MX23/i.MX28 LRADC" |
|---|
| .. | .. |
|---|
| 443 | 506 | Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi- |
|---|
| 444 | 507 | functions, such as regulators, RTC, codec, Coulomb counter, etc. |
|---|
| 445 | 508 | This driver includes core APIs _only_. You have to select |
|---|
| 446 | | - individul components like voltage regulators under corresponding |
|---|
| 509 | + individual components like voltage regulators under corresponding |
|---|
| 447 | 510 | menus in order to enable them. |
|---|
| 448 | 511 | We communicate with the Hi6421 via memory-mapped I/O. |
|---|
| 449 | 512 | |
|---|
| .. | .. |
|---|
| 525 | 588 | |
|---|
| 526 | 589 | config INTEL_SOC_PMIC_BXTWC |
|---|
| 527 | 590 | tristate "Support for Intel Broxton Whiskey Cove PMIC" |
|---|
| 528 | | - depends on INTEL_PMC_IPC |
|---|
| 591 | + depends on MFD_INTEL_PMC_BXT |
|---|
| 529 | 592 | select MFD_CORE |
|---|
| 530 | 593 | select REGMAP_IRQ |
|---|
| 531 | 594 | help |
|---|
| .. | .. |
|---|
| 563 | 626 | Select this option for supporting Dollar Cove (TI version) PMIC |
|---|
| 564 | 627 | device that is found on some Intel Cherry Trail systems. |
|---|
| 565 | 628 | |
|---|
| 629 | +config INTEL_SOC_PMIC_MRFLD |
|---|
| 630 | + tristate "Support for Intel Merrifield Basin Cove PMIC" |
|---|
| 631 | + depends on GPIOLIB |
|---|
| 632 | + depends on ACPI |
|---|
| 633 | + depends on INTEL_SCU |
|---|
| 634 | + select MFD_CORE |
|---|
| 635 | + select REGMAP_IRQ |
|---|
| 636 | + help |
|---|
| 637 | + Select this option for supporting Basin Cove PMIC device |
|---|
| 638 | + that is found on Intel Merrifield systems. |
|---|
| 639 | + |
|---|
| 566 | 640 | config MFD_INTEL_LPSS |
|---|
| 567 | 641 | tristate |
|---|
| 568 | 642 | select COMMON_CLK |
|---|
| .. | .. |
|---|
| 588 | 662 | |
|---|
| 589 | 663 | config MFD_INTEL_MSIC |
|---|
| 590 | 664 | bool "Intel MSIC" |
|---|
| 591 | | - depends on INTEL_SCU_IPC |
|---|
| 665 | + depends on INTEL_SCU |
|---|
| 592 | 666 | select MFD_CORE |
|---|
| 593 | 667 | help |
|---|
| 594 | 668 | Select this option to enable access to Intel MSIC (Avatele |
|---|
| 595 | 669 | Passage) chip. This chip embeds audio, battery, GPIO, etc. |
|---|
| 596 | 670 | devices used in Intel Medfield platforms. |
|---|
| 671 | + |
|---|
| 672 | +config MFD_INTEL_PMC_BXT |
|---|
| 673 | + tristate "Intel PMC Driver for Broxton" |
|---|
| 674 | + depends on X86 |
|---|
| 675 | + depends on X86_PLATFORM_DEVICES |
|---|
| 676 | + depends on ACPI |
|---|
| 677 | + select INTEL_SCU_IPC |
|---|
| 678 | + select MFD_CORE |
|---|
| 679 | + help |
|---|
| 680 | + This driver provides support for the PMC (Power Management |
|---|
| 681 | + Controller) on Intel Broxton and Apollo Lake. The PMC is a |
|---|
| 682 | + multi-function device that exposes IPC, General Control |
|---|
| 683 | + Register and P-unit access. In addition this creates devices |
|---|
| 684 | + for iTCO watchdog and telemetry that are part of the PMC. |
|---|
| 597 | 685 | |
|---|
| 598 | 686 | config MFD_IPAQ_MICRO |
|---|
| 599 | 687 | bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support" |
|---|
| .. | .. |
|---|
| 605 | 693 | AT90LS8535 microcontroller flashed with a special iPAQ |
|---|
| 606 | 694 | firmware using the custom protocol implemented in this driver. |
|---|
| 607 | 695 | |
|---|
| 696 | +config MFD_IQS62X |
|---|
| 697 | + tristate "Azoteq IQS620A/621/622/624/625 core support" |
|---|
| 698 | + depends on I2C |
|---|
| 699 | + select MFD_CORE |
|---|
| 700 | + select REGMAP_I2C |
|---|
| 701 | + help |
|---|
| 702 | + Say Y here if you want to build core support for the Azoteq IQS620A, |
|---|
| 703 | + IQS621, IQS622, IQS624 and IQS625 multi-function sensors. Additional |
|---|
| 704 | + options must be selected to enable device-specific functions. |
|---|
| 705 | + |
|---|
| 706 | + To compile this driver as a module, choose M here: the module will |
|---|
| 707 | + be called iqs62x. |
|---|
| 708 | + |
|---|
| 608 | 709 | config MFD_JANZ_CMODIO |
|---|
| 609 | 710 | tristate "Janz CMOD-IO PCI MODULbus Carrier Board" |
|---|
| 610 | 711 | select MFD_CORE |
|---|
| .. | .. |
|---|
| 614 | 715 | carrier board. This device is a PCI to MODULbus bridge which may |
|---|
| 615 | 716 | host many different types of MODULbus daughterboards, including |
|---|
| 616 | 717 | 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 | 718 | |
|---|
| 627 | 719 | config MFD_KEMPLD |
|---|
| 628 | 720 | tristate "Kontron module PLD device" |
|---|
| .. | .. |
|---|
| 724 | 816 | provides common support for accessing the device; additional drivers |
|---|
| 725 | 817 | must be enabled in order to use the functionality of the device. |
|---|
| 726 | 818 | |
|---|
| 819 | +config MFD_MAX77650 |
|---|
| 820 | + tristate "Maxim MAX77650/77651 PMIC Support" |
|---|
| 821 | + depends on I2C |
|---|
| 822 | + depends on OF || COMPILE_TEST |
|---|
| 823 | + select MFD_CORE |
|---|
| 824 | + select REGMAP_I2C |
|---|
| 825 | + select REGMAP_IRQ |
|---|
| 826 | + help |
|---|
| 827 | + Say Y here to add support for Maxim Semiconductor MAX77650 and |
|---|
| 828 | + MAX77651 Power Management ICs. This is the core multifunction |
|---|
| 829 | + driver for interacting with the device. The module name is |
|---|
| 830 | + 'max77650'. Additional drivers can be enabled in order to use |
|---|
| 831 | + the following functionalities of the device: GPIO, regulator, |
|---|
| 832 | + charger, LED, onkey. |
|---|
| 833 | + |
|---|
| 727 | 834 | config MFD_MAX77686 |
|---|
| 728 | 835 | tristate "Maxim Semiconductor MAX77686/802 PMIC Support" |
|---|
| 729 | 836 | depends on I2C |
|---|
| .. | .. |
|---|
| 814 | 921 | additional drivers must be enabled in order to use the functionality |
|---|
| 815 | 922 | of the device. |
|---|
| 816 | 923 | |
|---|
| 924 | +config MFD_MAX96745 |
|---|
| 925 | + tristate "Maxim Semiconductor MAX96745 GMSL2 Serializer Support" |
|---|
| 926 | + depends on I2C |
|---|
| 927 | + select MFD_CORE |
|---|
| 928 | + select REGMAP_I2C |
|---|
| 929 | + select I2C_MUX |
|---|
| 930 | + help |
|---|
| 931 | + Say yes here to add support for Maxim Semiconductor MAX96745. |
|---|
| 932 | + |
|---|
| 933 | +config MFD_MAX96755F |
|---|
| 934 | + tristate "Maxim Semiconductor MAX96755 GMSL2 Serializer Support" |
|---|
| 935 | + depends on I2C |
|---|
| 936 | + select MFD_CORE |
|---|
| 937 | + select REGMAP_I2C |
|---|
| 938 | + help |
|---|
| 939 | + Say yes here to add support for Maxim Semiconductor MAX96755. |
|---|
| 940 | + |
|---|
| 941 | +config MFD_MT6360 |
|---|
| 942 | + tristate "Mediatek MT6360 SubPMIC" |
|---|
| 943 | + select MFD_CORE |
|---|
| 944 | + select REGMAP_I2C |
|---|
| 945 | + select REGMAP_IRQ |
|---|
| 946 | + depends on I2C |
|---|
| 947 | + help |
|---|
| 948 | + Say Y here to enable MT6360 PMU/PMIC/LDO functional support. |
|---|
| 949 | + PMU part includes Charger, Flashlight, RGB LED |
|---|
| 950 | + PMIC part includes 2-channel BUCKs and 2-channel LDOs |
|---|
| 951 | + LDO part includes 4-channel LDOs |
|---|
| 952 | + |
|---|
| 817 | 953 | config MFD_MT6397 |
|---|
| 818 | 954 | tristate "MediaTek MT6397 PMIC Support" |
|---|
| 819 | 955 | select MFD_CORE |
|---|
| .. | .. |
|---|
| 850 | 986 | tristate "Support for Motorola CPCAP" |
|---|
| 851 | 987 | depends on SPI |
|---|
| 852 | 988 | depends on OF || COMPILE_TEST |
|---|
| 989 | + select MFD_CORE |
|---|
| 853 | 990 | select REGMAP_SPI |
|---|
| 854 | 991 | select REGMAP_IRQ |
|---|
| 855 | 992 | help |
|---|
| .. | .. |
|---|
| 858 | 995 | At least Motorola Droid 4 is known to use CPCAP. |
|---|
| 859 | 996 | |
|---|
| 860 | 997 | config MFD_VIPERBOARD |
|---|
| 861 | | - tristate "Nano River Technologies Viperboard" |
|---|
| 998 | + tristate "Nano River Technologies Viperboard" |
|---|
| 862 | 999 | select MFD_CORE |
|---|
| 863 | 1000 | depends on USB |
|---|
| 864 | 1001 | default n |
|---|
| .. | .. |
|---|
| 894 | 1031 | tristate "NXP PCF50633 ADC" |
|---|
| 895 | 1032 | depends on MFD_PCF50633 |
|---|
| 896 | 1033 | help |
|---|
| 897 | | - Say yes here if you want to include support for ADC in the |
|---|
| 898 | | - NXP PCF50633 chip. |
|---|
| 1034 | + Say yes here if you want to include support for ADC in the |
|---|
| 1035 | + NXP PCF50633 chip. |
|---|
| 899 | 1036 | |
|---|
| 900 | 1037 | config PCF50633_GPIO |
|---|
| 901 | 1038 | tristate "NXP PCF50633 GPIO" |
|---|
| 902 | 1039 | depends on MFD_PCF50633 |
|---|
| 903 | 1040 | help |
|---|
| 904 | | - Say yes here if you want to include support GPIO for pins on |
|---|
| 905 | | - the PCF50633 chip. |
|---|
| 1041 | + Say yes here if you want to include support GPIO for pins on |
|---|
| 1042 | + the PCF50633 chip. |
|---|
| 906 | 1043 | |
|---|
| 907 | 1044 | config UCB1400_CORE |
|---|
| 908 | 1045 | tristate "Philips UCB1400 Core driver" |
|---|
| .. | .. |
|---|
| 918 | 1055 | config MFD_PM8XXX |
|---|
| 919 | 1056 | tristate "Qualcomm PM8xxx PMIC chips driver" |
|---|
| 920 | 1057 | depends on (ARM || HEXAGON || COMPILE_TEST) |
|---|
| 921 | | - select IRQ_DOMAIN |
|---|
| 1058 | + select IRQ_DOMAIN_HIERARCHY |
|---|
| 922 | 1059 | select MFD_CORE |
|---|
| 923 | 1060 | select REGMAP |
|---|
| 924 | 1061 | help |
|---|
| .. | .. |
|---|
| 997 | 1134 | different functionality of the device. |
|---|
| 998 | 1135 | |
|---|
| 999 | 1136 | config MFD_RK618 |
|---|
| 1000 | | - bool "Rockchip RK618 MFD Driver" |
|---|
| 1137 | + tristate "Rockchip RK618 MFD Driver" |
|---|
| 1001 | 1138 | depends on I2C |
|---|
| 1002 | 1139 | depends on OF |
|---|
| 1003 | 1140 | select MFD_CORE |
|---|
| .. | .. |
|---|
| 1040 | 1177 | if you say yes here you get support for the RK630 when controlled |
|---|
| 1041 | 1178 | using SPI. |
|---|
| 1042 | 1179 | |
|---|
| 1180 | +config MFD_RK806 |
|---|
| 1181 | + tristate "Rockchip RK806 Power Management Chip" |
|---|
| 1182 | + select MFD_CORE |
|---|
| 1183 | + select REGMAP |
|---|
| 1184 | + select REGMAP_IRQ |
|---|
| 1185 | + help |
|---|
| 1186 | + If you say yes here you get support for the RK806 Power Management chips. |
|---|
| 1187 | + This driver provides common support for accessing the device |
|---|
| 1188 | + through SPI interface. The device supports multiple sub-devices |
|---|
| 1189 | + including interrupts, LDO & DCDC regulators, and onkey. |
|---|
| 1190 | + |
|---|
| 1191 | +config MFD_RK806_SPI |
|---|
| 1192 | + tristate "RK806 Power Management chip with SPI" |
|---|
| 1193 | + select MFD_RK806 |
|---|
| 1194 | + select REGMAP_SPI |
|---|
| 1195 | + depends on SPI_MASTER |
|---|
| 1196 | + help |
|---|
| 1197 | + If you say yes here you get support for the RK806 PM chips with SPI interface. |
|---|
| 1198 | + |
|---|
| 1043 | 1199 | config MFD_RK808 |
|---|
| 1044 | 1200 | tristate "Rockchip RK805/RK808/RK809/RK816/RK817/RK818 Power Management Chip" |
|---|
| 1045 | 1201 | depends on I2C && OF |
|---|
| .. | .. |
|---|
| 1047 | 1203 | select REGMAP_I2C |
|---|
| 1048 | 1204 | select REGMAP_IRQ |
|---|
| 1049 | 1205 | help |
|---|
| 1050 | | - If you say yes here you get support for the RK805, RK808 , RK809, |
|---|
| 1051 | | - RK816, RK817 and RK818 Power Management chips. |
|---|
| 1206 | + If you say yes here you get support for the RK805, RK808, RK809, |
|---|
| 1207 | + RK816, RK817, RK818 Power Management chips. |
|---|
| 1052 | 1208 | This driver provides common support for accessing the device |
|---|
| 1053 | 1209 | through I2C interface. The device supports multiple sub-devices |
|---|
| 1054 | 1210 | including interrupts, RTC, LDO & DCDC regulators, and onkey. |
|---|
| .. | .. |
|---|
| 1062 | 1218 | if you say yes here you get support for the RK1000, with func as |
|---|
| 1063 | 1219 | TVEncoder or CODEC. |
|---|
| 1064 | 1220 | |
|---|
| 1221 | +source "drivers/mfd/display-serdes/Kconfig" |
|---|
| 1222 | +source "drivers/mfd/rkx110_x120/Kconfig" |
|---|
| 1223 | + |
|---|
| 1065 | 1224 | config MFD_RN5T618 |
|---|
| 1066 | 1225 | tristate "Ricoh RN5T567/618 PMIC" |
|---|
| 1067 | 1226 | depends on I2C |
|---|
| 1068 | 1227 | depends on OF |
|---|
| 1069 | 1228 | select MFD_CORE |
|---|
| 1070 | 1229 | select REGMAP_I2C |
|---|
| 1230 | + select REGMAP_IRQ |
|---|
| 1071 | 1231 | help |
|---|
| 1072 | 1232 | Say yes here to add support for the Ricoh RN5T567, |
|---|
| 1073 | | - RN5T618, RC5T619 PMIC. |
|---|
| 1233 | + RN5T618, RC5T619 PMIC. |
|---|
| 1074 | 1234 | This driver provides common support for accessing the device, |
|---|
| 1075 | 1235 | additional drivers must be enabled in order to use the |
|---|
| 1076 | 1236 | functionality of the device. |
|---|
| 1077 | 1237 | |
|---|
| 1078 | 1238 | config MFD_SEC_CORE |
|---|
| 1079 | | - bool "SAMSUNG Electronics PMIC Series Support" |
|---|
| 1239 | + tristate "Samsung Electronics PMIC Series Support" |
|---|
| 1080 | 1240 | depends on I2C=y |
|---|
| 1081 | 1241 | select MFD_CORE |
|---|
| 1082 | 1242 | select REGMAP_I2C |
|---|
| 1083 | 1243 | select REGMAP_IRQ |
|---|
| 1084 | 1244 | help |
|---|
| 1085 | | - Support for the Samsung Electronics MFD series. |
|---|
| 1086 | | - This driver provides common support for accessing the device, |
|---|
| 1087 | | - additional drivers must be enabled in order to use the functionality |
|---|
| 1088 | | - of the device |
|---|
| 1245 | + Support for the Samsung Electronics PMIC devices coming |
|---|
| 1246 | + usually along with Samsung Exynos SoC chipset. |
|---|
| 1247 | + This driver provides common support for accessing the device, |
|---|
| 1248 | + additional drivers must be enabled in order to use the functionality |
|---|
| 1249 | + of the device |
|---|
| 1250 | + |
|---|
| 1251 | + To compile this driver as a module, choose M here: the |
|---|
| 1252 | + module will be called sec-core. |
|---|
| 1253 | + Have in mind that important core drivers (like regulators) depend |
|---|
| 1254 | + on this driver so building this as a module might require proper |
|---|
| 1255 | + initial ramdisk or might not boot up as well in certain scenarios. |
|---|
| 1089 | 1256 | |
|---|
| 1090 | 1257 | config MFD_SI476X_CORE |
|---|
| 1091 | 1258 | tristate "Silicon Laboratories 4761/64/68 AM/FM radio." |
|---|
| .. | .. |
|---|
| 1100 | 1267 | To compile this driver as a module, choose M here: the |
|---|
| 1101 | 1268 | module will be called si476x-core. |
|---|
| 1102 | 1269 | |
|---|
| 1270 | +config MFD_SIMPLE_MFD_I2C |
|---|
| 1271 | + tristate |
|---|
| 1272 | + depends on I2C |
|---|
| 1273 | + select REGMAP_I2C |
|---|
| 1274 | + help |
|---|
| 1275 | + This driver creates a single register map with the intention for it |
|---|
| 1276 | + to be shared by all sub-devices. |
|---|
| 1277 | + |
|---|
| 1278 | + Once the register map has been successfully initialised, any |
|---|
| 1279 | + sub-devices represented by child nodes in Device Tree will be |
|---|
| 1280 | + subsequently registered. |
|---|
| 1281 | + |
|---|
| 1282 | +config MFD_SL28CPLD |
|---|
| 1283 | + tristate "Kontron sl28cpld Board Management Controller" |
|---|
| 1284 | + depends on I2C |
|---|
| 1285 | + depends on ARCH_LAYERSCAPE || COMPILE_TEST |
|---|
| 1286 | + select MFD_SIMPLE_MFD_I2C |
|---|
| 1287 | + help |
|---|
| 1288 | + Say yes here to enable support for the Kontron sl28cpld board |
|---|
| 1289 | + management controller. |
|---|
| 1290 | + |
|---|
| 1291 | + It can be found on the following boards: |
|---|
| 1292 | + * SMARC-sAL28 |
|---|
| 1293 | + |
|---|
| 1103 | 1294 | config MFD_SM501 |
|---|
| 1104 | 1295 | tristate "Silicon Motion SM501" |
|---|
| 1105 | | - ---help--- |
|---|
| 1296 | + depends on HAS_DMA |
|---|
| 1297 | + help |
|---|
| 1106 | 1298 | This is the core driver for the Silicon Motion SM501 multimedia |
|---|
| 1107 | 1299 | companion chip. This device is a multifunction device which may |
|---|
| 1108 | 1300 | provide numerous interfaces including USB host controller, USB gadget, |
|---|
| .. | .. |
|---|
| 1113 | 1305 | config MFD_SM501_GPIO |
|---|
| 1114 | 1306 | bool "Export GPIO via GPIO layer" |
|---|
| 1115 | 1307 | depends on MFD_SM501 && GPIOLIB |
|---|
| 1116 | | - ---help--- |
|---|
| 1117 | | - This option uses the gpio library layer to export the 64 GPIO |
|---|
| 1118 | | - lines on the SM501. The platform data is used to supply the |
|---|
| 1119 | | - base number for the first GPIO line to register. |
|---|
| 1308 | + help |
|---|
| 1309 | + This option uses the gpio library layer to export the 64 GPIO |
|---|
| 1310 | + lines on the SM501. The platform data is used to supply the |
|---|
| 1311 | + base number for the first GPIO line to register. |
|---|
| 1120 | 1312 | |
|---|
| 1121 | 1313 | config MFD_SKY81452 |
|---|
| 1122 | 1314 | tristate "Skyworks Solutions SKY81452" |
|---|
| .. | .. |
|---|
| 1129 | 1321 | |
|---|
| 1130 | 1322 | This driver can also be built as a module. If so, the module |
|---|
| 1131 | 1323 | will be called sky81452. |
|---|
| 1132 | | - |
|---|
| 1133 | | -config MFD_SMSC |
|---|
| 1134 | | - bool "SMSC ECE1099 series chips" |
|---|
| 1135 | | - depends on I2C=y |
|---|
| 1136 | | - select MFD_CORE |
|---|
| 1137 | | - select REGMAP_I2C |
|---|
| 1138 | | - help |
|---|
| 1139 | | - If you say yes here you get support for the |
|---|
| 1140 | | - ece1099 chips from SMSC. |
|---|
| 1141 | | - |
|---|
| 1142 | | - To compile this driver as a module, choose M here: the |
|---|
| 1143 | | - module will be called smsc. |
|---|
| 1144 | 1324 | |
|---|
| 1145 | 1325 | config MFD_SC27XX_PMIC |
|---|
| 1146 | 1326 | tristate "Spreadtrum SC27xx PMICs" |
|---|
| .. | .. |
|---|
| 1203 | 1383 | chip. This connects to U8500 either on the SSP/SPI bus (deprecated |
|---|
| 1204 | 1384 | since hardware version v1.0) or the I2C bus via PRCMU. It also adds |
|---|
| 1205 | 1385 | the irq_chip parts for handling the Mixed Signal chip events. |
|---|
| 1206 | | - This chip embeds various other multimedia funtionalities as well. |
|---|
| 1386 | + This chip embeds various other multimedia functionalities as well. |
|---|
| 1207 | 1387 | |
|---|
| 1208 | 1388 | config AB8500_DEBUG |
|---|
| 1209 | | - bool "Enable debug info via debugfs" |
|---|
| 1210 | | - depends on AB8500_GPADC && DEBUG_FS |
|---|
| 1211 | | - default y if DEBUG_FS |
|---|
| 1212 | | - help |
|---|
| 1213 | | - Select this option if you want debug information using the debug |
|---|
| 1214 | | - filesystem, debugfs. |
|---|
| 1215 | | - |
|---|
| 1216 | | -config AB8500_GPADC |
|---|
| 1217 | | - bool "ST-Ericsson AB8500 GPADC driver" |
|---|
| 1218 | | - depends on AB8500_CORE && REGULATOR_AB8500 |
|---|
| 1219 | | - default y |
|---|
| 1389 | + bool "Enable debug info via debugfs" |
|---|
| 1390 | + depends on AB8500_GPADC && DEBUG_FS |
|---|
| 1391 | + default y if DEBUG_FS |
|---|
| 1220 | 1392 | help |
|---|
| 1221 | | - AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage |
|---|
| 1393 | + Select this option if you want debug information using the debug |
|---|
| 1394 | + filesystem, debugfs. |
|---|
| 1222 | 1395 | |
|---|
| 1223 | 1396 | config MFD_DB8500_PRCMU |
|---|
| 1224 | 1397 | bool "ST-Ericsson DB8500 Power Reset Control Management Unit" |
|---|
| .. | .. |
|---|
| 1241 | 1414 | |
|---|
| 1242 | 1415 | Currently supported devices are: |
|---|
| 1243 | 1416 | |
|---|
| 1244 | | - STMPE811: GPIO, Touchscreen |
|---|
| 1417 | + STMPE811: GPIO, Touchscreen, ADC |
|---|
| 1245 | 1418 | STMPE1601: GPIO, Keypad |
|---|
| 1246 | 1419 | STMPE1801: GPIO, Keypad |
|---|
| 1247 | 1420 | STMPE2401: GPIO, Keypad |
|---|
| .. | .. |
|---|
| 1254 | 1427 | GPIO: stmpe-gpio |
|---|
| 1255 | 1428 | Keypad: stmpe-keypad |
|---|
| 1256 | 1429 | Touchscreen: stmpe-ts |
|---|
| 1430 | + ADC: stmpe-adc |
|---|
| 1257 | 1431 | |
|---|
| 1258 | 1432 | menu "STMicroelectronics STMPE Interface Drivers" |
|---|
| 1259 | 1433 | depends on MFD_STMPE |
|---|
| .. | .. |
|---|
| 1280 | 1454 | |
|---|
| 1281 | 1455 | config MFD_SUN6I_PRCM |
|---|
| 1282 | 1456 | bool "Allwinner A31 PRCM controller" |
|---|
| 1283 | | - depends on ARCH_SUNXI |
|---|
| 1457 | + depends on ARCH_SUNXI || COMPILE_TEST |
|---|
| 1284 | 1458 | select MFD_CORE |
|---|
| 1285 | 1459 | help |
|---|
| 1286 | 1460 | Support for the PRCM (Power/Reset/Clock Management) unit available |
|---|
| .. | .. |
|---|
| 1345 | 1519 | select REGMAP_I2C |
|---|
| 1346 | 1520 | help |
|---|
| 1347 | 1521 | Say yes here to enable support for TI LMU chips. |
|---|
| 1348 | | - |
|---|
| 1349 | | - TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697. |
|---|
| 1350 | | - It consists of backlight, LED and regulator driver. |
|---|
| 1522 | + TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and |
|---|
| 1523 | + LM36274. It consists of backlight, LED and regulator driver. |
|---|
| 1351 | 1524 | It provides consistent device controls for lighting functions. |
|---|
| 1352 | 1525 | |
|---|
| 1353 | 1526 | config MFD_OMAP_USB_HOST |
|---|
| .. | .. |
|---|
| 1455 | 1628 | |
|---|
| 1456 | 1629 | config MFD_TPS68470 |
|---|
| 1457 | 1630 | bool "TI TPS68470 Power Management / LED chips" |
|---|
| 1458 | | - depends on ACPI && I2C=y |
|---|
| 1631 | + depends on ACPI && PCI && I2C=y |
|---|
| 1459 | 1632 | depends on I2C_DESIGNWARE_PLATFORM=y |
|---|
| 1460 | 1633 | select MFD_CORE |
|---|
| 1461 | 1634 | select REGMAP_I2C |
|---|
| .. | .. |
|---|
| 1665 | 1838 | tristate "Timberdale FPGA" |
|---|
| 1666 | 1839 | select MFD_CORE |
|---|
| 1667 | 1840 | depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST) |
|---|
| 1668 | | - ---help--- |
|---|
| 1841 | + help |
|---|
| 1669 | 1842 | This is the core driver for the timberdale FPGA. This device is a |
|---|
| 1670 | 1843 | multifunction device which exposes numerous platform devices. |
|---|
| 1671 | 1844 | |
|---|
| .. | .. |
|---|
| 1713 | 1886 | help |
|---|
| 1714 | 1887 | Support for Toshiba Mobile IO Controller TC6393XB |
|---|
| 1715 | 1888 | |
|---|
| 1889 | +config MFD_TQMX86 |
|---|
| 1890 | + tristate "TQ-Systems IO controller TQMX86" |
|---|
| 1891 | + select MFD_CORE |
|---|
| 1892 | + help |
|---|
| 1893 | + Say yes here to enable support for various functions of the |
|---|
| 1894 | + TQ-Systems IO controller and watchdog device, found on their |
|---|
| 1895 | + ComExpress CPU modules. |
|---|
| 1896 | + |
|---|
| 1716 | 1897 | config MFD_VX855 |
|---|
| 1717 | 1898 | tristate "VIA VX855/VX875 integrated south bridge" |
|---|
| 1718 | 1899 | depends on PCI |
|---|
| .. | .. |
|---|
| 1721 | 1902 | Say yes here to enable support for various functions of the |
|---|
| 1722 | 1903 | VIA VX855/VX875 south bridge. You will need to enable the vx855_spi |
|---|
| 1723 | 1904 | and/or vx855_gpio drivers for this to do anything useful. |
|---|
| 1905 | + |
|---|
| 1906 | +config MFD_LOCHNAGAR |
|---|
| 1907 | + bool "Cirrus Logic Lochnagar Audio Development Board" |
|---|
| 1908 | + select MFD_CORE |
|---|
| 1909 | + select REGMAP_I2C |
|---|
| 1910 | + depends on I2C=y && OF |
|---|
| 1911 | + help |
|---|
| 1912 | + Support for Cirrus Logic Lochnagar audio development board. |
|---|
| 1724 | 1913 | |
|---|
| 1725 | 1914 | config MFD_ARIZONA |
|---|
| 1726 | 1915 | select REGMAP |
|---|
| .. | .. |
|---|
| 1844 | 2033 | has on board GPIO and regulator functionality which is |
|---|
| 1845 | 2034 | supported via the relevant subsystems. This driver provides |
|---|
| 1846 | 2035 | core support for the WM8994, in order to use the actual |
|---|
| 1847 | | - functionaltiy of the device other drivers must be enabled. |
|---|
| 2036 | + functionality of the device other drivers must be enabled. |
|---|
| 1848 | 2037 | |
|---|
| 1849 | 2038 | config MFD_WM97xx |
|---|
| 1850 | 2039 | tristate "Wolfson Microelectronics WM97xx" |
|---|
| .. | .. |
|---|
| 1857 | 2046 | designed for smartphone applications. As well as audio functionality |
|---|
| 1858 | 2047 | it has on board GPIO and a touchscreen functionality which is |
|---|
| 1859 | 2048 | supported via the relevant subsystems. This driver provides core |
|---|
| 1860 | | - support for the WM97xx, in order to use the actual functionaltiy of |
|---|
| 2049 | + support for the WM97xx, in order to use the actual functionality of |
|---|
| 1861 | 2050 | the device other drivers must be enabled. |
|---|
| 1862 | 2051 | |
|---|
| 1863 | 2052 | config MFD_STW481X |
|---|
| .. | .. |
|---|
| 1882 | 2071 | Power Management ICs. BD71837 is designed to power processors like |
|---|
| 1883 | 2072 | NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring |
|---|
| 1884 | 2073 | and emergency shut down as well as 32,768KHz clock output. |
|---|
| 2074 | + |
|---|
| 2075 | +config MFD_ROHM_BD70528 |
|---|
| 2076 | + tristate "ROHM BD70528 Power Management IC" |
|---|
| 2077 | + depends on I2C=y |
|---|
| 2078 | + depends on OF |
|---|
| 2079 | + select REGMAP_I2C |
|---|
| 2080 | + select REGMAP_IRQ |
|---|
| 2081 | + select MFD_CORE |
|---|
| 2082 | + help |
|---|
| 2083 | + Select this option to get support for the ROHM BD70528 Power |
|---|
| 2084 | + Management IC. BD71837 is general purpose single-chip power |
|---|
| 2085 | + management IC for battery-powered portable devices. It contains |
|---|
| 2086 | + 3 ultra-low current consumption buck converters, 3 LDOs and 2 LED |
|---|
| 2087 | + drivers. Also included are 4 GPIOs, a real-time clock (RTC), a 32kHz |
|---|
| 2088 | + crystal oscillator, high-accuracy VREF for use with an external ADC, |
|---|
| 2089 | + 10 bits SAR ADC for battery temperature monitor and 1S battery |
|---|
| 2090 | + charger. |
|---|
| 2091 | + |
|---|
| 2092 | +config MFD_ROHM_BD71828 |
|---|
| 2093 | + tristate "ROHM BD71828 Power Management IC" |
|---|
| 2094 | + depends on I2C=y |
|---|
| 2095 | + depends on OF |
|---|
| 2096 | + select REGMAP_I2C |
|---|
| 2097 | + select REGMAP_IRQ |
|---|
| 2098 | + select MFD_CORE |
|---|
| 2099 | + help |
|---|
| 2100 | + Select this option to get support for the ROHM BD71828 Power |
|---|
| 2101 | + Management IC. BD71828GW is a single-chip power management IC for |
|---|
| 2102 | + battery-powered portable devices. The IC integrates 7 buck |
|---|
| 2103 | + converters, 7 LDOs, and a 1500 mA single-cell linear charger. |
|---|
| 2104 | + Also included is a Coulomb counter, a real-time clock (RTC), and |
|---|
| 2105 | + a 32.768 kHz clock gate. |
|---|
| 1885 | 2106 | |
|---|
| 1886 | 2107 | config MFD_STM32_LPTIMER |
|---|
| 1887 | 2108 | tristate "Support for STM32 Low-Power Timer" |
|---|
| .. | .. |
|---|
| 1908 | 2129 | for PWM and IIO Timer. This driver allow to share the |
|---|
| 1909 | 2130 | registers between the others drivers. |
|---|
| 1910 | 2131 | |
|---|
| 2132 | +config MFD_STPMIC1 |
|---|
| 2133 | + tristate "Support for STPMIC1 PMIC" |
|---|
| 2134 | + depends on (I2C=y && OF) |
|---|
| 2135 | + select REGMAP_I2C |
|---|
| 2136 | + select REGMAP_IRQ |
|---|
| 2137 | + select MFD_CORE |
|---|
| 2138 | + help |
|---|
| 2139 | + Support for ST Microelectronics STPMIC1 PMIC. STPMIC1 has power on |
|---|
| 2140 | + key, watchdog and regulator functionalities which are supported via |
|---|
| 2141 | + the relevant subsystems. This driver provides core support for the |
|---|
| 2142 | + STPMIC1. In order to use the actual functionality of the device other |
|---|
| 2143 | + drivers must be enabled. |
|---|
| 2144 | + |
|---|
| 2145 | + To compile this driver as a module, choose M here: the |
|---|
| 2146 | + module will be called stpmic1. |
|---|
| 2147 | + |
|---|
| 2148 | +config MFD_STMFX |
|---|
| 2149 | + tristate "Support for STMicroelectronics Multi-Function eXpander (STMFX)" |
|---|
| 2150 | + depends on I2C |
|---|
| 2151 | + depends on OF || COMPILE_TEST |
|---|
| 2152 | + select MFD_CORE |
|---|
| 2153 | + select REGMAP_I2C |
|---|
| 2154 | + help |
|---|
| 2155 | + Support for the STMicroelectronics Multi-Function eXpander. |
|---|
| 2156 | + |
|---|
| 2157 | + This driver provides common support for accessing the device, |
|---|
| 2158 | + additional drivers must be enabled in order to use the functionality |
|---|
| 2159 | + of the device. |
|---|
| 2160 | + |
|---|
| 2161 | +config MFD_WCD934X |
|---|
| 2162 | + tristate "Support for WCD9340/WCD9341 Codec" |
|---|
| 2163 | + depends on SLIMBUS |
|---|
| 2164 | + select REGMAP |
|---|
| 2165 | + select REGMAP_SLIMBUS |
|---|
| 2166 | + select REGMAP_IRQ |
|---|
| 2167 | + select MFD_CORE |
|---|
| 2168 | + help |
|---|
| 2169 | + Support for the Qualcomm WCD9340/WCD9341 Codec. |
|---|
| 2170 | + This driver provides common support WCD934x audio codec and its |
|---|
| 2171 | + associated Pin Controller, Soundwire Controller and Audio codec. |
|---|
| 2172 | + |
|---|
| 2173 | +config MFD_KHADAS_MCU |
|---|
| 2174 | + tristate "Support for Khadas System control Microcontroller" |
|---|
| 2175 | + depends on I2C |
|---|
| 2176 | + depends on ARCH_MESON || ARCH_ROCKCHIP || COMPILE_TEST |
|---|
| 2177 | + select MFD_CORE |
|---|
| 2178 | + select REGMAP_I2C |
|---|
| 2179 | + help |
|---|
| 2180 | + Support for the Khadas System control Microcontroller interface |
|---|
| 2181 | + present on their VIM and Edge boards. |
|---|
| 2182 | + |
|---|
| 2183 | + This Microcontroller is present on the Khadas VIM1, VIM2, VIM3 and |
|---|
| 2184 | + Edge boards. |
|---|
| 2185 | + |
|---|
| 2186 | + It provides multiple boot control features like password check, |
|---|
| 2187 | + power-on options, power-off control and system FAN control on recent |
|---|
| 2188 | + boards. |
|---|
| 2189 | + |
|---|
| 2190 | + This driver provides common support for accessing the device, |
|---|
| 2191 | + additional drivers must be enabled in order to use the functionality |
|---|
| 2192 | + of the device. |
|---|
| 2193 | + |
|---|
| 1911 | 2194 | menu "Multimedia Capabilities Port drivers" |
|---|
| 1912 | 2195 | depends on ARCH_SA1100 |
|---|
| 1913 | 2196 | |
|---|
| .. | .. |
|---|
| 1933 | 2216 | endmenu |
|---|
| 1934 | 2217 | |
|---|
| 1935 | 2218 | config MFD_VEXPRESS_SYSREG |
|---|
| 1936 | | - bool "Versatile Express System Registers" |
|---|
| 1937 | | - depends on VEXPRESS_CONFIG && GPIOLIB && !ARCH_USES_GETTIMEOFFSET |
|---|
| 2219 | + tristate "Versatile Express System Registers" |
|---|
| 2220 | + depends on VEXPRESS_CONFIG && GPIOLIB |
|---|
| 1938 | 2221 | default y |
|---|
| 1939 | | - select CLKSRC_MMIO |
|---|
| 1940 | 2222 | select GPIO_GENERIC_PLATFORM |
|---|
| 1941 | 2223 | select MFD_CORE |
|---|
| 1942 | 2224 | select MFD_SYSCON |
|---|
| .. | .. |
|---|
| 1952 | 2234 | Select this to get support for the Supervisory Processor |
|---|
| 1953 | 2235 | device found on several devices in RAVE line of hardware. |
|---|
| 1954 | 2236 | |
|---|
| 1955 | | -endmenu |
|---|
| 1956 | | - |
|---|
| 1957 | | -config FUSB_30X |
|---|
| 1958 | | - tristate "Fairchild fusb302 Support" |
|---|
| 1959 | | - depends on I2C |
|---|
| 2237 | +config SGI_MFD_IOC3 |
|---|
| 2238 | + tristate "SGI IOC3 core driver" |
|---|
| 2239 | + depends on PCI && MIPS && 64BIT |
|---|
| 2240 | + select MFD_CORE |
|---|
| 1960 | 2241 | help |
|---|
| 1961 | | - This option provides a driver for the Fairchild FUSB302. |
|---|
| 1962 | | - It support typec-pd functionality by controlled using I2C. |
|---|
| 2242 | + This option enables basic support for the SGI IOC3-based |
|---|
| 2243 | + controller cards. This option does not enable any specific |
|---|
| 2244 | + functions on such a card, but provides necessary infrastructure |
|---|
| 2245 | + for other drivers to utilize. |
|---|
| 1963 | 2246 | |
|---|
| 2247 | + If you have an SGI Origin, Octane, or a PCI IOC3 card, |
|---|
| 2248 | + then say Y. Otherwise say N. |
|---|
| 2249 | + |
|---|
| 2250 | +config MFD_INTEL_M10_BMC |
|---|
| 2251 | + tristate "Intel MAX 10 Board Management Controller" |
|---|
| 2252 | + depends on SPI_MASTER |
|---|
| 2253 | + select REGMAP_SPI_AVMM |
|---|
| 2254 | + select MFD_CORE |
|---|
| 2255 | + help |
|---|
| 2256 | + Support for the Intel MAX 10 board management controller using the |
|---|
| 2257 | + SPI interface. |
|---|
| 2258 | + |
|---|
| 2259 | + This driver provides common support for accessing the device, |
|---|
| 2260 | + additional drivers must be enabled in order to use the functionality |
|---|
| 2261 | + of the device. |
|---|
| 2262 | + |
|---|
| 2263 | +endmenu |
|---|
| 1964 | 2264 | endif |
|---|