| 1 | # |
| 2 | # Multifunction miscellaneous devices |
| 3 | # |
| 4 | |
| 5 | if HAS_IOMEM |
| 6 | menu "Multifunction device drivers" |
| 7 | |
| 8 | config MFD_CORE |
| 9 | tristate |
| 10 | select IRQ_DOMAIN |
| 11 | default n |
| 12 | |
| 13 | config MFD_88PM860X |
| 14 | bool "Support Marvell 88PM8606/88PM8607" |
| 15 | depends on I2C=y && GENERIC_HARDIRQS |
| 16 | select REGMAP_I2C |
| 17 | select MFD_CORE |
| 18 | help |
| 19 | This supports for Marvell 88PM8606/88PM8607 Power Management IC. |
| 20 | This includes the I2C driver and the core APIs _only_, you have to |
| 21 | select individual components like voltage regulators, RTC and |
| 22 | battery-charger under the corresponding menus. |
| 23 | |
| 24 | config MFD_88PM800 |
| 25 | tristate "Support Marvell 88PM800" |
| 26 | depends on I2C=y && GENERIC_HARDIRQS |
| 27 | select REGMAP_I2C |
| 28 | select REGMAP_IRQ |
| 29 | select MFD_CORE |
| 30 | help |
| 31 | This supports for Marvell 88PM800 Power Management IC. |
| 32 | This includes the I2C driver and the core APIs _only_, you have to |
| 33 | select individual components like voltage regulators, RTC and |
| 34 | battery-charger under the corresponding menus. |
| 35 | |
| 36 | config MFD_88PM805 |
| 37 | tristate "Support Marvell 88PM805" |
| 38 | depends on I2C=y && GENERIC_HARDIRQS |
| 39 | select REGMAP_I2C |
| 40 | select REGMAP_IRQ |
| 41 | select MFD_CORE |
| 42 | help |
| 43 | This supports for Marvell 88PM805 Power Management IC. This includes |
| 44 | the I2C driver and the core APIs _only_, you have to select individual |
| 45 | components like codec device, headset/Mic device under the |
| 46 | corresponding menus. |
| 47 | |
| 48 | config MFD_SM501 |
| 49 | tristate "Support for Silicon Motion SM501" |
| 50 | ---help--- |
| 51 | This is the core driver for the Silicon Motion SM501 multimedia |
| 52 | companion chip. This device is a multifunction device which may |
| 53 | provide numerous interfaces including USB host controller, USB gadget, |
| 54 | asynchronous serial ports, audio functions, and a dual display video |
| 55 | interface. The device may be connected by PCI or local bus with |
| 56 | varying functions enabled. |
| 57 | |
| 58 | config MFD_SM501_GPIO |
| 59 | bool "Export GPIO via GPIO layer" |
| 60 | depends on MFD_SM501 && GPIOLIB |
| 61 | ---help--- |
| 62 | This option uses the gpio library layer to export the 64 GPIO |
| 63 | lines on the SM501. The platform data is used to supply the |
| 64 | base number for the first GPIO line to register. |
| 65 | |
| 66 | config MFD_ASIC3 |
| 67 | bool "Support for Compaq ASIC3" |
| 68 | depends on GENERIC_HARDIRQS && GPIOLIB && ARM |
| 69 | select MFD_CORE |
| 70 | ---help--- |
| 71 | This driver supports the ASIC3 multifunction chip found on many |
| 72 | PDAs (mainly iPAQ and HTC based ones) |
| 73 | |
| 74 | config MFD_DAVINCI_VOICECODEC |
| 75 | tristate |
| 76 | select MFD_CORE |
| 77 | |
| 78 | config MFD_DM355EVM_MSP |
| 79 | bool "DaVinci DM355 EVM microcontroller" |
| 80 | depends on I2C=y && MACH_DAVINCI_DM355_EVM |
| 81 | help |
| 82 | This driver supports the MSP430 microcontroller used on these |
| 83 | boards. MSP430 firmware manages resets and power sequencing, |
| 84 | inputs from buttons and the IR remote, LEDs, an RTC, and more. |
| 85 | |
| 86 | config MFD_TI_SSP |
| 87 | tristate "TI Sequencer Serial Port support" |
| 88 | depends on ARCH_DAVINCI_TNETV107X |
| 89 | select MFD_CORE |
| 90 | ---help--- |
| 91 | Say Y here if you want support for the Sequencer Serial Port |
| 92 | in a Texas Instruments TNETV107X SoC. |
| 93 | |
| 94 | To compile this driver as a module, choose M here: the |
| 95 | module will be called ti-ssp. |
| 96 | |
| 97 | config HTC_EGPIO |
| 98 | bool "HTC EGPIO support" |
| 99 | depends on GENERIC_HARDIRQS && GPIOLIB && ARM |
| 100 | help |
| 101 | This driver supports the CPLD egpio chip present on |
| 102 | several HTC phones. It provides basic support for input |
| 103 | pins, output pins, and irqs. |
| 104 | |
| 105 | config HTC_PASIC3 |
| 106 | tristate "HTC PASIC3 LED/DS1WM chip support" |
| 107 | select MFD_CORE |
| 108 | help |
| 109 | This core driver provides register access for the LED/DS1WM |
| 110 | chips labeled "AIC2" and "AIC3", found on HTC Blueangel and |
| 111 | HTC Magician devices, respectively. Actual functionality is |
| 112 | handled by the leds-pasic3 and ds1wm drivers. |
| 113 | |
| 114 | config HTC_I2CPLD |
| 115 | bool "HTC I2C PLD chip support" |
| 116 | depends on I2C=y && GPIOLIB |
| 117 | help |
| 118 | If you say yes here you get support for the supposed CPLD |
| 119 | found on omap850 HTC devices like the HTC Wizard and HTC Herald. |
| 120 | This device provides input and output GPIOs through an I2C |
| 121 | interface to one or more sub-chips. |
| 122 | |
| 123 | config UCB1400_CORE |
| 124 | tristate "Philips UCB1400 Core driver" |
| 125 | depends on AC97_BUS |
| 126 | depends on GPIOLIB |
| 127 | help |
| 128 | This enables support for the Philips UCB1400 core functions. |
| 129 | The UCB1400 is an AC97 audio codec. |
| 130 | |
| 131 | To compile this driver as a module, choose M here: the |
| 132 | module will be called ucb1400_core. |
| 133 | |
| 134 | config MFD_LM3533 |
| 135 | tristate "LM3533 Lighting Power chip" |
| 136 | depends on I2C |
| 137 | select MFD_CORE |
| 138 | select REGMAP_I2C |
| 139 | help |
| 140 | Say yes here to enable support for National Semiconductor / TI |
| 141 | LM3533 Lighting Power chips. |
| 142 | |
| 143 | This driver provides common support for accessing the device; |
| 144 | additional drivers must be enabled in order to use the LED, |
| 145 | backlight or ambient-light-sensor functionality of the device. |
| 146 | |
| 147 | config TPS6105X |
| 148 | tristate "TPS61050/61052 Boost Converters" |
| 149 | depends on I2C |
| 150 | select REGULATOR |
| 151 | select MFD_CORE |
| 152 | select REGULATOR_FIXED_VOLTAGE |
| 153 | help |
| 154 | This option enables a driver for the TP61050/TPS61052 |
| 155 | high-power "white LED driver". This boost converter is |
| 156 | sometimes used for other things than white LEDs, and |
| 157 | also contains a GPIO pin. |
| 158 | |
| 159 | config TPS65010 |
| 160 | tristate "TPS6501x Power Management chips" |
| 161 | depends on I2C && GPIOLIB |
| 162 | default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK |
| 163 | help |
| 164 | If you say yes here you get support for the TPS6501x series of |
| 165 | Power Management chips. These include voltage regulators, |
| 166 | lithium ion/polymer battery charging, and other features that |
| 167 | are often used in portable devices like cell phones and cameras. |
| 168 | |
| 169 | This driver can also be built as a module. If so, the module |
| 170 | will be called tps65010. |
| 171 | |
| 172 | config TPS6507X |
| 173 | tristate "TPS6507x Power Management / Touch Screen chips" |
| 174 | select MFD_CORE |
| 175 | depends on I2C |
| 176 | help |
| 177 | If you say yes here you get support for the TPS6507x series of |
| 178 | Power Management / Touch Screen chips. These include voltage |
| 179 | regulators, lithium ion/polymer battery charging, touch screen |
| 180 | and other features that are often used in portable devices. |
| 181 | This driver can also be built as a module. If so, the module |
| 182 | will be called tps6507x. |
| 183 | |
| 184 | config MFD_TPS65217 |
| 185 | tristate "TPS65217 Power Management / White LED chips" |
| 186 | depends on I2C |
| 187 | select MFD_CORE |
| 188 | select REGMAP_I2C |
| 189 | help |
| 190 | If you say yes here you get support for the TPS65217 series of |
| 191 | Power Management / White LED chips. |
| 192 | These include voltage regulators, lithium ion/polymer battery |
| 193 | charger, wled and other features that are often used in portable |
| 194 | devices. |
| 195 | |
| 196 | This driver can also be built as a module. If so, the module |
| 197 | will be called tps65217. |
| 198 | |
| 199 | config MFD_TPS6586X |
| 200 | bool "TPS6586x Power Management chips" |
| 201 | depends on I2C=y && GENERIC_HARDIRQS |
| 202 | select MFD_CORE |
| 203 | select REGMAP_I2C |
| 204 | depends on REGULATOR |
| 205 | help |
| 206 | If you say yes here you get support for the TPS6586X series of |
| 207 | Power Management chips. |
| 208 | This driver provides common support for accessing the device, |
| 209 | additional drivers must be enabled in order to use the |
| 210 | functionality of the device. |
| 211 | |
| 212 | This driver can also be built as a module. If so, the module |
| 213 | will be called tps6586x. |
| 214 | |
| 215 | config MFD_TPS65910 |
| 216 | bool "TPS65910 Power Management chip" |
| 217 | depends on I2C=y && GPIOLIB |
| 218 | select MFD_CORE |
| 219 | select REGMAP_I2C |
| 220 | select IRQ_DOMAIN |
| 221 | help |
| 222 | if you say yes here you get support for the TPS65910 series of |
| 223 | Power Management chips. |
| 224 | |
| 225 | config MFD_TPS65912 |
| 226 | bool |
| 227 | depends on GPIOLIB |
| 228 | |
| 229 | config MFD_TPS65912_I2C |
| 230 | bool "TPS65912 Power Management chip with I2C" |
| 231 | select MFD_CORE |
| 232 | select MFD_TPS65912 |
| 233 | depends on I2C=y && GPIOLIB |
| 234 | help |
| 235 | If you say yes here you get support for the TPS65912 series of |
| 236 | PM chips with I2C interface. |
| 237 | |
| 238 | config MFD_TPS65912_SPI |
| 239 | bool "TPS65912 Power Management chip with SPI" |
| 240 | select MFD_CORE |
| 241 | select MFD_TPS65912 |
| 242 | depends on SPI_MASTER && GPIOLIB |
| 243 | help |
| 244 | If you say yes here you get support for the TPS65912 series of |
| 245 | PM chips with SPI interface. |
| 246 | |
| 247 | config MENELAUS |
| 248 | bool "Texas Instruments TWL92330/Menelaus PM chip" |
| 249 | depends on I2C=y && ARCH_OMAP2 |
| 250 | help |
| 251 | If you say yes here you get support for the Texas Instruments |
| 252 | TWL92330/Menelaus Power Management chip. This include voltage |
| 253 | regulators, Dual slot memory card transceivers, real-time clock |
| 254 | and other features that are often used in portable devices like |
| 255 | cell phones and PDAs. |
| 256 | |
| 257 | config TWL4030_CORE |
| 258 | bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support" |
| 259 | depends on I2C=y && GENERIC_HARDIRQS |
| 260 | select IRQ_DOMAIN |
| 261 | help |
| 262 | Say yes here if you have TWL4030 / TWL6030 family chip on your board. |
| 263 | This core driver provides register access and IRQ handling |
| 264 | facilities, and registers devices for the various functions |
| 265 | so that function-specific drivers can bind to them. |
| 266 | |
| 267 | These multi-function chips are found on many OMAP2 and OMAP3 |
| 268 | boards, providing power management, RTC, GPIO, keypad, a |
| 269 | high speed USB OTG transceiver, an audio codec (on most |
| 270 | versions) and many other features. |
| 271 | |
| 272 | config TWL4030_MADC |
| 273 | tristate "Texas Instruments TWL4030 MADC" |
| 274 | depends on TWL4030_CORE |
| 275 | help |
| 276 | This driver provides support for triton TWL4030-MADC. The |
| 277 | driver supports both RT and SW conversion methods. |
| 278 | |
| 279 | This driver can be built as a module. If so it will be |
| 280 | named twl4030-madc |
| 281 | |
| 282 | config TWL4030_POWER |
| 283 | bool "Support power resources on TWL4030 family chips" |
| 284 | depends on TWL4030_CORE && ARM |
| 285 | help |
| 286 | Say yes here if you want to use the power resources on the |
| 287 | TWL4030 family chips. Most of these resources are regulators, |
| 288 | which have a separate driver; some are control signals, such |
| 289 | as clock request handshaking. |
| 290 | |
| 291 | This driver uses board-specific data to initialize the resources |
| 292 | and load scripts controlling which resources are switched off/on |
| 293 | or reset when a sleep, wakeup or warm reset event occurs. |
| 294 | |
| 295 | config MFD_TWL4030_AUDIO |
| 296 | bool |
| 297 | depends on TWL4030_CORE |
| 298 | select MFD_CORE |
| 299 | default n |
| 300 | |
| 301 | config TWL6040_CORE |
| 302 | bool "Support for TWL6040 audio codec" |
| 303 | depends on I2C=y && GENERIC_HARDIRQS |
| 304 | select MFD_CORE |
| 305 | select REGMAP_I2C |
| 306 | select IRQ_DOMAIN |
| 307 | default n |
| 308 | help |
| 309 | Say yes here if you want support for Texas Instruments TWL6040 audio |
| 310 | codec. |
| 311 | This driver provides common support for accessing the device, |
| 312 | additional drivers must be enabled in order to use the |
| 313 | functionality of the device (audio, vibra). |
| 314 | |
| 315 | config MFD_STMPE |
| 316 | bool "Support STMicroelectronics STMPE" |
| 317 | depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS |
| 318 | select MFD_CORE |
| 319 | help |
| 320 | Support for the STMPE family of I/O Expanders from |
| 321 | STMicroelectronics. |
| 322 | |
| 323 | Currently supported devices are: |
| 324 | |
| 325 | STMPE811: GPIO, Touchscreen |
| 326 | STMPE1601: GPIO, Keypad |
| 327 | STMPE2401: GPIO, Keypad |
| 328 | STMPE2403: GPIO, Keypad |
| 329 | |
| 330 | This driver provides common support for accessing the device, |
| 331 | additional drivers must be enabled in order to use the functionality |
| 332 | of the device. Currently available sub drivers are: |
| 333 | |
| 334 | GPIO: stmpe-gpio |
| 335 | Keypad: stmpe-keypad |
| 336 | Touchscreen: stmpe-ts |
| 337 | |
| 338 | menu "STMPE Interface Drivers" |
| 339 | depends on MFD_STMPE |
| 340 | |
| 341 | config STMPE_I2C |
| 342 | bool "STMPE I2C Inteface" |
| 343 | depends on I2C=y |
| 344 | default y |
| 345 | help |
| 346 | This is used to enable I2C interface of STMPE |
| 347 | |
| 348 | config STMPE_SPI |
| 349 | bool "STMPE SPI Inteface" |
| 350 | depends on SPI_MASTER |
| 351 | help |
| 352 | This is used to enable SPI interface of STMPE |
| 353 | endmenu |
| 354 | |
| 355 | config MFD_TC3589X |
| 356 | bool "Support Toshiba TC35892 and variants" |
| 357 | depends on I2C=y && GENERIC_HARDIRQS |
| 358 | select MFD_CORE |
| 359 | help |
| 360 | Support for the Toshiba TC35892 and variants I/O Expander. |
| 361 | |
| 362 | This driver provides common support for accessing the device, |
| 363 | additional drivers must be enabled in order to use the |
| 364 | functionality of the device. |
| 365 | |
| 366 | config MFD_TMIO |
| 367 | bool |
| 368 | default n |
| 369 | |
| 370 | config MFD_T7L66XB |
| 371 | bool "Support Toshiba T7L66XB" |
| 372 | depends on ARM && HAVE_CLK |
| 373 | select MFD_CORE |
| 374 | select MFD_TMIO |
| 375 | help |
| 376 | Support for Toshiba Mobile IO Controller T7L66XB |
| 377 | |
| 378 | config MFD_SMSC |
| 379 | bool "Support for the SMSC ECE1099 series chips" |
| 380 | depends on I2C=y |
| 381 | select MFD_CORE |
| 382 | select REGMAP_I2C |
| 383 | help |
| 384 | If you say yes here you get support for the |
| 385 | ece1099 chips from SMSC. |
| 386 | |
| 387 | To compile this driver as a module, choose M here: the |
| 388 | module will be called smsc. |
| 389 | |
| 390 | config MFD_TC6387XB |
| 391 | bool "Support Toshiba TC6387XB" |
| 392 | depends on ARM && HAVE_CLK |
| 393 | select MFD_CORE |
| 394 | select MFD_TMIO |
| 395 | help |
| 396 | Support for Toshiba Mobile IO Controller TC6387XB |
| 397 | |
| 398 | config MFD_TC6393XB |
| 399 | bool "Support Toshiba TC6393XB" |
| 400 | depends on ARM && HAVE_CLK |
| 401 | select GPIOLIB |
| 402 | select MFD_CORE |
| 403 | select MFD_TMIO |
| 404 | help |
| 405 | Support for Toshiba Mobile IO Controller TC6393XB |
| 406 | |
| 407 | config PMIC_DA903X |
| 408 | bool "Dialog Semiconductor DA9030/DA9034 PMIC Support" |
| 409 | depends on I2C=y |
| 410 | help |
| 411 | Say yes here to support for Dialog Semiconductor DA9030 (a.k.a |
| 412 | ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC |
| 413 | usually found on PXA processors-based platforms. This includes |
| 414 | the I2C driver and the core APIs _only_, you have to select |
| 415 | individual components like LCD backlight, voltage regulators, |
| 416 | LEDs and battery-charger under the corresponding menus. |
| 417 | |
| 418 | config PMIC_DA9052 |
| 419 | bool |
| 420 | select MFD_CORE |
| 421 | |
| 422 | config MFD_DA9052_SPI |
| 423 | bool "Support Dialog Semiconductor DA9052/53 PMIC variants with SPI" |
| 424 | select REGMAP_SPI |
| 425 | select REGMAP_IRQ |
| 426 | select PMIC_DA9052 |
| 427 | depends on SPI_MASTER=y |
| 428 | help |
| 429 | Support for the Dialog Semiconductor DA9052 PMIC |
| 430 | when controlled using SPI. This driver provides common support |
| 431 | for accessing the device, additional drivers must be enabled in |
| 432 | order to use the functionality of the device. |
| 433 | |
| 434 | config MFD_DA9052_I2C |
| 435 | bool "Support Dialog Semiconductor DA9052/53 PMIC variants with I2C" |
| 436 | select REGMAP_I2C |
| 437 | select REGMAP_IRQ |
| 438 | select PMIC_DA9052 |
| 439 | depends on I2C=y |
| 440 | help |
| 441 | Support for the Dialog Semiconductor DA9052 PMIC |
| 442 | when controlled using I2C. This driver provides common support |
| 443 | for accessing the device, additional drivers must be enabled in |
| 444 | order to use the functionality of the device. |
| 445 | |
| 446 | config MFD_DA9055 |
| 447 | bool "Dialog Semiconductor DA9055 PMIC Support" |
| 448 | select REGMAP_I2C |
| 449 | select REGMAP_IRQ |
| 450 | select PMIC_DA9055 |
| 451 | select MFD_CORE |
| 452 | depends on I2C=y |
| 453 | help |
| 454 | Say yes here for support of Dialog Semiconductor DA9055. This is |
| 455 | a Power Management IC. This driver provides common support for |
| 456 | accessing the device as well as the I2C interface to the chip itself. |
| 457 | Additional drivers must be enabled in order to use the functionality |
| 458 | of the device. |
| 459 | |
| 460 | This driver can be built as a module. If built as a module it will be |
| 461 | called "da9055" |
| 462 | |
| 463 | config PMIC_ADP5520 |
| 464 | bool "Analog Devices ADP5520/01 MFD PMIC Core Support" |
| 465 | depends on I2C=y |
| 466 | help |
| 467 | Say yes here to add support for Analog Devices AD5520 and ADP5501, |
| 468 | Multifunction Power Management IC. This includes |
| 469 | the I2C driver and the core APIs _only_, you have to select |
| 470 | individual components like LCD backlight, LEDs, GPIOs and Kepad |
| 471 | under the corresponding menus. |
| 472 | |
| 473 | config MFD_LP8788 |
| 474 | bool "Texas Instruments LP8788 Power Management Unit Driver" |
| 475 | depends on I2C=y |
| 476 | select MFD_CORE |
| 477 | select REGMAP_I2C |
| 478 | select IRQ_DOMAIN |
| 479 | help |
| 480 | TI LP8788 PMU supports regulators, battery charger, RTC, |
| 481 | ADC, backlight driver and current sinks. |
| 482 | |
| 483 | config MFD_MAX77686 |
| 484 | bool "Maxim Semiconductor MAX77686 PMIC Support" |
| 485 | depends on I2C=y && GENERIC_HARDIRQS |
| 486 | select MFD_CORE |
| 487 | select REGMAP_I2C |
| 488 | select IRQ_DOMAIN |
| 489 | help |
| 490 | Say yes here to support for Maxim Semiconductor MAX77686. |
| 491 | This is a Power Management IC with RTC on chip. |
| 492 | This driver provides common support for accessing the device; |
| 493 | additional drivers must be enabled in order to use the functionality |
| 494 | of the device. |
| 495 | |
| 496 | config MFD_MAX77693 |
| 497 | bool "Maxim Semiconductor MAX77693 PMIC Support" |
| 498 | depends on I2C=y && GENERIC_HARDIRQS |
| 499 | select MFD_CORE |
| 500 | select REGMAP_I2C |
| 501 | help |
| 502 | Say yes here to support for Maxim Semiconductor MAX77693. |
| 503 | This is a companion Power Management IC with Flash, Haptic, Charger, |
| 504 | and MUIC(Micro USB Interface Controller) controls on chip. |
| 505 | This driver provides common support for accessing the device; |
| 506 | additional drivers must be enabled in order to use the functionality |
| 507 | of the device. |
| 508 | |
| 509 | config MFD_MAX8907 |
| 510 | tristate "Maxim Semiconductor MAX8907 PMIC Support" |
| 511 | select MFD_CORE |
| 512 | depends on I2C=y && GENERIC_HARDIRQS |
| 513 | select REGMAP_I2C |
| 514 | select REGMAP_IRQ |
| 515 | help |
| 516 | Say yes here to support for Maxim Semiconductor MAX8907. This is |
| 517 | a Power Management IC. This driver provides common support for |
| 518 | accessing the device; additional drivers must be enabled in order |
| 519 | to use the functionality of the device. |
| 520 | |
| 521 | config MFD_MAX8925 |
| 522 | bool "Maxim Semiconductor MAX8925 PMIC Support" |
| 523 | depends on I2C=y && GENERIC_HARDIRQS |
| 524 | select MFD_CORE |
| 525 | help |
| 526 | Say yes here to support for Maxim Semiconductor MAX8925. This is |
| 527 | a Power Management IC. This driver provides common support for |
| 528 | accessing the device, additional drivers must be enabled in order |
| 529 | to use the functionality of the device. |
| 530 | |
| 531 | config MFD_MAX8997 |
| 532 | bool "Maxim Semiconductor MAX8997/8966 PMIC Support" |
| 533 | depends on I2C=y && GENERIC_HARDIRQS |
| 534 | select MFD_CORE |
| 535 | select IRQ_DOMAIN |
| 536 | help |
| 537 | Say yes here to support for Maxim Semiconductor MAX8997/8966. |
| 538 | This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic, |
| 539 | MUIC controls on chip. |
| 540 | This driver provides common support for accessing the device; |
| 541 | additional drivers must be enabled in order to use the functionality |
| 542 | of the device. |
| 543 | |
| 544 | config MFD_MAX8998 |
| 545 | bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support" |
| 546 | depends on I2C=y && GENERIC_HARDIRQS |
| 547 | select MFD_CORE |
| 548 | help |
| 549 | Say yes here to support for Maxim Semiconductor MAX8998 and |
| 550 | National Semiconductor LP3974. This is a Power Management IC. |
| 551 | This driver provides common support for accessing the device, |
| 552 | additional drivers must be enabled in order to use the functionality |
| 553 | of the device. |
| 554 | |
| 555 | config MFD_SEC_CORE |
| 556 | bool "SAMSUNG Electronics PMIC Series Support" |
| 557 | depends on I2C=y && GENERIC_HARDIRQS |
| 558 | select MFD_CORE |
| 559 | select REGMAP_I2C |
| 560 | select REGMAP_IRQ |
| 561 | help |
| 562 | Support for the Samsung Electronics MFD series. |
| 563 | This driver provides common support for accessing the device, |
| 564 | additional drivers must be enabled in order to use the functionality |
| 565 | of the device |
| 566 | |
| 567 | config MFD_ARIZONA |
| 568 | select REGMAP |
| 569 | select REGMAP_IRQ |
| 570 | select MFD_CORE |
| 571 | bool |
| 572 | |
| 573 | config MFD_ARIZONA_I2C |
| 574 | tristate "Support Wolfson Microelectronics Arizona platform with I2C" |
| 575 | select MFD_ARIZONA |
| 576 | select MFD_CORE |
| 577 | select REGMAP_I2C |
| 578 | depends on I2C |
| 579 | help |
| 580 | Support for the Wolfson Microelectronics Arizona platform audio SoC |
| 581 | core functionality controlled via I2C. |
| 582 | |
| 583 | config MFD_ARIZONA_SPI |
| 584 | tristate "Support Wolfson Microelectronics Arizona platform with SPI" |
| 585 | select MFD_ARIZONA |
| 586 | select MFD_CORE |
| 587 | select REGMAP_SPI |
| 588 | depends on SPI_MASTER |
| 589 | help |
| 590 | Support for the Wolfson Microelectronics Arizona platform audio SoC |
| 591 | core functionality controlled via I2C. |
| 592 | |
| 593 | config MFD_WM5102 |
| 594 | bool "Support Wolfson Microelectronics WM5102" |
| 595 | depends on MFD_ARIZONA |
| 596 | help |
| 597 | Support for Wolfson Microelectronics WM5102 low power audio SoC |
| 598 | |
| 599 | config MFD_WM5110 |
| 600 | bool "Support Wolfson Microelectronics WM5110" |
| 601 | depends on MFD_ARIZONA |
| 602 | help |
| 603 | Support for Wolfson Microelectronics WM5110 low power audio SoC |
| 604 | |
| 605 | config MFD_WM8400 |
| 606 | bool "Support Wolfson Microelectronics WM8400" |
| 607 | select MFD_CORE |
| 608 | depends on I2C=y |
| 609 | select REGMAP_I2C |
| 610 | help |
| 611 | Support for the Wolfson Microelecronics WM8400 PMIC and audio |
| 612 | CODEC. This driver provides common support for accessing |
| 613 | the device, additional drivers must be enabled in order to use |
| 614 | the functionality of the device. |
| 615 | |
| 616 | config MFD_WM831X |
| 617 | bool |
| 618 | depends on GENERIC_HARDIRQS |
| 619 | |
| 620 | config MFD_WM831X_I2C |
| 621 | bool "Support Wolfson Microelectronics WM831x/2x PMICs with I2C" |
| 622 | select MFD_CORE |
| 623 | select MFD_WM831X |
| 624 | select REGMAP_I2C |
| 625 | select IRQ_DOMAIN |
| 626 | depends on I2C=y && GENERIC_HARDIRQS |
| 627 | help |
| 628 | Support for the Wolfson Microelecronics WM831x and WM832x PMICs |
| 629 | when controlled using I2C. This driver provides common support |
| 630 | for accessing the device, additional drivers must be enabled in |
| 631 | order to use the functionality of the device. |
| 632 | |
| 633 | config MFD_WM831X_SPI |
| 634 | bool "Support Wolfson Microelectronics WM831x/2x PMICs with SPI" |
| 635 | select MFD_CORE |
| 636 | select MFD_WM831X |
| 637 | select REGMAP_SPI |
| 638 | select IRQ_DOMAIN |
| 639 | depends on SPI_MASTER && GENERIC_HARDIRQS |
| 640 | help |
| 641 | Support for the Wolfson Microelecronics WM831x and WM832x PMICs |
| 642 | when controlled using SPI. This driver provides common support |
| 643 | for accessing the device, additional drivers must be enabled in |
| 644 | order to use the functionality of the device. |
| 645 | |
| 646 | config MFD_WM8350 |
| 647 | bool |
| 648 | depends on GENERIC_HARDIRQS |
| 649 | |
| 650 | config MFD_WM8350_CONFIG_MODE_0 |
| 651 | bool |
| 652 | depends on MFD_WM8350 |
| 653 | |
| 654 | config MFD_WM8350_CONFIG_MODE_1 |
| 655 | bool |
| 656 | depends on MFD_WM8350 |
| 657 | |
| 658 | config MFD_WM8350_CONFIG_MODE_2 |
| 659 | bool |
| 660 | depends on MFD_WM8350 |
| 661 | |
| 662 | config MFD_WM8350_CONFIG_MODE_3 |
| 663 | bool |
| 664 | depends on MFD_WM8350 |
| 665 | |
| 666 | config MFD_WM8351_CONFIG_MODE_0 |
| 667 | bool |
| 668 | depends on MFD_WM8350 |
| 669 | |
| 670 | config MFD_WM8351_CONFIG_MODE_1 |
| 671 | bool |
| 672 | depends on MFD_WM8350 |
| 673 | |
| 674 | config MFD_WM8351_CONFIG_MODE_2 |
| 675 | bool |
| 676 | depends on MFD_WM8350 |
| 677 | |
| 678 | config MFD_WM8351_CONFIG_MODE_3 |
| 679 | bool |
| 680 | depends on MFD_WM8350 |
| 681 | |
| 682 | config MFD_WM8352_CONFIG_MODE_0 |
| 683 | bool |
| 684 | depends on MFD_WM8350 |
| 685 | |
| 686 | config MFD_WM8352_CONFIG_MODE_1 |
| 687 | bool |
| 688 | depends on MFD_WM8350 |
| 689 | |
| 690 | config MFD_WM8352_CONFIG_MODE_2 |
| 691 | bool |
| 692 | depends on MFD_WM8350 |
| 693 | |
| 694 | config MFD_WM8352_CONFIG_MODE_3 |
| 695 | bool |
| 696 | depends on MFD_WM8350 |
| 697 | |
| 698 | config MFD_WM8350_I2C |
| 699 | bool "Support Wolfson Microelectronics WM8350 with I2C" |
| 700 | select MFD_WM8350 |
| 701 | depends on I2C=y && GENERIC_HARDIRQS |
| 702 | help |
| 703 | The WM8350 is an integrated audio and power management |
| 704 | subsystem with watchdog and RTC functionality for embedded |
| 705 | systems. This option enables core support for the WM8350 with |
| 706 | I2C as the control interface. Additional options must be |
| 707 | selected to enable support for the functionality of the chip. |
| 708 | |
| 709 | config MFD_WM8994 |
| 710 | bool "Support Wolfson Microelectronics WM8994" |
| 711 | select MFD_CORE |
| 712 | select REGMAP_I2C |
| 713 | select REGMAP_IRQ |
| 714 | depends on I2C=y && GENERIC_HARDIRQS |
| 715 | help |
| 716 | The WM8994 is a highly integrated hi-fi CODEC designed for |
| 717 | smartphone applicatiosn. As well as audio functionality it |
| 718 | has on board GPIO and regulator functionality which is |
| 719 | supported via the relevant subsystems. This driver provides |
| 720 | core support for the WM8994, in order to use the actual |
| 721 | functionaltiy of the device other drivers must be enabled. |
| 722 | |
| 723 | config MFD_PCF50633 |
| 724 | tristate "Support for NXP PCF50633" |
| 725 | depends on I2C |
| 726 | select REGMAP_I2C |
| 727 | help |
| 728 | Say yes here if you have NXP PCF50633 chip on your board. |
| 729 | This core driver provides register access and IRQ handling |
| 730 | facilities, and registers devices for the various functions |
| 731 | so that function-specific drivers can bind to them. |
| 732 | |
| 733 | config PCF50633_ADC |
| 734 | tristate "Support for NXP PCF50633 ADC" |
| 735 | depends on MFD_PCF50633 |
| 736 | help |
| 737 | Say yes here if you want to include support for ADC in the |
| 738 | NXP PCF50633 chip. |
| 739 | |
| 740 | config PCF50633_GPIO |
| 741 | tristate "Support for NXP PCF50633 GPIO" |
| 742 | depends on MFD_PCF50633 |
| 743 | help |
| 744 | Say yes here if you want to include support GPIO for pins on |
| 745 | the PCF50633 chip. |
| 746 | |
| 747 | config MFD_MC13783 |
| 748 | tristate |
| 749 | |
| 750 | config MFD_MC13XXX |
| 751 | tristate |
| 752 | depends on SPI_MASTER || I2C |
| 753 | select MFD_CORE |
| 754 | select MFD_MC13783 |
| 755 | help |
| 756 | Enable support for the Freescale MC13783 and MC13892 PMICs. |
| 757 | This driver provides common support for accessing the device, |
| 758 | additional drivers must be enabled in order to use the |
| 759 | functionality of the device. |
| 760 | |
| 761 | config MFD_MC13XXX_SPI |
| 762 | tristate "Freescale MC13783 and MC13892 SPI interface" |
| 763 | depends on SPI_MASTER |
| 764 | select REGMAP_SPI |
| 765 | select MFD_MC13XXX |
| 766 | help |
| 767 | Select this if your MC13xxx is connected via an SPI bus. |
| 768 | |
| 769 | config MFD_MC13XXX_I2C |
| 770 | tristate "Freescale MC13892 I2C interface" |
| 771 | depends on I2C |
| 772 | select REGMAP_I2C |
| 773 | select MFD_MC13XXX |
| 774 | help |
| 775 | Select this if your MC13xxx is connected via an I2C bus. |
| 776 | |
| 777 | config ABX500_CORE |
| 778 | bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions" |
| 779 | default y if ARCH_U300 || ARCH_U8500 |
| 780 | help |
| 781 | Say yes here if you have the ABX500 Mixed Signal IC family |
| 782 | chips. This core driver expose register access functions. |
| 783 | Functionality specific drivers using these functions can |
| 784 | remain unchanged when IC changes. Binding of the functions to |
| 785 | actual register access is done by the IC core driver. |
| 786 | |
| 787 | config AB3100_CORE |
| 788 | bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions" |
| 789 | depends on I2C=y && ABX500_CORE |
| 790 | select MFD_CORE |
| 791 | default y if ARCH_U300 |
| 792 | help |
| 793 | Select this to enable the AB3100 Mixed Signal IC core |
| 794 | functionality. This connects to a AB3100 on the I2C bus |
| 795 | and expose a number of symbols needed for dependent devices |
| 796 | to read and write registers and subscribe to events from |
| 797 | this multi-functional IC. This is needed to use other features |
| 798 | of the AB3100 such as battery-backed RTC, charging control, |
| 799 | LEDs, vibrator, system power and temperature, power management |
| 800 | and ALSA sound. |
| 801 | |
| 802 | config AB3100_OTP |
| 803 | tristate "ST-Ericsson AB3100 OTP functions" |
| 804 | depends on AB3100_CORE |
| 805 | default y if AB3100_CORE |
| 806 | help |
| 807 | Select this to enable the AB3100 Mixed Signal IC OTP (one-time |
| 808 | programmable memory) support. This exposes a sysfs file to read |
| 809 | out OTP values. |
| 810 | |
| 811 | config EZX_PCAP |
| 812 | bool "PCAP Support" |
| 813 | depends on GENERIC_HARDIRQS && SPI_MASTER |
| 814 | help |
| 815 | This enables the PCAP ASIC present on EZX Phones. This is |
| 816 | needed for MMC, TouchScreen, Sound, USB, etc.. |
| 817 | |
| 818 | config AB8500_CORE |
| 819 | bool "ST-Ericsson AB8500 Mixed Signal Power Management chip" |
| 820 | depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU |
| 821 | select MFD_CORE |
| 822 | select IRQ_DOMAIN |
| 823 | help |
| 824 | Select this option to enable access to AB8500 power management |
| 825 | chip. This connects to U8500 either on the SSP/SPI bus (deprecated |
| 826 | since hardware version v1.0) or the I2C bus via PRCMU. It also adds |
| 827 | the irq_chip parts for handling the Mixed Signal chip events. |
| 828 | This chip embeds various other multimedia funtionalities as well. |
| 829 | |
| 830 | config AB8500_DEBUG |
| 831 | bool "Enable debug info via debugfs" |
| 832 | depends on AB8500_CORE && DEBUG_FS |
| 833 | default y if DEBUG_FS |
| 834 | help |
| 835 | Select this option if you want debug information using the debug |
| 836 | filesystem, debugfs. |
| 837 | |
| 838 | config AB8500_GPADC |
| 839 | bool "AB8500 GPADC driver" |
| 840 | depends on AB8500_CORE && REGULATOR_AB8500 |
| 841 | default y |
| 842 | help |
| 843 | AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage |
| 844 | |
| 845 | config MFD_DB8500_PRCMU |
| 846 | bool "ST-Ericsson DB8500 Power Reset Control Management Unit" |
| 847 | depends on UX500_SOC_DB8500 |
| 848 | select MFD_CORE |
| 849 | help |
| 850 | Select this option to enable support for the DB8500 Power Reset |
| 851 | and Control Management Unit. This is basically an autonomous |
| 852 | system controller running an XP70 microprocessor, which is accessed |
| 853 | through a register map. |
| 854 | |
| 855 | config MFD_CS5535 |
| 856 | tristate "Support for CS5535 and CS5536 southbridge core functions" |
| 857 | select MFD_CORE |
| 858 | depends on PCI && X86 |
| 859 | ---help--- |
| 860 | This is the core driver for CS5535/CS5536 MFD functions. This is |
| 861 | necessary for using the board's GPIO and MFGPT functionality. |
| 862 | |
| 863 | config MFD_TIMBERDALE |
| 864 | tristate "Support for the Timberdale FPGA" |
| 865 | select MFD_CORE |
| 866 | depends on PCI && GPIOLIB |
| 867 | ---help--- |
| 868 | This is the core driver for the timberdale FPGA. This device is a |
| 869 | multifunction device which exposes numerous platform devices. |
| 870 | |
| 871 | The timberdale FPGA can be found on the Intel Atom development board |
| 872 | for in-vehicle infontainment, called Russellville. |
| 873 | |
| 874 | config LPC_SCH |
| 875 | tristate "Intel SCH LPC" |
| 876 | depends on PCI |
| 877 | select MFD_CORE |
| 878 | help |
| 879 | LPC bridge function of the Intel SCH provides support for |
| 880 | System Management Bus and General Purpose I/O. |
| 881 | |
| 882 | config LPC_ICH |
| 883 | tristate "Intel ICH LPC" |
| 884 | depends on PCI |
| 885 | select MFD_CORE |
| 886 | help |
| 887 | The LPC bridge function of the Intel ICH provides support for |
| 888 | many functional units. This driver provides needed support for |
| 889 | other drivers to control these functions, currently GPIO and |
| 890 | watchdog. |
| 891 | |
| 892 | config MFD_RDC321X |
| 893 | tristate "Support for RDC-R321x southbridge" |
| 894 | select MFD_CORE |
| 895 | depends on PCI |
| 896 | help |
| 897 | Say yes here if you want to have support for the RDC R-321x SoC |
| 898 | southbridge which provides access to GPIOs and Watchdog using the |
| 899 | southbridge PCI device configuration space. |
| 900 | |
| 901 | config MFD_JANZ_CMODIO |
| 902 | tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board" |
| 903 | select MFD_CORE |
| 904 | depends on PCI |
| 905 | help |
| 906 | This is the core driver for the Janz CMOD-IO PCI MODULbus |
| 907 | carrier board. This device is a PCI to MODULbus bridge which may |
| 908 | host many different types of MODULbus daughterboards, including |
| 909 | CAN and GPIO controllers. |
| 910 | |
| 911 | config MFD_JZ4740_ADC |
| 912 | bool "Support for the JZ4740 SoC ADC core" |
| 913 | select MFD_CORE |
| 914 | select GENERIC_IRQ_CHIP |
| 915 | depends on MACH_JZ4740 |
| 916 | help |
| 917 | Say yes here if you want support for the ADC unit in the JZ4740 SoC. |
| 918 | This driver is necessary for jz4740-battery and jz4740-hwmon driver. |
| 919 | |
| 920 | config MFD_VX855 |
| 921 | tristate "Support for VIA VX855/VX875 integrated south bridge" |
| 922 | depends on PCI |
| 923 | select MFD_CORE |
| 924 | help |
| 925 | Say yes here to enable support for various functions of the |
| 926 | VIA VX855/VX875 south bridge. You will need to enable the vx855_spi |
| 927 | and/or vx855_gpio drivers for this to do anything useful. |
| 928 | |
| 929 | config MFD_WL1273_CORE |
| 930 | tristate "Support for TI WL1273 FM radio." |
| 931 | depends on I2C |
| 932 | select MFD_CORE |
| 933 | default n |
| 934 | help |
| 935 | This is the core driver for the TI WL1273 FM radio. This MFD |
| 936 | driver connects the radio-wl1273 V4L2 module and the wl1273 |
| 937 | audio codec. |
| 938 | |
| 939 | config MFD_OMAP_USB_HOST |
| 940 | bool "Support OMAP USBHS core and TLL driver" |
| 941 | depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3 |
| 942 | default y |
| 943 | help |
| 944 | This is the core driver for the OAMP EHCI and OHCI drivers. |
| 945 | This MFD driver does the required setup functionalities for |
| 946 | OMAP USB Host drivers. |
| 947 | |
| 948 | config MFD_PM8XXX |
| 949 | tristate |
| 950 | |
| 951 | config MFD_PM8921_CORE |
| 952 | tristate "Qualcomm PM8921 PMIC chip" |
| 953 | depends on MSM_SSBI |
| 954 | select MFD_CORE |
| 955 | select MFD_PM8XXX |
| 956 | help |
| 957 | If you say yes to this option, support will be included for the |
| 958 | built-in PM8921 PMIC chip. |
| 959 | |
| 960 | This is required if your board has a PM8921 and uses its features, |
| 961 | such as: MPPs, GPIOs, regulators, interrupts, and PWM. |
| 962 | |
| 963 | Say M here if you want to include support for PM8921 chip as a module. |
| 964 | This will build a module called "pm8921-core". |
| 965 | |
| 966 | config MFD_PM8XXX_IRQ |
| 967 | bool "Support for Qualcomm PM8xxx IRQ features" |
| 968 | depends on MFD_PM8XXX |
| 969 | default y if MFD_PM8XXX |
| 970 | help |
| 971 | This is the IRQ driver for Qualcomm PM 8xxx PMIC chips. |
| 972 | |
| 973 | This is required to use certain other PM 8xxx features, such as GPIO |
| 974 | and MPP. |
| 975 | |
| 976 | config TPS65911_COMPARATOR |
| 977 | tristate |
| 978 | |
| 979 | config MFD_TPS65090 |
| 980 | bool "TPS65090 Power Management chips" |
| 981 | depends on I2C=y && GENERIC_HARDIRQS |
| 982 | select MFD_CORE |
| 983 | select REGMAP_I2C |
| 984 | help |
| 985 | If you say yes here you get support for the TPS65090 series of |
| 986 | Power Management chips. |
| 987 | This driver provides common support for accessing the device, |
| 988 | additional drivers must be enabled in order to use the |
| 989 | functionality of the device. |
| 990 | |
| 991 | config MFD_AAT2870_CORE |
| 992 | bool "Support for the AnalogicTech AAT2870" |
| 993 | select MFD_CORE |
| 994 | depends on I2C=y && GPIOLIB |
| 995 | help |
| 996 | If you say yes here you get support for the AAT2870. |
| 997 | This driver provides common support for accessing the device, |
| 998 | additional drivers must be enabled in order to use the |
| 999 | functionality of the device. |
| 1000 | |
| 1001 | config MFD_INTEL_MSIC |
| 1002 | bool "Support for Intel MSIC" |
| 1003 | depends on INTEL_SCU_IPC |
| 1004 | select MFD_CORE |
| 1005 | help |
| 1006 | Select this option to enable access to Intel MSIC (Avatele |
| 1007 | Passage) chip. This chip embeds audio, battery, GPIO, etc. |
| 1008 | devices used in Intel Medfield platforms. |
| 1009 | |
| 1010 | config MFD_RC5T583 |
| 1011 | bool "Ricoh RC5T583 Power Management system device" |
| 1012 | depends on I2C=y && GENERIC_HARDIRQS |
| 1013 | select MFD_CORE |
| 1014 | select REGMAP_I2C |
| 1015 | help |
| 1016 | Select this option to get support for the RICOH583 Power |
| 1017 | Management system device. |
| 1018 | This driver provides common support for accessing the device |
| 1019 | through i2c interface. The device supports multiple sub-devices |
| 1020 | like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey. |
| 1021 | Additional drivers must be enabled in order to use the |
| 1022 | different functionality of the device. |
| 1023 | |
| 1024 | config MFD_STA2X11 |
| 1025 | bool "STA2X11 multi function device support" |
| 1026 | depends on STA2X11 |
| 1027 | select MFD_CORE |
| 1028 | |
| 1029 | config MFD_SYSCON |
| 1030 | bool "System Controller Register R/W Based on Regmap" |
| 1031 | depends on OF |
| 1032 | select REGMAP_MMIO |
| 1033 | help |
| 1034 | Select this option to enable accessing system control registers |
| 1035 | via regmap. |
| 1036 | |
| 1037 | config MFD_PALMAS |
| 1038 | bool "Support for the TI Palmas series chips" |
| 1039 | select MFD_CORE |
| 1040 | select REGMAP_I2C |
| 1041 | select REGMAP_IRQ |
| 1042 | depends on I2C=y |
| 1043 | help |
| 1044 | If you say yes here you get support for the Palmas |
| 1045 | series of PMIC chips from Texas Instruments. |
| 1046 | |
| 1047 | endmenu |
| 1048 | endif |
| 1049 | |
| 1050 | menu "Multimedia Capabilities Port drivers" |
| 1051 | depends on ARCH_SA1100 |
| 1052 | |
| 1053 | config MCP |
| 1054 | tristate |
| 1055 | |
| 1056 | # Interface drivers |
| 1057 | config MCP_SA11X0 |
| 1058 | tristate "Support SA11x0 MCP interface" |
| 1059 | depends on ARCH_SA1100 |
| 1060 | select MCP |
| 1061 | |
| 1062 | # Chip drivers |
| 1063 | config MCP_UCB1200 |
| 1064 | bool "Support for UCB1200 / UCB1300" |
| 1065 | depends on MCP_SA11X0 |
| 1066 | select MCP |
| 1067 | |
| 1068 | config MCP_UCB1200_TS |
| 1069 | tristate "Touchscreen interface support" |
| 1070 | depends on MCP_UCB1200 && INPUT |
| 1071 | |
| 1072 | endmenu |