2005-08-18 09:06:59 +00:00
|
|
|
#
|
|
|
|
|
# Multifunction miscellaneous devices
|
|
|
|
|
#
|
|
|
|
|
|
2011-09-02 14:43:36 +00:00
|
|
|
if HAS_IOMEM
|
|
|
|
|
menu "Multifunction device drivers"
|
2007-02-20 21:58:01 +00:00
|
|
|
|
2008-06-27 09:37:19 +00:00
|
|
|
config MFD_CORE
|
|
|
|
|
tristate
|
2012-06-29 17:01:03 +00:00
|
|
|
select IRQ_DOMAIN
|
2008-06-27 09:37:19 +00:00
|
|
|
default n
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_CS5535
|
|
|
|
|
tristate "AMD CS5535 and CS5536 southbridge core functions"
|
2010-01-06 22:07:13 +00:00
|
|
|
select MFD_CORE
|
2014-06-16 11:54:15 +00:00
|
|
|
depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
|
2013-04-09 12:40:09 +00:00
|
|
|
---help---
|
|
|
|
|
This is the core driver for CS5535/CS5536 MFD functions. This is
|
|
|
|
|
necessary for using the board's GPIO and MFGPT functionality.
|
2010-01-06 22:07:13 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_AS3711
|
|
|
|
|
bool "AMS AS3711"
|
|
|
|
|
select MFD_CORE
|
mfd: Support 88pm80x in 80x driver
88PM800 and 88PM805 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according
to requirement.
88pm80x.c provides common i2c driver handling for both 800 and
805, such as i2c_driver init, regmap init, read/write api etc.
88pm800.c handles specifically for 800, such as chip init, irq
init/handle, mfd device register, including rtc, onkey, regulator(
to be add later) etc. besides that, 800 has three i2c device, one
regular i2c client, two other i2c dummy for gpadc and power purpose.
88pm805.c handles specifically for 805, such as chip init, irq
init/handle, mfd device register, including codec, headset/mic detect
etc.
the i2c operation of both 800 and 805 are via regmap, and 88pm80x-i2c
exported a group of r/w bulk r/w and bits set API for facility.
Signed-off-by: Qiao Zhou <zhouqiao@marvell.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-07-09 06:37:32 +00:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
mfd: Support 88pm80x in 80x driver
88PM800 and 88PM805 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according
to requirement.
88pm80x.c provides common i2c driver handling for both 800 and
805, such as i2c_driver init, regmap init, read/write api etc.
88pm800.c handles specifically for 800, such as chip init, irq
init/handle, mfd device register, including rtc, onkey, regulator(
to be add later) etc. besides that, 800 has three i2c device, one
regular i2c client, two other i2c dummy for gpadc and power purpose.
88pm805.c handles specifically for 805, such as chip init, irq
init/handle, mfd device register, including codec, headset/mic detect
etc.
the i2c operation of both 800 and 805 are via regmap, and 88pm80x-i2c
exported a group of r/w bulk r/w and bits set API for facility.
Signed-off-by: Qiao Zhou <zhouqiao@marvell.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-07-09 06:37:32 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the AS3711 PMIC from AMS
|
mfd: Support 88pm80x in 80x driver
88PM800 and 88PM805 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according
to requirement.
88pm80x.c provides common i2c driver handling for both 800 and
805, such as i2c_driver init, regmap init, read/write api etc.
88pm800.c handles specifically for 800, such as chip init, irq
init/handle, mfd device register, including rtc, onkey, regulator(
to be add later) etc. besides that, 800 has three i2c device, one
regular i2c client, two other i2c dummy for gpadc and power purpose.
88pm805.c handles specifically for 805, such as chip init, irq
init/handle, mfd device register, including codec, headset/mic detect
etc.
the i2c operation of both 800 and 805 are via regmap, and 88pm80x-i2c
exported a group of r/w bulk r/w and bits set API for facility.
Signed-off-by: Qiao Zhou <zhouqiao@marvell.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-07-09 06:37:32 +00:00
|
|
|
|
2013-10-22 07:38:46 +00:00
|
|
|
config MFD_AS3722
|
|
|
|
|
bool "ams AS3722 Power Management IC"
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
2013-11-18 17:25:59 +00:00
|
|
|
depends on I2C=y && OF
|
2013-10-22 07:38:46 +00:00
|
|
|
help
|
|
|
|
|
The ams AS3722 is a compact system PMU suitable for mobile phones,
|
|
|
|
|
tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
|
|
|
|
|
controllers, 11 LDOs, RTC, automatic battery, temperature and
|
|
|
|
|
over current monitoring, GPIOs, ADC and a watchdog.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config PMIC_ADP5520
|
|
|
|
|
bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
|
|
|
|
|
depends on I2C=y
|
|
|
|
|
help
|
|
|
|
|
Say yes here to add support for Analog Devices AD5520 and ADP5501,
|
|
|
|
|
Multifunction Power Management IC. This includes
|
|
|
|
|
the I2C driver and the core APIs _only_, you have to select
|
|
|
|
|
individual components like LCD backlight, LEDs, GPIOs and Kepad
|
|
|
|
|
under the corresponding menus.
|
|
|
|
|
|
|
|
|
|
config MFD_AAT2870_CORE
|
|
|
|
|
bool "AnalogicTech AAT2870"
|
mfd: Support 88pm80x in 80x driver
88PM800 and 88PM805 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according
to requirement.
88pm80x.c provides common i2c driver handling for both 800 and
805, such as i2c_driver init, regmap init, read/write api etc.
88pm800.c handles specifically for 800, such as chip init, irq
init/handle, mfd device register, including rtc, onkey, regulator(
to be add later) etc. besides that, 800 has three i2c device, one
regular i2c client, two other i2c dummy for gpadc and power purpose.
88pm805.c handles specifically for 805, such as chip init, irq
init/handle, mfd device register, including codec, headset/mic detect
etc.
the i2c operation of both 800 and 805 are via regmap, and 88pm80x-i2c
exported a group of r/w bulk r/w and bits set API for facility.
Signed-off-by: Qiao Zhou <zhouqiao@marvell.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-07-09 06:37:32 +00:00
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y && GPIOLIB
|
mfd: Support 88pm80x in 80x driver
88PM800 and 88PM805 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according
to requirement.
88pm80x.c provides common i2c driver handling for both 800 and
805, such as i2c_driver init, regmap init, read/write api etc.
88pm800.c handles specifically for 800, such as chip init, irq
init/handle, mfd device register, including rtc, onkey, regulator(
to be add later) etc. besides that, 800 has three i2c device, one
regular i2c client, two other i2c dummy for gpadc and power purpose.
88pm805.c handles specifically for 805, such as chip init, irq
init/handle, mfd device register, including codec, headset/mic detect
etc.
the i2c operation of both 800 and 805 are via regmap, and 88pm80x-i2c
exported a group of r/w bulk r/w and bits set API for facility.
Signed-off-by: Qiao Zhou <zhouqiao@marvell.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-07-09 06:37:32 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the AAT2870.
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the
|
|
|
|
|
functionality of the device.
|
mfd: Support 88pm80x in 80x driver
88PM800 and 88PM805 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according
to requirement.
88pm80x.c provides common i2c driver handling for both 800 and
805, such as i2c_driver init, regmap init, read/write api etc.
88pm800.c handles specifically for 800, such as chip init, irq
init/handle, mfd device register, including rtc, onkey, regulator(
to be add later) etc. besides that, 800 has three i2c device, one
regular i2c client, two other i2c dummy for gpadc and power purpose.
88pm805.c handles specifically for 805, such as chip init, irq
init/handle, mfd device register, including codec, headset/mic detect
etc.
the i2c operation of both 800 and 805 are via regmap, and 88pm80x-i2c
exported a group of r/w bulk r/w and bits set API for facility.
Signed-off-by: Qiao Zhou <zhouqiao@marvell.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-07-09 06:37:32 +00:00
|
|
|
|
2014-03-11 23:33:54 +00:00
|
|
|
config MFD_BCM590XX
|
|
|
|
|
tristate "Broadcom BCM590xx PMUs"
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
|
|
|
|
Support for the BCM590xx PMUs from Broadcom
|
|
|
|
|
|
2014-05-01 12:29:27 +00:00
|
|
|
config MFD_AXP20X
|
|
|
|
|
bool "X-Powers AXP20X"
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
|
|
|
|
depends on I2C=y
|
|
|
|
|
help
|
|
|
|
|
If you say Y here you get support for the X-Powers AXP202 and AXP209.
|
|
|
|
|
This driver include only the core APIs. You have to select individual
|
|
|
|
|
components like regulators or the PEK (Power Enable Key) under the
|
|
|
|
|
corresponding menus.
|
|
|
|
|
|
2013-02-25 22:08:37 +00:00
|
|
|
config MFD_CROS_EC
|
2013-04-09 12:40:09 +00:00
|
|
|
tristate "ChromeOS Embedded Controller"
|
2013-03-21 19:08:33 +00:00
|
|
|
select MFD_CORE
|
2013-02-25 22:08:37 +00:00
|
|
|
help
|
|
|
|
|
If you say Y here you get support for the ChromeOS Embedded
|
|
|
|
|
Controller (EC) providing keyboard, battery and power services.
|
2013-05-06 07:46:29 +00:00
|
|
|
You also need to enable the driver for the bus you are using. The
|
2013-02-25 22:08:37 +00:00
|
|
|
protocol for talking to the EC is defined by the bus driver.
|
2007-02-20 21:58:01 +00:00
|
|
|
|
2013-02-25 22:08:38 +00:00
|
|
|
config MFD_CROS_EC_I2C
|
|
|
|
|
tristate "ChromeOS Embedded Controller (I2C)"
|
|
|
|
|
depends on MFD_CROS_EC && I2C
|
2008-07-25 08:45:59 +00:00
|
|
|
|
2012-11-09 12:53:33 +00:00
|
|
|
help
|
2013-02-25 22:08:38 +00:00
|
|
|
If you say Y here, you get support for talking to the ChromeOS
|
|
|
|
|
EC through an I2C bus. This uses a simple byte-level protocol with
|
|
|
|
|
a checksum. Failing accesses will be retried three times to
|
|
|
|
|
improve reliability.
|
|
|
|
|
|
2013-02-25 22:08:39 +00:00
|
|
|
config MFD_CROS_EC_SPI
|
|
|
|
|
tristate "ChromeOS Embedded Controller (SPI)"
|
2013-12-09 10:05:39 +00:00
|
|
|
depends on MFD_CROS_EC && SPI && OF
|
2013-02-25 22:08:39 +00:00
|
|
|
|
|
|
|
|
---help---
|
|
|
|
|
If you say Y here, you get support for talking to the ChromeOS EC
|
|
|
|
|
through a SPI bus, using a byte-level protocol. Since the EC's
|
|
|
|
|
response time cannot be guaranteed, we support ignoring
|
|
|
|
|
'pre-amble' bytes before the response actually starts.
|
2012-11-09 12:53:33 +00:00
|
|
|
|
2008-02-07 08:14:49 +00:00
|
|
|
config MFD_ASIC3
|
2013-04-09 12:40:09 +00:00
|
|
|
bool "Compaq ASIC3"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on GPIOLIB && ARM
|
2009-06-15 10:10:24 +00:00
|
|
|
select MFD_CORE
|
2008-02-07 08:14:49 +00:00
|
|
|
---help---
|
|
|
|
|
This driver supports the ASIC3 multifunction chip found on many
|
|
|
|
|
PDAs (mainly iPAQ and HTC based ones)
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config PMIC_DA903X
|
|
|
|
|
bool "Dialog Semiconductor DA9030/DA9034 PMIC Support"
|
|
|
|
|
depends on I2C=y
|
mfd: Support 88pm80x in 80x driver
88PM800 and 88PM805 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according
to requirement.
88pm80x.c provides common i2c driver handling for both 800 and
805, such as i2c_driver init, regmap init, read/write api etc.
88pm800.c handles specifically for 800, such as chip init, irq
init/handle, mfd device register, including rtc, onkey, regulator(
to be add later) etc. besides that, 800 has three i2c device, one
regular i2c client, two other i2c dummy for gpadc and power purpose.
88pm805.c handles specifically for 805, such as chip init, irq
init/handle, mfd device register, including codec, headset/mic detect
etc.
the i2c operation of both 800 and 805 are via regmap, and 88pm80x-i2c
exported a group of r/w bulk r/w and bits set API for facility.
Signed-off-by: Qiao Zhou <zhouqiao@marvell.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-07-09 06:37:32 +00:00
|
|
|
help
|
2014-02-11 04:50:51 +00:00
|
|
|
Say yes here to add support for Dialog Semiconductor DA9030 (a.k.a
|
2013-04-09 12:40:09 +00:00
|
|
|
ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
|
|
|
|
|
usually found on PXA processors-based platforms. This includes
|
|
|
|
|
the I2C driver and the core APIs _only_, you have to select
|
|
|
|
|
individual components like LCD backlight, voltage regulators,
|
|
|
|
|
LEDs and battery-charger under the corresponding menus.
|
mfd: Support 88pm80x in 80x driver
88PM800 and 88PM805 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according
to requirement.
88pm80x.c provides common i2c driver handling for both 800 and
805, such as i2c_driver init, regmap init, read/write api etc.
88pm800.c handles specifically for 800, such as chip init, irq
init/handle, mfd device register, including rtc, onkey, regulator(
to be add later) etc. besides that, 800 has three i2c device, one
regular i2c client, two other i2c dummy for gpadc and power purpose.
88pm805.c handles specifically for 805, such as chip init, irq
init/handle, mfd device register, including codec, headset/mic detect
etc.
the i2c operation of both 800 and 805 are via regmap, and 88pm80x-i2c
exported a group of r/w bulk r/w and bits set API for facility.
Signed-off-by: Qiao Zhou <zhouqiao@marvell.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-07-09 06:37:32 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config PMIC_DA9052
|
|
|
|
|
bool
|
2010-03-11 15:32:21 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_DA9052_SPI
|
|
|
|
|
bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
|
|
|
|
|
select REGMAP_SPI
|
|
|
|
|
select REGMAP_IRQ
|
|
|
|
|
select PMIC_DA9052
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on SPI_MASTER=y
|
2008-12-22 11:05:27 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the Dialog Semiconductor DA9052 PMIC
|
|
|
|
|
when controlled using SPI. This driver provides common support
|
|
|
|
|
for accessing the device, additional drivers must be enabled in
|
|
|
|
|
order to use the functionality of the device.
|
2008-12-22 11:05:27 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_DA9052_I2C
|
|
|
|
|
bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
|
|
|
|
select PMIC_DA9052
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
help
|
|
|
|
|
Support for the Dialog Semiconductor DA9052 PMIC
|
|
|
|
|
when controlled using I2C. This driver provides common support
|
|
|
|
|
for accessing the device, additional drivers must be enabled in
|
|
|
|
|
order to use the functionality of the device.
|
2008-07-25 08:45:59 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_DA9055
|
|
|
|
|
bool "Dialog Semiconductor DA9055 PMIC Support"
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
2011-01-18 19:21:35 +00:00
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-11-09 12:53:33 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here for support of Dialog Semiconductor DA9055. This is
|
|
|
|
|
a Power Management IC. This driver provides common support for
|
|
|
|
|
accessing the device as well as the I2C interface to the chip itself.
|
|
|
|
|
Additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device.
|
2011-01-18 19:21:35 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
This driver can be built as a module. If built as a module it will be
|
|
|
|
|
called "da9055"
|
2011-01-18 19:21:35 +00:00
|
|
|
|
2013-07-29 17:00:43 +00:00
|
|
|
config MFD_DA9063
|
|
|
|
|
bool "Dialog Semiconductor DA9063 PMIC Support"
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-07-29 17:00:43 +00:00
|
|
|
help
|
|
|
|
|
Say yes here for support for the Dialog Semiconductor DA9063 PMIC.
|
|
|
|
|
This includes the I2C driver and core APIs.
|
|
|
|
|
Additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MC13XXX
|
|
|
|
|
tristate
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on (SPI_MASTER || I2C)
|
2012-10-16 07:25:43 +00:00
|
|
|
select MFD_CORE
|
2014-06-18 17:05:40 +00:00
|
|
|
select REGMAP_IRQ
|
2012-10-16 07:25:43 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Enable support for the Freescale MC13783 and MC13892 PMICs.
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the
|
|
|
|
|
functionality of the device.
|
2011-01-18 19:21:35 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MC13XXX_SPI
|
|
|
|
|
tristate "Freescale MC13783 and MC13892 SPI interface"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on SPI_MASTER
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_SPI
|
|
|
|
|
select MFD_MC13XXX
|
|
|
|
|
help
|
|
|
|
|
Select this if your MC13xxx is connected via an SPI bus.
|
2011-01-18 19:21:35 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MC13XXX_I2C
|
|
|
|
|
tristate "Freescale MC13892 I2C interface"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
select MFD_MC13XXX
|
2012-10-16 07:25:43 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Select this if your MC13xxx is connected via an I2C bus.
|
2012-10-16 07:25:43 +00:00
|
|
|
|
2008-04-09 18:20:34 +00:00
|
|
|
config HTC_EGPIO
|
|
|
|
|
bool "HTC EGPIO support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on GPIOLIB && ARM
|
2008-04-09 18:20:34 +00:00
|
|
|
help
|
|
|
|
|
This driver supports the CPLD egpio chip present on
|
|
|
|
|
several HTC phones. It provides basic support for input
|
|
|
|
|
pins, output pins, and irqs.
|
|
|
|
|
|
2008-04-12 12:25:41 +00:00
|
|
|
config HTC_PASIC3
|
|
|
|
|
tristate "HTC PASIC3 LED/DS1WM chip support"
|
2009-02-17 09:06:45 +00:00
|
|
|
select MFD_CORE
|
2008-04-12 12:25:41 +00:00
|
|
|
help
|
|
|
|
|
This core driver provides register access for the LED/DS1WM
|
|
|
|
|
chips labeled "AIC2" and "AIC3", found on HTC Blueangel and
|
|
|
|
|
HTC Magician devices, respectively. Actual functionality is
|
|
|
|
|
handled by the leds-pasic3 and ds1wm drivers.
|
|
|
|
|
|
2010-01-19 10:22:45 +00:00
|
|
|
config HTC_I2CPLD
|
|
|
|
|
bool "HTC I2C PLD chip support"
|
2010-01-21 03:55:34 +00:00
|
|
|
depends on I2C=y && GPIOLIB
|
2010-01-19 10:22:45 +00:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the supposed CPLD
|
|
|
|
|
found on omap850 HTC devices like the HTC Wizard and HTC Herald.
|
|
|
|
|
This device provides input and output GPIOs through an I2C
|
|
|
|
|
interface to one or more sub-chips.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config LPC_ICH
|
|
|
|
|
tristate "Intel ICH LPC"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on PCI
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_CORE
|
2008-08-03 20:34:08 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
The LPC bridge function of the Intel ICH provides support for
|
|
|
|
|
many functional units. This driver provides needed support for
|
|
|
|
|
other drivers to control these functions, currently GPIO and
|
|
|
|
|
watchdog.
|
2008-08-03 20:34:08 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config LPC_SCH
|
|
|
|
|
tristate "Intel SCH LPC"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on PCI
|
2012-05-03 10:26:36 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
LPC bridge function of the Intel SCH provides support for
|
|
|
|
|
System Management Bus and General Purpose I/O.
|
2012-05-03 10:26:36 +00:00
|
|
|
|
2014-06-03 05:26:03 +00:00
|
|
|
config INTEL_SOC_PMIC
|
|
|
|
|
bool "Support for Intel Atom SoC PMIC"
|
|
|
|
|
depends on I2C=y
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable support for the PMIC device
|
|
|
|
|
on some Intel SoC systems. The PMIC provides ADC, GPIO,
|
|
|
|
|
thermal, charger and related power management functions
|
|
|
|
|
on these systems.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_INTEL_MSIC
|
|
|
|
|
bool "Intel MSIC"
|
|
|
|
|
depends on INTEL_SCU_IPC
|
2011-03-24 19:12:47 +00:00
|
|
|
select MFD_CORE
|
2011-03-09 12:02:38 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Select this option to enable access to Intel MSIC (Avatele
|
|
|
|
|
Passage) chip. This chip embeds audio, battery, GPIO, etc.
|
|
|
|
|
devices used in Intel Medfield platforms.
|
2011-03-09 12:02:38 +00:00
|
|
|
|
2014-04-03 15:45:15 +00:00
|
|
|
config MFD_IPAQ_MICRO
|
|
|
|
|
bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
|
|
|
|
|
depends on SA1100_H3100 || SA1100_H3600
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
Select this to get support for the Microcontroller found in
|
|
|
|
|
the Compaq iPAQ handheld computers. This is an Atmel
|
|
|
|
|
AT90LS8535 microcontroller flashed with a special iPAQ
|
|
|
|
|
firmware using the custom protocol implemented in this driver.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_JANZ_CMODIO
|
|
|
|
|
tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
|
|
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on PCI
|
2008-12-22 11:16:27 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This is the core driver for the Janz CMOD-IO PCI MODULbus
|
|
|
|
|
carrier board. This device is a PCI to MODULbus bridge which may
|
|
|
|
|
host many different types of MODULbus daughterboards, including
|
|
|
|
|
CAN and GPIO controllers.
|
2008-12-22 11:16:27 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_JZ4740_ADC
|
|
|
|
|
bool "Janz JZ4740 ADC core"
|
2010-04-08 07:04:55 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
depends on MACH_JZ4740
|
2010-04-08 07:04:55 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here if you want support for the ADC unit in the JZ4740 SoC.
|
|
|
|
|
This driver is necessary for jz4740-battery and jz4740-hwmon driver.
|
2010-04-08 07:04:55 +00:00
|
|
|
|
2013-06-24 04:00:03 +00:00
|
|
|
config MFD_KEMPLD
|
|
|
|
|
tristate "Kontron module PLD device"
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
This is the core driver for the PLD (Programmable Logic Device) found
|
|
|
|
|
on some Kontron ETX and COMexpress (ETXexpress) modules. The PLD
|
|
|
|
|
device may provide functions like watchdog, GPIO, UART and I2C bus.
|
|
|
|
|
|
|
|
|
|
The following modules are supported:
|
2014-02-24 07:53:46 +00:00
|
|
|
* COMe-bHL6
|
2013-06-24 04:00:03 +00:00
|
|
|
* COMe-bIP#
|
|
|
|
|
* COMe-bPC2 (ETXexpress-PC)
|
|
|
|
|
* COMe-bSC# (ETXexpress-SC T#)
|
2014-02-24 07:53:46 +00:00
|
|
|
* COMe-cBT6
|
2013-06-24 04:00:03 +00:00
|
|
|
* COMe-cCT6
|
|
|
|
|
* COMe-cDC2 (microETXexpress-DC)
|
2014-02-24 07:53:46 +00:00
|
|
|
* COMe-cHL6
|
2013-06-24 04:00:03 +00:00
|
|
|
* COMe-cPC2 (microETXexpress-PC)
|
2014-02-24 07:53:46 +00:00
|
|
|
* COMe-mBT10
|
2013-06-24 04:00:03 +00:00
|
|
|
* COMe-mCT10
|
2014-02-24 07:53:46 +00:00
|
|
|
* COMe-mTT10 (nanoETXexpress-TT)
|
2013-06-24 04:00:03 +00:00
|
|
|
* ETX-OH
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called kempld-core.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_88PM800
|
|
|
|
|
tristate "Marvell 88PM800"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-01-11 10:41:41 +00:00
|
|
|
select REGMAP_I2C
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_IRQ
|
|
|
|
|
select MFD_CORE
|
2012-01-11 10:41:41 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This supports for Marvell 88PM800 Power Management IC.
|
|
|
|
|
This includes the I2C driver and the core APIs _only_, you have to
|
|
|
|
|
select individual components like voltage regulators, RTC and
|
|
|
|
|
battery-charger under the corresponding menus.
|
2012-01-11 10:41:41 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_88PM805
|
|
|
|
|
tristate "Marvell 88PM805"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-07-18 06:20:46 +00:00
|
|
|
select REGMAP_I2C
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_IRQ
|
|
|
|
|
select MFD_CORE
|
2011-04-15 12:04:45 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This supports for Marvell 88PM805 Power Management IC. This includes
|
|
|
|
|
the I2C driver and the core APIs _only_, you have to select individual
|
|
|
|
|
components like codec device, headset/Mic device under the
|
|
|
|
|
corresponding menus.
|
2011-04-15 12:04:45 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_88PM860X
|
|
|
|
|
bool "Marvell 88PM8606/88PM8607"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
This supports for Marvell 88PM8606/88PM8607 Power Management IC.
|
|
|
|
|
This includes the I2C driver and the core APIs _only_, you have to
|
|
|
|
|
select individual components like voltage regulators, RTC and
|
|
|
|
|
battery-charger under the corresponding menus.
|
2011-04-15 12:04:45 +00:00
|
|
|
|
2013-11-22 15:51:05 +00:00
|
|
|
config MFD_MAX14577
|
2014-04-14 09:17:18 +00:00
|
|
|
bool "Maxim Semiconductor MAX14577/77836 MUIC + Charger Support"
|
2013-11-22 15:51:05 +00:00
|
|
|
depends on I2C=y
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
2014-03-11 14:21:42 +00:00
|
|
|
select REGMAP_IRQ
|
2013-11-22 15:51:05 +00:00
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
help
|
2014-04-14 09:17:18 +00:00
|
|
|
Say yes here to add support for Maxim Semiconductor MAX14577 and
|
|
|
|
|
MAX77836 Micro-USB ICs with battery charger.
|
2013-11-22 15:51:05 +00:00
|
|
|
This driver provides common support for accessing the device;
|
|
|
|
|
additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MAX77686
|
2014-07-24 12:39:24 +00:00
|
|
|
bool "Maxim Semiconductor MAX77686/802 PMIC Support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2011-07-04 15:34:16 +00:00
|
|
|
select MFD_CORE
|
2012-02-21 12:51:34 +00:00
|
|
|
select REGMAP_I2C
|
2014-07-04 20:24:04 +00:00
|
|
|
select REGMAP_IRQ
|
2012-05-18 09:52:19 +00:00
|
|
|
select IRQ_DOMAIN
|
2011-07-04 15:34:16 +00:00
|
|
|
help
|
2014-07-24 12:39:24 +00:00
|
|
|
Say yes here to add support for Maxim Semiconductor MAX77686 and
|
|
|
|
|
MAX77802 which are Power Management IC with an RTC on chip.
|
2013-04-09 12:40:09 +00:00
|
|
|
This driver provides common support for accessing the device;
|
|
|
|
|
additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device.
|
2011-06-09 19:50:00 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MAX77693
|
|
|
|
|
bool "Maxim Semiconductor MAX77693 PMIC Support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2011-06-09 19:50:00 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_I2C
|
2014-05-21 06:52:48 +00:00
|
|
|
select REGMAP_IRQ
|
2011-06-09 19:50:00 +00:00
|
|
|
help
|
2014-02-11 04:50:51 +00:00
|
|
|
Say yes here to add support for Maxim Semiconductor MAX77693.
|
2013-04-09 12:40:09 +00:00
|
|
|
This is a companion Power Management IC with Flash, Haptic, Charger,
|
|
|
|
|
and MUIC(Micro USB Interface Controller) controls on chip.
|
|
|
|
|
This driver provides common support for accessing the device;
|
|
|
|
|
additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device.
|
2011-06-09 19:50:00 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MAX8907
|
|
|
|
|
tristate "Maxim Semiconductor MAX8907 PMIC Support"
|
2011-06-09 19:50:00 +00:00
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-11-14 15:39:28 +00:00
|
|
|
select REGMAP_I2C
|
2012-12-05 13:19:48 +00:00
|
|
|
select REGMAP_IRQ
|
2012-11-14 15:39:28 +00:00
|
|
|
help
|
2014-02-11 04:50:51 +00:00
|
|
|
Say yes here to add support for Maxim Semiconductor MAX8907. This is
|
2013-04-09 12:40:09 +00:00
|
|
|
a Power Management IC. This driver provides common support for
|
|
|
|
|
accessing the device; additional drivers must be enabled in order
|
|
|
|
|
to use the functionality of the device.
|
2012-11-14 15:39:28 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MAX8925
|
|
|
|
|
bool "Maxim Semiconductor MAX8925 PMIC Support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_CORE
|
2008-12-22 11:18:02 +00:00
|
|
|
help
|
2014-02-11 04:50:51 +00:00
|
|
|
Say yes here to add support for Maxim Semiconductor MAX8925. This is
|
2013-04-09 12:40:09 +00:00
|
|
|
a Power Management IC. This driver provides common support for
|
|
|
|
|
accessing the device, additional drivers must be enabled in order
|
|
|
|
|
to use the functionality of the device.
|
2008-12-22 11:18:02 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MAX8997
|
|
|
|
|
bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_CORE
|
2012-02-24 21:58:54 +00:00
|
|
|
select IRQ_DOMAIN
|
2008-10-15 10:15:39 +00:00
|
|
|
help
|
2014-02-11 04:50:51 +00:00
|
|
|
Say yes here to add support for Maxim Semiconductor MAX8997/8966.
|
2013-04-09 12:40:09 +00:00
|
|
|
This is a Power Management IC with RTC, Flash, Fuel Gauge, Haptic,
|
|
|
|
|
MUIC controls on chip.
|
|
|
|
|
This driver provides common support for accessing the device;
|
|
|
|
|
additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device.
|
2008-10-15 10:15:39 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_MAX8998
|
|
|
|
|
bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_CORE
|
2013-06-24 12:39:52 +00:00
|
|
|
select IRQ_DOMAIN
|
2011-03-01 13:42:26 +00:00
|
|
|
help
|
2014-02-11 04:50:51 +00:00
|
|
|
Say yes here to add support for Maxim Semiconductor MAX8998 and
|
2013-04-09 12:40:09 +00:00
|
|
|
National Semiconductor LP3974. This is a Power Management IC.
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device.
|
2011-03-01 13:42:26 +00:00
|
|
|
|
2014-08-27 17:51:45 +00:00
|
|
|
config MFD_MENF21BMC
|
|
|
|
|
tristate "MEN 14F021P00 Board Management Controller Support"
|
|
|
|
|
depends on I2C
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
Say yes here to add support for the MEN 14F021P00 BMC
|
|
|
|
|
which is a Board Management Controller connected to the I2C bus.
|
|
|
|
|
The device supports multiple sub-devices like LED, HWMON and WDT.
|
|
|
|
|
This driver provides common support for accessing the devices;
|
|
|
|
|
additional drivers must be enabled in order to use the
|
|
|
|
|
functionality of the BMC device.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so the module
|
|
|
|
|
will be called menf21bmc.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config EZX_PCAP
|
|
|
|
|
bool "Motorola EZXPCAP Support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on SPI_MASTER
|
2009-08-31 16:32:18 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This enables the PCAP ASIC present on EZX Phones. This is
|
|
|
|
|
needed for MMC, TouchScreen, Sound, USB, etc..
|
2009-08-31 16:32:18 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_VIPERBOARD
|
|
|
|
|
tristate "Nano River Technologies Viperboard"
|
2009-10-22 10:26:45 +00:00
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on USB
|
2009-10-22 10:26:45 +00:00
|
|
|
default n
|
2013-04-09 12:40:09 +00:00
|
|
|
help
|
|
|
|
|
Say yes here if you want support for Nano River Technologies
|
|
|
|
|
Viperboard.
|
|
|
|
|
There are mfd cell drivers available for i2c master, adc and
|
|
|
|
|
both gpios found on the board. The spi part does not yet
|
|
|
|
|
have a driver.
|
|
|
|
|
You need to select the mfd cell drivers separately.
|
|
|
|
|
The drivers do not support all features the board exposes.
|
2009-10-22 10:26:45 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_RETU
|
2013-04-09 19:51:25 +00:00
|
|
|
tristate "Nokia Retu and Tahvo multi-function device"
|
2011-04-27 07:14:07 +00:00
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C
|
2012-10-11 11:55:32 +00:00
|
|
|
select REGMAP_IRQ
|
2012-04-03 08:56:51 +00:00
|
|
|
help
|
2013-04-09 19:51:25 +00:00
|
|
|
Retu and Tahvo are a multi-function devices found on Nokia
|
|
|
|
|
Internet Tablets (770, N800 and N810).
|
2011-04-27 07:14:07 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_PCF50633
|
|
|
|
|
tristate "NXP PCF50633"
|
|
|
|
|
depends on I2C
|
|
|
|
|
select REGMAP_I2C
|
2010-07-02 11:22:08 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here if you have NXP PCF50633 chip on your board.
|
|
|
|
|
This core driver provides register access and IRQ handling
|
|
|
|
|
facilities, and registers devices for the various functions
|
|
|
|
|
so that function-specific drivers can bind to them.
|
2011-11-17 05:32:20 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config PCF50633_ADC
|
|
|
|
|
tristate "NXP PCF50633 ADC"
|
|
|
|
|
depends on MFD_PCF50633
|
2011-11-17 05:32:20 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here if you want to include support for ADC in the
|
|
|
|
|
NXP PCF50633 chip.
|
2011-11-17 05:32:21 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config PCF50633_GPIO
|
|
|
|
|
tristate "NXP PCF50633 GPIO"
|
|
|
|
|
depends on MFD_PCF50633
|
2011-11-17 05:32:21 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here if you want to include support GPIO for pins on
|
|
|
|
|
the PCF50633 chip.
|
2011-11-17 05:32:20 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config UCB1400_CORE
|
|
|
|
|
tristate "Philips UCB1400 Core driver"
|
|
|
|
|
depends on AC97_BUS
|
|
|
|
|
depends on GPIOLIB
|
2010-05-10 21:39:47 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This enables support for the Philips UCB1400 core functions.
|
|
|
|
|
The UCB1400 is an AC97 audio codec.
|
2010-05-10 21:39:47 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ucb1400_core.
|
2010-05-10 21:39:47 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_PM8XXX
|
|
|
|
|
tristate
|
2008-08-05 17:27:58 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_PM8921_CORE
|
|
|
|
|
tristate "Qualcomm PM8921 PMIC chip"
|
2014-02-26 18:59:25 +00:00
|
|
|
depends on (ARM || HEXAGON)
|
2014-02-26 18:59:21 +00:00
|
|
|
select IRQ_DOMAIN
|
2008-07-15 14:09:43 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_PM8XXX
|
2014-02-26 18:59:23 +00:00
|
|
|
select REGMAP
|
2008-07-15 14:09:43 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes to this option, support will be included for the
|
|
|
|
|
built-in PM8921 PMIC chip.
|
2008-07-15 14:09:43 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
This is required if your board has a PM8921 and uses its features,
|
|
|
|
|
such as: MPPs, GPIOs, regulators, interrupts, and PWM.
|
|
|
|
|
|
|
|
|
|
Say M here if you want to include support for PM8921 chip as a module.
|
|
|
|
|
This will build a module called "pm8921-core".
|
|
|
|
|
|
|
|
|
|
config MFD_RDC321X
|
|
|
|
|
tristate "RDC R-321x southbridge"
|
|
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on PCI
|
2013-04-09 12:40:09 +00:00
|
|
|
help
|
|
|
|
|
Say yes here if you want to have support for the RDC R-321x SoC
|
|
|
|
|
southbridge which provides access to GPIOs and Watchdog using the
|
|
|
|
|
southbridge PCI device configuration space.
|
|
|
|
|
|
|
|
|
|
config MFD_RTSX_PCI
|
|
|
|
|
tristate "Realtek PCI-E card reader"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on PCI
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
This supports for Realtek PCI-Express card reader including rts5209,
|
|
|
|
|
rts5229, rtl8411, etc. Realtek card reader supports access to many
|
|
|
|
|
types of memory cards, such as Memory Stick, Memory Stick Pro,
|
|
|
|
|
Secure Digital and MultiMediaCard.
|
|
|
|
|
|
2014-02-12 10:00:36 +00:00
|
|
|
config MFD_RTSX_USB
|
|
|
|
|
tristate "Realtek USB card reader"
|
|
|
|
|
depends on USB
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
Select this option to get support for Realtek USB 2.0 card readers
|
|
|
|
|
including RTS5129, RTS5139, RTS5179 and RTS5170.
|
|
|
|
|
Realtek card reader supports access to many types of memory cards,
|
|
|
|
|
such as Memory Stick Pro, Secure Digital and MultiMediaCard.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_RC5T583
|
|
|
|
|
bool "Ricoh RC5T583 Power Management system device"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
Select this option to get support for the RICOH583 Power
|
|
|
|
|
Management system device.
|
|
|
|
|
This driver provides common support for accessing the device
|
|
|
|
|
through i2c interface. The device supports multiple sub-devices
|
|
|
|
|
like GPIO, interrupts, RTC, LDO and DCDC regulators, onkey.
|
|
|
|
|
Additional drivers must be enabled in order to use the
|
|
|
|
|
different functionality of the device.
|
|
|
|
|
|
|
|
|
|
config MFD_SEC_CORE
|
|
|
|
|
bool "SAMSUNG Electronics PMIC Series Support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
2014-06-25 07:14:47 +00:00
|
|
|
select REGULATOR
|
2013-04-09 12:40:09 +00:00
|
|
|
help
|
|
|
|
|
Support for the Samsung Electronics MFD series.
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device
|
|
|
|
|
|
2013-04-18 16:58:30 +00:00
|
|
|
config MFD_SI476X_CORE
|
|
|
|
|
tristate "Silicon Laboratories 4761/64/68 AM/FM radio."
|
|
|
|
|
depends on I2C
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
This is the core driver for the SI476x series of AM/FM
|
|
|
|
|
radio. This MFD driver connects the radio-si476x V4L2 module
|
|
|
|
|
and the si476x audio codec.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called si476x-core.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_SM501
|
|
|
|
|
tristate "Silicon Motion SM501"
|
|
|
|
|
---help---
|
|
|
|
|
This is the core driver for the Silicon Motion SM501 multimedia
|
|
|
|
|
companion chip. This device is a multifunction device which may
|
|
|
|
|
provide numerous interfaces including USB host controller, USB gadget,
|
|
|
|
|
asynchronous serial ports, audio functions, and a dual display video
|
|
|
|
|
interface. The device may be connected by PCI or local bus with
|
|
|
|
|
varying functions enabled.
|
|
|
|
|
|
|
|
|
|
config MFD_SM501_GPIO
|
|
|
|
|
bool "Export GPIO via GPIO layer"
|
|
|
|
|
depends on MFD_SM501 && GPIOLIB
|
|
|
|
|
---help---
|
|
|
|
|
This option uses the gpio library layer to export the 64 GPIO
|
|
|
|
|
lines on the SM501. The platform data is used to supply the
|
|
|
|
|
base number for the first GPIO line to register.
|
2008-07-15 14:09:43 +00:00
|
|
|
|
2012-10-01 11:01:22 +00:00
|
|
|
config MFD_SMSC
|
2013-04-09 12:40:09 +00:00
|
|
|
bool "SMSC ECE1099 series chips"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-10-01 11:01:22 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the
|
|
|
|
|
ece1099 chips from SMSC.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called smsc.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config ABX500_CORE
|
|
|
|
|
bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
|
|
|
|
|
default y if ARCH_U300 || ARCH_U8500
|
2008-07-15 14:12:52 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here if you have the ABX500 Mixed Signal IC family
|
|
|
|
|
chips. This core driver expose register access functions.
|
|
|
|
|
Functionality specific drivers using these functions can
|
|
|
|
|
remain unchanged when IC changes. Binding of the functions to
|
|
|
|
|
actual register access is done by the IC core driver.
|
2008-07-15 14:12:52 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config AB3100_CORE
|
|
|
|
|
bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y && ABX500_CORE
|
2008-06-27 09:37:57 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
default y if ARCH_U300
|
2008-06-22 11:01:58 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Select this to enable the AB3100 Mixed Signal IC core
|
|
|
|
|
functionality. This connects to a AB3100 on the I2C bus
|
|
|
|
|
and expose a number of symbols needed for dependent devices
|
|
|
|
|
to read and write registers and subscribe to events from
|
|
|
|
|
this multi-functional IC. This is needed to use other features
|
|
|
|
|
of the AB3100 such as battery-backed RTC, charging control,
|
|
|
|
|
LEDs, vibrator, system power and temperature, power management
|
|
|
|
|
and ALSA sound.
|
2008-06-22 11:01:58 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config AB3100_OTP
|
|
|
|
|
tristate "ST-Ericsson AB3100 OTP functions"
|
|
|
|
|
depends on AB3100_CORE
|
|
|
|
|
default y if AB3100_CORE
|
2008-10-24 15:10:05 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Select this to enable the AB3100 Mixed Signal IC OTP (one-time
|
|
|
|
|
programmable memory) support. This exposes a sysfs file to read
|
|
|
|
|
out OTP values.
|
2009-10-12 15:22:38 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config AB8500_CORE
|
|
|
|
|
bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on ABX500_CORE && MFD_DB8500_PRCMU
|
2013-04-09 12:40:09 +00:00
|
|
|
select POWER_SUPPLY
|
2011-12-12 14:36:56 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable access to AB8500 power management
|
|
|
|
|
chip. This connects to U8500 either on the SSP/SPI bus (deprecated
|
|
|
|
|
since hardware version v1.0) or the I2C bus via PRCMU. It also adds
|
|
|
|
|
the irq_chip parts for handling the Mixed Signal chip events.
|
|
|
|
|
This chip embeds various other multimedia funtionalities as well.
|
2011-12-12 14:36:56 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config AB8500_DEBUG
|
|
|
|
|
bool "Enable debug info via debugfs"
|
2013-05-03 07:52:32 +00:00
|
|
|
depends on AB8500_GPADC && DEBUG_FS
|
2013-04-09 12:40:09 +00:00
|
|
|
default y if DEBUG_FS
|
|
|
|
|
help
|
|
|
|
|
Select this option if you want debug information using the debug
|
|
|
|
|
filesystem, debugfs.
|
|
|
|
|
|
|
|
|
|
config AB8500_GPADC
|
|
|
|
|
bool "ST-Ericsson AB8500 GPADC driver"
|
|
|
|
|
depends on AB8500_CORE && REGULATOR_AB8500
|
|
|
|
|
default y
|
2011-12-12 15:07:41 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
|
2011-12-12 15:07:41 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_DB8500_PRCMU
|
|
|
|
|
bool "ST-Ericsson DB8500 Power Reset Control Management Unit"
|
|
|
|
|
depends on UX500_SOC_DB8500
|
|
|
|
|
select MFD_CORE
|
2011-12-12 14:36:56 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Select this option to enable support for the DB8500 Power Reset
|
|
|
|
|
and Control Management Unit. This is basically an autonomous
|
|
|
|
|
system controller running an XP70 microprocessor, which is accessed
|
|
|
|
|
through a register map.
|
2011-12-12 14:36:56 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_STMPE
|
|
|
|
|
bool "STMicroelectronics STMPE"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on (I2C=y || SPI_MASTER=y)
|
2014-04-23 21:35:58 +00:00
|
|
|
depends on OF
|
2012-09-14 13:24:50 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the STMPE family of I/O Expanders from
|
|
|
|
|
STMicroelectronics.
|
2012-09-14 13:24:50 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
Currently supported devices are:
|
2012-09-14 13:24:50 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
STMPE811: GPIO, Touchscreen
|
|
|
|
|
STMPE1601: GPIO, Keypad
|
|
|
|
|
STMPE1801: GPIO, Keypad
|
|
|
|
|
STMPE2401: GPIO, Keypad
|
|
|
|
|
STMPE2403: GPIO, Keypad
|
|
|
|
|
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the functionality
|
|
|
|
|
of the device. Currently available sub drivers are:
|
|
|
|
|
|
|
|
|
|
GPIO: stmpe-gpio
|
|
|
|
|
Keypad: stmpe-keypad
|
|
|
|
|
Touchscreen: stmpe-ts
|
|
|
|
|
|
|
|
|
|
menu "STMicroelectronics STMPE Interface Drivers"
|
|
|
|
|
depends on MFD_STMPE
|
|
|
|
|
|
|
|
|
|
config STMPE_I2C
|
2013-09-29 11:54:15 +00:00
|
|
|
bool "STMicroelectronics STMPE I2C Interface"
|
2009-10-12 15:22:38 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
default y
|
2009-10-12 15:22:38 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This is used to enable I2C interface of STMPE
|
2008-10-24 15:10:05 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config STMPE_SPI
|
2013-09-29 11:54:15 +00:00
|
|
|
bool "STMicroelectronics STMPE SPI Interface"
|
2013-04-09 12:40:09 +00:00
|
|
|
depends on SPI_MASTER
|
2012-09-19 16:53:33 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This is used to enable SPI interface of STMPE
|
|
|
|
|
endmenu
|
2012-09-19 16:53:33 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_STA2X11
|
|
|
|
|
bool "STMicroelectronics STA2X11"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on STA2X11
|
2012-06-25 08:34:36 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_MMIO
|
|
|
|
|
|
2014-05-09 11:11:47 +00:00
|
|
|
config MFD_SUN6I_PRCM
|
|
|
|
|
bool "Allwinner A31 PRCM controller"
|
|
|
|
|
depends on ARCH_SUNXI
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
Support for the PRCM (Power/Reset/Clock Management) unit available
|
|
|
|
|
in A31 SoC.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_SYSCON
|
|
|
|
|
bool "System Controller Register R/W Based on Regmap"
|
|
|
|
|
select REGMAP_MMIO
|
2012-06-25 08:34:36 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Select this option to enable accessing system control registers
|
|
|
|
|
via regmap.
|
2012-06-25 08:34:36 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_DAVINCI_VOICECODEC
|
|
|
|
|
tristate
|
2012-05-14 20:50:39 +00:00
|
|
|
select MFD_CORE
|
2014-06-05 21:24:13 +00:00
|
|
|
select REGMAP_MMIO
|
2012-05-14 20:50:39 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TI_AM335X_TSCADC
|
|
|
|
|
tristate "TI ADC / Touch Screen chip support"
|
2012-08-15 16:28:46 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP
|
|
|
|
|
select REGMAP_MMIO
|
2012-08-15 16:28:46 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for Texas Instruments series
|
|
|
|
|
of Touch Screen /ADC chips.
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called ti_am335x_tscadc.
|
2012-08-15 16:28:46 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_DM355EVM_MSP
|
|
|
|
|
bool "TI DaVinci DM355 EVM microcontroller"
|
|
|
|
|
depends on I2C=y && MACH_DAVINCI_DM355_EVM
|
2010-01-08 11:29:23 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This driver supports the MSP430 microcontroller used on these
|
|
|
|
|
boards. MSP430 firmware manages resets and power sequencing,
|
|
|
|
|
inputs from buttons and the IR remote, LEDs, an RTC, and more.
|
2010-01-08 11:29:23 +00:00
|
|
|
|
2013-12-06 02:18:41 +00:00
|
|
|
config MFD_LP3943
|
|
|
|
|
tristate "TI/National Semiconductor LP3943 MFD Driver"
|
|
|
|
|
depends on I2C
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
Support for the TI/National Semiconductor LP3943.
|
|
|
|
|
This driver consists of GPIO and PWM drivers.
|
|
|
|
|
With these functionalities, it can be used for LED string control or
|
|
|
|
|
general usage such like a GPIO controller and a PWM controller.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_LP8788
|
|
|
|
|
bool "TI LP8788 Power Management Unit Driver"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2011-03-04 06:50:26 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_I2C
|
2012-07-02 00:02:55 +00:00
|
|
|
select IRQ_DOMAIN
|
2011-03-04 06:50:26 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
TI LP8788 PMU supports regulators, battery charger, RTC,
|
|
|
|
|
ADC, backlight driver and current sinks.
|
2011-03-04 06:50:26 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_OMAP_USB_HOST
|
|
|
|
|
bool "TI OMAP USBHS core and TLL driver"
|
|
|
|
|
depends on USB_EHCI_HCD_OMAP || USB_OHCI_HCD_OMAP3
|
|
|
|
|
default y
|
2010-06-16 07:04:16 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This is the core driver for the OAMP EHCI and OHCI drivers.
|
|
|
|
|
This MFD driver does the required setup functionalities for
|
|
|
|
|
OMAP USB Host drivers.
|
2010-06-16 07:04:16 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_PALMAS
|
|
|
|
|
bool "TI Palmas series chips"
|
2012-01-08 23:09:09 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
2012-07-11 12:08:11 +00:00
|
|
|
select REGMAP_IRQ
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-01-08 23:09:09 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the Palmas
|
|
|
|
|
series of PMIC chips from Texas Instruments.
|
2012-01-08 23:09:09 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config TPS6105X
|
|
|
|
|
tristate "TI TPS61050/61052 Boost Converters"
|
|
|
|
|
depends on I2C
|
|
|
|
|
select REGULATOR
|
2012-06-19 15:37:06 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGULATOR_FIXED_VOLTAGE
|
2012-06-19 15:37:06 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This option enables a driver for the TP61050/TPS61052
|
|
|
|
|
high-power "white LED driver". This boost converter is
|
|
|
|
|
sometimes used for other things than white LEDs, and
|
|
|
|
|
also contains a GPIO pin.
|
2012-06-19 15:37:06 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config TPS65010
|
|
|
|
|
tristate "TI TPS6501x Power Management chips"
|
|
|
|
|
depends on I2C && GPIOLIB
|
|
|
|
|
default y if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_OSK
|
2012-06-19 15:37:06 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the TPS6501x series of
|
|
|
|
|
Power Management chips. These include voltage regulators,
|
|
|
|
|
lithium ion/polymer battery charging, and other features that
|
|
|
|
|
are often used in portable devices like cell phones and cameras.
|
2012-06-19 15:37:06 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called tps65010.
|
|
|
|
|
|
|
|
|
|
config TPS6507X
|
|
|
|
|
tristate "TI TPS6507x Power Management / Touch Screen chips"
|
2012-06-19 15:37:06 +00:00
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C
|
2012-06-19 15:37:06 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the TPS6507x series of
|
|
|
|
|
Power Management / Touch Screen chips. These include voltage
|
|
|
|
|
regulators, lithium ion/polymer battery charging, touch screen
|
|
|
|
|
and other features that are often used in portable devices.
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called tps6507x.
|
2012-06-19 15:37:06 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config TPS65911_COMPARATOR
|
|
|
|
|
tristate
|
|
|
|
|
|
|
|
|
|
config MFD_TPS65090
|
|
|
|
|
bool "TI TPS65090 Power Management chips"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-06-19 15:37:06 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
2012-07-10 11:37:58 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the TPS65090 series of
|
|
|
|
|
Power Management chips.
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the
|
|
|
|
|
functionality of the device.
|
2012-07-10 11:37:58 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TPS65217
|
|
|
|
|
tristate "TI TPS65217 Power Management / White LED chips"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C
|
2008-12-18 09:54:22 +00:00
|
|
|
select MFD_CORE
|
2011-08-23 17:56:19 +00:00
|
|
|
select REGMAP_I2C
|
2008-09-10 17:58:42 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the TPS65217 series of
|
|
|
|
|
Power Management / White LED chips.
|
|
|
|
|
These include voltage regulators, lithium ion/polymer battery
|
|
|
|
|
charger, wled and other features that are often used in portable
|
|
|
|
|
devices.
|
2008-09-10 17:58:42 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called tps65217.
|
2010-10-19 21:57:56 +00:00
|
|
|
|
2014-02-06 05:50:12 +00:00
|
|
|
config MFD_TPS65218
|
|
|
|
|
tristate "TI TPS65218 Power Management chips"
|
|
|
|
|
depends on I2C
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
2014-03-10 15:23:25 +00:00
|
|
|
select REGMAP_IRQ
|
2014-02-06 05:50:12 +00:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the TPS65218 series of
|
|
|
|
|
Power Management chips.
|
|
|
|
|
These include voltage regulators, gpio and other features
|
|
|
|
|
that are often used in portable devices. Only regulator
|
|
|
|
|
component is currently supported.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called tps65218.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TPS6586X
|
|
|
|
|
bool "TI TPS6586x Power Management chips"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2009-07-27 13:45:58 +00:00
|
|
|
select MFD_CORE
|
2011-06-10 18:28:10 +00:00
|
|
|
select REGMAP_I2C
|
2009-07-27 13:45:58 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the TPS6586X series of
|
|
|
|
|
Power Management chips.
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the
|
|
|
|
|
functionality of the device.
|
2009-07-27 13:45:58 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called tps6586x.
|
2010-10-19 21:57:56 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TPS65910
|
|
|
|
|
bool "TI TPS65910 Power Management chip"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y && GPIOLIB
|
2010-10-19 22:00:11 +00:00
|
|
|
select MFD_CORE
|
2011-06-10 18:28:10 +00:00
|
|
|
select REGMAP_I2C
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_IRQ
|
2012-05-14 21:14:24 +00:00
|
|
|
select IRQ_DOMAIN
|
2010-10-19 22:00:11 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
if you say yes here you get support for the TPS65910 series of
|
|
|
|
|
Power Management chips.
|
2008-12-18 22:09:50 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TPS65912
|
|
|
|
|
bool "TI TPS65912 Power Management chip"
|
|
|
|
|
depends on GPIOLIB
|
2013-04-17 21:28:47 +00:00
|
|
|
select MFD_CORE
|
2010-10-19 22:00:11 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the TPS65912 series of
|
|
|
|
|
PM chips.
|
2008-12-18 22:09:50 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TPS65912_I2C
|
|
|
|
|
bool "TI TPS65912 Power Management chip with I2C"
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select MFD_TPS65912
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y && GPIOLIB
|
2013-04-09 12:40:09 +00:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the TPS65912 series of
|
|
|
|
|
PM chips with I2C interface.
|
2008-12-18 22:09:50 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TPS65912_SPI
|
|
|
|
|
bool "TI TPS65912 Power Management chip with SPI"
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select MFD_TPS65912
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on SPI_MASTER && GPIOLIB
|
2008-10-10 14:58:11 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the TPS65912 series of
|
|
|
|
|
PM chips with SPI interface.
|
2008-10-10 14:58:11 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TPS80031
|
|
|
|
|
bool "TI TPS80031/TPS80032 Power Management chips"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2010-01-29 18:20:29 +00:00
|
|
|
select MFD_CORE
|
2011-06-17 12:02:27 +00:00
|
|
|
select REGMAP_I2C
|
2011-10-25 08:19:04 +00:00
|
|
|
select REGMAP_IRQ
|
2010-01-29 18:20:29 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the Texas Instruments
|
|
|
|
|
TPS80031/ TPS80032 Fully Integrated Power Management with Power
|
|
|
|
|
Path and Battery Charger. The device provides five configurable
|
|
|
|
|
step-down converters, 11 general purpose LDOs, USB OTG Module,
|
|
|
|
|
ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
|
|
|
|
|
Power Path from USB, 32K clock generator.
|
2010-01-29 18:20:29 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config TWL4030_CORE
|
|
|
|
|
bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2013-04-09 12:40:09 +00:00
|
|
|
select IRQ_DOMAIN
|
2011-08-08 08:04:40 +00:00
|
|
|
select REGMAP_I2C
|
2009-01-09 00:49:01 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here if you have TWL4030 / TWL6030 family chip on your board.
|
2009-01-09 00:49:01 +00:00
|
|
|
This core driver provides register access and IRQ handling
|
|
|
|
|
facilities, and registers devices for the various functions
|
|
|
|
|
so that function-specific drivers can bind to them.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
These multi-function chips are found on many OMAP2 and OMAP3
|
|
|
|
|
boards, providing power management, RTC, GPIO, keypad, a
|
|
|
|
|
high speed USB OTG transceiver, an audio codec (on most
|
|
|
|
|
versions) and many other features.
|
2010-09-28 14:37:20 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config TWL4030_POWER
|
|
|
|
|
bool "TI TWL4030 power resources"
|
|
|
|
|
depends on TWL4030_CORE && ARM
|
2012-04-01 06:41:39 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here if you want to use the power resources on the
|
|
|
|
|
TWL4030 family chips. Most of these resources are regulators,
|
|
|
|
|
which have a separate driver; some are control signals, such
|
|
|
|
|
as clock request handshaking.
|
2012-04-01 06:41:39 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
This driver uses board-specific data to initialize the resources
|
|
|
|
|
and load scripts controlling which resources are switched off/on
|
|
|
|
|
or reset when a sleep, wakeup or warm reset event occurs.
|
2010-05-01 16:26:20 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TWL4030_AUDIO
|
|
|
|
|
bool "TI TWL4030 Audio"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on TWL4030_CORE
|
2010-08-20 08:27:12 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
default n
|
mfd: add PCAP driver
The PCAP Asic as present on EZX phones is a multi function device with
voltage regulators, ADC, touch screen controller, RTC, USB transceiver,
leds controller, and audio codec.
It has two SPI ports, typically one is connected to the application
processor and another to the baseband, this driver provides read/write
functions to its registers, irq demultiplexer and ADC
queueing/abstraction.
This chip is used on a lot of Motorola phones, it was manufactured by TI
as a custom product with the name PTWL93017, later this design evolved
into the ATLAS PMIC from Freescale (MC13783).
Signed-off-by: Daniel Ribeiro <drwyrm@gmail.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2009-05-28 18:43:37 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config TWL6040_CORE
|
|
|
|
|
bool "TI TWL6040 audio codec"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2010-05-19 09:39:02 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
|
|
|
|
default n
|
2009-10-12 15:11:52 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Say yes here if you want support for Texas Instruments TWL6040 audio
|
|
|
|
|
codec.
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the
|
|
|
|
|
functionality of the device (audio, vibra).
|
2011-02-22 09:11:13 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MENELAUS
|
|
|
|
|
bool "TI TWL92330/Menelaus PM chip"
|
|
|
|
|
depends on I2C=y && ARCH_OMAP2
|
2011-02-22 09:11:13 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
If you say yes here you get support for the Texas Instruments
|
|
|
|
|
TWL92330/Menelaus Power Management chip. This include voltage
|
|
|
|
|
regulators, Dual slot memory card transceivers, real-time clock
|
|
|
|
|
and other features that are often used in portable devices like
|
|
|
|
|
cell phones and PDAs.
|
2010-09-13 14:05:04 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WL1273_CORE
|
|
|
|
|
tristate "TI WL1273 FM radio"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C
|
2011-05-15 20:53:56 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
default n
|
2011-05-15 20:53:56 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
This is the core driver for the TI WL1273 FM radio. This MFD
|
|
|
|
|
driver connects the radio-wl1273 V4L2 module and the wl1273
|
|
|
|
|
audio codec.
|
2011-05-15 20:53:56 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_LM3533
|
|
|
|
|
tristate "TI/National Semiconductor LM3533 Lighting Power chip"
|
|
|
|
|
depends on I2C
|
2010-11-26 10:52:35 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enable support for National Semiconductor / TI
|
|
|
|
|
LM3533 Lighting Power chips.
|
|
|
|
|
|
|
|
|
|
This driver provides common support for accessing the device;
|
|
|
|
|
additional drivers must be enabled in order to use the LED,
|
|
|
|
|
backlight or ambient-light-sensor functionality of the device.
|
2010-11-26 10:52:35 +00:00
|
|
|
|
2010-02-04 11:18:52 +00:00
|
|
|
config MFD_TIMBERDALE
|
2013-04-09 12:40:09 +00:00
|
|
|
tristate "Timberdale FPGA"
|
2010-02-04 11:18:52 +00:00
|
|
|
select MFD_CORE
|
2014-06-16 11:56:01 +00:00
|
|
|
depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST)
|
2010-02-04 11:18:52 +00:00
|
|
|
---help---
|
|
|
|
|
This is the core driver for the timberdale FPGA. This device is a
|
|
|
|
|
multifunction device which exposes numerous platform devices.
|
|
|
|
|
|
|
|
|
|
The timberdale FPGA can be found on the Intel Atom development board
|
|
|
|
|
for in-vehicle infontainment, called Russellville.
|
2010-02-19 10:26:25 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TC3589X
|
|
|
|
|
bool "Toshiba TC35892 and variants"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2010-02-19 10:26:25 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the Toshiba TC35892 and variants I/O Expander.
|
2010-02-19 10:26:25 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the
|
|
|
|
|
functionality of the device.
|
2012-03-28 14:43:10 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TMIO
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
|
|
|
|
config MFD_T7L66XB
|
|
|
|
|
bool "Toshiba T7L66XB"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on ARM && HAVE_CLK
|
2010-03-21 00:06:05 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_TMIO
|
2010-03-21 00:06:05 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for Toshiba Mobile IO Controller T7L66XB
|
2010-03-21 00:06:05 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TC6387XB
|
|
|
|
|
bool "Toshiba TC6387XB"
|
|
|
|
|
depends on ARM && HAVE_CLK
|
2010-04-07 07:43:00 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_TMIO
|
2010-04-07 07:43:00 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for Toshiba Mobile IO Controller TC6387XB
|
2010-04-07 07:43:00 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_TC6393XB
|
|
|
|
|
bool "Toshiba TC6393XB"
|
|
|
|
|
depends on ARM && HAVE_CLK
|
|
|
|
|
select GPIOLIB
|
2010-07-12 01:48:08 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_TMIO
|
2010-07-12 01:48:08 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for Toshiba Mobile IO Controller TC6393XB
|
2010-07-12 01:48:08 +00:00
|
|
|
|
2010-09-30 20:55:41 +00:00
|
|
|
config MFD_VX855
|
2013-04-09 12:40:09 +00:00
|
|
|
tristate "VIA VX855/VX875 integrated south bridge"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on PCI
|
2010-09-30 20:55:41 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enable support for various functions of the
|
|
|
|
|
VIA VX855/VX875 south bridge. You will need to enable the vx855_spi
|
|
|
|
|
and/or vx855_gpio drivers for this to do anything useful.
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_ARIZONA
|
|
|
|
|
select REGMAP
|
|
|
|
|
select REGMAP_IRQ
|
2010-12-10 14:41:33 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
bool
|
2011-04-05 21:40:52 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_ARIZONA_I2C
|
|
|
|
|
tristate "Wolfson Microelectronics Arizona platform with I2C"
|
|
|
|
|
select MFD_ARIZONA
|
2011-04-05 21:40:52 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_I2C
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C
|
2011-04-05 21:40:53 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the Wolfson Microelectronics Arizona platform audio SoC
|
|
|
|
|
core functionality controlled via I2C.
|
2011-06-23 02:15:51 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_ARIZONA_SPI
|
|
|
|
|
tristate "Wolfson Microelectronics Arizona platform with SPI"
|
|
|
|
|
select MFD_ARIZONA
|
2012-03-16 05:40:19 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select REGMAP_SPI
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on SPI_MASTER
|
2012-03-16 05:40:19 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the Wolfson Microelectronics Arizona platform audio SoC
|
|
|
|
|
core functionality controlled via I2C.
|
2012-03-16 05:40:19 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WM5102
|
|
|
|
|
bool "Wolfson Microelectronics WM5102"
|
|
|
|
|
depends on MFD_ARIZONA
|
2011-07-04 17:48:12 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for Wolfson Microelectronics WM5102 low power audio SoC
|
2011-07-04 17:48:12 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WM5110
|
|
|
|
|
bool "Wolfson Microelectronics WM5110"
|
|
|
|
|
depends on MFD_ARIZONA
|
2011-09-21 11:03:07 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for Wolfson Microelectronics WM5110 low power audio SoC
|
2011-09-21 11:03:07 +00:00
|
|
|
|
2013-06-13 08:43:29 +00:00
|
|
|
config MFD_WM8997
|
2013-07-17 11:21:09 +00:00
|
|
|
bool "Wolfson Microelectronics WM8997"
|
2013-06-13 08:43:29 +00:00
|
|
|
depends on MFD_ARIZONA
|
|
|
|
|
help
|
|
|
|
|
Support for Wolfson Microelectronics WM8997 low power audio SoC
|
|
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WM8400
|
|
|
|
|
bool "Wolfson Microelectronics WM8400"
|
2012-02-28 13:05:17 +00:00
|
|
|
select MFD_CORE
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-02-28 13:05:17 +00:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the Wolfson Microelecronics WM8400 PMIC and audio
|
|
|
|
|
CODEC. This driver provides common support for accessing
|
|
|
|
|
the device, additional drivers must be enabled in order to use
|
|
|
|
|
the functionality of the device.
|
2012-04-12 08:48:44 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WM831X
|
|
|
|
|
bool
|
2012-03-16 20:12:32 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WM831X_I2C
|
|
|
|
|
bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
|
2012-05-15 06:48:57 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_WM831X
|
2012-05-15 06:48:57 +00:00
|
|
|
select REGMAP_I2C
|
2013-04-09 12:40:09 +00:00
|
|
|
select IRQ_DOMAIN
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-05-15 06:48:57 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the Wolfson Microelecronics WM831x and WM832x PMICs
|
|
|
|
|
when controlled using I2C. This driver provides common support
|
|
|
|
|
for accessing the device, additional drivers must be enabled in
|
|
|
|
|
order to use the functionality of the device.
|
2012-05-15 06:48:57 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WM831X_SPI
|
|
|
|
|
bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
|
2012-11-05 14:48:23 +00:00
|
|
|
select MFD_CORE
|
2013-04-09 12:40:09 +00:00
|
|
|
select MFD_WM831X
|
|
|
|
|
select REGMAP_SPI
|
|
|
|
|
select IRQ_DOMAIN
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on SPI_MASTER
|
2012-11-05 14:48:23 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
Support for the Wolfson Microelecronics WM831x and WM832x PMICs
|
|
|
|
|
when controlled using SPI. This driver provides common support
|
|
|
|
|
for accessing the device, additional drivers must be enabled in
|
|
|
|
|
order to use the functionality of the device.
|
2012-11-05 14:48:23 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WM8350
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config MFD_WM8350_I2C
|
|
|
|
|
bool "Wolfson Microelectronics WM8350 with I2C"
|
|
|
|
|
select MFD_WM8350
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-11-18 16:36:20 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
The WM8350 is an integrated audio and power management
|
|
|
|
|
subsystem with watchdog and RTC functionality for embedded
|
|
|
|
|
systems. This option enables core support for the WM8350 with
|
|
|
|
|
I2C as the control interface. Additional options must be
|
|
|
|
|
selected to enable support for the functionality of the chip.
|
2012-11-18 16:36:20 +00:00
|
|
|
|
2013-04-09 12:40:09 +00:00
|
|
|
config MFD_WM8994
|
|
|
|
|
bool "Wolfson Microelectronics WM8994"
|
2012-11-22 10:12:04 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select REGMAP_IRQ
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on I2C=y
|
2012-11-22 10:12:04 +00:00
|
|
|
help
|
2013-04-09 12:40:09 +00:00
|
|
|
The WM8994 is a highly integrated hi-fi CODEC designed for
|
|
|
|
|
smartphone applicatiosn. As well as audio functionality it
|
|
|
|
|
has on board GPIO and regulator functionality which is
|
|
|
|
|
supported via the relevant subsystems. This driver provides
|
|
|
|
|
core support for the WM8994, in order to use the actual
|
|
|
|
|
functionaltiy of the device other drivers must be enabled.
|
2012-11-22 10:12:04 +00:00
|
|
|
|
2013-09-22 19:49:18 +00:00
|
|
|
config MFD_STW481X
|
2014-06-05 21:24:14 +00:00
|
|
|
tristate "Support for ST Microelectronics STw481x"
|
2013-09-22 19:49:18 +00:00
|
|
|
depends on I2C && ARCH_NOMADIK
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable the STw481x chip driver used
|
|
|
|
|
in various ST Microelectronics and ST-Ericsson embedded
|
|
|
|
|
Nomadik series.
|
|
|
|
|
|
2005-08-18 09:06:59 +00:00
|
|
|
menu "Multimedia Capabilities Port drivers"
|
2006-03-24 11:18:21 +00:00
|
|
|
depends on ARCH_SA1100
|
2005-08-18 09:06:59 +00:00
|
|
|
|
|
|
|
|
config MCP
|
|
|
|
|
tristate
|
|
|
|
|
|
2005-08-18 09:08:15 +00:00
|
|
|
# Interface drivers
|
|
|
|
|
config MCP_SA11X0
|
|
|
|
|
tristate "Support SA11x0 MCP interface"
|
|
|
|
|
depends on ARCH_SA1100
|
|
|
|
|
select MCP
|
|
|
|
|
|
2005-09-11 09:26:31 +00:00
|
|
|
# Chip drivers
|
|
|
|
|
config MCP_UCB1200
|
2014-06-05 21:24:12 +00:00
|
|
|
tristate "Support for UCB1200 / UCB1300"
|
2012-01-21 14:58:28 +00:00
|
|
|
depends on MCP_SA11X0
|
|
|
|
|
select MCP
|
2005-09-11 09:26:31 +00:00
|
|
|
|
2005-09-11 09:26:57 +00:00
|
|
|
config MCP_UCB1200_TS
|
|
|
|
|
tristate "Touchscreen interface support"
|
|
|
|
|
depends on MCP_UCB1200 && INPUT
|
|
|
|
|
|
2005-08-18 09:06:59 +00:00
|
|
|
endmenu
|
mfd: Versatile Express config infrastructure
Versatile Express platform has an elaborated configuration system,
consisting of microcontrollers residing on the mother- and
daughterboards known as Motherboard/Daughterboard Configuration
Controller (MCC and DCC). The controllers are responsible for
the platform initialization (reset generation, flash programming,
FPGA bitfiles loading etc.) but also control clock generators,
voltage regulators, gather environmental data like temperature,
power consumption etc. Even the video output switch (FPGA) is
controlled that way.
Those devices are _not_ visible in the main address space and
the usual communication channel uses some kind of a bridge in
the peripheral block sending commands (requests) to the
controllers and receiving responses. It can take up to
500 microseconds for a transaction to be completed, therefore
it is important to provide a non-blocking interface to it.
This patch adds an abstraction of this infrastructure. Bridge
drivers can register themselves with the framework. Then,
a driver of a device can request an abstract "function" - the
request will be redirected to a bridge referred by thedd
"arm,vexpress,config-bridge" property of the device tree node.
Signed-off-by: Pawel Moll <pawel.moll@arm.com>
2012-09-24 13:55:40 +00:00
|
|
|
|
2014-04-23 09:49:31 +00:00
|
|
|
config MFD_VEXPRESS_SYSREG
|
|
|
|
|
bool "Versatile Express System Registers"
|
2014-05-26 15:25:22 +00:00
|
|
|
depends on VEXPRESS_CONFIG && GPIOLIB
|
2014-04-23 09:49:31 +00:00
|
|
|
default y
|
|
|
|
|
select CLKSRC_MMIO
|
|
|
|
|
select GPIO_GENERIC_PLATFORM
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select MFD_SYSCON
|
mfd: Versatile Express config infrastructure
Versatile Express platform has an elaborated configuration system,
consisting of microcontrollers residing on the mother- and
daughterboards known as Motherboard/Daughterboard Configuration
Controller (MCC and DCC). The controllers are responsible for
the platform initialization (reset generation, flash programming,
FPGA bitfiles loading etc.) but also control clock generators,
voltage regulators, gather environmental data like temperature,
power consumption etc. Even the video output switch (FPGA) is
controlled that way.
Those devices are _not_ visible in the main address space and
the usual communication channel uses some kind of a bridge in
the peripheral block sending commands (requests) to the
controllers and receiving responses. It can take up to
500 microseconds for a transaction to be completed, therefore
it is important to provide a non-blocking interface to it.
This patch adds an abstraction of this infrastructure. Bridge
drivers can register themselves with the framework. Then,
a driver of a device can request an abstract "function" - the
request will be redirected to a bridge referred by thedd
"arm,vexpress,config-bridge" property of the device tree node.
Signed-off-by: Pawel Moll <pawel.moll@arm.com>
2012-09-24 13:55:40 +00:00
|
|
|
help
|
2014-04-23 09:49:31 +00:00
|
|
|
System Registers are the platform configuration block
|
|
|
|
|
on the ARM Ltd. Versatile Express board.
|
2014-01-29 10:09:53 +00:00
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
endif
|
