linux-toradex.git/include/linux/regulator/driver.h, branch v3.7.4

Merge remote-tracking branches 'regulator/topic/core', 'regulator/topic/bypass', 'regulator/topic/tol', 'regulator/topic/drivers' and 'regulator/topic/tps6586x' into regulator-next

2012-09-28T13:45:07+00:00

regulator: core: Provide regmap get/set bypass operations

2012-09-10T03:25:10+00:00

Signed-off-by: Mark Brown

regulator: core: Support bypass mode

2012-09-10T03:25:10+00:00

Many regulators support a bypass mode where they simply switch their
input supply to the output. This is mainly used in low power retention
states where power consumption is extremely low so higher voltage or
less clean supplies can be used.

Support this by providing ops for the drivers and a consumer API which
allows the device to be put into bypass mode if all consumers enable it
and the machine enables permission for this.

This is not supported as a mode since the existing modes are rarely used
due to fuzzy definition and mostly redundant with modern hardware which is
able to respond promptly to load changes.

Signed-off-by: Mark Brown 
Reviewed-by: Graeme Gregory

regulator: Clarify documentation for regmap in the config

2012-08-31T17:42:36+00:00

Signed-off-by: Mark Brown

regulator: Update comment for set_current_limit callback of struct regulator_ops

2012-08-28T18:00:27+00:00

The regulators should be tending to the maximum in the available range and
consumers should specify the widest range possible.

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown

Merge branch 'regulator-drivers' into regulator-next

2012-07-22T18:32:00+00:00

regulator: Add REGULATOR_STATUS_UNDEFINED.

2012-07-12T17:19:24+00:00

REGULATOR_STATUS_UNDEFINED is to be returned by regulator, if any other state
doesn't really apply.

Signed-off-by: Krystian Garbaciak 
Signed-off-by: Mark Brown

regulator: core: Add core support for GPIO controlled enable lines

2012-07-03T19:29:27+00:00

It is very common for regulators to support having their enable signal
controlled by a GPIO. Since there are a bunch of fiddly things to get
right like handling the operations when the enable signal is tied to
a rail and it's just replicated code add support for this to the core.

Drivers should set ena_gpio in their config if they have a GPIO control,
using ena_gpio_flags to specify any flags (including GPIOF_OUT_INIT_ for
the initial state) and ena_gpio_invert if the GPIO is active low. The
core will then override any enable and disable operations the driver has
and instead control the specified GPIO.

This will in the future also allow us to further extend the core by
identifying when several enable signals have been tied together and
handling this properly.

Signed-off-by: Mark Brown

regulator: core: Allow fixed enable_time to be set in the regulator_desc

2012-07-03T19:28:33+00:00

Many regulators have a fixed specification for their enable time. Allow
this to be set in the regulator_desc as a number to save them having to
implement an explicit operation.

Signed-off-by: Mark Brown

regulator: core: Change the unit of ramp_delay from mV/uS to uV/uS

2012-06-18T09:56:58+00:00

This change makes it possible to set ramp_delay with 0.xxx mV/uS without
truncation issue.

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown