kernel.git/drivers/regulator/core.c, branch linux-2.6.33.y

regulator: Fix display of null constraints for regulators

2010-02-12T11:19:57Z

If the regulator constraints are empty and there is no voltage reported then nothing will be added to the text displayed for the constraints, leading to random stack data being printed. This is unlikely to happen for practical regulators since most will at least report a voltage but should still be fixed. Signed-off-by: Mark Brown Cc: stable@kernel.org Signed-off-by: Liam Girdwood

regulator: Fix unbalanced disables/enables in regulator_bulk_{enable,disable} error path

2009-12-17T10:27:28Z

Currently it is possible for regulator_bulk_{enable,disable} operations to generate unbalanced regulator_{disable,enable} calls in its error path. In case of an error only those regulators of the bulk operation which actually had been enabled/disabled should get their original state restored. Signed-off-by: Lars-Peter Clausen Acked-by: Mark Brown Signed-off-by: Liam Girdwood

regulator: core.c: Small coding style cleanup (indentation fixup)

2009-12-17T10:27:27Z

Signed-off-by: Stefan Roese Cc: Liam Girdwood Cc: Mark Brown Acked-by: Mark Brown Signed-off-by: Liam Girdwood

regulator: Handle regulators without suspend mode configuration

2009-12-17T10:27:25Z

Since some regulators in the system may not support suspend mode configuration we need to allow some regulators to have a missing suspend mode configuration. Do this by requiring that disabled regulators are explicitly flagged and then skip over regulators that have no state specified. Try to avoid surprises by warning the if we could set the state but no configuration is provided. This also ensures that an all zeros configuration generates a warning rather than silently disabling the regulator. Reported-by: Joonyoung Shim Signed-off-by: Mark Brown Signed-off-by: Liam Girdwood

regulator: Factor out regulator name pretty printing

2009-12-17T10:27:24Z

Some of the regulator API functions have code to allow the machine constraints to override the device supplied name for the regulator in the constraints in order to help tie logging to supplies on the board and disambiguate when there is more than one regulator chip in the system. Factor this code out into a new rdev_get_name() function and use it throughout the regulator API so that we always use the same name. Signed-off-by: Mark Brown Signed-off-by: Liam Girdwood

regulator: Display actual settings with constraints

2009-12-17T10:27:24Z

When voltage or current constraints are either missing or specify a range display the actual setting along with the constraints if we can. This can aid debugging of configuration problems. Signed-off-by: Mark Brown Signed-off-by: Liam Girdwood

regulator: Also lift apply_uV into machine_constraints_voltage()

2009-12-17T10:27:24Z

It makes sense to do all the voltage configuration in the one split out function. Signed-off-by: Mark Brown Signed-off-by: Liam Girdwood

regulator: Factor out voltage constraint setup

2009-12-17T10:27:23Z

This allows constraints to take effect on regulators that support voltage setting but for which the board does not specify a voltage range (for example, because it is fixed correctly at system startup). Signed-off-by: Mark Brown Signed-off-by: Liam Girdwood

regulator: Report error codes for bulk operations

2009-12-17T10:27:23Z

If we're going to log an error we may as well log what the error code that we're failing on is. Signed-off-by: Mark Brown Signed-off-by: Liam Girdwood

regulator: Handle missing constraints in _regulator_disable()

2009-11-16T09:57:16Z

Signed-off-by: Mark Brown Signed-off-by: Liam Girdwood