From: Mark Brown broonie@linaro.org
In the spirit of conservatism that governs our general approach to permissions it is better if we don't touch regulators we weren't explicitly given permissions to control. This avoids the need to explicitly specify unknown regulators in DT as always on, if a regulator is not otherwise involved in software control it can be omitted from the DT.
Regulators explicitly given constraints in DT still need to have an always on constraint specified as before.
Signed-off-by: Mark Brown broonie@linaro.org --- drivers/regulator/core.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index af7a17677f3d..d7f111781867 100644 --- a/drivers/regulator/core.c +++ b/drivers/regulator/core.c @@ -3822,8 +3822,9 @@ static int __init regulator_init_complete(void) mutex_lock(®ulator_list_mutex);
/* If we have a full configuration then disable any regulators - * which are not in use or always_on. This will become the - * default behaviour in the future. + * we have permission to change the status for and which are + * not in use or always_on. This is effectively the default + * for DT and ACPI as they have full constraints. */ list_for_each_entry(rdev, ®ulator_list, list) { ops = rdev->desc->ops; @@ -3832,6 +3833,9 @@ static int __init regulator_init_complete(void) if (c && c->always_on) continue;
+ if (c && !(c->valid_ops_mask & REGULATOR_CHANGE_STATUS)) + continue; + mutex_lock(&rdev->mutex);
if (rdev->use_count)