| 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | # |
| 3 | # Multifunction miscellaneous devices |
| 4 | # |
| 5 | |
| 6 | if HAS_IOMEM |
| 7 | menu "Multifunction device drivers" |
| 8 | |
| 9 | config MFD_CORE |
| 10 | tristate |
| 11 | select IRQ_DOMAIN |
| 12 | default n |
| 13 | |
| 14 | config MFD_CS5535 |
| 15 | tristate "AMD CS5535 and CS5536 southbridge core functions" |
| 16 | select MFD_CORE |
| 17 | depends on PCI && (X86_32 || (X86 && COMPILE_TEST)) |
| 18 | depends on !UML |
| 19 | help |
| 20 | This is the core driver for CS5535/CS5536 MFD functions. This is |
| 21 | necessary for using the board's GPIO and MFGPT functionality. |
| 22 | |
| 23 | config MFD_ADP5585 |
| 24 | tristate "Analog Devices ADP5585 keypad decoder and I/O expander driver" |
| 25 | select MFD_CORE |
| 26 | select REGMAP_I2C |
| 27 | depends on I2C |
| 28 | depends on OF |
| 29 | help |
| 30 | Say yes here to add support for the Analog Devices ADP5585 GPIO |
| 31 | expander, PWM and keypad controller. This includes the I2C driver and |
| 32 | the core APIs _only_, you have to select individual components like |
| 33 | the GPIO and PWM functions under the corresponding menus. |
| 34 | |
| 35 | config MFD_ALTERA_A10SR |
| 36 | bool "Altera Arria10 DevKit System Resource chip" |
| 37 | depends on ARCH_INTEL_SOCFPGA && SPI_MASTER=y && OF |
| 38 | select REGMAP_SPI |
| 39 | select MFD_CORE |
| 40 | help |
| 41 | Support for the Altera Arria10 DevKit MAX5 System Resource chip |
| 42 | using the SPI interface. This driver provides common support for |
| 43 | accessing the external gpio extender (LEDs & buttons) and |
| 44 | power supply alarms (hwmon). |
| 45 | |
| 46 | config MFD_ALTERA_SYSMGR |
| 47 | bool "Altera SOCFPGA System Manager" |
| 48 | depends on ARCH_INTEL_SOCFPGA || COMPILE_TEST |
| 49 | depends on OF |
| 50 | select MFD_SYSCON |
| 51 | help |
| 52 | Select this to get System Manager support for all Altera branded |
| 53 | SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by |
| 54 | using regmap_mmio accesses for ARM32 parts and SMC calls to |
| 55 | EL3 for ARM64 parts. |
| 56 | |
| 57 | config MFD_ACT8945A |
| 58 | tristate "Active-semi ACT8945A" |
| 59 | select MFD_CORE |
| 60 | select REGMAP_I2C |
| 61 | depends on I2C && OF |
| 62 | help |
| 63 | Support for the ACT8945A PMIC from Active-semi. This device |
| 64 | features three step-down DC/DC converters and four low-dropout |
| 65 | linear regulators, along with a complete ActivePath battery |
| 66 | charger. |
| 67 | |
| 68 | config MFD_SUN4I_GPADC |
| 69 | tristate "Allwinner sunxi platforms' GPADC MFD driver" |
| 70 | select MFD_CORE |
| 71 | select REGMAP_MMIO |
| 72 | select REGMAP_IRQ |
| 73 | depends on ARCH_SUNXI || COMPILE_TEST |
| 74 | depends on !TOUCHSCREEN_SUN4I |
| 75 | help |
| 76 | Select this to get support for Allwinner SoCs (A10, A13 and A31) ADC. |
| 77 | This driver will only map the hardware interrupt and registers, you |
| 78 | have to select individual drivers based on this MFD to be able to use |
| 79 | the ADC or the thermal sensor. This will try to probe the ADC driver |
| 80 | sun4i-gpadc-iio and the hwmon driver iio_hwmon. |
| 81 | |
| 82 | To compile this driver as a module, choose M here: the module will be |
| 83 | called sun4i-gpadc. |
| 84 | |
| 85 | config MFD_AS3711 |
| 86 | bool "AMS AS3711" |
| 87 | select MFD_CORE |
| 88 | select REGMAP_I2C |
| 89 | select REGMAP_IRQ |
| 90 | depends on I2C=y |
| 91 | help |
| 92 | Support for the AS3711 PMIC from AMS |
| 93 | |
| 94 | config MFD_SMPRO |
| 95 | tristate "Ampere Computing SMpro core driver" |
| 96 | depends on I2C |
| 97 | select MFD_CORE |
| 98 | select REGMAP_I2C |
| 99 | help |
| 100 | Say yes here to enable SMpro driver support for Ampere's Altra |
| 101 | processor family. |
| 102 | |
| 103 | Ampere's Altra SMpro exposes an I2C regmap interface that can |
| 104 | be accessed by child devices. |
| 105 | |
| 106 | config MFD_AS3722 |
| 107 | tristate "ams AS3722 Power Management IC" |
| 108 | select MFD_CORE |
| 109 | select REGMAP_I2C |
| 110 | select REGMAP_IRQ |
| 111 | depends on I2C=y && OF |
| 112 | help |
| 113 | The ams AS3722 is a compact system PMU suitable for mobile phones, |
| 114 | tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down |
| 115 | controllers, 11 LDOs, RTC, automatic battery, temperature and |
| 116 | over current monitoring, GPIOs, ADC and a watchdog. |
| 117 | |
| 118 | config PMIC_ADP5520 |
| 119 | bool "Analog Devices ADP5520/01 MFD PMIC Core Support" |
| 120 | depends on I2C=y |
| 121 | help |
| 122 | Say yes here to add support for Analog Devices ADP5520 and ADP5501, |
| 123 | Multifunction Power Management IC. This includes |
| 124 | the I2C driver and the core APIs _only_, you have to select |
| 125 | individual components like LCD backlight, LEDs, GPIOs and Kepad |
| 126 | under the corresponding menus. |
| 127 | |
| 128 | config MFD_AAT2870_CORE |
| 129 | bool "AnalogicTech AAT2870" |
| 130 | select MFD_CORE |
| 131 | depends on I2C=y |
| 132 | depends on GPIOLIB || COMPILE_TEST |
| 133 | depends on GPIOLIB_LEGACY |
| 134 | help |
| 135 | If you say yes here you get support for the AAT2870. |
| 136 | This driver provides common support for accessing the device, |
| 137 | additional drivers must be enabled in order to use the |
| 138 | functionality of the device. |
| 139 | |
| 140 | config MFD_AT91_USART |
| 141 | tristate "AT91 USART Driver" |
| 142 | select MFD_CORE |
| 143 | depends on ARCH_MICROCHIP || COMPILE_TEST |
| 144 | help |
| 145 | Select this to get support for AT91 USART IP. This is a wrapper |
| 146 | over at91-usart-serial driver and usart-spi-driver. Only one function |
| 147 | can be used at a time. The choice is done at boot time by the probe |
| 148 | function of this MFD driver according to a device tree property. |
| 149 | |
| 150 | config MFD_ATMEL_FLEXCOM |
| 151 | tristate "Atmel Flexcom (Flexible Serial Communication Unit)" |
| 152 | select MFD_CORE |
| 153 | depends on OF |
| 154 | help |
| 155 | Select this to get support for Atmel Flexcom. This is a wrapper |
| 156 | which embeds a SPI controller, a I2C controller and a USART. Only |
| 157 | one function can be used at a time. The choice is done at boot time |
| 158 | by the probe function of this MFD driver according to a device tree |
| 159 | property. |
| 160 | |
| 161 | config MFD_ATMEL_HLCDC |
| 162 | tristate "Atmel HLCDC (High-end LCD Controller)" |
| 163 | select MFD_CORE |
| 164 | select REGMAP_MMIO |
| 165 | depends on OF |
| 166 | help |
| 167 | If you say yes here you get support for the HLCDC block. |
| 168 | This driver provides common support for accessing the device, |
| 169 | additional drivers must be enabled in order to use the |
| 170 | functionality of the device. |
| 171 | |
| 172 | config MFD_ATMEL_SMC |
| 173 | bool |
| 174 | select MFD_SYSCON |
| 175 | |
| 176 | config MFD_BCM590XX |
| 177 | tristate "Broadcom BCM590xx PMUs" |
| 178 | select MFD_CORE |
| 179 | select REGMAP_I2C |
| 180 | depends on I2C |
| 181 | help |
| 182 | Support for the BCM590xx PMUs from Broadcom |
| 183 | |
| 184 | config MFD_BD9571MWV |
| 185 | tristate "ROHM BD9571MWV PMIC" |
| 186 | select MFD_CORE |
| 187 | select REGMAP_I2C |
| 188 | select REGMAP_IRQ |
| 189 | depends on I2C |
| 190 | help |
| 191 | Support for the ROHM BD9571MWV PMIC, which contains single |
| 192 | voltage regulator, voltage sampling units, GPIO block and |
| 193 | watchdog block. |
| 194 | |
| 195 | This driver can also be built as a module. If so, the module |
| 196 | will be called bd9571mwv. |
| 197 | |
| 198 | config MFD_AC100 |
| 199 | tristate "X-Powers AC100" |
| 200 | select MFD_CORE |
| 201 | depends on SUNXI_RSB |
| 202 | help |
| 203 | If you say Y here you get support for the X-Powers AC100 audio codec |
| 204 | IC. |
| 205 | This driver include only the core APIs. You have to select individual |
| 206 | components like codecs or RTC under the corresponding menus. |
| 207 | |
| 208 | config MFD_AXP20X |
| 209 | tristate |
| 210 | select MFD_CORE |
| 211 | select REGMAP_IRQ |
| 212 | |
| 213 | config MFD_AXP20X_I2C |
| 214 | tristate "X-Powers AXP series PMICs with I2C" |
| 215 | select MFD_AXP20X |
| 216 | select REGMAP_I2C |
| 217 | depends on I2C |
| 218 | help |
| 219 | If you say Y here you get support for the X-Powers AXP series power |
| 220 | management ICs (PMICs) controlled with I2C. |
| 221 | This driver include only the core APIs. You have to select individual |
| 222 | components like regulators or the PEK (Power Enable Key) under the |
| 223 | corresponding menus. |
| 224 | |
| 225 | Note on x86 this provides an ACPI OpRegion, so this must be 'y' |
| 226 | (builtin) and not a module, as the OpRegion must be available as |
| 227 | soon as possible. For the same reason the I2C bus driver options |
| 228 | I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too. |
| 229 | |
| 230 | config MFD_AXP20X_RSB |
| 231 | tristate "X-Powers AXP series PMICs with RSB" |
| 232 | select MFD_AXP20X |
| 233 | depends on SUNXI_RSB |
| 234 | help |
| 235 | If you say Y here you get support for the X-Powers AXP series power |
| 236 | management ICs (PMICs) controlled with RSB. |
| 237 | This driver include only the core APIs. You have to select individual |
| 238 | components like regulators or the PEK (Power Enable Key) under the |
| 239 | corresponding menus. |
| 240 | |
| 241 | config MFD_CGBC |
| 242 | tristate "Congatec Board Controller" |
| 243 | select MFD_CORE |
| 244 | depends on X86 |
| 245 | help |
| 246 | This is the core driver of the Board Controller found on some Congatec |
| 247 | SMARC modules. The Board Controller provides functions like watchdog, |
| 248 | I2C busses, and GPIO controller. |
| 249 | |
| 250 | To compile this driver as a module, choose M here: the module will be |
| 251 | called cgbc-core. |
| 252 | |
| 253 | config MFD_CROS_EC_DEV |
| 254 | tristate "ChromeOS Embedded Controller multifunction device" |
| 255 | select MFD_CORE |
| 256 | depends on CROS_EC |
| 257 | default CROS_EC |
| 258 | help |
| 259 | Select this to get support for ChromeOS Embedded Controller |
| 260 | sub-devices. This driver will instantiate additional drivers such |
| 261 | as RTC, USBPD, etc. but you have to select the individual drivers. |
| 262 | |
| 263 | To compile this driver as a module, choose M here: the module will be |
| 264 | called cros-ec-dev. |
| 265 | |
| 266 | config MFD_CS40L50_CORE |
| 267 | tristate |
| 268 | select MFD_CORE |
| 269 | select FW_CS_DSP |
| 270 | select REGMAP_IRQ |
| 271 | |
| 272 | config MFD_CS40L50_I2C |
| 273 | tristate "Cirrus Logic CS40L50 (I2C)" |
| 274 | select REGMAP_I2C |
| 275 | select MFD_CS40L50_CORE |
| 276 | depends on I2C |
| 277 | help |
| 278 | Select this to support the Cirrus Logic CS40L50 Haptic |
| 279 | Driver over I2C. |
| 280 | |
| 281 | This driver can be built as a module. If built as a module it will be |
| 282 | called "cs40l50-i2c". |
| 283 | |
| 284 | config MFD_CS40L50_SPI |
| 285 | tristate "Cirrus Logic CS40L50 (SPI)" |
| 286 | select REGMAP_SPI |
| 287 | select MFD_CS40L50_CORE |
| 288 | depends on SPI |
| 289 | help |
| 290 | Select this to support the Cirrus Logic CS40L50 Haptic |
| 291 | Driver over SPI. |
| 292 | |
| 293 | This driver can be built as a module. If built as a module it will be |
| 294 | called "cs40l50-spi". |
| 295 | |
| 296 | config MFD_CS42L43 |
| 297 | tristate |
| 298 | select MFD_CORE |
| 299 | select REGMAP |
| 300 | select REGMAP_IRQ |
| 301 | |
| 302 | config MFD_CS42L43_I2C |
| 303 | tristate "Cirrus Logic CS42L43 (I2C)" |
| 304 | depends on I2C |
| 305 | select REGMAP_I2C |
| 306 | select MFD_CS42L43 |
| 307 | help |
| 308 | Select this to support the Cirrus Logic CS42L43 PC CODEC with |
| 309 | headphone and class D speaker drivers over I2C. |
| 310 | |
| 311 | config MFD_CS42L43_SDW |
| 312 | tristate "Cirrus Logic CS42L43 (SoundWire)" |
| 313 | depends on SOUNDWIRE |
| 314 | select REGMAP_SOUNDWIRE |
| 315 | select MFD_CS42L43 |
| 316 | help |
| 317 | Select this to support the Cirrus Logic CS42L43 PC CODEC with |
| 318 | headphone and class D speaker drivers over SoundWire. |
| 319 | |
| 320 | config MFD_LOCHNAGAR |
| 321 | bool "Cirrus Logic Lochnagar Audio Development Board" |
| 322 | select MFD_CORE |
| 323 | select REGMAP_I2C |
| 324 | depends on I2C=y && OF |
| 325 | help |
| 326 | Support for Cirrus Logic Lochnagar audio development board. |
| 327 | |
| 328 | config MFD_MACSMC |
| 329 | tristate "Apple Silicon System Management Controller (SMC)" |
| 330 | depends on ARCH_APPLE || COMPILE_TEST |
| 331 | depends on OF |
| 332 | depends on APPLE_RTKIT |
| 333 | select MFD_CORE |
| 334 | help |
| 335 | The System Management Controller (SMC) on Apple Silicon machines is a |
| 336 | piece of hardware that exposes various functionalities such as |
| 337 | temperature sensors, voltage/power meters, shutdown/reboot handling, |
| 338 | GPIOs and more. |
| 339 | |
| 340 | Communication happens via a shared mailbox using the RTKit protocol |
| 341 | which is also used for other co-processors. The SMC protocol then |
| 342 | allows reading and writing many different keys which implement the |
| 343 | various features. The MFD core device handles this protocol and |
| 344 | exposes it to the sub-devices. |
| 345 | |
| 346 | config MFD_MADERA |
| 347 | tristate "Cirrus Logic Madera codecs" |
| 348 | select MFD_CORE |
| 349 | select REGMAP |
| 350 | select REGMAP_IRQ |
| 351 | select MADERA_IRQ |
| 352 | select PINCTRL |
| 353 | select PINCTRL_MADERA |
| 354 | help |
| 355 | Support for the Cirrus Logic Madera platform audio codecs |
| 356 | |
| 357 | config MFD_MADERA_I2C |
| 358 | tristate "Cirrus Logic Madera codecs with I2C" |
| 359 | depends on MFD_MADERA |
| 360 | depends on I2C |
| 361 | select REGMAP_I2C |
| 362 | help |
| 363 | Support for the Cirrus Logic Madera platform audio SoC |
| 364 | core functionality controlled via I2C. |
| 365 | |
| 366 | config MFD_MADERA_SPI |
| 367 | tristate "Cirrus Logic Madera codecs with SPI" |
| 368 | depends on MFD_MADERA |
| 369 | depends on SPI_MASTER |
| 370 | select REGMAP_SPI |
| 371 | help |
| 372 | Support for the Cirrus Logic Madera platform audio SoC |
| 373 | core functionality controlled via SPI. |
| 374 | |
| 375 | config MFD_CS47L15 |
| 376 | bool "Cirrus Logic CS47L15" |
| 377 | select PINCTRL_CS47L15 |
| 378 | depends on MFD_MADERA |
| 379 | help |
| 380 | Support for Cirrus Logic CS47L15 Smart Codec |
| 381 | |
| 382 | config MFD_CS47L35 |
| 383 | bool "Cirrus Logic CS47L35" |
| 384 | select PINCTRL_CS47L35 |
| 385 | depends on MFD_MADERA |
| 386 | help |
| 387 | Support for Cirrus Logic CS47L35 Smart Codec |
| 388 | |
| 389 | config MFD_CS47L85 |
| 390 | bool "Cirrus Logic CS47L85" |
| 391 | select PINCTRL_CS47L85 |
| 392 | depends on MFD_MADERA |
| 393 | help |
| 394 | Support for Cirrus Logic CS47L85 Smart Codec |
| 395 | |
| 396 | config MFD_CS47L90 |
| 397 | bool "Cirrus Logic CS47L90/91" |
| 398 | select PINCTRL_CS47L90 |
| 399 | depends on MFD_MADERA |
| 400 | help |
| 401 | Support for Cirrus Logic CS47L90 and CS47L91 Smart Codecs |
| 402 | |
| 403 | config MFD_CS47L92 |
| 404 | bool "Cirrus Logic CS47L92/93" |
| 405 | select PINCTRL_CS47L92 |
| 406 | depends on MFD_MADERA |
| 407 | help |
| 408 | Support for Cirrus Logic CS42L92, CS47L92 and CS47L93 Smart Codecs |
| 409 | |
| 410 | config MFD_TN48M_CPLD |
| 411 | tristate "Delta Networks TN48M switch CPLD driver" |
| 412 | depends on I2C |
| 413 | depends on ARCH_MVEBU || COMPILE_TEST |
| 414 | select MFD_SIMPLE_MFD_I2C |
| 415 | help |
| 416 | Select this option to enable support for Delta Networks TN48M switch |
| 417 | CPLD. It consists of reset and GPIO drivers. CPLD provides GPIOS-s |
| 418 | for the SFP slots as well as power supply related information. |
| 419 | SFP support depends on the GPIO driver being selected. |
| 420 | |
| 421 | config PMIC_DA903X |
| 422 | bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" |
| 423 | depends on I2C=y |
| 424 | help |
| 425 | Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a |
| 426 | ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC |
| 427 | usually found on PXA processors-based platforms. This includes |
| 428 | the I2C driver and the core APIs _only_, you have to select |
| 429 | individual components like LCD backlight, voltage regulators, |
| 430 | LEDs and battery-charger under the corresponding menus. |
| 431 | |
| 432 | config PMIC_DA9052 |
| 433 | bool |
| 434 | select MFD_CORE |
| 435 | |
| 436 | config MFD_DA9052_SPI |
| 437 | bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI" |
| 438 | select REGMAP_SPI |
| 439 | select REGMAP_IRQ |
| 440 | select PMIC_DA9052 |
| 441 | depends on SPI_MASTER=y |
| 442 | help |
| 443 | Support for the Dialog Semiconductor DA9052 PMIC |
| 444 | when controlled using SPI. This driver provides common support |
| 445 | for accessing the device, additional drivers must be enabled in |
| 446 | order to use the functionality of the device. |
| 447 | |
| 448 | config MFD_DA9052_I2C |
| 449 | bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C" |
| 450 | select REGMAP_I2C |
| 451 | select REGMAP_IRQ |
| 452 | select PMIC_DA9052 |
| 453 | depends on I2C=y |
| 454 | help |
| 455 | Support for the Dialog Semiconductor DA9052 PMIC |
| 456 | when controlled using I2C. This driver provides common support |
| 457 | for accessing the device, additional drivers must be enabled in |
| 458 | order to use the functionality of the device. |
| 459 | |
| 460 | config MFD_DA9055 |
| 461 | bool "Dialog Semiconductor DA9055 PMIC Support" |
| 462 | select REGMAP_I2C |
| 463 | select REGMAP_IRQ |
| 464 | select MFD_CORE |
| 465 | depends on I2C=y |
| 466 | help |
| 467 | Say yes here for support of Dialog Semiconductor DA9055. This is |
| 468 | a Power Management IC. This driver provides common support for |
| 469 | accessing the device as well as the I2C interface to the chip itself. |
| 470 | Additional drivers must be enabled in order to use the functionality |
| 471 | of the device. |
| 472 | |
| 473 | config MFD_DA9062 |
| 474 | tristate "Dialog Semiconductor DA9062/61 PMIC Support" |
| 475 | select MFD_CORE |
| 476 | select REGMAP_I2C |
| 477 | select REGMAP_IRQ |
| 478 | depends on I2C |
| 479 | help |
| 480 | Say yes here for support for the Dialog Semiconductor DA9061 and |
| 481 | DA9062 PMICs. |
| 482 | This includes the I2C driver and core APIs. |
| 483 | Additional drivers must be enabled in order to use the functionality |
| 484 | of the device. |
| 485 | |
| 486 | config MFD_DA9063 |
| 487 | tristate "Dialog Semiconductor DA9063 PMIC Support" |
| 488 | select MFD_CORE |
| 489 | select REGMAP_I2C |
| 490 | select REGMAP_IRQ |
| 491 | depends on I2C |
| 492 | help |
| 493 | Say yes here for support for the Dialog Semiconductor DA9063 PMIC. |
| 494 | This includes the I2C driver and core APIs. |
| 495 | Additional drivers must be enabled in order to use the functionality |
| 496 | of the device. |
| 497 | |
| 498 | config MFD_DA9150 |
| 499 | tristate "Dialog Semiconductor DA9150 Charger Fuel-Gauge chip" |
| 500 | depends on I2C |
| 501 | select MFD_CORE |
| 502 | select REGMAP_I2C |
| 503 | select REGMAP_IRQ |
| 504 | help |
| 505 | This adds support for the DA9150 integrated charger and fuel-gauge |
| 506 | chip. This driver provides common support for accessing the device. |
| 507 | Additional drivers must be enabled in order to use the specific |
| 508 | features of the device. |
| 509 | |
| 510 | config MFD_DLN2 |
| 511 | tristate "Diolan DLN2 support" |
| 512 | select MFD_CORE |
| 513 | depends on USB |
| 514 | help |
| 515 | This adds support for Diolan USB-I2C/SPI/GPIO Master Adapter |
| 516 | DLN-2. Additional drivers such as I2C_DLN2, GPIO_DLN2, |
| 517 | etc. must be enabled in order to use the functionality of |
| 518 | the device. |
| 519 | |
| 520 | config MFD_ENE_KB3930 |
| 521 | tristate "ENE KB3930 Embedded Controller support" |
| 522 | depends on I2C |
| 523 | depends on MACH_MMP3_DT || COMPILE_TEST |
| 524 | select MFD_CORE |
| 525 | help |
| 526 | This adds support for the power-off functionality and access to |
| 527 | the registers that control LEDS and USB port power on ENE KB3930 |
| 528 | Embedded Controller. To use the LED functionality LEDS_ARIEL must |
| 529 | be enabled. |
| 530 | |
| 531 | config MFD_EXYNOS_LPASS |
| 532 | tristate "Samsung Exynos SoC Low Power Audio Subsystem" |
| 533 | depends on ARCH_EXYNOS || COMPILE_TEST |
| 534 | select MFD_CORE |
| 535 | select REGMAP_MMIO |
| 536 | help |
| 537 | Select this option to enable support for Samsung Exynos Low Power |
| 538 | Audio Subsystem present on some of Samsung Exynos |
| 539 | SoCs (e.g. Exynos5433). |
| 540 | Choose Y here only if you build for such Samsung SoC. |
| 541 | |
| 542 | config MFD_GATEWORKS_GSC |
| 543 | tristate "Gateworks System Controller" |
| 544 | depends on I2C && OF |
| 545 | select MFD_CORE |
| 546 | select REGMAP_I2C |
| 547 | select REGMAP_IRQ |
| 548 | help |
| 549 | Enable support for the Gateworks System Controller (GSC) found |
| 550 | on Gateworks Single Board Computers supporting system functions |
| 551 | such as push-button monitor, multiple ADC's for voltage and |
| 552 | temperature monitoring, fan controller and watchdog monitor. |
| 553 | This driver provides common support for accessing the device. |
| 554 | Additional drivers must be enabled in order to use the |
| 555 | functionality of the device. |
| 556 | |
| 557 | config MFD_MC13XXX |
| 558 | tristate |
| 559 | depends on SPI_MASTER || I2C |
| 560 | select MFD_CORE |
| 561 | select REGMAP_IRQ |
| 562 | help |
| 563 | Enable support for the Freescale MC13783 and MC13892 PMICs. |
| 564 | This driver provides common support for accessing the device, |
| 565 | additional drivers must be enabled in order to use the |
| 566 | functionality of the device. |
| 567 | |
| 568 | config MFD_MC13XXX_SPI |
| 569 | tristate "Freescale MC13783 and MC13892 SPI interface" |
| 570 | depends on SPI_MASTER |
| 571 | select REGMAP_SPI |
| 572 | select MFD_MC13XXX |
| 573 | help |
| 574 | Select this if your MC13xxx is connected via an SPI bus. |
| 575 | |
| 576 | config MFD_MC13XXX_I2C |
| 577 | tristate "Freescale MC13892 I2C interface" |
| 578 | depends on I2C |
| 579 | select REGMAP_I2C |
| 580 | select MFD_MC13XXX |
| 581 | help |
| 582 | Select this if your MC13xxx is connected via an I2C bus. |
| 583 | |
| 584 | config MFD_MP2629 |
| 585 | tristate "Monolithic Power Systems MP2629 ADC and Battery charger" |
| 586 | depends on I2C |
| 587 | select REGMAP_I2C |
| 588 | select MFD_CORE |
| 589 | help |
| 590 | Select this option to enable support for Monolithic Power Systems |
| 591 | battery charger. This provides ADC, thermal and battery charger power |
| 592 | management functions. |
| 593 | |
| 594 | config MFD_MXS_LRADC |
| 595 | tristate "Freescale i.MX23/i.MX28 LRADC" |
| 596 | depends on ARCH_MXS || COMPILE_TEST |
| 597 | select MFD_CORE |
| 598 | select STMP_DEVICE |
| 599 | help |
| 600 | Say yes here to build support for the Low Resolution |
| 601 | Analog-to-Digital Converter (LRADC) found on the i.MX23 and i.MX28 |
| 602 | processors. This driver provides common support for accessing the |
| 603 | device, additional drivers must be enabled in order to use the |
| 604 | functionality of the device: |
| 605 | mxs-lradc-adc for ADC readings |
| 606 | mxs-lradc-ts for touchscreen support |
| 607 | |
| 608 | This driver can also be built as a module. If so, the module will be |
| 609 | called mxs-lradc. |
| 610 | |
| 611 | config MFD_MX25_TSADC |
| 612 | tristate "Freescale i.MX25 integrated Touchscreen and ADC unit" |
| 613 | select REGMAP_MMIO |
| 614 | depends on (SOC_IMX25 && OF) || COMPILE_TEST |
| 615 | help |
| 616 | Enable support for the integrated Touchscreen and ADC unit of the |
| 617 | i.MX25 processors. They consist of a conversion queue for general |
| 618 | purpose ADC and a queue for Touchscreens. |
| 619 | |
| 620 | config MFD_PF1550 |
| 621 | tristate "NXP PF1550 PMIC Support" |
| 622 | depends on I2C=y && OF |
| 623 | select MFD_CORE |
| 624 | select REGMAP_I2C |
| 625 | select REGMAP_IRQ |
| 626 | help |
| 627 | Say yes here to add support for NXP PF1550. This is a companion Power |
| 628 | Management IC with regulators, onkey, and charger control on chip. |
| 629 | This driver provides common support for accessing the device; |
| 630 | additional drivers must be enabled in order to use the functionality |
| 631 | of the device. |
| 632 | |
| 633 | This driver can also be built as a module and if so will be called |
| 634 | pf1550. |
| 635 | |
| 636 | config MFD_HI6421_PMIC |
| 637 | tristate "HiSilicon Hi6421 PMU/Codec IC" |
| 638 | depends on OF |
| 639 | select MFD_CORE |
| 640 | select REGMAP_MMIO |
| 641 | help |
| 642 | Add support for HiSilicon Hi6421 PMIC. Hi6421 includes multi- |
| 643 | functions, such as regulators, RTC, codec, Coulomb counter, etc. |
| 644 | This driver includes core APIs _only_. You have to select |
| 645 | individual components like voltage regulators under corresponding |
| 646 | menus in order to enable them. |
| 647 | We communicate with the Hi6421 via memory-mapped I/O. |
| 648 | |
| 649 | config MFD_HI6421_SPMI |
| 650 | tristate "HiSilicon Hi6421v600 SPMI PMU/Codec IC" |
| 651 | depends on OF |
| 652 | depends on SPMI |
| 653 | select MFD_CORE |
| 654 | select REGMAP_SPMI |
| 655 | help |
| 656 | Add support for HiSilicon Hi6421v600 SPMI PMIC. Hi6421 includes |
| 657 | multi-functions, such as regulators, RTC, codec, Coulomb counter, |
| 658 | etc. |
| 659 | |
| 660 | This driver includes core APIs _only_. You have to select |
| 661 | individual components like voltage regulators under corresponding |
| 662 | menus in order to enable them. |
| 663 | We communicate with the Hi6421v600 via a SPMI bus. |
| 664 | |
| 665 | config MFD_HI655X_PMIC |
| 666 | tristate "HiSilicon Hi655X series PMU/Codec IC" |
| 667 | depends on ARCH_HISI || COMPILE_TEST |
| 668 | depends on OF |
| 669 | select MFD_CORE |
| 670 | select REGMAP_MMIO |
| 671 | select REGMAP_IRQ |
| 672 | help |
| 673 | Select this option to enable Hisilicon hi655x series pmic driver. |
| 674 | |
| 675 | config MFD_INTEL_QUARK_I2C_GPIO |
| 676 | tristate "Intel Quark MFD I2C GPIO" |
| 677 | depends on PCI |
| 678 | depends on X86 |
| 679 | depends on COMMON_CLK |
| 680 | select MFD_CORE |
| 681 | help |
| 682 | This MFD provides support for I2C and GPIO that exist only |
| 683 | in a single PCI device. It splits the 2 IO devices to |
| 684 | their respective IO driver. |
| 685 | The GPIO exports a total amount of 8 interrupt-capable GPIOs. |
| 686 | |
| 687 | config LPC_ICH |
| 688 | tristate "Intel ICH LPC" |
| 689 | depends on PCI |
| 690 | select MFD_CORE |
| 691 | select P2SB if X86 |
| 692 | help |
| 693 | The LPC bridge function of the Intel ICH provides support for |
| 694 | many functional units. This driver provides needed support for |
| 695 | other drivers to control these functions, currently GPIO and |
| 696 | watchdog. |
| 697 | |
| 698 | config LPC_SCH |
| 699 | tristate "Intel SCH LPC" |
| 700 | depends on PCI |
| 701 | select MFD_CORE |
| 702 | help |
| 703 | LPC bridge function of the Intel SCH provides support for |
| 704 | System Management Bus and General Purpose I/O. |
| 705 | |
| 706 | config INTEL_SOC_PMIC |
| 707 | bool "Support for Crystal Cove PMIC" |
| 708 | depends on HAS_IOMEM && I2C=y && GPIOLIB && COMMON_CLK |
| 709 | depends on (X86 && ACPI) || COMPILE_TEST |
| 710 | depends on I2C_DESIGNWARE_PLATFORM=y || COMPILE_TEST |
| 711 | select MFD_CORE |
| 712 | select REGMAP_I2C |
| 713 | select REGMAP_IRQ |
| 714 | help |
| 715 | Select this option to enable support for Crystal Cove PMIC |
| 716 | on some Intel SoC systems. The PMIC provides ADC, GPIO, |
| 717 | thermal, charger and related power management functions |
| 718 | on these systems. |
| 719 | |
| 720 | This option is a bool as it provides an ACPI OpRegion which must be |
| 721 | available before any devices using it are probed. This option also |
| 722 | causes the designware-i2c driver to be builtin for the same reason. |
| 723 | |
| 724 | config INTEL_SOC_PMIC_BXTWC |
| 725 | tristate "Support for Intel Broxton Whiskey Cove PMIC" |
| 726 | depends on MFD_INTEL_PMC_BXT |
| 727 | select MFD_CORE |
| 728 | select REGMAP_IRQ |
| 729 | help |
| 730 | Select this option to enable support for Whiskey Cove PMIC |
| 731 | on Intel Broxton systems. The PMIC provides ADC, GPIO, |
| 732 | thermal, charger and related power management functions |
| 733 | on these systems. |
| 734 | |
| 735 | config INTEL_SOC_PMIC_CHTWC |
| 736 | bool "Support for Intel Cherry Trail Whiskey Cove PMIC" |
| 737 | depends on ACPI && HAS_IOMEM && I2C=y && COMMON_CLK |
| 738 | depends on X86 || COMPILE_TEST |
| 739 | depends on I2C_DESIGNWARE_PLATFORM=y |
| 740 | select MFD_CORE |
| 741 | select REGMAP_I2C |
| 742 | select REGMAP_IRQ |
| 743 | help |
| 744 | Select this option to enable support for the Intel Cherry Trail |
| 745 | Whiskey Cove PMIC found on some Intel Cherry Trail systems. |
| 746 | |
| 747 | This option is a bool as it provides an ACPI OpRegion which must be |
| 748 | available before any devices using it are probed. This option also |
| 749 | causes the designware-i2c driver to be builtin for the same reason. |
| 750 | |
| 751 | config INTEL_SOC_PMIC_CHTDC_TI |
| 752 | tristate "Support for Intel Cherry Trail Dollar Cove TI PMIC" |
| 753 | depends on GPIOLIB |
| 754 | depends on I2C=y && I2C_DESIGNWARE_PLATFORM=y |
| 755 | depends on ACPI |
| 756 | depends on X86 |
| 757 | select MFD_CORE |
| 758 | select REGMAP_I2C |
| 759 | select REGMAP_IRQ |
| 760 | help |
| 761 | Select this option for supporting Dollar Cove (TI version) PMIC |
| 762 | device that is found on some Intel Cherry Trail systems. |
| 763 | |
| 764 | This option is a bool as it provides an ACPI OpRegion which must be |
| 765 | available before any devices using it are probed. This option also |
| 766 | needs the designware-i2c driver to be builtin for the same reason. |
| 767 | |
| 768 | config INTEL_SOC_PMIC_MRFLD |
| 769 | tristate "Support for Intel Merrifield Basin Cove PMIC" |
| 770 | depends on GPIOLIB |
| 771 | depends on ACPI |
| 772 | depends on INTEL_SCU |
| 773 | select MFD_CORE |
| 774 | select REGMAP_IRQ |
| 775 | help |
| 776 | Select this option for supporting Basin Cove PMIC device |
| 777 | that is found on Intel Merrifield systems. |
| 778 | |
| 779 | config MFD_INTEL_LPSS |
| 780 | tristate |
| 781 | select COMMON_CLK |
| 782 | select MFD_CORE |
| 783 | |
| 784 | config MFD_INTEL_LPSS_ACPI |
| 785 | tristate "Intel Low Power Subsystem support in ACPI mode" |
| 786 | select MFD_INTEL_LPSS |
| 787 | depends on X86 && ACPI |
| 788 | help |
| 789 | This driver supports Intel Low Power Subsystem (LPSS) devices such as |
| 790 | I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake |
| 791 | PCH) in ACPI mode. |
| 792 | |
| 793 | config MFD_INTEL_LPSS_PCI |
| 794 | tristate "Intel Low Power Subsystem support in PCI mode" |
| 795 | select MFD_INTEL_LPSS |
| 796 | depends on X86 && PCI |
| 797 | help |
| 798 | This driver supports Intel Low Power Subsystem (LPSS) devices such as |
| 799 | I2C, SPI and HS-UART starting from Intel Sunrisepoint (Intel Skylake |
| 800 | PCH) in PCI mode. |
| 801 | |
| 802 | config MFD_INTEL_PMC_BXT |
| 803 | tristate "Intel PMC Driver for Broxton" |
| 804 | depends on X86 |
| 805 | depends on X86_PLATFORM_DEVICES |
| 806 | depends on ACPI |
| 807 | select INTEL_SCU_IPC |
| 808 | select MFD_CORE |
| 809 | help |
| 810 | This driver provides support for the PMC (Power Management |
| 811 | Controller) on Intel Broxton and Apollo Lake. The PMC is a |
| 812 | multi-function device that exposes IPC, General Control |
| 813 | Register and P-unit access. In addition this creates devices |
| 814 | for iTCO watchdog and telemetry that are part of the PMC. |
| 815 | |
| 816 | config MFD_IPAQ_MICRO |
| 817 | bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support" |
| 818 | depends on SA1100_H3600 |
| 819 | select MFD_CORE |
| 820 | help |
| 821 | Select this to get support for the Microcontroller found in |
| 822 | the Compaq iPAQ handheld computers. This is an Atmel |
| 823 | AT90LS8535 microcontroller flashed with a special iPAQ |
| 824 | firmware using the custom protocol implemented in this driver. |
| 825 | |
| 826 | config MFD_IQS62X |
| 827 | tristate "Azoteq IQS620A/621/622/624/625 core support" |
| 828 | depends on I2C |
| 829 | select MFD_CORE |
| 830 | select REGMAP_I2C |
| 831 | help |
| 832 | Say Y here if you want to build core support for the Azoteq IQS620A, |
| 833 | IQS621, IQS622, IQS624 and IQS625 multi-function sensors. Additional |
| 834 | options must be selected to enable device-specific functions. |
| 835 | |
| 836 | To compile this driver as a module, choose M here: the module will |
| 837 | be called iqs62x. |
| 838 | |
| 839 | config MFD_JANZ_CMODIO |
| 840 | tristate "Janz CMOD-IO PCI MODULbus Carrier Board" |
| 841 | select MFD_CORE |
| 842 | depends on PCI |
| 843 | help |
| 844 | This is the core driver for the Janz CMOD-IO PCI MODULbus |
| 845 | carrier board. This device is a PCI to MODULbus bridge which may |
| 846 | host many different types of MODULbus daughterboards, including |
| 847 | CAN and GPIO controllers. |
| 848 | |
| 849 | config MFD_KEMPLD |
| 850 | tristate "Kontron module PLD device" |
| 851 | select MFD_CORE |
| 852 | help |
| 853 | This is the core driver for the PLD (Programmable Logic Device) found |
| 854 | on some Kontron ETX and nearly all COMexpress (ETXexpress) modules as |
| 855 | well as on some other Kontron products. The PLD device may provide |
| 856 | functions like watchdog, GPIO, UART and I2C bus. |
| 857 | |
| 858 | This driver can also be built as a module. If so, the module |
| 859 | will be called kempld-core. |
| 860 | |
| 861 | config MFD_88PM800 |
| 862 | tristate "Marvell 88PM800" |
| 863 | depends on I2C |
| 864 | select REGMAP_I2C |
| 865 | select REGMAP_IRQ |
| 866 | select MFD_CORE |
| 867 | help |
| 868 | This supports for Marvell 88PM800 Power Management IC. |
| 869 | This includes the I2C driver and the core APIs _only_, you have to |
| 870 | select individual components like voltage regulators, RTC and |
| 871 | battery-charger under the corresponding menus. |
| 872 | |
| 873 | config MFD_88PM805 |
| 874 | tristate "Marvell 88PM805" |
| 875 | depends on I2C |
| 876 | select REGMAP_I2C |
| 877 | select REGMAP_IRQ |
| 878 | select MFD_CORE |
| 879 | help |
| 880 | This supports for Marvell 88PM805 Power Management IC. This includes |
| 881 | the I2C driver and the core APIs _only_, you have to select individual |
| 882 | components like codec device, headset/Mic device under the |
| 883 | corresponding menus. |
| 884 | |
| 885 | config MFD_88PM860X |
| 886 | bool "Marvell 88PM8606/88PM8607" |
| 887 | depends on I2C=y |
| 888 | select REGMAP_I2C |
| 889 | select MFD_CORE |
| 890 | help |
| 891 | This supports for Marvell 88PM8606/88PM8607 Power Management IC. |
| 892 | This includes the I2C driver and the core APIs _only_, you have to |
| 893 | select individual components like voltage regulators, RTC and |
| 894 | battery-charger under the corresponding menus. |
| 895 | |
| 896 | config MFD_88PM886_PMIC |
| 897 | bool "Marvell 88PM886 PMIC" |
| 898 | depends on I2C=y |
| 899 | depends on OF |
| 900 | select REGMAP_I2C |
| 901 | select REGMAP_IRQ |
| 902 | select MFD_CORE |
| 903 | help |
| 904 | This enables support for Marvell 88PM886 Power Management IC. |
| 905 | This includes the I2C driver and the core APIs _only_, you have to |
| 906 | select individual components like onkey under the corresponding menus. |
| 907 | |
| 908 | config MFD_MAX5970 |
| 909 | tristate "Maxim 5970/5978 power switch and monitor" |
| 910 | depends on I2C |
| 911 | select MFD_SIMPLE_MFD_I2C |
| 912 | help |
| 913 | This driver controls a Maxim 5970/5978 switch via I2C bus. |
| 914 | The MAX5970/5978 is a smart switch with no output regulation, but |
| 915 | fault protection and voltage and current monitoring capabilities. |
| 916 | Also it supports upto 4 indication leds. |
| 917 | |
| 918 | config MFD_MAX14577 |
| 919 | tristate "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support" |
| 920 | depends on I2C |
| 921 | select MFD_CORE |
| 922 | select REGMAP_I2C |
| 923 | select REGMAP_IRQ |
| 924 | select IRQ_DOMAIN |
| 925 | help |
| 926 | Say yes here to add support for Maxim Semiconductor MAX14577 and |
| 927 | MAX77836 Micro-USB ICs with battery charger. |
| 928 | This driver provides common support for accessing the device; |
| 929 | additional drivers must be enabled in order to use the functionality |
| 930 | of the device. |
| 931 | |
| 932 | config MFD_MAX77541 |
| 933 | tristate "Analog Devices MAX77541/77540 PMIC Support" |
| 934 | depends on I2C=y |
| 935 | select MFD_CORE |
| 936 | select REGMAP_I2C |
| 937 | select REGMAP_IRQ |
| 938 | help |
| 939 | Say yes here to add support for Analog Devices MAX77541 and |
| 940 | MAX77540 Power Management ICs. This driver provides |
| 941 | common support for accessing the device; additional drivers |
| 942 | must be enabled in order to use the functionality of the device. |
| 943 | There are regulators and adc. |
| 944 | |
| 945 | config MFD_MAX77620 |
| 946 | tristate "Maxim Semiconductor MAX77620 and MAX20024 PMIC Support" |
| 947 | depends on I2C=y |
| 948 | depends on OF |
| 949 | select MFD_CORE |
| 950 | select REGMAP_I2C |
| 951 | select REGMAP_IRQ |
| 952 | select IRQ_DOMAIN |
| 953 | help |
| 954 | Say yes here to add support for Maxim Semiconductor MAX77620 and |
| 955 | MAX20024 which are Power Management IC with General purpose pins, |
| 956 | RTC, regulators, clock generator, watchdog etc. This driver |
| 957 | provides common support for accessing the device; additional drivers |
| 958 | must be enabled in order to use the functionality of the device. |
| 959 | |
| 960 | config MFD_MAX77650 |
| 961 | tristate "Maxim MAX77650/77651 PMIC Support" |
| 962 | depends on I2C |
| 963 | depends on OF |
| 964 | select MFD_CORE |
| 965 | select REGMAP_I2C |
| 966 | select REGMAP_IRQ |
| 967 | help |
| 968 | Say Y here to add support for Maxim Semiconductor MAX77650 and |
| 969 | MAX77651 Power Management ICs. This is the core multifunction |
| 970 | driver for interacting with the device. The module name is |
| 971 | 'max77650'. Additional drivers can be enabled in order to use |
| 972 | the following functionalities of the device: GPIO, regulator, |
| 973 | charger, LED, onkey. |
| 974 | |
| 975 | config MFD_MAX77686 |
| 976 | tristate "Maxim Semiconductor MAX77686/802 PMIC Support" |
| 977 | depends on I2C |
| 978 | depends on OF |
| 979 | select MFD_CORE |
| 980 | select REGMAP_I2C |
| 981 | select REGMAP_IRQ |
| 982 | select IRQ_DOMAIN |
| 983 | help |
| 984 | Say yes here to add support for Maxim Semiconductor MAX77686 and |
| 985 | MAX77802 which are Power Management IC with an RTC on chip. |
| 986 | This driver provides common support for accessing the device; |
| 987 | additional drivers must be enabled in order to use the functionality |
| 988 | of the device. |
| 989 | |
| 990 | config MFD_MAX77693 |
| 991 | tristate "Maxim Semiconductor MAX77693 PMIC Support" |
| 992 | depends on I2C |
| 993 | select MFD_CORE |
| 994 | select REGMAP_I2C |
| 995 | select REGMAP_IRQ |
| 996 | help |
| 997 | Say yes here to add support for Maxim Semiconductor MAX77693. |
| 998 | This is a companion Power Management IC with Flash, Haptic, Charger, |
| 999 | and MUIC(Micro USB Interface Controller) controls on chip. |
| 1000 | This driver provides common support for accessing the device; |
| 1001 | additional drivers must be enabled in order to use the functionality |
| 1002 | of the device. |
| 1003 | |
| 1004 | config MFD_MAX77705 |
| 1005 | tristate "Maxim MAX77705 PMIC Support" |
| 1006 | depends on I2C |
| 1007 | select MFD_CORE |
| 1008 | select MFD_SIMPLE_MFD_I2C |
| 1009 | help |
| 1010 | Say yes here to add support for Maxim Integrated MAX77705 PMIC. |
| 1011 | This is a Power Management IC with Charger, safe LDOs, Flash, Haptic |
| 1012 | and MUIC controls on chip. |
| 1013 | This driver provides common support for accessing the device; |
| 1014 | additional drivers must be enabled in order to use the functionality |
| 1015 | of the device. |
| 1016 | |
| 1017 | config MFD_MAX77714 |
| 1018 | tristate "Maxim Semiconductor MAX77714 PMIC Support" |
| 1019 | depends on I2C |
| 1020 | depends on OF |
| 1021 | select MFD_CORE |
| 1022 | select REGMAP_I2C |
| 1023 | help |
| 1024 | Say yes here to add support for Maxim Semiconductor MAX77714. |
| 1025 | This is a Power Management IC with 4 buck regulators, 9 |
| 1026 | low-dropout regulators, 8 GPIOs, RTC, watchdog etc. This driver |
| 1027 | provides common support for accessing the device; additional |
| 1028 | drivers must be enabled in order to use each functionality of the |
| 1029 | device. |
| 1030 | |
| 1031 | config MFD_MAX77759 |
| 1032 | tristate "Maxim Integrated MAX77759 PMIC" |
| 1033 | depends on I2C |
| 1034 | depends on OF |
| 1035 | select IRQ_DOMAIN |
| 1036 | select MFD_CORE |
| 1037 | select REGMAP_I2C |
| 1038 | select REGMAP_IRQ |
| 1039 | help |
| 1040 | Say yes here to add support for Maxim Integrated MAX77759. |
| 1041 | This is a companion Power Management IC for USB Type-C applications |
| 1042 | with Battery Charger, Fuel Gauge, temperature sensors, USB Type-C |
| 1043 | Port Controller (TCPC), NVMEM, and additional GPIO interfaces. |
| 1044 | This driver provides common support for accessing the device; |
| 1045 | additional drivers must be enabled in order to use the functionality |
| 1046 | of the device. |
| 1047 | |
| 1048 | To compile this driver as a module, choose M here: the module will be |
| 1049 | called max77759. |
| 1050 | |
| 1051 | config MFD_MAX77843 |
| 1052 | bool "Maxim Semiconductor MAX77843 PMIC Support" |
| 1053 | depends on I2C=y |
| 1054 | select MFD_CORE |
| 1055 | select REGMAP_I2C |
| 1056 | select REGMAP_IRQ |
| 1057 | help |
| 1058 | Say yes here to add support for Maxim Semiconductor MAX77843. |
| 1059 | This is companion Power Management IC with LEDs, Haptic, Charger, |
| 1060 | Fuel Gauge, MUIC(Micro USB Interface Controller) controls on chip. |
| 1061 | This driver provides common support for accessing the device; |
| 1062 | additional drivers must be enabled in order to use the functionality |
| 1063 | of the device. |
| 1064 | |
| 1065 | config MFD_MAX8907 |
| 1066 | tristate "Maxim Semiconductor MAX8907 PMIC Support" |
| 1067 | select MFD_CORE |
| 1068 | depends on I2C |
| 1069 | select REGMAP_I2C |
| 1070 | select REGMAP_IRQ |
| 1071 | help |
| 1072 | Say yes here to add support for Maxim Semiconductor MAX8907. This is |
| 1073 | a Power Management IC. This driver provides common support for |
| 1074 | accessing the device; additional drivers must be enabled in order |
| 1075 | to use the functionality of the device. |
| 1076 | |
| 1077 | config MFD_MAX8925 |
| 1078 | bool "Maxim Semiconductor MAX8925 PMIC Support" |
| 1079 | depends on I2C=y |
| 1080 | select MFD_CORE |
| 1081 | help |
| 1082 | Say yes here to add support for Maxim Semiconductor MAX8925. This is |
| 1083 | a Power Management IC. This driver provides common support for |
| 1084 | accessing the device, additional drivers must be enabled in order |
| 1085 | to use the functionality of the device. |
| 1086 | |
| 1087 | config MFD_MAX8997 |
| 1088 | bool "Maxim Semiconductor MAX8997/8966 PMIC Support" |
| 1089 | depends on I2C=y |
| 1090 | select MFD_CORE |
| 1091 | select IRQ_DOMAIN |
| 1092 | help |
| 1093 | Say yes here to add support for Maxim Semiconductor MAX8997/8966. |
| 1094 | This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic, |
| 1095 | MUIC controls on chip. |
| 1096 | This driver provides common support for accessing the device; |
| 1097 | additional drivers must be enabled in order to use the functionality |
| 1098 | of the device. |
| 1099 | |
| 1100 | config MFD_MAX8998 |
| 1101 | bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support" |
| 1102 | depends on I2C=y |
| 1103 | select MFD_CORE |
| 1104 | select IRQ_DOMAIN |
| 1105 | help |
| 1106 | Say yes here to add support for Maxim Semiconductor MAX8998 and |
| 1107 | National Semiconductor LP3974. This is a Power Management IC. |
| 1108 | This driver provides common support for accessing the device, |
| 1109 | additional drivers must be enabled in order to use the functionality |
| 1110 | of the device. |
| 1111 | |
| 1112 | config MFD_MT6360 |
| 1113 | tristate "Mediatek MT6360 SubPMIC" |
| 1114 | select MFD_CORE |
| 1115 | select REGMAP_I2C |
| 1116 | select REGMAP_IRQ |
| 1117 | select CRC8 |
| 1118 | depends on I2C |
| 1119 | help |
| 1120 | Say Y here to enable MT6360 PMU/PMIC/LDO functional support. |
| 1121 | PMU part includes Charger, Flashlight, RGB LED |
| 1122 | PMIC part includes 2-channel BUCKs and 2-channel LDOs |
| 1123 | LDO part includes 4-channel LDOs |
| 1124 | |
| 1125 | config MFD_MT6370 |
| 1126 | tristate "MediaTek MT6370 SubPMIC" |
| 1127 | select MFD_CORE |
| 1128 | select REGMAP_I2C |
| 1129 | select REGMAP_IRQ |
| 1130 | depends on I2C |
| 1131 | help |
| 1132 | Say Y here to enable MT6370 SubPMIC functional support. |
| 1133 | It consists of a single cell battery charger with ADC monitoring, RGB |
| 1134 | LEDs, dual channel flashlight, WLED backlight driver, display bias |
| 1135 | voltage supply, one general purpose LDO, and the USB Type-C & PD |
| 1136 | controller complies with the latest USB Type-C and PD standards. |
| 1137 | |
| 1138 | This driver can also be built as a module. If so, the module |
| 1139 | will be called "mt6370". |
| 1140 | |
| 1141 | config MFD_MT6397 |
| 1142 | tristate "MediaTek MT6397 PMIC Support" |
| 1143 | select MFD_CORE |
| 1144 | select IRQ_DOMAIN |
| 1145 | help |
| 1146 | Say yes here to add support for MediaTek MT6397 PMIC. This is |
| 1147 | a Power Management IC. This driver provides common support for |
| 1148 | accessing the device; additional drivers must be enabled in order |
| 1149 | to use the functionality of the device. |
| 1150 | |
| 1151 | config MFD_MENF21BMC |
| 1152 | tristate "MEN 14F021P00 Board Management Controller Support" |
| 1153 | depends on I2C |
| 1154 | select MFD_CORE |
| 1155 | help |
| 1156 | Say yes here to add support for the MEN 14F021P00 BMC |
| 1157 | which is a Board Management Controller connected to the I2C bus. |
| 1158 | The device supports multiple sub-devices like LED, HWMON and WDT. |
| 1159 | This driver provides common support for accessing the devices; |
| 1160 | additional drivers must be enabled in order to use the |
| 1161 | functionality of the BMC device. |
| 1162 | |
| 1163 | This driver can also be built as a module. If so the module |
| 1164 | will be called menf21bmc. |
| 1165 | |
| 1166 | config MFD_NCT6694 |
| 1167 | tristate "Nuvoton NCT6694 support" |
| 1168 | select MFD_CORE |
| 1169 | depends on USB |
| 1170 | help |
| 1171 | This enables support for the Nuvoton USB device NCT6694, which shares |
| 1172 | peripherals. |
| 1173 | The Nuvoton NCT6694 is a peripheral expander with 16 GPIO chips, |
| 1174 | 6 I2C controllers, 2 CANfd controllers, 2 Watchdog timers, ADC, |
| 1175 | PWM, and RTC. |
| 1176 | This driver provides core APIs to access the NCT6694 hardware |
| 1177 | monitoring and control features. |
| 1178 | Additional drivers must be enabled to utilize the specific |
| 1179 | functionalities of the device. |
| 1180 | |
| 1181 | config MFD_OCELOT |
| 1182 | tristate "Microsemi Ocelot External Control Support" |
| 1183 | depends on SPI_MASTER |
| 1184 | select MFD_CORE |
| 1185 | select REGMAP_SPI |
| 1186 | help |
| 1187 | Ocelot is a family of networking chips that support multiple ethernet |
| 1188 | and fibre interfaces. In addition to networking, they contain several |
| 1189 | other functions, including pinctrl, MDIO, and communication with |
| 1190 | external chips. While some chips have an internal processor capable of |
| 1191 | running an OS, others don't. All chips can be controlled externally |
| 1192 | through different interfaces, including SPI, I2C, and PCIe. |
| 1193 | |
| 1194 | Say yes here to add support for Ocelot chips (VSC7511, VSC7512, |
| 1195 | VSC7513, VSC7514) controlled externally. |
| 1196 | |
| 1197 | To compile this driver as a module, choose M here: the module will be |
| 1198 | called ocelot-soc. |
| 1199 | |
| 1200 | If unsure, say N. |
| 1201 | |
| 1202 | config MFD_CPCAP |
| 1203 | tristate "Support for Motorola CPCAP" |
| 1204 | depends on SPI |
| 1205 | depends on OF |
| 1206 | select MFD_CORE |
| 1207 | select REGMAP_SPI |
| 1208 | select REGMAP_IRQ |
| 1209 | help |
| 1210 | Say yes here if you want to include driver for CPCAP. |
| 1211 | It is used on many Motorola phones and tablets as a PMIC. |
| 1212 | At least Motorola Droid 4 is known to use CPCAP. |
| 1213 | |
| 1214 | config MFD_VIPERBOARD |
| 1215 | tristate "Nano River Technologies Viperboard" |
| 1216 | select MFD_CORE |
| 1217 | depends on USB |
| 1218 | default n |
| 1219 | help |
| 1220 | Say yes here if you want support for Nano River Technologies |
| 1221 | Viperboard. |
| 1222 | There are mfd cell drivers available for i2c master, adc and |
| 1223 | both gpios found on the board. The spi part does not yet |
| 1224 | have a driver. |
| 1225 | You need to select the mfd cell drivers separately. |
| 1226 | The drivers do not support all features the board exposes. |
| 1227 | |
| 1228 | config MFD_NTXEC |
| 1229 | tristate "Netronix embedded controller (EC)" |
| 1230 | depends on OF |
| 1231 | depends on I2C |
| 1232 | select REGMAP_I2C |
| 1233 | select MFD_CORE |
| 1234 | help |
| 1235 | Say yes here if you want to support the embedded controller found in |
| 1236 | certain e-book readers designed by the original design manufacturer |
| 1237 | Netronix. |
| 1238 | |
| 1239 | config MFD_RETU |
| 1240 | tristate "Nokia Retu and Tahvo multi-function device" |
| 1241 | select MFD_CORE |
| 1242 | depends on I2C |
| 1243 | select REGMAP_IRQ |
| 1244 | help |
| 1245 | Retu and Tahvo are a multi-function devices found on Nokia |
| 1246 | Internet Tablets (770, N800 and N810). |
| 1247 | |
| 1248 | config MFD_PM8XXX |
| 1249 | tristate "Qualcomm PM8xxx PMIC chips driver" |
| 1250 | depends on ARM || HEXAGON || COMPILE_TEST |
| 1251 | select IRQ_DOMAIN_HIERARCHY |
| 1252 | select MFD_CORE |
| 1253 | select REGMAP |
| 1254 | help |
| 1255 | If you say yes to this option, support will be included for the |
| 1256 | built-in PM8xxx PMIC chips. |
| 1257 | |
| 1258 | This is required if your board has a PM8xxx and uses its features, |
| 1259 | such as: MPPs, GPIOs, regulators, interrupts, and PWM. |
| 1260 | |
| 1261 | Say M here if you want to include support for PM8xxx chips as a |
| 1262 | module. This will build a module called "pm8xxx-core". |
| 1263 | |
| 1264 | config MFD_QCOM_RPM |
| 1265 | tristate "Qualcomm Resource Power Manager (RPM)" |
| 1266 | depends on ARCH_QCOM && OF |
| 1267 | help |
| 1268 | If you say yes to this option, support will be included for the |
| 1269 | Resource Power Manager system found in the Qualcomm 8660, 8960 and |
| 1270 | 8064 based devices. |
| 1271 | |
| 1272 | This is required to access many regulators, clocks and bus |
| 1273 | frequencies controlled by the RPM on these devices. |
| 1274 | |
| 1275 | Say M here if you want to include support for the Qualcomm RPM as a |
| 1276 | module. This will build a module called "qcom_rpm". |
| 1277 | |
| 1278 | config MFD_SPACEMIT_P1 |
| 1279 | tristate "SpacemiT P1 PMIC" |
| 1280 | depends on ARCH_SPACEMIT || COMPILE_TEST |
| 1281 | depends on I2C |
| 1282 | select MFD_SIMPLE_MFD_I2C |
| 1283 | default m if ARCH_SPACEMIT |
| 1284 | help |
| 1285 | This option supports the I2C-based SpacemiT P1 PMIC, which |
| 1286 | contains regulators, a power switch, GPIOs, an RTC, and more. |
| 1287 | This option is selected when any of the supported sub-devices |
| 1288 | is configured. The basic functionality is implemented by the |
| 1289 | simple MFD I2C driver. |
| 1290 | |
| 1291 | config MFD_SPMI_PMIC |
| 1292 | tristate "Qualcomm SPMI PMICs" |
| 1293 | depends on ARCH_QCOM || COMPILE_TEST |
| 1294 | depends on OF |
| 1295 | depends on SPMI |
| 1296 | select REGMAP_SPMI |
| 1297 | help |
| 1298 | This enables support for the Qualcomm SPMI PMICs. |
| 1299 | These PMICs are currently used with the Snapdragon 800 series of |
| 1300 | SoCs. Note, that this will only be useful paired with descriptions |
| 1301 | of the independent functions as children nodes in the device tree. |
| 1302 | |
| 1303 | Say M here if you want to include support for the SPMI PMIC |
| 1304 | series as a module. The module will be called "qcom-spmi-pmic". |
| 1305 | |
| 1306 | config MFD_SY7636A |
| 1307 | tristate "Silergy SY7636A voltage regulator" |
| 1308 | depends on I2C |
| 1309 | select MFD_SIMPLE_MFD_I2C |
| 1310 | help |
| 1311 | Enable support for Silergy SY7636A voltage regulator. |
| 1312 | |
| 1313 | To enable support for building sub-devices as modules, |
| 1314 | choose M here. |
| 1315 | |
| 1316 | config MFD_RDC321X |
| 1317 | tristate "RDC R-321x southbridge" |
| 1318 | select MFD_CORE |
| 1319 | depends on PCI |
| 1320 | help |
| 1321 | Say yes here if you want to have support for the RDC R-321x SoC |
| 1322 | southbridge which provides access to GPIOs and Watchdog using the |
| 1323 | southbridge PCI device configuration space. |
| 1324 | |
| 1325 | config MFD_RT4831 |
| 1326 | tristate "Richtek RT4831 four channel WLED and Display Bias Voltage" |
| 1327 | depends on I2C |
| 1328 | select MFD_CORE |
| 1329 | select REGMAP_I2C |
| 1330 | help |
| 1331 | This enables support for the Richtek RT4831 that includes 4 channel |
| 1332 | WLED driving and Display Bias Voltage. It's commonly used to provide |
| 1333 | power to the LCD display and LCD backlight. |
| 1334 | |
| 1335 | config MFD_RT5033 |
| 1336 | tristate "Richtek RT5033 Power Management IC" |
| 1337 | depends on I2C |
| 1338 | select MFD_CORE |
| 1339 | select REGMAP_I2C |
| 1340 | select REGMAP_IRQ |
| 1341 | help |
| 1342 | This driver provides for the Richtek RT5033 Power Management IC, |
| 1343 | which includes the I2C driver and the Core APIs. This driver provides |
| 1344 | common support for accessing the device. The device supports multiple |
| 1345 | sub-devices like charger, fuel gauge, flash LED, current source, |
| 1346 | LDO and Buck. |
| 1347 | |
| 1348 | config MFD_RT5120 |
| 1349 | tristate "Richtek RT5120 Power Management IC" |
| 1350 | depends on I2C |
| 1351 | select MFD_CORE |
| 1352 | select REGMAP_I2C |
| 1353 | select REGMAP_IRQ |
| 1354 | help |
| 1355 | The enables support for Richtek RT5120 PMIC. It includes four high |
| 1356 | efficiency buck converters and one LDO voltage regulator. The device |
| 1357 | is targeted at providing the CPU voltage, memory, I/O and peripheral |
| 1358 | power rails in home entertainment devices. |
| 1359 | |
| 1360 | config MFD_RC5T583 |
| 1361 | bool "Ricoh RC5T583 Power Management system device" |
| 1362 | depends on I2C=y |
| 1363 | select MFD_CORE |
| 1364 | select REGMAP_I2C |
| 1365 | help |
| 1366 | Select this option to get support for the RICOH583 Power |
| 1367 | Management system device. |
| 1368 | This driver provides common support for accessing the device |
| 1369 | through i2c interface. The device supports multiple sub-devices |
| 1370 | like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey. |
| 1371 | Additional drivers must be enabled in order to use the |
| 1372 | different functionality of the device. |
| 1373 | |
| 1374 | config MFD_RK8XX |
| 1375 | tristate |
| 1376 | select MFD_CORE |
| 1377 | |
| 1378 | config MFD_RK8XX_I2C |
| 1379 | tristate "Rockchip RK8xx Power Management Chips" |
| 1380 | depends on I2C && OF |
| 1381 | select MFD_CORE |
| 1382 | select REGMAP_I2C |
| 1383 | select REGMAP_IRQ |
| 1384 | select MFD_RK8XX |
| 1385 | help |
| 1386 | If you say yes here you get support for the RK801, RK805, RK808, |
| 1387 | RK809, RK816, RK817 and RK818 Power Management chips. |
| 1388 | This driver provides common support for accessing the device |
| 1389 | through I2C interface. The device supports multiple sub-devices |
| 1390 | including interrupts, RTC, LDO & DCDC regulators, and onkey. |
| 1391 | |
| 1392 | config MFD_RK8XX_SPI |
| 1393 | tristate "Rockchip RK806 Power Management Chip" |
| 1394 | depends on SPI && OF |
| 1395 | select MFD_CORE |
| 1396 | select REGMAP_SPI |
| 1397 | select REGMAP_IRQ |
| 1398 | select MFD_RK8XX |
| 1399 | help |
| 1400 | If you say yes here you get support for the RK806 Power Management |
| 1401 | chip. |
| 1402 | This driver provides common support for accessing the device |
| 1403 | through an SPI interface. The device supports multiple sub-devices |
| 1404 | including interrupts, LDO & DCDC regulators, and power on-key. |
| 1405 | |
| 1406 | config MFD_RN5T618 |
| 1407 | tristate "Ricoh RN5T567/618 PMIC" |
| 1408 | depends on I2C |
| 1409 | depends on OF |
| 1410 | select MFD_CORE |
| 1411 | select REGMAP_I2C |
| 1412 | select REGMAP_IRQ |
| 1413 | help |
| 1414 | Say yes here to add support for the Ricoh RN5T567, |
| 1415 | RN5T618, RC5T619 PMIC. |
| 1416 | This driver provides common support for accessing the device, |
| 1417 | additional drivers must be enabled in order to use the |
| 1418 | functionality of the device. |
| 1419 | |
| 1420 | config MFD_SEC_CORE |
| 1421 | tristate |
| 1422 | select MFD_CORE |
| 1423 | select REGMAP_IRQ |
| 1424 | |
| 1425 | config MFD_SEC_ACPM |
| 1426 | tristate "Samsung Electronics S2MPG1x PMICs" |
| 1427 | depends on EXYNOS_ACPM_PROTOCOL |
| 1428 | depends on OF |
| 1429 | select MFD_SEC_CORE |
| 1430 | help |
| 1431 | Support for the Samsung Electronics PMICs with ACPM interface. |
| 1432 | This is a Power Management IC for mobile applications with buck |
| 1433 | converters, various LDOs, power meters, RTC, clock outputs, and |
| 1434 | additional GPIOs interfaces. |
| 1435 | This driver provides common support for accessing the device; |
| 1436 | additional drivers must be enabled in order to use the functionality |
| 1437 | of the device. |
| 1438 | |
| 1439 | To compile this driver as a module, choose M here: the module will be |
| 1440 | called sec-acpm. |
| 1441 | |
| 1442 | config MFD_SEC_I2C |
| 1443 | tristate "Samsung Electronics S2MPA/S2MPS1X/S2MPU/S5M series PMICs" |
| 1444 | depends on I2C=y |
| 1445 | depends on OF |
| 1446 | select MFD_SEC_CORE |
| 1447 | select REGMAP_I2C |
| 1448 | help |
| 1449 | Support for the Samsung Electronics PMIC devices with I2C interface |
| 1450 | coming usually along with Samsung Exynos SoC chipset. |
| 1451 | This driver provides common support for accessing the device, |
| 1452 | additional drivers must be enabled in order to use the functionality |
| 1453 | of the device. |
| 1454 | |
| 1455 | To compile this driver as a module, choose M here: the |
| 1456 | module will be called sec-i2c. |
| 1457 | Have in mind that important core drivers (like regulators) depend |
| 1458 | on this driver so building this as a module might require proper |
| 1459 | initial ramdisk or might not boot up as well in certain scenarios. |
| 1460 | |
| 1461 | config MFD_SI476X_CORE |
| 1462 | tristate "Silicon Laboratories 4761/64/68 AM/FM radio." |
| 1463 | depends on I2C |
| 1464 | select MFD_CORE |
| 1465 | select REGMAP_I2C |
| 1466 | help |
| 1467 | This is the core driver for the SI476x series of AM/FM |
| 1468 | radio. This MFD driver connects the radio-si476x V4L2 module |
| 1469 | and the si476x audio codec. |
| 1470 | |
| 1471 | To compile this driver as a module, choose M here: the |
| 1472 | module will be called si476x-core. |
| 1473 | |
| 1474 | config MFD_SIMPLE_MFD_I2C |
| 1475 | tristate |
| 1476 | depends on I2C |
| 1477 | select MFD_CORE |
| 1478 | select REGMAP_I2C |
| 1479 | help |
| 1480 | This driver creates a single register map with the intention for it |
| 1481 | to be shared by all sub-devices. |
| 1482 | |
| 1483 | Once the register map has been successfully initialised, any |
| 1484 | sub-devices represented by child nodes in Device Tree will be |
| 1485 | subsequently registered. |
| 1486 | |
| 1487 | config MFD_SL28CPLD |
| 1488 | tristate "Kontron sl28cpld Board Management Controller" |
| 1489 | depends on I2C |
| 1490 | depends on ARCH_LAYERSCAPE || COMPILE_TEST |
| 1491 | select MFD_SIMPLE_MFD_I2C |
| 1492 | help |
| 1493 | Say yes here to enable support for the Kontron sl28cpld board |
| 1494 | management controller. |
| 1495 | |
| 1496 | It can be found on the following boards: |
| 1497 | * SMARC-sAL28 |
| 1498 | |
| 1499 | config MFD_SM501 |
| 1500 | tristate "Silicon Motion SM501" |
| 1501 | depends on HAS_DMA |
| 1502 | help |
| 1503 | This is the core driver for the Silicon Motion SM501 multimedia |
| 1504 | companion chip. This device is a multifunction device which may |
| 1505 | provide numerous interfaces including USB host controller, USB gadget, |
| 1506 | asynchronous serial ports, audio functions, and a dual display video |
| 1507 | interface. The device may be connected by PCI or local bus with |
| 1508 | varying functions enabled. |
| 1509 | |
| 1510 | config MFD_SM501_GPIO |
| 1511 | bool "Export GPIO via GPIO layer" |
| 1512 | depends on MFD_SM501 && GPIOLIB |
| 1513 | help |
| 1514 | This option uses the gpio library layer to export the 64 GPIO |
| 1515 | lines on the SM501. The platform data is used to supply the |
| 1516 | base number for the first GPIO line to register. |
| 1517 | |
| 1518 | config MFD_SKY81452 |
| 1519 | tristate "Skyworks Solutions SKY81452" |
| 1520 | select MFD_CORE |
| 1521 | select REGMAP_I2C |
| 1522 | depends on I2C |
| 1523 | help |
| 1524 | This is the core driver for the Skyworks SKY81452 backlight and |
| 1525 | voltage regulator device. |
| 1526 | |
| 1527 | This driver can also be built as a module. If so, the module |
| 1528 | will be called sky81452. |
| 1529 | |
| 1530 | config MFD_SC27XX_PMIC |
| 1531 | tristate "Spreadtrum SC27xx PMICs" |
| 1532 | depends on ARCH_SPRD || COMPILE_TEST |
| 1533 | depends on SPI_MASTER |
| 1534 | select MFD_CORE |
| 1535 | select REGMAP_SPI |
| 1536 | select REGMAP_IRQ |
| 1537 | help |
| 1538 | This enables support for the Spreadtrum SC27xx PMICs with SPI |
| 1539 | interface. The SC27xx series PMICs integrate power management, |
| 1540 | audio codec, battery management and user interface support |
| 1541 | function (such as RTC, Typec, indicator and so on) in a single chip. |
| 1542 | |
| 1543 | This driver provides common support for accessing the SC27xx PMICs, |
| 1544 | and it also adds the irq_chip parts for handling the PMIC chip events. |
| 1545 | |
| 1546 | config RZ_MTU3 |
| 1547 | tristate "Renesas RZ/G2L MTU3a core driver" |
| 1548 | depends on (ARCH_RZG2L && OF) || COMPILE_TEST |
| 1549 | select MFD_CORE |
| 1550 | help |
| 1551 | Select this option to enable Renesas RZ/G2L MTU3a core driver for |
| 1552 | the Multi-Function Timer Pulse Unit 3 (MTU3a) hardware available |
| 1553 | on SoCs from Renesas. The core driver shares the clk and channel |
| 1554 | register access for the other child devices like Counter, PWM, |
| 1555 | Clock Source, and Clock event. |
| 1556 | |
| 1557 | config ABX500_CORE |
| 1558 | bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" |
| 1559 | depends on ARCH_U8500 || COMPILE_TEST |
| 1560 | default y if ARCH_U8500 |
| 1561 | help |
| 1562 | Say yes here if you have the ABX500 Mixed Signal IC family |
| 1563 | chips. This core driver expose register access functions. |
| 1564 | Functionality specific drivers using these functions can |
| 1565 | remain unchanged when IC changes. Binding of the functions to |
| 1566 | actual register access is done by the IC core driver. |
| 1567 | |
| 1568 | config AB8500_CORE |
| 1569 | bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" |
| 1570 | depends on ABX500_CORE && MFD_DB8500_PRCMU |
| 1571 | select POWER_SUPPLY |
| 1572 | select MFD_CORE |
| 1573 | select IRQ_DOMAIN |
| 1574 | help |
| 1575 | Select this option to enable access to AB8500 power management |
| 1576 | chip. This connects to U8500 either on the SSP/SPI bus (deprecated |
| 1577 | since hardware version v1.0) or the I2C bus via PRCMU. It also adds |
| 1578 | the irq_chip parts for handling the Mixed Signal chip events. |
| 1579 | This chip embeds various other multimedia functionalities as well. |
| 1580 | |
| 1581 | config MFD_DB8500_PRCMU |
| 1582 | bool "ST-Ericsson DB8500 Power Reset Control Management Unit" |
| 1583 | depends on UX500_SOC_DB8500 |
| 1584 | select MFD_CORE |
| 1585 | help |
| 1586 | Select this option to enable support for the DB8500 Power Reset |
| 1587 | and Control Management Unit. This is basically an autonomous |
| 1588 | system controller running an XP70 microprocessor, which is accessed |
| 1589 | through a register map. |
| 1590 | |
| 1591 | config MFD_STMPE |
| 1592 | tristate "STMicroelectronics STMPE" |
| 1593 | depends on I2C || SPI_MASTER |
| 1594 | depends on OF |
| 1595 | select MFD_CORE |
| 1596 | help |
| 1597 | Support for the STMPE family of I/O Expanders from |
| 1598 | STMicroelectronics. |
| 1599 | |
| 1600 | Currently supported devices are: |
| 1601 | |
| 1602 | STMPE811: GPIO, Touchscreen, ADC |
| 1603 | STMPE1601: GPIO, Keypad |
| 1604 | STMPE1801: GPIO, Keypad |
| 1605 | STMPE2401: GPIO, Keypad |
| 1606 | STMPE2403: GPIO, Keypad |
| 1607 | |
| 1608 | This driver provides common support for accessing the device, |
| 1609 | additional drivers must be enabled in order to use the functionality |
| 1610 | of the device. Currently available sub drivers are: |
| 1611 | |
| 1612 | GPIO: stmpe-gpio |
| 1613 | Keypad: stmpe-keypad |
| 1614 | Touchscreen: stmpe-ts |
| 1615 | ADC: stmpe-adc |
| 1616 | |
| 1617 | menu "STMicroelectronics STMPE Interface Drivers" |
| 1618 | depends on MFD_STMPE |
| 1619 | |
| 1620 | config STMPE_I2C |
| 1621 | tristate "STMicroelectronics STMPE I2C Interface" |
| 1622 | depends on I2C |
| 1623 | default y |
| 1624 | help |
| 1625 | This is used to enable I2C interface of STMPE |
| 1626 | |
| 1627 | config STMPE_SPI |
| 1628 | tristate "STMicroelectronics STMPE SPI Interface" |
| 1629 | depends on SPI_MASTER |
| 1630 | help |
| 1631 | This is used to enable SPI interface of STMPE |
| 1632 | endmenu |
| 1633 | |
| 1634 | config MFD_SUN6I_PRCM |
| 1635 | bool "Allwinner A31/A23/A33 PRCM controller" |
| 1636 | depends on ARCH_SUNXI || COMPILE_TEST |
| 1637 | select MFD_CORE |
| 1638 | help |
| 1639 | Support for the PRCM (Power/Reset/Clock Management) unit available |
| 1640 | in the A31, A23, and A33 SoCs. Other Allwinner SoCs contain similar |
| 1641 | hardware, but they do not use this driver. |
| 1642 | |
| 1643 | config MFD_SYSCON |
| 1644 | bool "System Controller Register R/W Based on Regmap" |
| 1645 | select REGMAP_MMIO |
| 1646 | help |
| 1647 | Select this option to enable accessing system control registers |
| 1648 | via regmap. |
| 1649 | |
| 1650 | config MFD_TI_AM335X_TSCADC |
| 1651 | tristate "TI ADC / Touch Screen chip support" |
| 1652 | depends on ARCH_OMAP2PLUS || ARCH_K3 || COMPILE_TEST |
| 1653 | select MFD_CORE |
| 1654 | select REGMAP |
| 1655 | select REGMAP_MMIO |
| 1656 | help |
| 1657 | If you say yes here you get support for Texas Instruments series |
| 1658 | of Touch Screen /ADC chips. |
| 1659 | To compile this driver as a module, choose M here: the |
| 1660 | module will be called ti_am335x_tscadc. |
| 1661 | |
| 1662 | config MFD_LP3943 |
| 1663 | tristate "TI/National Semiconductor LP3943 MFD Driver" |
| 1664 | depends on I2C |
| 1665 | select MFD_CORE |
| 1666 | select REGMAP_I2C |
| 1667 | help |
| 1668 | Support for the TI/National Semiconductor LP3943. |
| 1669 | This driver consists of GPIO and PWM drivers. |
| 1670 | With these functionalities, it can be used for LED string control or |
| 1671 | general usage such like a GPIO controller and a PWM controller. |
| 1672 | |
| 1673 | config MFD_LP8788 |
| 1674 | bool "TI LP8788 Power Management Unit Driver" |
| 1675 | depends on I2C=y |
| 1676 | select MFD_CORE |
| 1677 | select REGMAP_I2C |
| 1678 | select IRQ_DOMAIN |
| 1679 | help |
| 1680 | TI LP8788 PMU supports regulators, battery charger, RTC, |
| 1681 | ADC, backlight driver and current sinks. |
| 1682 | |
| 1683 | config MFD_TI_LMU |
| 1684 | tristate "TI Lighting Management Unit driver" |
| 1685 | depends on I2C |
| 1686 | select MFD_CORE |
| 1687 | select REGMAP_I2C |
| 1688 | help |
| 1689 | Say yes here to enable support for TI LMU chips. |
| 1690 | TI LMU MFD supports LM3532, LM3631, LM3632, LM3633, LM3695 and |
| 1691 | LM36274. It consists of backlight, LED and regulator driver. |
| 1692 | It provides consistent device controls for lighting functions. |
| 1693 | |
| 1694 | config MFD_BQ257XX |
| 1695 | tristate "TI BQ257XX Buck/Boost Charge Controller" |
| 1696 | depends on I2C |
| 1697 | select MFD_CORE |
| 1698 | select REGMAP_I2C |
| 1699 | help |
| 1700 | Support Texas Instruments BQ25703 Buck/Boost converter with |
| 1701 | charge controller. It consists of regulators that provide |
| 1702 | system voltage and OTG voltage, and a charger manager for |
| 1703 | batteries containing one or more cells. |
| 1704 | |
| 1705 | config MFD_OMAP_USB_HOST |
| 1706 | bool "TI OMAP USBHS core and TLL driver" |
| 1707 | depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3 |
| 1708 | depends on COMMON_CLK |
| 1709 | default y |
| 1710 | help |
| 1711 | This is the core driver for the OAMP EHCI and OHCI drivers. |
| 1712 | This MFD driver does the required setup functionalities for |
| 1713 | OMAP USB Host drivers. |
| 1714 | |
| 1715 | config MFD_PALMAS |
| 1716 | tristate "TI Palmas series chips" |
| 1717 | select MFD_CORE |
| 1718 | select REGMAP_I2C |
| 1719 | select REGMAP_IRQ |
| 1720 | depends on I2C=y |
| 1721 | help |
| 1722 | If you say yes here you get support for the Palmas |
| 1723 | series of PMIC chips from Texas Instruments. |
| 1724 | |
| 1725 | config TPS6105X |
| 1726 | tristate "TI TPS61050/61052 Boost Converters" |
| 1727 | depends on I2C |
| 1728 | select REGMAP_I2C |
| 1729 | select REGULATOR |
| 1730 | select MFD_CORE |
| 1731 | select REGULATOR_FIXED_VOLTAGE |
| 1732 | help |
| 1733 | This option enables a driver for the TP61050/TPS61052 |
| 1734 | high-power "white LED driver". This boost converter is |
| 1735 | sometimes used for other things than white LEDs, and |
| 1736 | also contains a GPIO pin. |
| 1737 | |
| 1738 | config TPS65010 |
| 1739 | tristate "TI TPS6501x Power Management chips" |
| 1740 | depends on I2C && GPIOLIB |
| 1741 | default MACH_OMAP_OSK |
| 1742 | help |
| 1743 | If you say yes here you get support for the TPS6501x series of |
| 1744 | Power Management chips. These include voltage regulators, |
| 1745 | lithium ion/polymer battery charging, and other features that |
| 1746 | are often used in portable devices like cell phones and cameras. |
| 1747 | |
| 1748 | This driver can also be built as a module. If so, the module |
| 1749 | will be called tps65010. |
| 1750 | |
| 1751 | config TPS6507X |
| 1752 | tristate "TI TPS6507x Power Management / Touch Screen chips" |
| 1753 | select MFD_CORE |
| 1754 | depends on I2C |
| 1755 | help |
| 1756 | If you say yes here you get support for the TPS6507x series of |
| 1757 | Power Management / Touch Screen chips. These include voltage |
| 1758 | regulators, lithium ion/polymer battery charging, touch screen |
| 1759 | and other features that are often used in portable devices. |
| 1760 | This driver can also be built as a module. If so, the module |
| 1761 | will be called tps6507x. |
| 1762 | |
| 1763 | config MFD_TPS65086 |
| 1764 | tristate "TI TPS65086 Power Management Integrated Chips (PMICs)" |
| 1765 | select MFD_CORE |
| 1766 | select REGMAP |
| 1767 | select REGMAP_IRQ |
| 1768 | select REGMAP_I2C |
| 1769 | depends on I2C |
| 1770 | help |
| 1771 | If you say yes here you get support for the TPS65086 series of |
| 1772 | Power Management chips. |
| 1773 | This driver provides common support for accessing the device, |
| 1774 | additional drivers must be enabled in order to use the |
| 1775 | functionality of the device. |
| 1776 | |
| 1777 | config TPS65911_COMPARATOR |
| 1778 | tristate |
| 1779 | |
| 1780 | config MFD_TPS65090 |
| 1781 | bool "TI TPS65090 Power Management chips" |
| 1782 | depends on I2C=y |
| 1783 | select MFD_CORE |
| 1784 | select REGMAP_I2C |
| 1785 | select REGMAP_IRQ |
| 1786 | help |
| 1787 | If you say yes here you get support for the TPS65090 series of |
| 1788 | Power Management chips. |
| 1789 | This driver provides common support for accessing the device, |
| 1790 | additional drivers must be enabled in order to use the |
| 1791 | functionality of the device. |
| 1792 | |
| 1793 | config MFD_TPS65217 |
| 1794 | tristate "TI TPS65217 Power Management / White LED chips" |
| 1795 | depends on I2C && OF |
| 1796 | select MFD_CORE |
| 1797 | select REGMAP_I2C |
| 1798 | select IRQ_DOMAIN |
| 1799 | help |
| 1800 | If you say yes here you get support for the TPS65217 series of |
| 1801 | Power Management / White LED chips. |
| 1802 | These include voltage regulators, lithium ion/polymer battery |
| 1803 | charger, wled and other features that are often used in portable |
| 1804 | devices. |
| 1805 | |
| 1806 | This driver can also be built as a module. If so, the module |
| 1807 | will be called tps65217. |
| 1808 | |
| 1809 | config MFD_TI_LP873X |
| 1810 | tristate "TI LP873X Power Management IC" |
| 1811 | depends on I2C |
| 1812 | select MFD_CORE |
| 1813 | select REGMAP_I2C |
| 1814 | help |
| 1815 | If you say yes here then you get support for the LP873X series of |
| 1816 | Power Management Integrated Circuits (PMIC). |
| 1817 | These include voltage regulators, thermal protection, configurable |
| 1818 | General Purpose Outputs (GPO) that are used in portable devices. |
| 1819 | |
| 1820 | This driver can also be built as a module. If so, the module |
| 1821 | will be called lp873x. |
| 1822 | |
| 1823 | config MFD_TI_LP87565 |
| 1824 | tristate "TI LP87565 Power Management IC" |
| 1825 | depends on I2C && OF |
| 1826 | select MFD_CORE |
| 1827 | select REGMAP_I2C |
| 1828 | help |
| 1829 | If you say yes here then you get support for the LP87565 series of |
| 1830 | Power Management Integrated Circuits (PMIC). |
| 1831 | These include voltage regulators, thermal protection, configurable |
| 1832 | General Purpose Outputs (GPO) that are used in portable devices. |
| 1833 | |
| 1834 | This driver can also be built as a module. If so, the module |
| 1835 | will be called lp87565. |
| 1836 | |
| 1837 | config MFD_TPS65218 |
| 1838 | tristate "TI TPS65218 Power Management chips" |
| 1839 | depends on I2C && OF |
| 1840 | select MFD_CORE |
| 1841 | select REGMAP_I2C |
| 1842 | select REGMAP_IRQ |
| 1843 | help |
| 1844 | If you say yes here you get support for the TPS65218 series of |
| 1845 | Power Management chips. |
| 1846 | These include voltage regulators, gpio and other features |
| 1847 | that are often used in portable devices. |
| 1848 | |
| 1849 | This driver can also be built as a module. If so, the module |
| 1850 | will be called tps65218. |
| 1851 | |
| 1852 | config MFD_TPS65219 |
| 1853 | tristate "TI TPS65219 Power Management IC" |
| 1854 | depends on I2C && OF |
| 1855 | select MFD_CORE |
| 1856 | select REGMAP_I2C |
| 1857 | select REGMAP_IRQ |
| 1858 | help |
| 1859 | If you say yes here you get support for the TPS65219 series of Power |
| 1860 | Management ICs. These include voltage regulators, GPIOs and |
| 1861 | push/power button that is often used in portable devices. |
| 1862 | |
| 1863 | This driver can also be built as a module. If so, the module |
| 1864 | will be called tps65219. |
| 1865 | |
| 1866 | config MFD_TPS6586X |
| 1867 | bool "TI TPS6586x Power Management chips" |
| 1868 | depends on I2C=y |
| 1869 | select MFD_CORE |
| 1870 | select REGMAP_I2C |
| 1871 | help |
| 1872 | If you say yes here you get support for the TPS6586X series of |
| 1873 | Power Management chips. |
| 1874 | This driver provides common support for accessing the device, |
| 1875 | additional drivers must be enabled in order to use the |
| 1876 | functionality of the device. |
| 1877 | |
| 1878 | This driver can also be built as a module. If so, the module |
| 1879 | will be called tps6586x. |
| 1880 | |
| 1881 | config MFD_TPS65910 |
| 1882 | bool "TI TPS65910 Power Management chip" |
| 1883 | depends on I2C=y |
| 1884 | depends on GPIOLIB || COMPILE_TEST |
| 1885 | select MFD_CORE |
| 1886 | select REGMAP_I2C |
| 1887 | select REGMAP_IRQ |
| 1888 | select IRQ_DOMAIN |
| 1889 | help |
| 1890 | if you say yes here you get support for the TPS65910 series of |
| 1891 | Power Management chips. |
| 1892 | |
| 1893 | config MFD_TPS65912 |
| 1894 | tristate |
| 1895 | select MFD_CORE |
| 1896 | select REGMAP |
| 1897 | select REGMAP_IRQ |
| 1898 | |
| 1899 | config MFD_TPS65912_I2C |
| 1900 | tristate "TI TPS65912 Power Management chip with I2C" |
| 1901 | select MFD_TPS65912 |
| 1902 | select REGMAP_I2C |
| 1903 | depends on I2C |
| 1904 | help |
| 1905 | If you say yes here you get support for the TPS65912 series of |
| 1906 | PM chips with I2C interface. |
| 1907 | |
| 1908 | config MFD_TPS65912_SPI |
| 1909 | tristate "TI TPS65912 Power Management chip with SPI" |
| 1910 | select MFD_TPS65912 |
| 1911 | select REGMAP_SPI |
| 1912 | depends on SPI_MASTER |
| 1913 | help |
| 1914 | If you say yes here you get support for the TPS65912 series of |
| 1915 | PM chips with SPI interface. |
| 1916 | |
| 1917 | config MFD_TPS6594 |
| 1918 | tristate |
| 1919 | select MFD_CORE |
| 1920 | select REGMAP |
| 1921 | select REGMAP_IRQ |
| 1922 | |
| 1923 | config MFD_TPS6594_I2C |
| 1924 | tristate "TI TPS6594 Power Management chip with I2C" |
| 1925 | select MFD_TPS6594 |
| 1926 | select REGMAP_I2C |
| 1927 | select CRC8 |
| 1928 | depends on I2C |
| 1929 | help |
| 1930 | If you say yes here you get support for the TPS6594 series of |
| 1931 | PM chips with I2C interface. |
| 1932 | |
| 1933 | This driver can also be built as a module. If so, the module |
| 1934 | will be called tps6594-i2c. |
| 1935 | |
| 1936 | config MFD_TPS6594_SPI |
| 1937 | tristate "TI TPS6594 Power Management chip with SPI" |
| 1938 | select MFD_TPS6594 |
| 1939 | select REGMAP_SPI |
| 1940 | select CRC8 |
| 1941 | depends on SPI_MASTER |
| 1942 | help |
| 1943 | If you say yes here you get support for the TPS6594 series of |
| 1944 | PM chips with SPI interface. |
| 1945 | |
| 1946 | This driver can also be built as a module. If so, the module |
| 1947 | will be called tps6594-spi. |
| 1948 | |
| 1949 | config TWL4030_CORE |
| 1950 | bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support" |
| 1951 | depends on I2C=y |
| 1952 | select IRQ_DOMAIN |
| 1953 | select MFD_CORE |
| 1954 | select REGMAP_I2C |
| 1955 | help |
| 1956 | Say yes here if you have TWL4030 / TWL6030 family chip on your board. |
| 1957 | This core driver provides register access and IRQ handling |
| 1958 | facilities, and registers devices for the various functions |
| 1959 | so that function-specific drivers can bind to them. |
| 1960 | |
| 1961 | These multi-function chips are found on many OMAP2 and OMAP3 |
| 1962 | boards, providing power management, RTC, GPIO, keypad, a |
| 1963 | high speed USB OTG transceiver, an audio codec (on most |
| 1964 | versions) and many other features. |
| 1965 | |
| 1966 | config TWL4030_POWER |
| 1967 | bool "TI TWL4030 power resources" |
| 1968 | depends on TWL4030_CORE && ARM |
| 1969 | help |
| 1970 | Say yes here if you want to use the power resources on the |
| 1971 | TWL4030 family chips. Most of these resources are regulators, |
| 1972 | which have a separate driver; some are control signals, such |
| 1973 | as clock request handshaking. |
| 1974 | |
| 1975 | This driver uses board-specific data to initialize the resources |
| 1976 | and load scripts controlling which resources are switched off/on |
| 1977 | or reset when a sleep, wakeup or warm reset event occurs. |
| 1978 | |
| 1979 | config MFD_TWL4030_AUDIO |
| 1980 | bool "TI TWL4030 Audio" |
| 1981 | depends on TWL4030_CORE |
| 1982 | select MFD_CORE |
| 1983 | default n |
| 1984 | |
| 1985 | config TWL6040_CORE |
| 1986 | bool "TI TWL6040 audio codec" |
| 1987 | depends on I2C=y |
| 1988 | select MFD_CORE |
| 1989 | select REGMAP_I2C |
| 1990 | select REGMAP_IRQ |
| 1991 | default n |
| 1992 | help |
| 1993 | Say yes here if you want support for Texas Instruments TWL6040 audio |
| 1994 | codec. |
| 1995 | This driver provides common support for accessing the device, |
| 1996 | additional drivers must be enabled in order to use the |
| 1997 | functionality of the device (audio, vibra). |
| 1998 | |
| 1999 | config MENELAUS |
| 2000 | bool "TI TWL92330/Menelaus PM chip" |
| 2001 | depends on I2C=y && ARCH_OMAP2 |
| 2002 | help |
| 2003 | If you say yes here you get support for the Texas Instruments |
| 2004 | TWL92330/Menelaus Power Management chip. This include voltage |
| 2005 | regulators, Dual slot memory card transceivers, real-time clock |
| 2006 | and other features that are often used in portable devices like |
| 2007 | cell phones and PDAs. |
| 2008 | |
| 2009 | config MFD_LM3533 |
| 2010 | tristate "TI/National Semiconductor LM3533 Lighting Power chip" |
| 2011 | depends on I2C |
| 2012 | select MFD_CORE |
| 2013 | select REGMAP_I2C |
| 2014 | help |
| 2015 | Say yes here to enable support for National Semiconductor / TI |
| 2016 | LM3533 Lighting Power chips. |
| 2017 | |
| 2018 | This driver provides common support for accessing the device; |
| 2019 | additional drivers must be enabled in order to use the LED, |
| 2020 | backlight or ambient-light-sensor functionality of the device. |
| 2021 | |
| 2022 | config MFD_TIMBERDALE |
| 2023 | tristate "Timberdale FPGA" |
| 2024 | select MFD_CORE |
| 2025 | depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST) |
| 2026 | help |
| 2027 | This is the core driver for the timberdale FPGA. This device is a |
| 2028 | multifunction device which exposes numerous platform devices. |
| 2029 | |
| 2030 | The timberdale FPGA can be found on the Intel Atom development board |
| 2031 | for in-vehicle infotainment, called Russellville. |
| 2032 | |
| 2033 | config MFD_TC3589X |
| 2034 | bool "Toshiba TC35892 and variants" |
| 2035 | depends on I2C=y |
| 2036 | depends on OF |
| 2037 | select MFD_CORE |
| 2038 | help |
| 2039 | Support for the Toshiba TC35892 and variants I/O Expander. |
| 2040 | |
| 2041 | This driver provides common support for accessing the device, |
| 2042 | additional drivers must be enabled in order to use the |
| 2043 | functionality of the device. |
| 2044 | |
| 2045 | config MFD_TQMX86 |
| 2046 | tristate "TQ-Systems IO controller TQMX86" |
| 2047 | select MFD_CORE |
| 2048 | help |
| 2049 | Say yes here to enable support for various functions of the |
| 2050 | TQ-Systems IO controller and watchdog device, found on their |
| 2051 | ComExpress CPU modules. |
| 2052 | |
| 2053 | config MFD_VX855 |
| 2054 | tristate "VIA VX855/VX875 integrated south bridge" |
| 2055 | depends on PCI |
| 2056 | select MFD_CORE |
| 2057 | help |
| 2058 | Say yes here to enable support for various functions of the |
| 2059 | VIA VX855/VX875 south bridge. You will need to enable the vx855_spi |
| 2060 | and/or vx855_gpio drivers for this to do anything useful. |
| 2061 | |
| 2062 | config MFD_ARIZONA |
| 2063 | select REGMAP |
| 2064 | select REGMAP_IRQ |
| 2065 | select MFD_CORE |
| 2066 | tristate |
| 2067 | |
| 2068 | config MFD_ARIZONA_I2C |
| 2069 | tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with I2C" |
| 2070 | select MFD_ARIZONA |
| 2071 | select REGMAP_I2C |
| 2072 | depends on I2C |
| 2073 | help |
| 2074 | Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform |
| 2075 | audio SoC core functionality controlled via I2C. |
| 2076 | |
| 2077 | config MFD_ARIZONA_SPI |
| 2078 | tristate "Cirrus Logic/Wolfson Microelectronics Arizona platform with SPI" |
| 2079 | select MFD_ARIZONA |
| 2080 | select REGMAP_SPI |
| 2081 | depends on SPI_MASTER |
| 2082 | help |
| 2083 | Support for the Cirrus Logic/Wolfson Microelectronics Arizona platform |
| 2084 | audio SoC core functionality controlled via SPI. |
| 2085 | |
| 2086 | config MFD_CS47L24 |
| 2087 | bool "Cirrus Logic CS47L24 and WM1831" |
| 2088 | depends on MFD_ARIZONA |
| 2089 | help |
| 2090 | Support for Cirrus Logic CS47L24 and WM1831 low power audio SoC |
| 2091 | |
| 2092 | config MFD_WM5102 |
| 2093 | bool "Wolfson Microelectronics WM5102" |
| 2094 | depends on MFD_ARIZONA |
| 2095 | help |
| 2096 | Support for Wolfson Microelectronics WM5102 low power audio SoC |
| 2097 | |
| 2098 | config MFD_WM5110 |
| 2099 | bool "Wolfson Microelectronics WM5110 and WM8280/WM8281" |
| 2100 | depends on MFD_ARIZONA |
| 2101 | help |
| 2102 | Support for Wolfson Microelectronics WM5110 and WM8280/WM8281 |
| 2103 | low power audio SoC |
| 2104 | |
| 2105 | config MFD_WM8997 |
| 2106 | bool "Wolfson Microelectronics WM8997" |
| 2107 | depends on MFD_ARIZONA |
| 2108 | help |
| 2109 | Support for Wolfson Microelectronics WM8997 low power audio SoC |
| 2110 | |
| 2111 | config MFD_WM8998 |
| 2112 | bool "Wolfson Microelectronics WM8998" |
| 2113 | depends on MFD_ARIZONA |
| 2114 | help |
| 2115 | Support for Wolfson Microelectronics WM8998 low power audio SoC |
| 2116 | |
| 2117 | config MFD_WM8400 |
| 2118 | bool "Wolfson Microelectronics WM8400" |
| 2119 | select MFD_CORE |
| 2120 | depends on I2C=y |
| 2121 | select REGMAP_I2C |
| 2122 | help |
| 2123 | Support for the Wolfson Microelecronics WM8400 PMIC and audio |
| 2124 | CODEC. This driver provides common support for accessing |
| 2125 | the device, additional drivers must be enabled in order to use |
| 2126 | the functionality of the device. |
| 2127 | |
| 2128 | config MFD_WM831X |
| 2129 | bool |
| 2130 | |
| 2131 | config MFD_WM831X_I2C |
| 2132 | bool "Wolfson Microelectronics WM831x/2x PMICs with I2C" |
| 2133 | select MFD_CORE |
| 2134 | select MFD_WM831X |
| 2135 | select REGMAP_I2C |
| 2136 | select IRQ_DOMAIN |
| 2137 | depends on I2C=y |
| 2138 | help |
| 2139 | Support for the Wolfson Microelecronics WM831x and WM832x PMICs |
| 2140 | when controlled using I2C. This driver provides common support |
| 2141 | for accessing the device, additional drivers must be enabled in |
| 2142 | order to use the functionality of the device. |
| 2143 | |
| 2144 | config MFD_WM831X_SPI |
| 2145 | bool "Wolfson Microelectronics WM831x/2x PMICs with SPI" |
| 2146 | select MFD_CORE |
| 2147 | select MFD_WM831X |
| 2148 | select REGMAP_SPI |
| 2149 | select IRQ_DOMAIN |
| 2150 | depends on SPI_MASTER |
| 2151 | help |
| 2152 | Support for the Wolfson Microelecronics WM831x and WM832x PMICs |
| 2153 | when controlled using SPI. This driver provides common support |
| 2154 | for accessing the device, additional drivers must be enabled in |
| 2155 | order to use the functionality of the device. |
| 2156 | |
| 2157 | config MFD_WM8350 |
| 2158 | bool |
| 2159 | |
| 2160 | config MFD_WM8350_I2C |
| 2161 | bool "Wolfson Microelectronics WM8350 with I2C" |
| 2162 | select MFD_WM8350 |
| 2163 | select REGMAP_I2C |
| 2164 | depends on I2C=y |
| 2165 | help |
| 2166 | The WM8350 is an integrated audio and power management |
| 2167 | subsystem with watchdog and RTC functionality for embedded |
| 2168 | systems. This option enables core support for the WM8350 with |
| 2169 | I2C as the control interface. Additional options must be |
| 2170 | selected to enable support for the functionality of the chip. |
| 2171 | |
| 2172 | config MFD_WM8994 |
| 2173 | tristate "Wolfson Microelectronics WM8994" |
| 2174 | select MFD_CORE |
| 2175 | select REGMAP_I2C |
| 2176 | select REGMAP_IRQ |
| 2177 | depends on I2C |
| 2178 | help |
| 2179 | The WM8994 is a highly integrated hi-fi CODEC designed for |
| 2180 | smartphone applications. As well as audio functionality it |
| 2181 | has on board GPIO and regulator functionality which is |
| 2182 | supported via the relevant subsystems. This driver provides |
| 2183 | core support for the WM8994, in order to use the actual |
| 2184 | functionality of the device other drivers must be enabled. |
| 2185 | |
| 2186 | config MFD_WM97xx |
| 2187 | tristate "Wolfson Microelectronics WM97xx" |
| 2188 | select MFD_CORE |
| 2189 | select REGMAP_AC97 |
| 2190 | select AC97_BUS_COMPAT |
| 2191 | depends on AC97_BUS_NEW |
| 2192 | help |
| 2193 | The WM9705, WM9712 and WM9713 is a highly integrated hi-fi CODEC |
| 2194 | designed for smartphone applications. As well as audio functionality |
| 2195 | it has on board GPIO and a touchscreen functionality which is |
| 2196 | supported via the relevant subsystems. This driver provides core |
| 2197 | support for the WM97xx, in order to use the actual functionality of |
| 2198 | the device other drivers must be enabled. |
| 2199 | |
| 2200 | config MFD_STW481X |
| 2201 | tristate "Support for ST Microelectronics STw481x" |
| 2202 | depends on I2C && (ARCH_NOMADIK || COMPILE_TEST) |
| 2203 | select REGMAP_I2C |
| 2204 | select MFD_CORE |
| 2205 | help |
| 2206 | Select this option to enable the STw481x chip driver used |
| 2207 | in various ST Microelectronics and ST-Ericsson embedded |
| 2208 | Nomadik series. |
| 2209 | |
| 2210 | config MFD_ROHM_PWRBUTTON |
| 2211 | tristate |
| 2212 | select MFD_CORE |
| 2213 | |
| 2214 | config MFD_ROHM_BD718XX |
| 2215 | tristate "ROHM BD71837 Power Management IC" |
| 2216 | depends on I2C=y |
| 2217 | depends on OF |
| 2218 | select REGMAP_I2C |
| 2219 | select REGMAP_IRQ |
| 2220 | select MFD_CORE |
| 2221 | select MFD_ROHM_PWRBUTTON |
| 2222 | help |
| 2223 | Select this option to get support for the ROHM BD71837 |
| 2224 | Power Management ICs. BD71837 is designed to power processors like |
| 2225 | NXP i.MX8. It contains 8 BUCK outputs and 7 LDOs, voltage monitoring |
| 2226 | and emergency shut down as well as 32,768KHz clock output. |
| 2227 | |
| 2228 | config MFD_ROHM_BD71828 |
| 2229 | tristate "ROHM BD718[15/28/79], BD72720 and BD73900 PMICs" |
| 2230 | depends on I2C=y |
| 2231 | depends on OF |
| 2232 | select REGMAP_I2C |
| 2233 | select REGMAP_IRQ |
| 2234 | select MFD_CORE |
| 2235 | select MFD_ROHM_PWRBUTTON |
| 2236 | help |
| 2237 | Select this option to get support for the ROHM BD71815, BD71828, |
| 2238 | BD71879, BD72720 and BD73900 Power Management ICs (PMICs). These are |
| 2239 | single-chip Power Management ICs (PMIC), mainly for battery-powered |
| 2240 | portable devices. |
| 2241 | The BD71815 has 5 bucks, 7 LDOs, and a boost for driving LEDs. |
| 2242 | The BD718[28/79] have 7 buck converters and 7 LDOs. |
| 2243 | The BD72720 and the BD73900 have 10 bucks and 11 LDOs. |
| 2244 | All ICs provide a single-cell linear charger, a Coulomb counter, |
| 2245 | a Real-Time Clock (RTC), GPIOs and a 32.768 kHz clock gate. |
| 2246 | |
| 2247 | config MFD_ROHM_BD957XMUF |
| 2248 | tristate "ROHM BD9576MUF and BD9573MUF Power Management ICs" |
| 2249 | depends on I2C=y |
| 2250 | depends on OF |
| 2251 | select REGMAP_I2C |
| 2252 | select REGMAP_IRQ |
| 2253 | select MFD_CORE |
| 2254 | help |
| 2255 | Select this option to get support for the ROHM BD9576MUF and |
| 2256 | BD9573MUF Power Management ICs. BD9576 and BD9573 are primarily |
| 2257 | designed to be used to power R-Car series processors. |
| 2258 | |
| 2259 | config MFD_ROHM_BD96801 |
| 2260 | tristate "ROHM BD96801 Power Management IC" |
| 2261 | depends on I2C=y |
| 2262 | depends on OF |
| 2263 | select REGMAP_I2C |
| 2264 | select REGMAP_IRQ |
| 2265 | select MFD_CORE |
| 2266 | help |
| 2267 | Select this option to get support for the ROHM BD96801 Power |
| 2268 | Management IC. The ROHM BD96801 is a highly scalable Power Management |
| 2269 | IC for industrial and automotive use. The BD96801 can be used as a |
| 2270 | master PMIC in a chained PMIC solution with suitable companion PMICs. |
| 2271 | |
| 2272 | config MFD_STM32_LPTIMER |
| 2273 | tristate "Support for STM32 Low-Power Timer" |
| 2274 | depends on (ARCH_STM32 && OF) || COMPILE_TEST |
| 2275 | select MFD_CORE |
| 2276 | select REGMAP |
| 2277 | select REGMAP_MMIO |
| 2278 | help |
| 2279 | Select this option to enable STM32 Low-Power Timer driver |
| 2280 | used for PWM, IIO Trigger, IIO Encoder and Counter. Shared |
| 2281 | resources are also dealt with here. |
| 2282 | |
| 2283 | To compile this driver as a module, choose M here: the |
| 2284 | module will be called stm32-lptimer. |
| 2285 | |
| 2286 | config MFD_STM32_TIMERS |
| 2287 | tristate "Support for STM32 Timers" |
| 2288 | depends on (ARCH_STM32 && OF) || COMPILE_TEST |
| 2289 | select MFD_CORE |
| 2290 | select REGMAP |
| 2291 | select REGMAP_MMIO |
| 2292 | help |
| 2293 | Select this option to enable STM32 timers driver used |
| 2294 | for PWM and IIO Timer. This driver allow to share the |
| 2295 | registers between the others drivers. |
| 2296 | |
| 2297 | config MFD_STPMIC1 |
| 2298 | tristate "Support for STPMIC1 PMIC" |
| 2299 | depends on I2C=y && OF |
| 2300 | select REGMAP_I2C |
| 2301 | select REGMAP_IRQ |
| 2302 | select MFD_CORE |
| 2303 | help |
| 2304 | Support for ST Microelectronics STPMIC1 PMIC. STPMIC1 has power on |
| 2305 | key, watchdog and regulator functionalities which are supported via |
| 2306 | the relevant subsystems. This driver provides core support for the |
| 2307 | STPMIC1. In order to use the actual functionality of the device other |
| 2308 | drivers must be enabled. |
| 2309 | |
| 2310 | To compile this driver as a module, choose M here: the |
| 2311 | module will be called stpmic1. |
| 2312 | |
| 2313 | config MFD_STMFX |
| 2314 | tristate "Support for STMicroelectronics Multi-Function eXpander (STMFX)" |
| 2315 | depends on I2C |
| 2316 | depends on OF |
| 2317 | select MFD_CORE |
| 2318 | select REGMAP_I2C |
| 2319 | help |
| 2320 | Support for the STMicroelectronics Multi-Function eXpander. |
| 2321 | |
| 2322 | This driver provides common support for accessing the device, |
| 2323 | additional drivers must be enabled in order to use the functionality |
| 2324 | of the device. |
| 2325 | |
| 2326 | config MFD_WCD934X |
| 2327 | tristate "Support for WCD9340/WCD9341 Codec" |
| 2328 | depends on SLIMBUS |
| 2329 | select REGMAP |
| 2330 | select REGMAP_SLIMBUS |
| 2331 | select REGMAP_IRQ |
| 2332 | select MFD_CORE |
| 2333 | help |
| 2334 | Support for the Qualcomm WCD9340/WCD9341 Codec. |
| 2335 | This driver provides common support WCD934x audio codec and its |
| 2336 | associated Pin Controller, Soundwire Controller and Audio codec. |
| 2337 | |
| 2338 | config MFD_ATC260X |
| 2339 | tristate |
| 2340 | select MFD_CORE |
| 2341 | select REGMAP |
| 2342 | select REGMAP_IRQ |
| 2343 | |
| 2344 | config MFD_ATC260X_I2C |
| 2345 | tristate "Actions Semi ATC260x PMICs with I2C" |
| 2346 | select MFD_ATC260X |
| 2347 | select REGMAP_I2C |
| 2348 | depends on I2C |
| 2349 | help |
| 2350 | Support for the Actions Semi ATC260x PMICs controlled via I2C. |
| 2351 | |
| 2352 | This driver provides common support for accessing the ATC2603C |
| 2353 | and ATC2609A chip variants, additional drivers must be enabled |
| 2354 | in order to use the functionality of the device. |
| 2355 | |
| 2356 | config MFD_KHADAS_MCU |
| 2357 | tristate "Support for Khadas System control Microcontroller" |
| 2358 | depends on I2C |
| 2359 | depends on ARCH_MESON || ARCH_ROCKCHIP || COMPILE_TEST |
| 2360 | select MFD_CORE |
| 2361 | select REGMAP_I2C |
| 2362 | help |
| 2363 | Support for the Khadas System control Microcontroller interface |
| 2364 | present on their VIM and Edge boards. |
| 2365 | |
| 2366 | This Microcontroller is present on the Khadas VIM1, VIM2, VIM3 and |
| 2367 | Edge boards. |
| 2368 | |
| 2369 | It provides multiple boot control features like password check, |
| 2370 | power-on options, power-off control and system FAN control on recent |
| 2371 | boards. |
| 2372 | |
| 2373 | This driver provides common support for accessing the device, |
| 2374 | additional drivers must be enabled in order to use the functionality |
| 2375 | of the device. |
| 2376 | |
| 2377 | config MFD_ACER_A500_EC |
| 2378 | tristate "Support for Acer Iconia Tab A500 Embedded Controller" |
| 2379 | depends on I2C |
| 2380 | depends on (ARCH_TEGRA_2x_SOC && OF) || COMPILE_TEST |
| 2381 | select MFD_CORE |
| 2382 | select REGMAP |
| 2383 | help |
| 2384 | Support for Embedded Controller found on Acer Iconia Tab A500. |
| 2385 | The controller itself is ENE KB930, it is running firmware |
| 2386 | customized for the specific needs of the Acer A500 hardware. |
| 2387 | |
| 2388 | config MFD_QCOM_PM8008 |
| 2389 | tristate "Qualcomm PM8008 Power Management IC" |
| 2390 | depends on I2C && OF |
| 2391 | select MFD_CORE |
| 2392 | select REGMAP_I2C |
| 2393 | select REGMAP_IRQ |
| 2394 | help |
| 2395 | Select this option to get support for the Qualcomm Technologies, Inc. |
| 2396 | PM8008 PMIC chip. PM8008 is a dedicated camera PMIC that integrates |
| 2397 | all the necessary power management, housekeeping, and interface |
| 2398 | support functions into a single IC. This driver provides common |
| 2399 | support for accessing the device by instantiating all the child nodes |
| 2400 | under it in the device tree. Additional drivers must be enabled in |
| 2401 | order to use the functionality of the device. |
| 2402 | |
| 2403 | menu "Multimedia Capabilities Port drivers" |
| 2404 | depends on ARCH_SA1100 |
| 2405 | |
| 2406 | config MCP |
| 2407 | tristate |
| 2408 | |
| 2409 | # Interface drivers |
| 2410 | config MCP_SA11X0 |
| 2411 | tristate "Support SA11x0 MCP interface" |
| 2412 | depends on ARCH_SA1100 |
| 2413 | select MCP |
| 2414 | |
| 2415 | # Chip drivers |
| 2416 | config MCP_UCB1200 |
| 2417 | tristate "Support for UCB1200 / UCB1300" |
| 2418 | depends on MCP_SA11X0 |
| 2419 | select MCP |
| 2420 | |
| 2421 | config MCP_UCB1200_TS |
| 2422 | tristate "Touchscreen interface support" |
| 2423 | depends on MCP_UCB1200 && INPUT |
| 2424 | |
| 2425 | endmenu |
| 2426 | |
| 2427 | config MFD_VEXPRESS_SYSREG |
| 2428 | tristate "Versatile Express System Registers" |
| 2429 | depends on VEXPRESS_CONFIG && GPIOLIB |
| 2430 | default y |
| 2431 | select GPIO_GENERIC_PLATFORM |
| 2432 | select MFD_CORE |
| 2433 | select MFD_SYSCON |
| 2434 | help |
| 2435 | System Registers are the platform configuration block |
| 2436 | on the ARM Ltd. Versatile Express board. |
| 2437 | |
| 2438 | config RAVE_SP_CORE |
| 2439 | tristate "RAVE SP MCU core driver" |
| 2440 | depends on SERIAL_DEV_BUS |
| 2441 | select CRC_ITU_T |
| 2442 | help |
| 2443 | Select this to get support for the Supervisory Processor |
| 2444 | device found on several devices in RAVE line of hardware. |
| 2445 | |
| 2446 | config SGI_MFD_IOC3 |
| 2447 | bool "SGI IOC3 core driver" |
| 2448 | depends on PCI && MIPS && 64BIT |
| 2449 | select MFD_CORE |
| 2450 | help |
| 2451 | This option enables basic support for the SGI IOC3-based |
| 2452 | controller cards. This option does not enable any specific |
| 2453 | functions on such a card, but provides necessary infrastructure |
| 2454 | for other drivers to utilize. |
| 2455 | |
| 2456 | If you have an SGI Origin, Octane, or a PCI IOC3 card, |
| 2457 | then say Y. Otherwise say N. |
| 2458 | |
| 2459 | config MFD_INTEL_M10_BMC_CORE |
| 2460 | tristate |
| 2461 | select MFD_CORE |
| 2462 | select REGMAP |
| 2463 | default n |
| 2464 | |
| 2465 | config MFD_INTEL_M10_BMC_SPI |
| 2466 | tristate "Intel MAX 10 Board Management Controller with SPI" |
| 2467 | depends on SPI_MASTER |
| 2468 | select MFD_INTEL_M10_BMC_CORE |
| 2469 | select REGMAP_SPI_AVMM |
| 2470 | help |
| 2471 | Support for the Intel MAX 10 board management controller using the |
| 2472 | SPI interface. |
| 2473 | |
| 2474 | This driver provides common support for accessing the device, |
| 2475 | additional drivers must be enabled in order to use the functionality |
| 2476 | of the device. |
| 2477 | |
| 2478 | config MFD_INTEL_M10_BMC_PMCI |
| 2479 | tristate "Intel MAX 10 Board Management Controller with PMCI" |
| 2480 | depends on FPGA_DFL |
| 2481 | select MFD_INTEL_M10_BMC_CORE |
| 2482 | select REGMAP |
| 2483 | help |
| 2484 | Support for the Intel MAX 10 board management controller via PMCI. |
| 2485 | |
| 2486 | This driver provides common support for accessing the device, |
| 2487 | additional drivers must be enabled in order to use the functionality |
| 2488 | of the device. |
| 2489 | |
| 2490 | config MFD_LOONGSON_SE |
| 2491 | tristate "Loongson Security Engine chip controller driver" |
| 2492 | depends on LOONGARCH && ACPI |
| 2493 | select MFD_CORE |
| 2494 | help |
| 2495 | The Loongson Security Engine chip supports RNG, SM2, SM3 and |
| 2496 | SM4 accelerator engines. Each engine have its own DMA buffer |
| 2497 | provided by the controller. The kernel cannot directly send |
| 2498 | commands to the engine and must first send them to the controller, |
| 2499 | which will forward them to the corresponding engine. |
| 2500 | |
| 2501 | config MFD_LS2K_BMC_CORE |
| 2502 | bool "Loongson-2K Board Management Controller Support" |
| 2503 | depends on PCI && ACPI_GENERIC_GSI |
| 2504 | select MFD_CORE |
| 2505 | help |
| 2506 | Say yes here to add support for the Loongson-2K BMC which is a Board |
| 2507 | Management Controller connected to the PCIe bus. The device supports |
| 2508 | multiple sub-devices like display and IPMI. This driver provides common |
| 2509 | support for accessing the devices. |
| 2510 | |
| 2511 | The display is enabled by default in the driver, while the IPMI interface |
| 2512 | is enabled independently through the IPMI_LS2K option in the IPMI section. |
| 2513 | |
| 2514 | config MFD_QNAP_MCU |
| 2515 | tristate "QNAP microcontroller unit core driver" |
| 2516 | depends on SERIAL_DEV_BUS |
| 2517 | select MFD_CORE |
| 2518 | help |
| 2519 | Select this to get support for the QNAP MCU device found in |
| 2520 | several devices of QNAP network attached storage products that |
| 2521 | implements additional functionality for the device, like fan |
| 2522 | and LED control. |
| 2523 | |
| 2524 | This driver implements the base serial protocol to talk to the |
| 2525 | device and provides functions for the other parts to hook into. |
| 2526 | |
| 2527 | config MFD_RSMU_I2C |
| 2528 | tristate "Renesas Synchronization Management Unit with I2C" |
| 2529 | depends on I2C && OF |
| 2530 | select MFD_CORE |
| 2531 | select REGMAP_I2C |
| 2532 | help |
| 2533 | Support for the Renesas Synchronization Management Unit, such as |
| 2534 | Clockmatrix and 82P33XXX series. This option supports I2C as |
| 2535 | the control interface. |
| 2536 | |
| 2537 | This driver provides common support for accessing the device. |
| 2538 | Additional drivers must be enabled in order to use the functionality |
| 2539 | of the device. |
| 2540 | |
| 2541 | config MFD_RSMU_SPI |
| 2542 | tristate "Renesas Synchronization Management Unit with SPI" |
| 2543 | depends on SPI && OF |
| 2544 | select MFD_CORE |
| 2545 | select REGMAP_SPI |
| 2546 | help |
| 2547 | Support for the Renesas Synchronization Management Unit, such as |
| 2548 | Clockmatrix and 82P33XXX series. This option supports SPI as |
| 2549 | the control interface. |
| 2550 | |
| 2551 | This driver provides common support for accessing the device. |
| 2552 | Additional drivers must be enabled in order to use the functionality |
| 2553 | of the device. |
| 2554 | |
| 2555 | config MFD_UPBOARD_FPGA |
| 2556 | tristate "Support for the AAeon UP board FPGA" |
| 2557 | depends on (X86 && ACPI) |
| 2558 | select MFD_CORE |
| 2559 | help |
| 2560 | Select this option to enable the AAEON UP and UP^2 onboard FPGA. |
| 2561 | This is the core driver of this FPGA, which has a pin controller and a |
| 2562 | LED controller. |
| 2563 | |
| 2564 | To compile this driver as a module, choose M here: the module will be |
| 2565 | called upboard-fpga. |
| 2566 | |
| 2567 | config MFD_MAX7360 |
| 2568 | tristate "Maxim MAX7360 I2C IO Expander" |
| 2569 | depends on I2C |
| 2570 | select MFD_CORE |
| 2571 | select REGMAP_I2C |
| 2572 | select REGMAP_IRQ |
| 2573 | help |
| 2574 | Say yes here to add support for Maxim MAX7360 device, embedding |
| 2575 | keypad, rotary encoder, PWM and GPIO features. |
| 2576 | |
| 2577 | This driver provides common support for accessing the device; |
| 2578 | additional drivers must be enabled in order to use the functionality |
| 2579 | of the device. |
| 2580 | |
| 2581 | endmenu |
| 2582 | endif |