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