1# 2# Multifunction miscellaneous devices 3# 4 5menuconfig MFD_SUPPORT 6 bool "Multifunction device drivers" 7 depends on HAS_IOMEM 8 default y 9 help 10 Multifunction devices embed several functions (e.g. GPIOs, 11 touchscreens, keyboards, current regulators, power management chips, 12 etc...) in one single integrated circuit. They usually talk to the 13 main CPU through one or more IRQ lines and low speed data busses (SPI, 14 I2C, etc..). They appear as one single device to the main system 15 through the data bus and the MFD framework allows for sub devices 16 (a.k.a. functions) to appear as discrete platform devices. 17 MFDs are typically found on embedded platforms. 18 19 This option alone does not add any kernel code. 20 21if MFD_SUPPORT 22 23config MFD_CORE 24 tristate 25 default n 26 27config MFD_88PM860X 28 bool "Support Marvell 88PM8606/88PM8607" 29 depends on I2C=y && GENERIC_HARDIRQS 30 select MFD_CORE 31 help 32 This supports for Marvell 88PM8606/88PM8607 Power Management IC. 33 This includes the I2C driver and the core APIs _only_, you have to 34 select individual components like voltage regulators, RTC and 35 battery-charger under the corresponding menus. 36 37config MFD_SM501 38 tristate "Support for Silicon Motion SM501" 39 ---help--- 40 This is the core driver for the Silicon Motion SM501 multimedia 41 companion chip. This device is a multifunction device which may 42 provide numerous interfaces including USB host controller, USB gadget, 43 asynchronous serial ports, audio functions, and a dual display video 44 interface. The device may be connected by PCI or local bus with 45 varying functions enabled. 46 47config MFD_SM501_GPIO 48 bool "Export GPIO via GPIO layer" 49 depends on MFD_SM501 && GPIOLIB 50 ---help--- 51 This option uses the gpio library layer to export the 64 GPIO 52 lines on the SM501. The platform data is used to supply the 53 base number for the first GPIO line to register. 54 55config MFD_ASIC3 56 bool "Support for Compaq ASIC3" 57 depends on GENERIC_HARDIRQS && GPIOLIB && ARM 58 select MFD_CORE 59 ---help--- 60 This driver supports the ASIC3 multifunction chip found on many 61 PDAs (mainly iPAQ and HTC based ones) 62 63config MFD_SH_MOBILE_SDHI 64 bool "Support for SuperH Mobile SDHI" 65 depends on SUPERH || ARCH_SHMOBILE 66 select MFD_CORE 67 select TMIO_MMC_DMA 68 ---help--- 69 This driver supports the SDHI hardware block found in many 70 SuperH Mobile SoCs. 71 72config MFD_DAVINCI_VOICECODEC 73 tristate 74 select MFD_CORE 75 76config MFD_DM355EVM_MSP 77 bool "DaVinci DM355 EVM microcontroller" 78 depends on I2C && MACH_DAVINCI_DM355_EVM 79 help 80 This driver supports the MSP430 microcontroller used on these 81 boards. MSP430 firmware manages resets and power sequencing, 82 inputs from buttons and the IR remote, LEDs, an RTC, and more. 83 84config HTC_EGPIO 85 bool "HTC EGPIO support" 86 depends on GENERIC_HARDIRQS && GPIOLIB && ARM 87 help 88 This driver supports the CPLD egpio chip present on 89 several HTC phones. It provides basic support for input 90 pins, output pins, and irqs. 91 92config HTC_PASIC3 93 tristate "HTC PASIC3 LED/DS1WM chip support" 94 select MFD_CORE 95 help 96 This core driver provides register access for the LED/DS1WM 97 chips labeled "AIC2" and "AIC3", found on HTC Blueangel and 98 HTC Magician devices, respectively. Actual functionality is 99 handled by the leds-pasic3 and ds1wm drivers. 100 101config HTC_I2CPLD 102 bool "HTC I2C PLD chip support" 103 depends on I2C=y && GPIOLIB 104 help 105 If you say yes here you get support for the supposed CPLD 106 found on omap850 HTC devices like the HTC Wizard and HTC Herald. 107 This device provides input and output GPIOs through an I2C 108 interface to one or more sub-chips. 109 110config UCB1400_CORE 111 tristate "Philips UCB1400 Core driver" 112 depends on AC97_BUS 113 depends on GPIOLIB 114 help 115 This enables support for the Philips UCB1400 core functions. 116 The UCB1400 is an AC97 audio codec. 117 118 To compile this driver as a module, choose M here: the 119 module will be called ucb1400_core. 120 121config TPS65010 122 tristate "TPS6501x Power Management chips" 123 depends on I2C && GPIOLIB 124 default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK 125 help 126 If you say yes here you get support for the TPS6501x series of 127 Power Management chips. These include voltage regulators, 128 lithium ion/polymer battery charging, and other features that 129 are often used in portable devices like cell phones and cameras. 130 131 This driver can also be built as a module. If so, the module 132 will be called tps65010. 133 134config TPS6507X 135 tristate "TPS6507x Power Management / Touch Screen chips" 136 select MFD_CORE 137 depends on I2C 138 help 139 If you say yes here you get support for the TPS6507x series of 140 Power Management / Touch Screen chips. These include voltage 141 regulators, lithium ion/polymer battery charging, touch screen 142 and other features that are often used in portable devices. 143 This driver can also be built as a module. If so, the module 144 will be called tps6507x. 145 146config MENELAUS 147 bool "Texas Instruments TWL92330/Menelaus PM chip" 148 depends on I2C=y && ARCH_OMAP2 149 help 150 If you say yes here you get support for the Texas Instruments 151 TWL92330/Menelaus Power Management chip. This include voltage 152 regulators, Dual slot memory card transceivers, real-time clock 153 and other features that are often used in portable devices like 154 cell phones and PDAs. 155 156config TWL4030_CORE 157 bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support" 158 depends on I2C=y && GENERIC_HARDIRQS 159 help 160 Say yes here if you have TWL4030 / TWL6030 family chip on your board. 161 This core driver provides register access and IRQ handling 162 facilities, and registers devices for the various functions 163 so that function-specific drivers can bind to them. 164 165 These multi-function chips are found on many OMAP2 and OMAP3 166 boards, providing power management, RTC, GPIO, keypad, a 167 high speed USB OTG transceiver, an audio codec (on most 168 versions) and many other features. 169 170config TWL4030_POWER 171 bool "Support power resources on TWL4030 family chips" 172 depends on TWL4030_CORE && ARM 173 help 174 Say yes here if you want to use the power resources on the 175 TWL4030 family chips. Most of these resources are regulators, 176 which have a separate driver; some are control signals, such 177 as clock request handshaking. 178 179 This driver uses board-specific data to initialize the resources 180 and load scripts controling which resources are switched off/on 181 or reset when a sleep, wakeup or warm reset event occurs. 182 183config TWL4030_CODEC 184 bool 185 depends on TWL4030_CORE 186 select MFD_CORE 187 default n 188 189config TWL6030_PWM 190 tristate "TWL6030 PWM (Pulse Width Modulator) Support" 191 depends on TWL4030_CORE 192 select HAVE_PWM 193 default n 194 help 195 Say yes here if you want support for TWL6030 PWM. 196 This is used to control charging LED brightness. 197 198config MFD_STMPE 199 bool "Support STMicroelectronics STMPE" 200 depends on I2C=y && GENERIC_HARDIRQS 201 select MFD_CORE 202 help 203 Support for the STMPE family of I/O Expanders from 204 STMicroelectronics. 205 206 Currently supported devices are: 207 208 STMPE811: GPIO, Touchscreen 209 STMPE1601: GPIO, Keypad 210 STMPE2401: GPIO, Keypad 211 STMPE2403: GPIO, Keypad 212 213 This driver provides common support for accessing the device, 214 additional drivers must be enabled in order to use the functionality 215 of the device. Currently available sub drivers are: 216 217 GPIO: stmpe-gpio 218 Keypad: stmpe-keypad 219 Touchscreen: stmpe-ts 220 221config MFD_TC35892 222 bool "Support Toshiba TC35892" 223 depends on I2C=y && GENERIC_HARDIRQS 224 select MFD_CORE 225 help 226 Support for the Toshiba TC35892 I/O Expander. 227 228 This driver provides common support for accessing the device, 229 additional drivers must be enabled in order to use the 230 functionality of the device. 231 232config MFD_TMIO 233 bool 234 default n 235 236config TMIO_MMC_DMA 237 bool 238 select DMA_ENGINE 239 select DMADEVICES 240 241config MFD_T7L66XB 242 bool "Support Toshiba T7L66XB" 243 depends on ARM && HAVE_CLK 244 select MFD_CORE 245 select MFD_TMIO 246 help 247 Support for Toshiba Mobile IO Controller T7L66XB 248 249config MFD_TC6387XB 250 bool "Support Toshiba TC6387XB" 251 depends on ARM && HAVE_CLK 252 select MFD_CORE 253 select MFD_TMIO 254 help 255 Support for Toshiba Mobile IO Controller TC6387XB 256 257config MFD_TC6393XB 258 bool "Support Toshiba TC6393XB" 259 depends on GPIOLIB && ARM 260 select MFD_CORE 261 select MFD_TMIO 262 help 263 Support for Toshiba Mobile IO Controller TC6393XB 264 265config PMIC_DA903X 266 bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" 267 depends on I2C=y 268 help 269 Say yes here to support for Dialog Semiconductor DA9030 (a.k.a 270 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC 271 usually found on PXA processors-based platforms. This includes 272 the I2C driver and the core APIs _only_, you have to select 273 individual components like LCD backlight, voltage regulators, 274 LEDs and battery-charger under the corresponding menus. 275 276config PMIC_ADP5520 277 bool "Analog Devices ADP5520/01 MFD PMIC Core Support" 278 depends on I2C=y 279 help 280 Say yes here to add support for Analog Devices AD5520 and ADP5501, 281 Multifunction Power Management IC. This includes 282 the I2C driver and the core APIs _only_, you have to select 283 individual components like LCD backlight, LEDs, GPIOs and Kepad 284 under the corresponding menus. 285 286config MFD_MAX8925 287 bool "Maxim Semiconductor MAX8925 PMIC Support" 288 depends on I2C=y && GENERIC_HARDIRQS 289 select MFD_CORE 290 help 291 Say yes here to support for Maxim Semiconductor MAX8925. This is 292 a Power Management IC. This driver provies common support for 293 accessing the device, additional drivers must be enabled in order 294 to use the functionality of the device. 295 296config MFD_MAX8998 297 bool "Maxim Semiconductor MAX8998 PMIC Support" 298 depends on I2C=y 299 select MFD_CORE 300 help 301 Say yes here to support for Maxim Semiconductor MAX8998. This is 302 a Power Management IC. This driver provies common support for 303 accessing the device, additional drivers must be enabled in order 304 to use the functionality of the device. 305 306config MFD_WM8400 307 tristate "Support Wolfson Microelectronics WM8400" 308 select MFD_CORE 309 depends on I2C 310 help 311 Support for the Wolfson Microelecronics WM8400 PMIC and audio 312 CODEC. This driver provides common support for accessing 313 the device, additional drivers must be enabled in order to use 314 the functionality of the device. 315 316config MFD_WM831X 317 bool "Support Wolfson Microelectronics WM831x/2x PMICs" 318 select MFD_CORE 319 depends on I2C=y && GENERIC_HARDIRQS 320 help 321 Support for the Wolfson Microelecronics WM831x and WM832x PMICs. 322 This driver provides common support for accessing the device, 323 additional drivers must be enabled in order to use the 324 functionality of the device. 325 326config MFD_WM8350 327 bool 328 depends on GENERIC_HARDIRQS 329 330config MFD_WM8350_CONFIG_MODE_0 331 bool 332 depends on MFD_WM8350 333 334config MFD_WM8350_CONFIG_MODE_1 335 bool 336 depends on MFD_WM8350 337 338config MFD_WM8350_CONFIG_MODE_2 339 bool 340 depends on MFD_WM8350 341 342config MFD_WM8350_CONFIG_MODE_3 343 bool 344 depends on MFD_WM8350 345 346config MFD_WM8351_CONFIG_MODE_0 347 bool 348 depends on MFD_WM8350 349 350config MFD_WM8351_CONFIG_MODE_1 351 bool 352 depends on MFD_WM8350 353 354config MFD_WM8351_CONFIG_MODE_2 355 bool 356 depends on MFD_WM8350 357 358config MFD_WM8351_CONFIG_MODE_3 359 bool 360 depends on MFD_WM8350 361 362config MFD_WM8352_CONFIG_MODE_0 363 bool 364 depends on MFD_WM8350 365 366config MFD_WM8352_CONFIG_MODE_1 367 bool 368 depends on MFD_WM8350 369 370config MFD_WM8352_CONFIG_MODE_2 371 bool 372 depends on MFD_WM8350 373 374config MFD_WM8352_CONFIG_MODE_3 375 bool 376 depends on MFD_WM8350 377 378config MFD_WM8350_I2C 379 bool "Support Wolfson Microelectronics WM8350 with I2C" 380 select MFD_WM8350 381 depends on I2C=y && GENERIC_HARDIRQS 382 help 383 The WM8350 is an integrated audio and power management 384 subsystem with watchdog and RTC functionality for embedded 385 systems. This option enables core support for the WM8350 with 386 I2C as the control interface. Additional options must be 387 selected to enable support for the functionality of the chip. 388 389config MFD_WM8994 390 bool "Support Wolfson Microelectronics WM8994" 391 select MFD_CORE 392 depends on I2C=y && GENERIC_HARDIRQS 393 help 394 The WM8994 is a highly integrated hi-fi CODEC designed for 395 smartphone applicatiosn. As well as audio functionality it 396 has on board GPIO and regulator functionality which is 397 supported via the relevant subsystems. This driver provides 398 core support for the WM8994, in order to use the actual 399 functionaltiy of the device other drivers must be enabled. 400 401config MFD_PCF50633 402 tristate "Support for NXP PCF50633" 403 depends on I2C 404 help 405 Say yes here if you have NXP PCF50633 chip on your board. 406 This core driver provides register access and IRQ handling 407 facilities, and registers devices for the various functions 408 so that function-specific drivers can bind to them. 409 410config MFD_MC13783 411 tristate "Support Freescale MC13783" 412 depends on SPI_MASTER 413 select MFD_CORE 414 help 415 Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC. 416 This driver provides common support for accessing the device, 417 additional drivers must be enabled in order to use the 418 functionality of the device. 419 420config PCF50633_ADC 421 tristate "Support for NXP PCF50633 ADC" 422 depends on MFD_PCF50633 423 help 424 Say yes here if you want to include support for ADC in the 425 NXP PCF50633 chip. 426 427config PCF50633_GPIO 428 tristate "Support for NXP PCF50633 GPIO" 429 depends on MFD_PCF50633 430 help 431 Say yes here if you want to include support GPIO for pins on 432 the PCF50633 chip. 433 434config ABX500_CORE 435 bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" 436 default y if ARCH_U300 437 help 438 Say yes here if you have the ABX500 Mixed Signal IC family 439 chips. This core driver expose register access functions. 440 Functionality specific drivers using these functions can 441 remain unchanged when IC changes. Binding of the functions to 442 actual register access is done by the IC core driver. 443 444config AB3100_CORE 445 bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" 446 depends on I2C=y && ABX500_CORE 447 default y if ARCH_U300 448 help 449 Select this to enable the AB3100 Mixed Signal IC core 450 functionality. This connects to a AB3100 on the I2C bus 451 and expose a number of symbols needed for dependent devices 452 to read and write registers and subscribe to events from 453 this multi-functional IC. This is needed to use other features 454 of the AB3100 such as battery-backed RTC, charging control, 455 LEDs, vibrator, system power and temperature, power management 456 and ALSA sound. 457 458config AB3100_OTP 459 tristate "ST-Ericsson AB3100 OTP functions" 460 depends on AB3100_CORE 461 default y if AB3100_CORE 462 help 463 Select this to enable the AB3100 Mixed Signal IC OTP (one-time 464 programmable memory) support. This exposes a sysfs file to read 465 out OTP values. 466 467config EZX_PCAP 468 bool "PCAP Support" 469 depends on GENERIC_HARDIRQS && SPI_MASTER 470 help 471 This enables the PCAP ASIC present on EZX Phones. This is 472 needed for MMC, TouchScreen, Sound, USB, etc.. 473 474config AB8500_CORE 475 bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" 476 depends on SPI=y && GENERIC_HARDIRQS 477 select MFD_CORE 478 help 479 Select this option to enable access to AB8500 power management 480 chip. This connects to U8500 on the SSP/SPI bus and exports 481 read/write functions for the devices to get access to this chip. 482 This chip embeds various other multimedia funtionalities as well. 483 484config AB3550_CORE 485 bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions" 486 select MFD_CORE 487 depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE 488 help 489 Select this to enable the AB3550 Mixed Signal IC core 490 functionality. This connects to a AB3550 on the I2C bus 491 and expose a number of symbols needed for dependent devices 492 to read and write registers and subscribe to events from 493 this multi-functional IC. This is needed to use other features 494 of the AB3550 such as battery-backed RTC, charging control, 495 LEDs, vibrator, system power and temperature, power management 496 and ALSA sound. 497 498config MFD_TIMBERDALE 499 tristate "Support for the Timberdale FPGA" 500 select MFD_CORE 501 depends on PCI && GPIOLIB 502 ---help--- 503 This is the core driver for the timberdale FPGA. This device is a 504 multifunction device which exposes numerous platform devices. 505 506 The timberdale FPGA can be found on the Intel Atom development board 507 for in-vehicle infontainment, called Russellville. 508 509config LPC_SCH 510 tristate "Intel SCH LPC" 511 depends on PCI 512 select MFD_CORE 513 help 514 LPC bridge function of the Intel SCH provides support for 515 System Management Bus and General Purpose I/O. 516 517config MFD_RDC321X 518 tristate "Support for RDC-R321x southbridge" 519 select MFD_CORE 520 depends on PCI 521 help 522 Say yes here if you want to have support for the RDC R-321x SoC 523 southbridge which provides access to GPIOs and Watchdog using the 524 southbridge PCI device configuration space. 525 526config MFD_JANZ_CMODIO 527 tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board" 528 select MFD_CORE 529 depends on PCI 530 help 531 This is the core driver for the Janz CMOD-IO PCI MODULbus 532 carrier board. This device is a PCI to MODULbus bridge which may 533 host many different types of MODULbus daughterboards, including 534 CAN and GPIO controllers. 535 536config MFD_JZ4740_ADC 537 tristate "Support for the JZ4740 SoC ADC core" 538 select MFD_CORE 539 depends on MACH_JZ4740 540 help 541 Say yes here if you want support for the ADC unit in the JZ4740 SoC. 542 This driver is necessary for jz4740-battery and jz4740-hwmon driver. 543 544config MFD_TPS6586X 545 tristate "TPS6586x Power Management chips" 546 depends on I2C && GPIOLIB 547 select MFD_CORE 548 help 549 If you say yes here you get support for the TPS6586X series of 550 Power Management chips. 551 This driver provides common support for accessing the device, 552 additional drivers must be enabled in order to use the 553 functionality of the device. 554 555 This driver can also be built as a module. If so, the module 556 will be called tps6586x. 557 558endif # MFD_SUPPORT 559 560menu "Multimedia Capabilities Port drivers" 561 depends on ARCH_SA1100 562 563config MCP 564 tristate 565 566# Interface drivers 567config MCP_SA11X0 568 tristate "Support SA11x0 MCP interface" 569 depends on ARCH_SA1100 570 select MCP 571 572# Chip drivers 573config MCP_UCB1200 574 tristate "Support for UCB1200 / UCB1300" 575 depends on MCP 576 577config MCP_UCB1200_TS 578 tristate "Touchscreen interface support" 579 depends on MCP_UCB1200 && INPUT 580 581endmenu 582