kernel/linux.git/include/linux/regulator/consumer.h, branch v3.12.13

Merge remote-tracking branch 'regulator/topic/optional' into regulator-next

2013-09-01T12:50:17+00:00

regulator: Add devm_regulator_get_exclusive()

2013-08-29T18:38:33+00:00

Add a resource managed regulator_get_exclusive() Signed-off-by: Matthias Kaehlcke Signed-off-by: Mark Brown

regulator: core: Provide hints to the core about optional supplies

2013-07-31T08:56:39+00:00

While the majority of supplies on devices are mandatory and can't be physically omitted for electrical reasons some devices do have optional supplies and need to know if they are missing, MMC being the most common of these. Currently the core accurately reports all errors when regulators are requested since it does not know if the supply is one that must be provided even if by a regulator software does not know about or if it is one that may genuinely be disconnected. In order to allow this behaviour to be changed and stub regulators to be provided in the former case add a new regulator request function regulator_get_optional() which provides a hint to the core that the regulator may genuinely not be connected. Currently the implementation is identical to the current behaviour, future patches will add support in the core for returning stub regulators in the case where normal regulator_get() fails and the board has requested it. Signed-off-by: Mark Brown Acked-by: Chris Ball

regulator: core: Add missing stub for regulator_get_exclusive()

2013-07-31T08:56:38+00:00

Signed-off-by: Mark Brown

regulator: core: Make set_voltage_tol() try for mid-range first

2013-07-15T10:20:08+00:00

The expected semantic for something expressed as a tolerance is that it should deliver the specified value with some deviation allowed but this is not what set_voltage_tol() currently does. Instead it just passes the maximum possible range to set_voltage() which will typically result in a voltage aimed at lower than the target voltage. Instead first try to set a voltage between the target voltage and the upper limit, then fall back on the full range. This will be much more robust against physical variation in systems and makes the API behave more like users would expect. Signed-off-by: Mark Brown

regulator: core: add regulator_get_linear_step()

2013-06-07T10:19:29+00:00

Add regulator_get_linear_step(), which returns the voltage step size between VSEL values for linear regulators. This is intended for use by regulator consumers which build their own voltage-to-VSEL tables. Signed-off-by: Paul Walmsley Reviewed-by: Andrew Chew Cc: Matthew Longnecker Signed-off-by: Mark Brown

regulator: core: Mark all get and enable calls as __must_check

2013-03-04T02:35:58+00:00

It's generally important that devices have power when they expect it so drivers really ought to be checking for errors on the power up paths. Signed-off-by: Mark Brown

Merge remote-tracking branch 'regulator/topic/tol' into regulator-next

2012-12-10T03:43:22+00:00

Merge remote-tracking branch 'regulator/topic/stub' into regulator-next

2012-12-10T03:43:20+00:00

regulators: add regulator_can_change_voltage() function

2012-12-06T06:13:34+00:00

Introduce a regulator_can_change_voltage() function for the subsytems or drivers which might check if applying voltage change is possible and use special workaround code when the driver is used with fixed regulators or regulators with disabled ability to change the voltage. Signed-off-by: Marek Szyprowski Signed-off-by: Mark Brown