2005-08-18 13:06:59 +04:00
#
# Multifunction miscellaneous devices
#
2011-09-02 18:43:36 +04:00
if HAS_IOMEM
menu "Multifunction device drivers"
2007-02-21 00:58:01 +03:00
2008-06-27 13:37:19 +04:00
config MFD_CORE
tristate
2012-06-29 21:01:03 +04:00
select IRQ_DOMAIN
2008-06-27 13:37:19 +04:00
default n
2013-04-09 16:40:09 +04:00
config MFD_CS5535
tristate "AMD CS5535 and CS5536 southbridge core functions"
2010-01-07 01:07:13 +03:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
depends on PCI && X86
---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-07 01:07:13 +03:00
2013-04-09 16:40:09 +04: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 10:37:32 +04:00
select REGMAP_I2C
select REGMAP_IRQ
2013-04-09 16:40:09 +04:00
depends on I2C=y && GENERIC_HARDIRQS
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 10:37:32 +04:00
help
2013-04-09 16:40:09 +04: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 10:37:32 +04:00
2013-04-09 16:40:09 +04: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 10:37:32 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
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 10:37:32 +04:00
help
2013-04-09 16:40:09 +04: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 10:37:32 +04:00
2013-02-26 02:08:37 +04:00
config MFD_CROS_EC
2013-04-09 16:40:09 +04:00
tristate "ChromeOS Embedded Controller"
2013-03-21 23:08:33 +04:00
select MFD_CORE
2013-02-26 02:08:37 +04:00
help
If you say Y here you get support for the ChromeOS Embedded
Controller (EC) providing keyboard, battery and power services.
You also ned to enable the driver for the bus you are using. The
protocol for talking to the EC is defined by the bus driver.
2007-02-21 00:58:01 +03:00
2013-02-26 02:08:38 +04:00
config MFD_CROS_EC_I2C
tristate "ChromeOS Embedded Controller (I2C)"
depends on MFD_CROS_EC && I2C
2008-07-25 12:45:59 +04:00
2012-11-09 16:53:33 +04:00
help
2013-02-26 02:08:38 +04: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-26 02:08:39 +04:00
config MFD_CROS_EC_SPI
tristate "ChromeOS Embedded Controller (SPI)"
depends on MFD_CROS_EC && SPI
---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 16:53:33 +04:00
2008-02-07 11:14:49 +03:00
config MFD_ASIC3
2013-04-09 16:40:09 +04:00
bool "Compaq ASIC3"
2008-09-25 02:39:05 +04:00
depends on GENERIC_HARDIRQS && GPIOLIB && ARM
2009-06-15 14:10:24 +04:00
select MFD_CORE
2008-02-07 11:14:49 +03:00
---help---
This driver supports the ASIC3 multifunction chip found on many
PDAs (mainly iPAQ and HTC based ones)
2013-04-09 16:40:09 +04: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 10:37:32 +04:00
help
2013-04-09 16:40:09 +04:00
Say yes here to support for Dialog Semiconductor DA9030 (a.k.a
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 10:37:32 +04:00
2013-04-09 16:40:09 +04:00
config PMIC_DA9052
bool
2010-03-11 18:32:21 +03:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
config MFD_DA9052_SPI
bool "Dialog Semiconductor DA9052/53 PMIC variants with SPI"
select REGMAP_SPI
select REGMAP_IRQ
select PMIC_DA9052
depends on SPI_MASTER=y && GENERIC_HARDIRQS
2008-12-22 14:05:27 +03:00
help
2013-04-09 16:40:09 +04: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 14:05:27 +03:00
2013-04-09 16:40:09 +04:00
config MFD_DA9052_I2C
bool "Dialog Semiconductor DA9052/53 PMIC variants with I2C"
select REGMAP_I2C
select REGMAP_IRQ
select PMIC_DA9052
depends on I2C=y && GENERIC_HARDIRQS
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 12:45:59 +04:00
2013-04-09 16:40:09 +04:00
config MFD_DA9055
bool "Dialog Semiconductor DA9055 PMIC Support"
select REGMAP_I2C
select REGMAP_IRQ
2011-01-18 22:21:35 +03:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2012-11-09 16:53:33 +04:00
help
2013-04-09 16:40:09 +04: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 22:21:35 +03:00
2013-04-09 16:40:09 +04:00
This driver can be built as a module. If built as a module it will be
called "da9055"
2011-01-18 22:21:35 +03:00
2013-04-09 16:40:09 +04:00
config MFD_MC13783
2010-03-11 18:32:21 +03:00
tristate
2008-12-22 14:05:27 +03:00
2013-04-09 16:40:09 +04:00
config MFD_MC13XXX
tristate
depends on (SPI_MASTER || I2C) && GENERIC_HARDIRQS
2012-10-16 11:25:43 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select MFD_MC13783
2012-10-16 11:25:43 +04:00
help
2013-04-09 16:40:09 +04: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 22:21:35 +03:00
2013-04-09 16:40:09 +04:00
config MFD_MC13XXX_SPI
tristate "Freescale MC13783 and MC13892 SPI interface"
depends on SPI_MASTER && GENERIC_HARDIRQS
select REGMAP_SPI
select MFD_MC13XXX
help
Select this if your MC13xxx is connected via an SPI bus.
2011-01-18 22:21:35 +03:00
2013-04-09 16:40:09 +04:00
config MFD_MC13XXX_I2C
tristate "Freescale MC13892 I2C interface"
depends on I2C && GENERIC_HARDIRQS
select REGMAP_I2C
select MFD_MC13XXX
2012-10-16 11:25:43 +04:00
help
2013-04-09 16:40:09 +04:00
Select this if your MC13xxx is connected via an I2C bus.
2012-10-16 11:25:43 +04:00
2008-04-09 22:20:34 +04:00
config HTC_EGPIO
bool "HTC EGPIO support"
2008-07-25 12:46:11 +04:00
depends on GENERIC_HARDIRQS && GPIOLIB && ARM
2008-04-09 22:20:34 +04: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 16:25:41 +04:00
config HTC_PASIC3
tristate "HTC PASIC3 LED/DS1WM chip support"
2009-02-17 12:06:45 +03:00
select MFD_CORE
2013-02-06 20:23:51 +04:00
depends on GENERIC_HARDIRQS
2008-04-12 16:25:41 +04: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 13:22:45 +03:00
config HTC_I2CPLD
bool "HTC I2C PLD chip support"
2010-01-21 06:55:34 +03:00
depends on I2C=y && GPIOLIB
2010-01-19 13:22:45 +03: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 16:40:09 +04:00
config LPC_ICH
tristate "Intel ICH LPC"
depends on PCI && GENERIC_HARDIRQS
select MFD_CORE
2008-08-04 00:34:08 +04:00
help
2013-04-09 16:40:09 +04: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-04 00:34:08 +04:00
2013-04-09 16:40:09 +04:00
config LPC_SCH
tristate "Intel SCH LPC"
depends on PCI && GENERIC_HARDIRQS
2012-05-03 14:26:36 +04:00
select MFD_CORE
help
2013-04-09 16:40:09 +04:00
LPC bridge function of the Intel SCH provides support for
System Management Bus and General Purpose I/O.
2012-05-03 14:26:36 +04:00
2013-04-09 16:40:09 +04:00
config MFD_INTEL_MSIC
bool "Intel MSIC"
depends on INTEL_SCU_IPC
2011-03-24 22:12:47 +03:00
select MFD_CORE
2011-03-09 15:02:38 +03:00
help
2013-04-09 16:40:09 +04: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 15:02:38 +03:00
2013-04-09 16:40:09 +04:00
config MFD_JANZ_CMODIO
tristate "Janz CMOD-IO PCI MODULbus Carrier Board"
select MFD_CORE
depends on PCI && GENERIC_HARDIRQS
2008-12-22 14:16:27 +03:00
help
2013-04-09 16:40:09 +04: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 14:16:27 +03:00
2013-04-09 16:40:09 +04:00
config MFD_JZ4740_ADC
bool "Janz JZ4740 ADC core"
2010-04-08 11:04:55 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select GENERIC_IRQ_CHIP
depends on MACH_JZ4740
2010-04-08 11:04:55 +04:00
help
2013-04-09 16:40:09 +04: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 11:04:55 +04:00
2013-04-09 16:40:09 +04:00
config MFD_88PM800
tristate "Marvell 88PM800"
depends on I2C=y && GENERIC_HARDIRQS
2012-01-11 14:41:41 +04:00
select REGMAP_I2C
2013-04-09 16:40:09 +04:00
select REGMAP_IRQ
select MFD_CORE
2012-01-11 14:41:41 +04:00
help
2013-04-09 16:40:09 +04: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 14:41:41 +04:00
2013-04-09 16:40:09 +04:00
config MFD_88PM805
tristate "Marvell 88PM805"
2012-07-18 10:20:50 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2012-07-18 10:20:46 +04:00
select REGMAP_I2C
2013-04-09 16:40:09 +04:00
select REGMAP_IRQ
select MFD_CORE
2011-04-15 16:04:45 +04:00
help
2013-04-09 16:40:09 +04: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 16:04:45 +04:00
2013-04-09 16:40:09 +04:00
config MFD_88PM860X
bool "Marvell 88PM8606/88PM8607"
depends on I2C=y && GENERIC_HARDIRQS
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 16:04:45 +04:00
2013-04-09 16:40:09 +04:00
config MFD_MAX77686
bool "Maxim Semiconductor MAX77686 PMIC Support"
depends on I2C=y && GENERIC_HARDIRQS
2011-07-04 19:34:16 +04:00
select MFD_CORE
2012-02-21 16:51:34 +04:00
select REGMAP_I2C
2012-05-18 13:52:19 +04:00
select IRQ_DOMAIN
2011-07-04 19:34:16 +04:00
help
2013-04-09 16:40:09 +04:00
Say yes here to support for Maxim Semiconductor MAX77686.
This is a Power Management IC with RTC 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 23:50:00 +04:00
2013-04-09 16:40:09 +04:00
config MFD_MAX77693
bool "Maxim Semiconductor MAX77693 PMIC Support"
depends on I2C=y && GENERIC_HARDIRQS
2011-06-09 23:50:00 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP_I2C
2011-06-09 23:50:00 +04:00
help
2013-04-09 16:40:09 +04:00
Say yes here to support for Maxim Semiconductor MAX77693.
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 23:50:00 +04:00
2013-04-09 16:40:09 +04:00
config MFD_MAX8907
tristate "Maxim Semiconductor MAX8907 PMIC Support"
2011-06-09 23:50:00 +04:00
select MFD_CORE
2012-11-14 19:39:28 +04:00
depends on I2C=y && GENERIC_HARDIRQS
select REGMAP_I2C
2012-12-05 17:19:48 +04:00
select REGMAP_IRQ
2012-11-14 19:39:28 +04:00
help
2013-04-09 16:40:09 +04:00
Say yes here to support for Maxim Semiconductor MAX8907. 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.
2012-11-14 19:39:28 +04:00
2013-04-09 16:40:09 +04:00
config MFD_MAX8925
bool "Maxim Semiconductor MAX8925 PMIC Support"
depends on I2C=y && GENERIC_HARDIRQS
select MFD_CORE
2008-12-22 14:18:02 +03:00
help
2013-04-09 16:40:09 +04:00
Say yes here to support for Maxim Semiconductor MAX8925. 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.
2008-12-22 14:18:02 +03:00
2013-04-09 16:40:09 +04:00
config MFD_MAX8997
bool "Maxim Semiconductor MAX8997/8966 PMIC Support"
2012-02-07 13:47:21 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2013-04-09 16:40:09 +04:00
select MFD_CORE
2012-02-25 01:58:54 +04:00
select IRQ_DOMAIN
2008-10-15 14:15:39 +04:00
help
2013-04-09 16:40:09 +04:00
Say yes here to support for Maxim Semiconductor MAX8997/8966.
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 14:15:39 +04:00
2013-04-09 16:40:09 +04:00
config MFD_MAX8998
bool "Maxim Semiconductor MAX8998/National LP3974 PMIC Support"
depends on I2C=y && GENERIC_HARDIRQS
select MFD_CORE
2011-03-01 16:42:26 +03:00
help
2013-04-09 16:40:09 +04:00
Say yes here to support for Maxim Semiconductor MAX8998 and
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 16:42:26 +03:00
2013-04-09 16:40:09 +04:00
config EZX_PCAP
bool "Motorola EZXPCAP Support"
depends on GENERIC_HARDIRQS && SPI_MASTER
2009-08-31 20:32:18 +04:00
help
2013-04-09 16:40:09 +04:00
This enables the PCAP ASIC present on EZX Phones. This is
needed for MMC, TouchScreen, Sound, USB, etc..
2009-08-31 20:32:18 +04:00
2013-04-09 16:40:09 +04:00
config MFD_VIPERBOARD
tristate "Nano River Technologies Viperboard"
2009-10-22 14:26:45 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
depends on USB && GENERIC_HARDIRQS
2009-10-22 14:26:45 +04:00
default n
2013-04-09 16:40:09 +04: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 14:26:45 +04:00
2013-04-09 16:40:09 +04:00
config MFD_RETU
2013-04-09 23:51:25 +04:00
tristate "Nokia Retu and Tahvo multi-function device"
2011-04-27 11:14:07 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
depends on I2C && GENERIC_HARDIRQS
2012-10-11 15:55:32 +04:00
select REGMAP_IRQ
2012-04-03 12:56:51 +04:00
help
2013-04-09 23:51:25 +04:00
Retu and Tahvo are a multi-function devices found on Nokia
Internet Tablets (770, N800 and N810).
2011-04-27 11:14:07 +04:00
2013-04-09 16:40:09 +04:00
config MFD_PCF50633
tristate "NXP PCF50633"
depends on I2C
select REGMAP_I2C
2010-07-02 15:22:08 +04:00
help
2013-04-09 16:40:09 +04: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 09:32:20 +04:00
2013-04-09 16:40:09 +04:00
config PCF50633_ADC
tristate "NXP PCF50633 ADC"
depends on MFD_PCF50633
2011-11-17 09:32:20 +04:00
help
2013-04-09 16:40:09 +04:00
Say yes here if you want to include support for ADC in the
NXP PCF50633 chip.
2011-11-17 09:32:21 +04:00
2013-04-09 16:40:09 +04:00
config PCF50633_GPIO
tristate "NXP PCF50633 GPIO"
depends on MFD_PCF50633
2011-11-17 09:32:21 +04:00
help
2013-04-09 16:40:09 +04:00
Say yes here if you want to include support GPIO for pins on
the PCF50633 chip.
2011-11-17 09:32:20 +04:00
2013-04-09 16:40:09 +04:00
config UCB1400_CORE
tristate "Philips UCB1400 Core driver"
depends on AC97_BUS
depends on GPIOLIB
2010-05-11 01:39:47 +04:00
help
2013-04-09 16:40:09 +04:00
This enables support for the Philips UCB1400 core functions.
The UCB1400 is an AC97 audio codec.
2010-05-11 01:39:47 +04:00
2013-04-09 16:40:09 +04:00
To compile this driver as a module, choose M here: the
module will be called ucb1400_core.
2010-05-11 01:39:47 +04:00
2013-04-09 16:40:09 +04:00
config MFD_PM8XXX
tristate
2008-08-05 21:27:58 +04:00
2013-04-09 16:40:09 +04:00
config MFD_PM8921_CORE
tristate "Qualcomm PM8921 PMIC chip"
For 3.10 we have a few new MFD drivers for:
- The ChromeOS embedded controller which provides keyboard, battery and power
management services. This controller is accessible through i2c or SPI.
- Silicon Laboratories 476x controller, providing access to their FM chipset
and their audio codec.
- Realtek's RTS5249, a memory stick, MMC and SD/SDIO PCI based reader.
- Nokia's Tahvo power button and watchdog device. This device is very similar
to Retu and is thus supported by the same code base.
- STMicroelectronics STMPE1801, a keyboard and GPIO controller supported by
the stmpe driver.
- ST-Ericsson AB8540 and AB8505 power management and voltage converter
controllers through the existing ab8500 code.
Some other drivers got cleaned up or improved. In particular:
- The Linaro/STE guys got the ab8500 driver in sync with their internal code
through a series of optimizations, fixes and improvements.
- The AS3711 and OMAP USB drivers now have DT support.
- The arizona clock and interrupt handling code got improved.
- The wm5102 register patch and boot mechanism also got improved.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAABAgAGBQJRhttxAAoJEIqAPN1PVmxKl6QP/ilyz2OnuZSJKAT+N3tt0EpR
6hFk0H6uSiHJ5aNyA22WGJq97R3jW9eGK9uD4AKCQ05l9UF/c5+YeXtmGHtxDLCb
jBrErfB6GmEn1H2TzVK+Rp1WPAB/yoYHJosgGNCwohvuffhMiogSVHlI09EY4mQh
2Eo0RTN1UXKXSOZN+E7hb+GbIFzU8eOlEFdc2jh4qtfsvMDANbEByrZM6s0QFB31
LPn03uBL0+iwE8KW2144LKsfzeOos4JWbumyG9Lh6BugUSy1e/Zvv7aWNVeMvY8C
0+ZUk0bzRm9g7e3X4iYLPSboZt7J6DLaBlWXnUaOsJb+YRkUGh094ySdKojP3EiK
8SWSfH4EDwIANKC4zyXMcyny8OewySyrTTd0BTlbgHFyDmvmHk213crsCcilHzRb
3wrX0ETrk96Dkla4/e7IAyME+AbrglStHVGGf2hexlPm2nZdLsE8lfyo9yqjPqzy
w49y7mpTA5PVE63szB1tI/58W2snZtXAEdQGjZmDQp29vDZaeR1t3W/IhKNG30JN
SZGiX3H/6YS4MDZ48N709H83hM4V93XrHKsN59NjQe8NZ7AnSIfns9IgMciGBv7r
aBE+Uwm9htK270Hvl5q8qDDnKaVGYOFlCq9qaeZ2k8NPyyRlQCRpJYjtSplYAnGr
iLI0JdM32u3qdf5IT+Cw
=Wq20
-----END PGP SIGNATURE-----
Merge tag 'mfd-3.10-1' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-next
Pull MFD update from Samuel Ortiz:
"For 3.10 we have a few new MFD drivers for:
- The ChromeOS embedded controller which provides keyboard, battery
and power management services. This controller is accessible
through i2c or SPI.
- Silicon Laboratories 476x controller, providing access to their FM
chipset and their audio codec.
- Realtek's RTS5249, a memory stick, MMC and SD/SDIO PCI based
reader.
- Nokia's Tahvo power button and watchdog device. This device is
very similar to Retu and is thus supported by the same code base.
- STMicroelectronics STMPE1801, a keyboard and GPIO controller
supported by the stmpe driver.
- ST-Ericsson AB8540 and AB8505 power management and voltage
converter controllers through the existing ab8500 code.
Some other drivers got cleaned up or improved. In particular:
- The Linaro/STE guys got the ab8500 driver in sync with their
internal code through a series of optimizations, fixes and
improvements.
- The AS3711 and OMAP USB drivers now have DT support.
- The arizona clock and interrupt handling code got improved.
- The wm5102 register patch and boot mechanism also got improved."
* tag 'mfd-3.10-1' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-next: (104 commits)
mfd: si476x: Don't use 0bNNN
mfd: vexpress: Handle pending config transactions
mfd: ab8500: Export ab8500_gpadc_sw_hw_convert properly
mfd: si476x: Fix i2c warning
mfd: si476x: Add header files and Kbuild plumbing
mfd: si476x: Add chip properties handling code
mfd: si476x: Add the bulk of the core driver
mfd: si476x: Add commands abstraction layer
mfd: rtsx: Support RTS5249
mfd: retu: Add Tahvo support
mfd: ucb1400: Pass ucb1400-gpio data through ac97 bus
mfd: wm8994: Add some OF properties
mfd: wm8994: Add device ID data to WM8994 OF device IDs
input: Export matrix_keypad_parse_of_params()
mfd: tps65090: Add compatible string for charger subnode
mfd: db8500-prcmu: Support platform dependant device selection
mfd: syscon: Fix warnings when printing resource_size_t
of: Add stub of_get_parent for non-OF builds
mfd: omap-usb-tll: Convert to devm_ioremap_resource()
mfd: omap-usb-host: Convert to devm_ioremap_resource()
...
2013-05-06 04:36:20 +04:00
depends on SSBI && BROKEN
2008-07-15 18:09:43 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select MFD_PM8XXX
2008-07-15 18:09:43 +04:00
help
2013-04-09 16:40:09 +04:00
If you say yes to this option, support will be included for the
built-in PM8921 PMIC chip.
2008-07-15 18:09:43 +04:00
2013-04-09 16:40:09 +04: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_PM8XXX_IRQ
bool "Qualcomm PM8xxx IRQ features"
depends on MFD_PM8XXX
default y if MFD_PM8XXX
help
This is the IRQ driver for Qualcomm PM 8xxx PMIC chips.
This is required to use certain other PM 8xxx features, such as GPIO
and MPP.
config MFD_RDC321X
tristate "RDC R-321x southbridge"
select MFD_CORE
depends on PCI && GENERIC_HARDIRQS
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"
depends on PCI && GENERIC_HARDIRQS
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.
config MFD_RC5T583
bool "Ricoh RC5T583 Power Management system device"
depends on I2C=y && GENERIC_HARDIRQS
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"
depends on I2C=y && GENERIC_HARDIRQS
select MFD_CORE
select REGMAP_I2C
select REGMAP_IRQ
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 20:58:30 +04: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 16:40:09 +04: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 18:09:43 +04:00
2012-10-01 15:01:22 +04:00
config MFD_SMSC
2013-04-09 16:40:09 +04:00
bool "SMSC ECE1099 series chips"
2013-02-06 20:23:51 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2012-10-01 15:01:22 +04: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 16:40:09 +04:00
config ABX500_CORE
bool "ST-Ericsson ABX500 Mixed Signal Circuit register functions"
default y if ARCH_U300 || ARCH_U8500
2008-07-15 18:12:52 +04:00
help
2013-04-09 16:40:09 +04: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 18:12:52 +04:00
2013-04-09 16:40:09 +04:00
config AB3100_CORE
bool "ST-Ericsson AB3100 Mixed Signal Circuit core functions"
depends on I2C=y && ABX500_CORE && GENERIC_HARDIRQS
2008-06-27 13:37:57 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
default y if ARCH_U300
2008-06-22 15:01:58 +04:00
help
2013-04-09 16:40:09 +04: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 15:01:58 +04:00
2013-04-09 16:40:09 +04:00
config AB3100_OTP
tristate "ST-Ericsson AB3100 OTP functions"
depends on AB3100_CORE
default y if AB3100_CORE
2008-10-24 19:10:05 +04:00
help
2013-04-09 16:40:09 +04: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 19:22:38 +04:00
2013-04-09 16:40:09 +04:00
config AB8500_CORE
bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
depends on GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU
select POWER_SUPPLY
2011-12-12 18:36:56 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04: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 18:36:56 +04:00
2013-04-09 16:40:09 +04:00
config AB8500_DEBUG
bool "Enable debug info via debugfs"
depends on AB8500_CORE && DEBUG_FS
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 19:07:41 +04:00
help
2013-04-09 16:40:09 +04:00
AB8500 GPADC driver used to convert Acc and battery/ac/usb voltage
2011-12-12 19:07:41 +04:00
2013-04-09 16:40:09 +04: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 18:36:56 +04:00
help
2013-04-09 16:40:09 +04: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 18:36:56 +04:00
2013-04-09 16:40:09 +04:00
config MFD_STMPE
bool "STMicroelectronics STMPE"
depends on (I2C=y || SPI_MASTER=y) && GENERIC_HARDIRQS
2012-09-14 17:24:50 +04:00
select MFD_CORE
help
2013-04-09 16:40:09 +04:00
Support for the STMPE family of I/O Expanders from
STMicroelectronics.
2012-09-14 17:24:50 +04:00
2013-04-09 16:40:09 +04:00
Currently supported devices are:
2012-09-14 17:24:50 +04:00
2013-04-09 16:40:09 +04: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
bool "STMicroelectronics STMPE I2C Inteface"
2009-10-12 19:22:38 +04:00
depends on I2C=y
2013-04-09 16:40:09 +04:00
default y
2009-10-12 19:22:38 +04:00
help
2013-04-09 16:40:09 +04:00
This is used to enable I2C interface of STMPE
2008-10-24 19:10:05 +04:00
2013-04-09 16:40:09 +04:00
config STMPE_SPI
bool "STMicroelectronics STMPE SPI Inteface"
depends on SPI_MASTER
2012-09-19 20:53:33 +04:00
help
2013-04-09 16:40:09 +04:00
This is used to enable SPI interface of STMPE
endmenu
2012-09-19 20:53:33 +04:00
2013-04-09 16:40:09 +04:00
config MFD_STA2X11
bool "STMicroelectronics STA2X11"
depends on STA2X11 && GENERIC_HARDIRQS
2012-06-25 12:34:36 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP_MMIO
config MFD_SYSCON
bool "System Controller Register R/W Based on Regmap"
select REGMAP_MMIO
2012-06-25 12:34:36 +04:00
help
2013-04-09 16:40:09 +04:00
Select this option to enable accessing system control registers
via regmap.
2012-06-25 12:34:36 +04:00
2013-04-09 16:40:09 +04:00
config MFD_DAVINCI_VOICECODEC
tristate
2012-05-15 00:50:39 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
config MFD_TI_AM335X_TSCADC
tristate "TI ADC / Touch Screen chip support"
2012-08-15 20:28:46 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP
select REGMAP_MMIO
depends on GENERIC_HARDIRQS
2012-08-15 20:28:46 +04:00
help
2013-04-09 16:40:09 +04: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 20:28:46 +04:00
2013-04-09 16:40:09 +04:00
config MFD_DM355EVM_MSP
bool "TI DaVinci DM355 EVM microcontroller"
depends on I2C=y && MACH_DAVINCI_DM355_EVM
2010-01-08 14:29:23 +03:00
help
2013-04-09 16:40:09 +04: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 14:29:23 +03:00
2013-04-09 16:40:09 +04:00
config MFD_LP8788
bool "TI LP8788 Power Management Unit Driver"
2011-03-04 09:50:26 +03:00
depends on I2C=y && GENERIC_HARDIRQS
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP_I2C
2012-07-02 04:02:55 +04:00
select IRQ_DOMAIN
2011-03-04 09:50:26 +03:00
help
2013-04-09 16:40:09 +04:00
TI LP8788 PMU supports regulators, battery charger, RTC,
ADC, backlight driver and current sinks.
2011-03-04 09:50:26 +03:00
2013-04-09 16:40:09 +04: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 11:04:16 +04:00
help
2013-04-09 16:40:09 +04: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 11:04:16 +04:00
2013-04-09 16:40:09 +04:00
config MFD_PALMAS
bool "TI Palmas series chips"
2012-01-09 03:09:09 +04:00
select MFD_CORE
select REGMAP_I2C
2012-07-11 16:08:11 +04:00
select REGMAP_IRQ
2013-04-09 16:40:09 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2012-01-09 03:09:09 +04:00
help
2013-04-09 16:40:09 +04:00
If you say yes here you get support for the Palmas
series of PMIC chips from Texas Instruments.
2012-01-09 03:09:09 +04:00
2013-04-09 16:40:09 +04:00
config MFD_TI_SSP
tristate "TI Sequencer Serial Port support"
depends on ARCH_DAVINCI_TNETV107X && GENERIC_HARDIRQS
2012-07-27 17:24:27 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
---help---
Say Y here if you want support for the Sequencer Serial Port
in a Texas Instruments TNETV107X SoC.
2012-06-19 19:37:06 +04:00
2013-04-09 16:40:09 +04:00
To compile this driver as a module, choose M here: the
module will be called ti-ssp.
config TPS6105X
tristate "TI TPS61050/61052 Boost Converters"
depends on I2C
select REGULATOR
2012-06-19 19:37:06 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGULATOR_FIXED_VOLTAGE
depends on GENERIC_HARDIRQS
2012-06-19 19:37:06 +04:00
help
2013-04-09 16:40:09 +04: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 19:37:06 +04:00
2013-04-09 16:40:09 +04: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 19:37:06 +04:00
help
2013-04-09 16:40:09 +04: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 19:37:06 +04:00
2013-04-09 16:40:09 +04: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 19:37:06 +04:00
select MFD_CORE
2013-02-06 20:23:51 +04:00
depends on I2C && GENERIC_HARDIRQS
2012-06-19 19:37:06 +04:00
help
2013-04-09 16:40:09 +04: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 19:37:06 +04:00
2013-04-09 16:40:09 +04:00
config TPS65911_COMPARATOR
tristate
config MFD_TPS65090
bool "TI TPS65090 Power Management chips"
depends on I2C=y && GENERIC_HARDIRQS
2012-06-19 19:37:06 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP_I2C
select REGMAP_IRQ
2012-07-10 15:37:58 +04:00
help
2013-04-09 16:40:09 +04: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 15:37:58 +04:00
2013-04-09 16:40:09 +04:00
config MFD_TPS65217
tristate "TI TPS65217 Power Management / White LED chips"
depends on I2C && GENERIC_HARDIRQS
2008-12-18 12:54:22 +03:00
select MFD_CORE
2011-08-23 21:56:19 +04:00
select REGMAP_I2C
2008-09-10 21:58:42 +04:00
help
2013-04-09 16:40:09 +04: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 21:58:42 +04:00
2013-04-09 16:40:09 +04:00
This driver can also be built as a module. If so, the module
will be called tps65217.
2010-10-20 01:57:56 +04:00
2013-04-09 16:40:09 +04:00
config MFD_TPS6586X
bool "TI TPS6586x Power Management chips"
2013-02-06 20:23:51 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2009-07-27 17:45:58 +04:00
select MFD_CORE
2011-06-10 22:28:10 +04:00
select REGMAP_I2C
2009-07-27 17:45:58 +04:00
help
2013-04-09 16:40:09 +04: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 17:45:58 +04:00
2013-04-09 16:40:09 +04:00
This driver can also be built as a module. If so, the module
will be called tps6586x.
2010-10-20 01:57:56 +04:00
2013-04-09 16:40:09 +04:00
config MFD_TPS65910
bool "TI TPS65910 Power Management chip"
depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
2010-10-20 02:00:11 +04:00
select MFD_CORE
2011-06-10 22:28:10 +04:00
select REGMAP_I2C
2013-04-09 16:40:09 +04:00
select REGMAP_IRQ
2012-05-15 01:14:24 +04:00
select IRQ_DOMAIN
2010-10-20 02:00:11 +04:00
help
2013-04-09 16:40:09 +04:00
if you say yes here you get support for the TPS65910 series of
Power Management chips.
2008-12-19 01:09:50 +03:00
2013-04-09 16:40:09 +04:00
config MFD_TPS65912
bool "TI TPS65912 Power Management chip"
depends on GPIOLIB
2013-04-18 01:28:47 +04:00
select MFD_CORE
2010-10-20 02:00:11 +04:00
help
2013-04-09 16:40:09 +04:00
If you say yes here you get support for the TPS65912 series of
PM chips.
2008-12-19 01:09:50 +03:00
2013-04-09 16:40:09 +04:00
config MFD_TPS65912_I2C
bool "TI TPS65912 Power Management chip with I2C"
select MFD_CORE
select MFD_TPS65912
depends on I2C=y && GPIOLIB && GENERIC_HARDIRQS
help
If you say yes here you get support for the TPS65912 series of
PM chips with I2C interface.
2008-12-19 01:09:50 +03:00
2013-04-09 16:40:09 +04:00
config MFD_TPS65912_SPI
bool "TI TPS65912 Power Management chip with SPI"
select MFD_CORE
select MFD_TPS65912
depends on SPI_MASTER && GPIOLIB && GENERIC_HARDIRQS
2008-10-10 18:58:11 +04:00
help
2013-04-09 16:40:09 +04:00
If you say yes here you get support for the TPS65912 series of
PM chips with SPI interface.
2008-10-10 18:58:11 +04:00
2013-04-09 16:40:09 +04:00
config MFD_TPS80031
bool "TI TPS80031/TPS80032 Power Management chips"
depends on I2C=y && GENERIC_HARDIRQS
2010-01-29 21:20:29 +03:00
select MFD_CORE
2011-06-17 16:02:27 +04:00
select REGMAP_I2C
2011-10-25 12:19:04 +04:00
select REGMAP_IRQ
2010-01-29 21:20:29 +03:00
help
2013-04-09 16:40:09 +04: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 21:20:29 +03:00
2013-04-09 16:40:09 +04:00
config TWL4030_CORE
bool "TI TWL4030/TWL5030/TWL6030/TPS659x0 Support"
depends on I2C=y && GENERIC_HARDIRQS
select IRQ_DOMAIN
2011-08-08 12:04:40 +04:00
select REGMAP_I2C
2009-01-09 03:49:01 +03:00
help
2013-04-09 16:40:09 +04:00
Say yes here if you have TWL4030 / TWL6030 family chip on your board.
2009-01-09 03:49:01 +03: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 16:40:09 +04: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 18:37:20 +04:00
2013-04-09 16:40:09 +04:00
config TWL4030_MADC
tristate "TI TWL4030 MADC"
depends on TWL4030_CORE
2009-08-19 03:40:28 +04:00
help
2013-04-09 16:40:09 +04:00
This driver provides support for triton TWL4030-MADC. The
driver supports both RT and SW conversion methods.
2009-08-19 03:40:28 +04:00
2013-04-09 16:40:09 +04:00
This driver can be built as a module. If so it will be
named twl4030-madc
2012-04-01 10:41:38 +04:00
2013-04-09 16:40:09 +04:00
config TWL4030_POWER
bool "TI TWL4030 power resources"
depends on TWL4030_CORE && ARM
2012-04-01 10:41:39 +04:00
help
2013-04-09 16:40:09 +04: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 10:41:39 +04:00
2013-04-09 16:40:09 +04: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 20:26:20 +04:00
2013-04-09 16:40:09 +04:00
config MFD_TWL4030_AUDIO
bool "TI TWL4030 Audio"
depends on TWL4030_CORE && GENERIC_HARDIRQS
2010-08-20 12:27:12 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04: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 22:43:37 +04:00
2013-04-09 16:40:09 +04:00
config TWL6040_CORE
bool "TI TWL6040 audio codec"
depends on I2C=y && GENERIC_HARDIRQS
2010-05-19 13:39:02 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP_I2C
select REGMAP_IRQ
default n
2009-10-12 19:11:52 +04:00
help
2013-04-09 16:40:09 +04: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 12:11:13 +03:00
2013-04-09 16:40:09 +04:00
config MENELAUS
bool "TI TWL92330/Menelaus PM chip"
depends on I2C=y && ARCH_OMAP2
2011-02-22 12:11:13 +03:00
help
2013-04-09 16:40:09 +04: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 18:05:04 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WL1273_CORE
tristate "TI WL1273 FM radio"
depends on I2C && GENERIC_HARDIRQS
2011-05-16 00:53:56 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
default n
2011-05-16 00:53:56 +04:00
help
2013-04-09 16:40:09 +04: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-16 00:53:56 +04:00
2013-04-09 16:40:09 +04:00
config MFD_LM3533
tristate "TI/National Semiconductor LM3533 Lighting Power chip"
depends on I2C
2010-11-26 13:52:35 +03:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP_I2C
depends on GENERIC_HARDIRQS
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 13:52:35 +03:00
2010-02-04 14:18:52 +03:00
config MFD_TIMBERDALE
2013-04-09 16:40:09 +04:00
tristate "Timberdale FPGA"
2010-02-04 14:18:52 +03:00
select MFD_CORE
2010-02-12 18:30:55 +03:00
depends on PCI && GPIOLIB
2010-02-04 14:18:52 +03: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 13:26:25 +03:00
2013-04-09 16:40:09 +04:00
config MFD_TC3589X
bool "Toshiba TC35892 and variants"
depends on I2C=y && GENERIC_HARDIRQS
2010-02-19 13:26:25 +03:00
select MFD_CORE
help
2013-04-09 16:40:09 +04:00
Support for the Toshiba TC35892 and variants I/O Expander.
2010-02-19 13:26:25 +03:00
2013-04-09 16:40:09 +04: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 18:43:10 +04:00
2013-04-09 16:40:09 +04:00
config MFD_TMIO
bool
default n
config MFD_T7L66XB
bool "Toshiba T7L66XB"
depends on ARM && HAVE_CLK && GENERIC_HARDIRQS
2010-03-21 03:06:05 +03:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select MFD_TMIO
2010-03-21 03:06:05 +03:00
help
2013-04-09 16:40:09 +04:00
Support for Toshiba Mobile IO Controller T7L66XB
2010-03-21 03:06:05 +03:00
2013-04-09 16:40:09 +04:00
config MFD_TC6387XB
bool "Toshiba TC6387XB"
depends on ARM && HAVE_CLK
2010-04-07 11:43:00 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select MFD_TMIO
2010-04-07 11:43:00 +04:00
help
2013-04-09 16:40:09 +04:00
Support for Toshiba Mobile IO Controller TC6387XB
2010-04-07 11:43:00 +04:00
2013-04-09 16:40:09 +04:00
config MFD_TC6393XB
bool "Toshiba TC6393XB"
depends on ARM && HAVE_CLK
select GPIOLIB
2010-07-12 05:48:08 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select MFD_TMIO
2010-07-12 05:48:08 +04:00
help
2013-04-09 16:40:09 +04:00
Support for Toshiba Mobile IO Controller TC6393XB
2010-07-12 05:48:08 +04:00
2010-10-01 00:55:41 +04:00
config MFD_VX855
2013-04-09 16:40:09 +04:00
tristate "VIA VX855/VX875 integrated south bridge"
2013-02-06 20:23:51 +04:00
depends on PCI && GENERIC_HARDIRQS
2010-10-01 00:55:41 +04: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 16:40:09 +04:00
config MFD_ARIZONA
select REGMAP
select REGMAP_IRQ
2010-12-10 17:41:33 +03:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
bool
2011-04-06 01:40:52 +04:00
2013-04-09 16:40:09 +04:00
config MFD_ARIZONA_I2C
tristate "Wolfson Microelectronics Arizona platform with I2C"
select MFD_ARIZONA
2011-04-06 01:40:52 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP_I2C
depends on I2C && GENERIC_HARDIRQS
2011-04-06 01:40:53 +04:00
help
2013-04-09 16:40:09 +04:00
Support for the Wolfson Microelectronics Arizona platform audio SoC
core functionality controlled via I2C.
2011-06-23 06:15:51 +04:00
2013-04-09 16:40:09 +04:00
config MFD_ARIZONA_SPI
tristate "Wolfson Microelectronics Arizona platform with SPI"
select MFD_ARIZONA
2012-03-16 09:40:19 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select REGMAP_SPI
depends on SPI_MASTER && GENERIC_HARDIRQS
2012-03-16 09:40:19 +04:00
help
2013-04-09 16:40:09 +04:00
Support for the Wolfson Microelectronics Arizona platform audio SoC
core functionality controlled via I2C.
2012-03-16 09:40:19 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WM5102
bool "Wolfson Microelectronics WM5102"
depends on MFD_ARIZONA
2011-07-04 21:48:12 +04:00
help
2013-04-09 16:40:09 +04:00
Support for Wolfson Microelectronics WM5102 low power audio SoC
2011-07-04 21:48:12 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WM5110
bool "Wolfson Microelectronics WM5110"
depends on MFD_ARIZONA
2011-09-21 15:03:07 +04:00
help
2013-04-09 16:40:09 +04:00
Support for Wolfson Microelectronics WM5110 low power audio SoC
2011-09-21 15:03:07 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WM8400
bool "Wolfson Microelectronics WM8400"
2012-02-28 17:05:17 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2012-02-28 17:05:17 +04:00
select REGMAP_I2C
help
2013-04-09 16:40:09 +04: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 12:48:44 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WM831X
bool
depends on GENERIC_HARDIRQS
2012-03-17 00:12:32 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WM831X_I2C
bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
2012-05-15 10:48:57 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select MFD_WM831X
2012-05-15 10:48:57 +04:00
select REGMAP_I2C
2013-04-09 16:40:09 +04:00
select IRQ_DOMAIN
2013-02-06 20:23:51 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2012-05-15 10:48:57 +04:00
help
2013-04-09 16:40:09 +04: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 10:48:57 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WM831X_SPI
bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
2012-11-05 18:48:23 +04:00
select MFD_CORE
2013-04-09 16:40:09 +04:00
select MFD_WM831X
select REGMAP_SPI
select IRQ_DOMAIN
depends on SPI_MASTER && GENERIC_HARDIRQS
2012-11-05 18:48:23 +04:00
help
2013-04-09 16:40:09 +04: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 18:48:23 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WM8350
bool
depends on GENERIC_HARDIRQS
config MFD_WM8350_I2C
bool "Wolfson Microelectronics WM8350 with I2C"
select MFD_WM8350
depends on I2C=y && GENERIC_HARDIRQS
2012-11-18 20:36:20 +04:00
help
2013-04-09 16:40:09 +04: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 20:36:20 +04:00
2013-04-09 16:40:09 +04:00
config MFD_WM8994
bool "Wolfson Microelectronics WM8994"
2012-11-22 14:12:04 +04:00
select MFD_CORE
select REGMAP_I2C
select REGMAP_IRQ
2013-02-06 20:23:51 +04:00
depends on I2C=y && GENERIC_HARDIRQS
2012-11-22 14:12:04 +04:00
help
2013-04-09 16:40:09 +04: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 14:12:04 +04:00
2011-09-02 18:43:36 +04:00
endmenu
endif
2007-02-21 00:58:01 +03:00
2005-08-18 13:06:59 +04:00
menu "Multimedia Capabilities Port drivers"
2006-03-24 14:18:21 +03:00
depends on ARCH_SA1100
2005-08-18 13:06:59 +04:00
config MCP
tristate
2005-08-18 13:08:15 +04:00
# Interface drivers
config MCP_SA11X0
tristate "Support SA11x0 MCP interface"
depends on ARCH_SA1100
select MCP
2005-09-11 13:26:31 +04:00
# Chip drivers
config MCP_UCB1200
2012-01-21 18:58:28 +04:00
bool "Support for UCB1200 / UCB1300"
depends on MCP_SA11X0
select MCP
2005-09-11 13:26:31 +04:00
2005-09-11 13:26:57 +04:00
config MCP_UCB1200_TS
tristate "Touchscreen interface support"
depends on MCP_UCB1200 && INPUT
2005-08-18 13:06:59 +04: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 17:55:40 +04:00
config VEXPRESS_CONFIG
bool
help
Platform configuration infrastructure for the ARM Ltd.
Versatile Express.
