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

regulator: core: update kernel documentation for regulator_desc

2013-03-01T06:07:22+00:00

commit df367931 (regulator: core: Provide regmap get/set bypass
operations) introduced regulator_[gs]et_bypass_regmap

However structure documentation for regulator_desc needs an update.
./scripts/kernel-doc include/linux/regulator/driver.h >/dev/null
generates:
Warning(include/linux/regulator/driver.h:233): No description found for parameter 'bypass_reg'
Warning(include/linux/regulator/driver.h:233): No description found for parameter 'bypass_mask'

Cc: Liam Girdwood 
Cc: Mark Brown 
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Nishanth Menon 
Signed-off-by: Mark Brown

regulator: core: Allow specify apply_[reg|bit] for regmap based voltage_sel operations

2012-12-24T16:34:11+00:00

Some DVM regulators needs to update apply_bit after setting vsel_reg to
initiate voltage change on the output.  This patch adds apply_reg and
apply_bit to struct regulator_desc and update
regulator_set_voltage_sel_regmap() to set apply_bit of apply_reg when
apply_bit is set.

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

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

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

regulator: core: Allow specific minimal selector for starting linear mapping

2012-11-27T20:07:40+00:00

Some drivers (at least 3 drivers) have such variant of linear mapping that
the first few selectors are invalid and the reset are linear mapping.
Let's support this case in core.

This patch adds linear_min_sel in struct regulator_desc,
so we can allow specific minimal selector for starting linear mapping.
Then extends regulator_[map|list]_voltage_linear() to support this feature.

Note that for selectors less than min_linear_index, we need count them to
n_voltages so regulator_list_voltage() won't fail while checking the boundary
for selector before calling list_voltage callback.

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

regulator: core: Support for continuous voltage range

2012-10-15T02:56:08+00:00

Some regulators can set any voltage within the constraints range,
not being limited to specified operating points.

This patch makes it possible to describe such regulator and makes
the regulator_is_supported_voltage() function behave correctly.

Signed-off-by: Pawel Moll 
Signed-off-by: Mark Brown

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