drivers/mfd/Kconfig

   1 #
   2 # Multifunction miscellaneous devices
   3 #
   4
   5 menuconfig 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
  21 if MFD_SUPPORT
  22
  23 config MFD_CORE
  24         tristate
  25         default n
  26
  27 config 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
  37 config 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
  47 config 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
  55 config 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
  63 config 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
  72 config MFD_DAVINCI_VOICECODEC
  73         tristate
  74         select MFD_CORE
  75
  76 config 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
  84 config 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
  92 config 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
 101 config 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
 110 config 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
 121 config 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
 134 config 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
 146 config 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
 156 config 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
 170 config 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
 183 config TWL4030_CODEC
 184         bool
 185         depends on TWL4030_CORE
 186         select MFD_CORE
 187         default n
 188
 189 config MFD_STMPE
 190         bool "Support STMicroelectronics STMPE"
 191         depends on I2C=y && GENERIC_HARDIRQS
 192         select MFD_CORE
 193         help
 194           Support for the STMPE family of I/O Expanders from
 195           STMicroelectronics.
 196
 197           Currently supported devices are:
 198
 199                 STMPE811: GPIO, Touchscreen
 200                 STMPE1601: GPIO, Keypad
 201                 STMPE2401: GPIO, Keypad
 202                 STMPE2403: GPIO, Keypad
 203
 204           This driver provides common support for accessing the device,
 205           additional drivers must be enabled in order to use the functionality
 206           of the device.  Currently available sub drivers are:
 207
 208                 GPIO: stmpe-gpio
 209                 Keypad: stmpe-keypad
 210                 Touchscreen: stmpe-ts
 211
 212 config MFD_TC35892
 213         bool "Support Toshiba TC35892"
 214         depends on I2C=y && GENERIC_HARDIRQS
 215         select MFD_CORE
 216         help
 217           Support for the Toshiba TC35892 I/O Expander.
 218
 219           This driver provides common support for accessing the device,
 220           additional drivers must be enabled in order to use the
 221           functionality of the device.
 222
 223 config MFD_TMIO
 224         bool
 225         default n
 226
 227 config TMIO_MMC_DMA
 228         bool
 229         select DMA_ENGINE
 230         select DMADEVICES
 231
 232 config MFD_T7L66XB
 233         bool "Support Toshiba T7L66XB"
 234         depends on ARM && HAVE_CLK
 235         select MFD_CORE
 236         select MFD_TMIO
 237         help
 238           Support for Toshiba Mobile IO Controller T7L66XB
 239
 240 config MFD_TC6387XB
 241         bool "Support Toshiba TC6387XB"
 242         depends on ARM && HAVE_CLK
 243         select MFD_CORE
 244         select MFD_TMIO
 245         help
 246           Support for Toshiba Mobile IO Controller TC6387XB
 247
 248 config MFD_TC6393XB
 249         bool "Support Toshiba TC6393XB"
 250         depends on GPIOLIB && ARM
 251         select MFD_CORE
 252         select MFD_TMIO
 253         help
 254           Support for Toshiba Mobile IO Controller TC6393XB
 255
 256 config PMIC_DA903X
 257         bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
 258         depends on I2C=y
 259         help
 260           Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
 261           ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
 262           usually found on PXA processors-based platforms. This includes
 263           the I2C driver and the core APIs _only_, you have to select
 264           individual components like LCD backlight, voltage regulators,
 265           LEDs and battery-charger under the corresponding menus.
 266
 267 config PMIC_ADP5520
 268         bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
 269         depends on I2C=y
 270         help
 271           Say yes here to add support for Analog Devices AD5520 and ADP5501,
 272           Multifunction Power Management IC. This includes
 273           the I2C driver and the core APIs _only_, you have to select
 274           individual components like LCD backlight, LEDs, GPIOs and Kepad
 275           under the corresponding menus.
 276
 277 config MFD_MAX8925
 278         bool "Maxim Semiconductor MAX8925 PMIC Support"
 279         depends on I2C=y && GENERIC_HARDIRQS
 280         select MFD_CORE
 281         help
 282           Say yes here to support for Maxim Semiconductor MAX8925. This is
 283           a Power Management IC. This driver provies common support for
 284           accessing the device, additional drivers must be enabled in order
 285           to use the functionality of the device.
 286
 287 config MFD_WM8400
 288         tristate "Support Wolfson Microelectronics WM8400"
 289         select MFD_CORE
 290         depends on I2C
 291         help
 292           Support for the Wolfson Microelecronics WM8400 PMIC and audio
 293           CODEC.  This driver provides common support for accessing
 294           the device, additional drivers must be enabled in order to use
 295           the functionality of the device.
 296
 297 config MFD_WM831X
 298         bool "Support Wolfson Microelectronics WM831x/2x PMICs"
 299         select MFD_CORE
 300         depends on I2C=y && GENERIC_HARDIRQS
 301         help
 302           Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
 303           This driver provides common support for accessing the device,
 304           additional drivers must be enabled in order to use the
 305           functionality of the device.
 306
 307 config MFD_WM8350
 308         bool
 309         depends on GENERIC_HARDIRQS
 310
 311 config MFD_WM8350_CONFIG_MODE_0
 312         bool
 313         depends on MFD_WM8350
 314
 315 config MFD_WM8350_CONFIG_MODE_1
 316         bool
 317         depends on MFD_WM8350
 318
 319 config MFD_WM8350_CONFIG_MODE_2
 320         bool
 321         depends on MFD_WM8350
 322
 323 config MFD_WM8350_CONFIG_MODE_3
 324         bool
 325         depends on MFD_WM8350
 326
 327 config MFD_WM8351_CONFIG_MODE_0
 328         bool
 329         depends on MFD_WM8350
 330
 331 config MFD_WM8351_CONFIG_MODE_1
 332         bool
 333         depends on MFD_WM8350
 334
 335 config MFD_WM8351_CONFIG_MODE_2
 336         bool
 337         depends on MFD_WM8350
 338
 339 config MFD_WM8351_CONFIG_MODE_3
 340         bool
 341         depends on MFD_WM8350
 342
 343 config MFD_WM8352_CONFIG_MODE_0
 344         bool
 345         depends on MFD_WM8350
 346
 347 config MFD_WM8352_CONFIG_MODE_1
 348         bool
 349         depends on MFD_WM8350
 350
 351 config MFD_WM8352_CONFIG_MODE_2
 352         bool
 353         depends on MFD_WM8350
 354
 355 config MFD_WM8352_CONFIG_MODE_3
 356         bool
 357         depends on MFD_WM8350
 358
 359 config MFD_WM8350_I2C
 360         bool "Support Wolfson Microelectronics WM8350 with I2C"
 361         select MFD_WM8350
 362         depends on I2C=y && GENERIC_HARDIRQS
 363         help
 364           The WM8350 is an integrated audio and power management
 365           subsystem with watchdog and RTC functionality for embedded
 366           systems.  This option enables core support for the WM8350 with
 367           I2C as the control interface.  Additional options must be
 368           selected to enable support for the functionality of the chip.
 369
 370 config MFD_WM8994
 371         bool "Support Wolfson Microelectronics WM8994"
 372         select MFD_CORE
 373         depends on I2C=y && GENERIC_HARDIRQS
 374         help
 375           The WM8994 is a highly integrated hi-fi CODEC designed for
 376           smartphone applicatiosn.  As well as audio functionality it
 377           has on board GPIO and regulator functionality which is
 378           supported via the relevant subsystems.  This driver provides
 379           core support for the WM8994, in order to use the actual
 380           functionaltiy of the device other drivers must be enabled.
 381
 382 config MFD_PCF50633
 383         tristate "Support for NXP PCF50633"
 384         depends on I2C
 385         help
 386           Say yes here if you have NXP PCF50633 chip on your board.
 387           This core driver provides register access and IRQ handling
 388           facilities, and registers devices for the various functions
 389           so that function-specific drivers can bind to them.
 390
 391 config MFD_MC13783
 392         tristate "Support Freescale MC13783"
 393         depends on SPI_MASTER
 394         select MFD_CORE
 395         help
 396           Support for the Freescale (Atlas) MC13783 PMIC and audio CODEC.
 397           This driver provides common support for accessing  the device,
 398           additional drivers must be enabled in order to use the
 399           functionality of the device.
 400
 401 config PCF50633_ADC
 402         tristate "Support for NXP PCF50633 ADC"
 403         depends on MFD_PCF50633
 404         help
 405          Say yes here if you want to include support for ADC in the
 406          NXP PCF50633 chip.
 407
 408 config PCF50633_GPIO
 409         tristate "Support for NXP PCF50633 GPIO"
 410         depends on MFD_PCF50633
 411         help
 412          Say yes here if you want to include support GPIO for pins on
 413          the PCF50633 chip.
 414
 415 config ABX500_CORE
 416         bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
 417         default y if ARCH_U300
 418         help
 419           Say yes here if you have the ABX500 Mixed Signal IC family
 420           chips. This core driver expose register access functions.
 421           Functionality specific drivers using these functions can
 422           remain unchanged when IC changes. Binding of the functions to
 423           actual register access is done by the IC core driver.
 424
 425 config AB3100_CORE
 426         bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
 427         depends on I2C=y && ABX500_CORE
 428         default y if ARCH_U300
 429         help
 430           Select this to enable the AB3100 Mixed Signal IC core
 431           functionality. This connects to a AB3100 on the I2C bus
 432           and expose a number of symbols needed for dependent devices
 433           to read and write registers and subscribe to events from
 434           this multi-functional IC. This is needed to use other features
 435           of the AB3100 such as battery-backed RTC, charging control,
 436           LEDs, vibrator, system power and temperature, power management
 437           and ALSA sound.
 438
 439 config AB3100_OTP
 440         tristate "ST-Ericsson AB3100 OTP functions"
 441         depends on AB3100_CORE
 442         default y if AB3100_CORE
 443         help
 444           Select this to enable the AB3100 Mixed Signal IC OTP (one-time
 445           programmable memory) support. This exposes a sysfs file to read
 446           out OTP values.
 447
 448 config EZX_PCAP
 449         bool "PCAP Support"
 450         depends on GENERIC_HARDIRQS && SPI_MASTER
 451         help
 452           This enables the PCAP ASIC present on EZX Phones. This is
 453           needed for MMC, TouchScreen, Sound, USB, etc..
 454
 455 config AB8500_CORE
 456         bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
 457         depends on SPI=y && GENERIC_HARDIRQS
 458         select MFD_CORE
 459         help
 460           Select this option to enable access to AB8500 power management
 461           chip. This connects to U8500 on the SSP/SPI bus and exports
 462           read/write functions for the devices to get access to this chip.
 463           This chip embeds various other multimedia funtionalities as well.
 464
 465 config AB3550_CORE
 466         bool "ST-Ericsson AB3550 Mixed Signal Circuit core functions"
 467         select MFD_CORE
 468         depends on I2C=y && GENERIC_HARDIRQS && ABX500_CORE
 469         help
 470           Select this to enable the AB3550 Mixed Signal IC core
 471           functionality. This connects to a AB3550 on the I2C bus
 472           and expose a number of symbols needed for dependent devices
 473           to read and write registers and subscribe to events from
 474           this multi-functional IC. This is needed to use other features
 475           of the AB3550 such as battery-backed RTC, charging control,
 476           LEDs, vibrator, system power and temperature, power management
 477           and ALSA sound.
 478
 479 config MFD_TIMBERDALE
 480         tristate "Support for the Timberdale FPGA"
 481         select MFD_CORE
 482         depends on PCI && GPIOLIB
 483         ---help---
 484         This is the core driver for the timberdale FPGA. This device is a
 485         multifunction device which exposes numerous platform devices.
 486
 487         The timberdale FPGA can be found on the Intel Atom development board
 488         for in-vehicle infontainment, called Russellville.
 489
 490 config LPC_SCH
 491         tristate "Intel SCH LPC"
 492         depends on PCI
 493         select MFD_CORE
 494         help
 495           LPC bridge function of the Intel SCH provides support for
 496           System Management Bus and General Purpose I/O.
 497
 498 config MFD_RDC321X
 499         tristate "Support for RDC-R321x southbridge"
 500         select MFD_CORE
 501         depends on PCI
 502         help
 503           Say yes here if you want to have support for the RDC R-321x SoC
 504           southbridge which provides access to GPIOs and Watchdog using the
 505           southbridge PCI device configuration space.
 506
 507 config MFD_JANZ_CMODIO
 508         tristate "Support for Janz CMOD-IO PCI MODULbus Carrier Board"
 509         select MFD_CORE
 510         depends on PCI
 511         help
 512           This is the core driver for the Janz CMOD-IO PCI MODULbus
 513           carrier board. This device is a PCI to MODULbus bridge which may
 514           host many different types of MODULbus daughterboards, including
 515           CAN and GPIO controllers.
 516
 517 endif # MFD_SUPPORT
 518
 519 menu "Multimedia Capabilities Port drivers"
 520         depends on ARCH_SA1100
 521
 522 config MCP
 523         tristate
 524
 525 # Interface drivers
 526 config MCP_SA11X0
 527         tristate "Support SA11x0 MCP interface"
 528         depends on ARCH_SA1100
 529         select MCP
 530
 531 # Chip drivers
 532 config MCP_UCB1200
 533         tristate "Support for UCB1200 / UCB1300"
 534         depends on MCP
 535
 536 config MCP_UCB1200_TS
 537         tristate "Touchscreen interface support"
 538         depends on MCP_UCB1200 && INPUT
 539
 540 endmenu