From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Mike Tipton <mdtipton@codeaurora.org>,
Taniya Das <tdas@codeaurora.org>, Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] clk: qcom: gdsc: Ensure regulator init state matches GDSC state
Date: Sat, 31 Jul 2021 01:02:31 -0700 [thread overview]
Message-ID: <162771855184.714452.5922758777501573850@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210721224056.3035016-1-bjorn.andersson@linaro.org>
Quoting Bjorn Andersson (2021-07-21 15:40:56)
> As GDSCs are registered and found to be already enabled gdsc_init()
> ensures that 1) the kernel state matches the hardware state, and 2)
> votable GDSCs are properly enabled from this master as well.
>
> But as the (optional) supply regulator is enabled deep into
> gdsc_toggle_logic(), which is only executed for votable GDSCs the
> kernel's state of the regulator might not match the hardware. The
> regulator might be automatically turned off if no other users are
> present or the next call to gdsc_disable() would cause an unbalanced
> regulator_disable().
>
> But as the votable case deals with an already enabled GDSC, most of
> gdsc_enable() and gdsc_toggle_logic() can be skipped. Reducing it to
> just clearing the SW_COLLAPSE_MASK and enabling hardware control allow
> us to simply call regulator_enable() in both cases.
>
> The enablement of hardware control seems to be an independent property
> from the GDSC being enabled, so this is moved outside that conditional
> segment.
>
> Lastly, as the propagation of ALWAY_ON to GENPD_FLAG_ALWAYS_ON needs to
> happen regardless of the initial state this is grouped together with the
> other sc->pd updates at the end of the function.
>
> Cc: stable@vger.kernel.org
> Fixes: 37416e554961 ("clk: qcom: gdsc: Handle GDSC regulator supplies")
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---
I was hoping someone from qcom would review it. I'll take a look in the
next couple of days and probably throw it on clk-fixes for the next rc.
-Stephen
>
> Changes since v1:
> - Refactored into if (on) else if (ALWAYS_ON) style
> - Extracted relevant parts of gdsc_enable() to call under VOTABLE
> - Turn on hwctrl if requested for non-votable gdscs
>
> drivers/clk/qcom/gdsc.c | 54 +++++++++++++++++++++++++++--------------
> 1 file changed, 36 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/clk/qcom/gdsc.c b/drivers/clk/qcom/gdsc.c
> index 51ed640e527b..4ece326ea233 100644
> --- a/drivers/clk/qcom/gdsc.c
> +++ b/drivers/clk/qcom/gdsc.c
> @@ -357,27 +357,43 @@ static int gdsc_init(struct gdsc *sc)
> if (on < 0)
> return on;
>
> - /*
> - * Votable GDSCs can be ON due to Vote from other masters.
> - * If a Votable GDSC is ON, make sure we have a Vote.
> - */
> - if ((sc->flags & VOTABLE) && on)
> - gdsc_enable(&sc->pd);
> + if (on) {
> + /* The regulator must be on, sync the kernel state */
> + if (sc->rsupply) {
> + ret = regulator_enable(sc->rsupply);
> + if (ret < 0)
> + return ret;
> + }
>
> - /*
> - * Make sure the retain bit is set if the GDSC is already on, otherwise
> - * we end up turning off the GDSC and destroying all the register
> - * contents that we thought we were saving.
> - */
> - if ((sc->flags & RETAIN_FF_ENABLE) && on)
> - gdsc_retain_ff_on(sc);
> + /*
> + * Votable GDSCs can be ON due to Vote from other masters.
> + * If a Votable GDSC is ON, make sure we have a Vote.
> + */
> + if (sc->flags & VOTABLE) {
> + ret = regmap_update_bits(sc->regmap, sc->gdscr,
> + SW_COLLAPSE_MASK, val);
> + if (ret)
> + return ret;
> + }
> +
> + /* Turn on HW trigger mode if supported */
> + if (sc->flags & HW_CTRL) {
> + ret = gdsc_hwctrl(sc, true);
> + if (ret < 0)
> + return ret;
> + }
>
> - /* If ALWAYS_ON GDSCs are not ON, turn them ON */
> - if (sc->flags & ALWAYS_ON) {
> - if (!on)
> - gdsc_enable(&sc->pd);
> + /*
> + * Make sure the retain bit is set if the GDSC is already on,
> + * otherwise we end up turning off the GDSC and destroying all
> + * the register contents that we thought we were saving.
> + */
> + if (sc->flags & RETAIN_FF_ENABLE)
> + gdsc_retain_ff_on(sc);
> + } else if (sc->flags & ALWAYS_ON) {
> + /* If ALWAYS_ON GDSCs are not ON, turn them ON */
> + gdsc_enable(&sc->pd);
> on = true;
> - sc->pd.flags |= GENPD_FLAG_ALWAYS_ON;
> }
>
> if (on || (sc->pwrsts & PWRSTS_RET))
> @@ -385,6 +401,8 @@ static int gdsc_init(struct gdsc *sc)
> else
> gdsc_clear_mem_on(sc);
>
> + if (sc->flags & ALWAYS_ON)
> + sc->pd.flags |= GENPD_FLAG_ALWAYS_ON;
> if (!sc->pd.power_off)
> sc->pd.power_off = gdsc_disable;
> if (!sc->pd.power_on)
> --
> 2.29.2
>
next prev parent reply other threads:[~2021-07-31 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 22:40 [PATCH v2] clk: qcom: gdsc: Ensure regulator init state matches GDSC state Bjorn Andersson
2021-07-31 8:02 ` Stephen Boyd [this message]
2021-08-06 1:21 ` Stephen Boyd
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=162771855184.714452.5922758777501573850@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdtipton@codeaurora.org \
--cc=mturquette@baylibre.com \
--cc=stable@vger.kernel.org \
--cc=tdas@codeaurora.org \
--cc=vkoul@kernel.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).