From: Douglas Anderson <dianders@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Marc Gonzalez <marc.w.gonzalez@free.fr>,
evgreen@chromium.org, swboyd@chromium.org,
Dmitry Osipenko <digetx@gmail.com>,
ryandcase@chromium.org, David Collins <collinsd@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/2] regulator: core: Avoid propagating to supplies when possible
Date: Tue, 20 Nov 2018 09:52:54 -0800 [thread overview]
Message-ID: <20181120175255.227783-2-dianders@chromium.org> (raw)
In-Reply-To: <20181120175255.227783-1-dianders@chromium.org>
When we called regulator_enable() on a regulator we'd end up
propagating that call all the way up the chain every time. This is a
bit of a waste of time. A child regulator already refcounts its own
enables so it should avoid passing on to its parent unless the
refcount transitioned between 0 and 1.
Historically this hasn't been a huge problem since we skipped dealing
with enable for always-on regulators. In a previous patch, however,
we removed the always-on optimization. On one system, the debugfs
regulator_summary was now showing a "use_count" of 33 for a top-level
regulator.
Let's implement this optimization. This turns out to be fairly
trivial with the recent reorganization of the regulator core.
NOTE: as part of this patch I'll make "always-on" regulators start
with a use count of 1. This keeps the counts clean when recursively
resolving regulators.
ALSO NOTE: this commit also contains somewhat of a bug fix to
regulator_force_disable(). It was incorrectly looping over
"rdev->open_count" when it should have been looping over use_count.
We have to touch that code anyway (since we should no longer loop at
all), so we'll fix it together in one patch. Also: since this comes
after commit f8702f9e4aa7 ("regulator: core: Use ww_mutex for
regulators locking") we can now move to use _regulator_disable() for
our supply and keep it in the lock.
Signed-off-by: Douglas Anderson <dianders@chromium.org>
---
NOTE: this patch is based atop the patch ("regulator: core: Only count
load for enabled consumers") because that patch changed the signature
of _regulator_disable() and this patch touches calls to
_regulator_disable(). If desired the order of the two patches could
be swapped.
Changes in v2:
- Squashed in ("Remove loop disabling supplies in regulator_force_disable()")
drivers/regulator/core.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 1271b5406ad7..dbe2f2e6e625 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -1824,6 +1824,7 @@ static int regulator_resolve_supply(struct regulator_dev *rdev)
rdev->supply = NULL;
return ret;
}
+ rdev->use_count = 1;
}
return 0;
@@ -2493,7 +2494,7 @@ static int _regulator_enable(struct regulator *regulator)
lockdep_assert_held_once(&rdev->mutex.base);
- if (rdev->supply) {
+ if (rdev->use_count == 0 && rdev->supply) {
ret = _regulator_enable(rdev->supply);
if (ret < 0)
return ret;
@@ -2541,7 +2542,7 @@ static int _regulator_enable(struct regulator *regulator)
_regulator_handle_consumer_disable(regulator);
err_disable_supply:
- if (rdev->supply)
+ if (rdev->use_count == 0 && rdev->supply)
_regulator_disable(rdev->supply);
return ret;
@@ -2650,7 +2651,7 @@ static int _regulator_disable(struct regulator *regulator)
if (ret == 0 && rdev->coupling_desc.n_coupled > 1)
ret = regulator_balance_voltage(rdev, PM_SUSPEND_ON);
- if (ret == 0 && rdev->supply)
+ if (ret == 0 && rdev->use_count == 0 && rdev->supply)
ret = _regulator_disable(rdev->supply);
return ret;
@@ -2735,11 +2736,10 @@ int regulator_force_disable(struct regulator *regulator)
ret = drms_uA_update(rdev);
}
- regulator_unlock_dependent(rdev, &ww_ctx);
+ if (rdev->use_count != 0 && rdev->supply)
+ _regulator_disable(rdev->supply);
- if (rdev->supply)
- while (rdev->open_count--)
- regulator_disable(rdev->supply);
+ regulator_unlock_dependent(rdev, &ww_ctx);
return ret;
}
--
2.19.1.1215.g8438c0b245-goog
prev parent reply other threads:[~2018-11-20 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 17:52 [PATCH v2 1/2] regulator: core: Only count load for enabled consumers Douglas Anderson
2018-11-20 17:52 ` Douglas Anderson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181120175255.227783-2-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=collinsd@codeaurora.org \
--cc=digetx@gmail.com \
--cc=evgreen@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=ryandcase@chromium.org \
--cc=swboyd@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).