2008-04-30 12:13:42 -04:00
|
|
|
#
|
|
|
|
|
# Makefile for regulator drivers.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_REGULATOR) += core.o
|
|
|
|
|
obj-$(CONFIG_REGULATOR_FIXED_VOLTAGE) += fixed.o
|
|
|
|
|
obj-$(CONFIG_REGULATOR_VIRTUAL_CONSUMER) += virtual.o
|
|
|
|
|
|
2008-07-11 11:28:06 -04:00
|
|
|
obj-$(CONFIG_REGULATOR_BQ24022) += bq24022.o
|
regulator: twl4030 regulators
Support most of the LDO regulators in the twl4030 family chips.
In the case of LDOs supporting MMC/SD, the voltage controls are
used; but in most other cases, the regulator framework is only
used to enable/disable a supplies, conserving power when a given
voltage rail is not needed.
The drivers/mfd/twl4030-core.c code already sets up the various
regulators according to board-specific configuration, and knows
that some chips don't provide the full set of voltage rails.
The omitted regulators are intended to be under hardware control,
such as during the hardware-mediated system powerup, powerdown,
and suspend states. Unless/until software hooks are known to
be safe, they won't be exported here.
These regulators implement the new get_status() operation, but
can't realistically implement get_mode(); the status output is
effectively the result of a vote, with the relevant hardware
inputs not exposed.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
2009-02-08 13:37:06 -05:00
|
|
|
obj-$(CONFIG_REGULATOR_TWL4030) += twl4030-regulator.o
|
2008-10-10 10:58:15 -04:00
|
|
|
obj-$(CONFIG_REGULATOR_WM8350) += wm8350-regulator.o
|
2008-09-11 06:12:01 -04:00
|
|
|
obj-$(CONFIG_REGULATOR_WM8400) += wm8400-regulator.o
|
2008-08-26 16:16:08 -04:00
|
|
|
obj-$(CONFIG_REGULATOR_DA903X) += da903x.o
|
2009-01-08 19:51:01 -05:00
|
|
|
obj-$(CONFIG_REGULATOR_PCF50633) += pcf50633-regulator.o
|
2008-07-11 11:28:06 -04:00
|
|
|
|
2008-04-30 12:13:42 -04:00
|
|
|
ccflags-$(CONFIG_REGULATOR_DEBUG) += -DDEBUG
|
