[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181120002654.1891-7-dianders@chromium.org>
Date: Mon, 19 Nov 2018 16:26:54 -0800
From: Douglas Anderson <dianders@...omium.org>
To: Mark Brown <broonie@...nel.org>
Cc: Bjorn Andersson <bjorn.andersson@...aro.org>, evgreen@...omium.org,
swboyd@...omium.org, Dmitry Osipenko <digetx@...il.com>,
ryandcase@...omium.org, David Collins <collinsd@...eaurora.org>,
linux-arm-msm@...r.kernel.org,
Douglas Anderson <dianders@...omium.org>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH 7/7] regulator: core: Remove loop disabling supplies in regulator_force_disable()
In regulator_force_disable() there was a strange loop that looked like:
while (rdev->open_count--)
regulator_disable(rdev->supply);
I'm not totally sure what the goal was for this loop, but it seems
wrong to me. If anything I think maybe we should have been looping
over our use_count, but even that might be a little strange. For now
let's just remove the code and we can add something back in if someone
can explain what's expected.
Fixes: f8702f9e4aa7 ("regulator: core: Use ww_mutex for regulators locking")
Signed-off-by: Douglas Anderson <dianders@...omium.org>
---
drivers/regulator/core.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 2eda87520832..963081aba17a 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -2738,10 +2738,6 @@ int regulator_force_disable(struct regulator *regulator)
regulator_unlock_dependent(rdev, &ww_ctx);
- if (rdev->supply)
- while (rdev->open_count--)
- regulator_disable(rdev->supply);
-
return ret;
}
EXPORT_SYMBOL_GPL(regulator_force_disable);
--
2.19.1.1215.g8438c0b245-goog
Powered by blists - more mailing lists