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