From: Stephen Boyd <sboyd@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
agross@kernel.org, andersson@kernel.org
Cc: konrad.dybcio@linaro.org, mturquette@baylibre.com,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
stable@vger.kernel.org, Amit Pundir <amit.pundir@linaro.org>
Subject: Re: [PATCH] clk: qcom: gfm-mux: use runtime pm while accessing registers
Date: Tue, 21 Mar 2023 11:46:10 -0700 [thread overview]
Message-ID: <c5273d67493cbb008f13d7538837828a.sboyd@kernel.org> (raw)
In-Reply-To: <20230321175758.26738-1-srinivas.kandagatla@linaro.org>
Quoting Srinivas Kandagatla (2023-03-21 10:57:58)
> gfm mux driver does support runtime pm but we never use it while
> accessing registers. Looks like this driver was getting lucky and
> totally depending on other drivers to leave the clk on.
>
> Fix this by doing runtime pm while accessing registers.
>
> Fixes: a2d8f507803e ("clk: qcom: Add support to LPASS AUDIO_CC Glitch Free Mux clocks")
> Cc: stable@vger.kernel.org
> Reported-by: Amit Pundir <amit.pundir@linaro.org>
Is there a link to the report?
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---
> drivers/clk/qcom/lpass-gfm-sm8250.c | 29 ++++++++++++++++++++++++++++-
> 1 file changed, 28 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clk/qcom/lpass-gfm-sm8250.c b/drivers/clk/qcom/lpass-gfm-sm8250.c
> index 96f476f24eb2..bcf0ea534f7f 100644
> --- a/drivers/clk/qcom/lpass-gfm-sm8250.c
> +++ b/drivers/clk/qcom/lpass-gfm-sm8250.c
> @@ -38,14 +38,37 @@ struct clk_gfm {
> static u8 clk_gfm_get_parent(struct clk_hw *hw)
> {
> struct clk_gfm *clk = to_clk_gfm(hw);
> + int ret;
> + u8 parent;
> +
> + ret = pm_runtime_resume_and_get(clk->priv->dev);
> + if (ret < 0 && ret != -EACCES) {
> + dev_err_ratelimited(clk->priv->dev,
> + "pm_runtime_resume_and_get failed in %s, ret %d\n",
> + __func__, ret);
> + return ret;
> + }
> +
> + parent = readl(clk->gfm_mux) & clk->mux_mask;
> +
> + pm_runtime_mark_last_busy(clk->priv->dev);
>
> - return readl(clk->gfm_mux) & clk->mux_mask;
> + return parent;
> }
>
> static int clk_gfm_set_parent(struct clk_hw *hw, u8 index)
> {
> struct clk_gfm *clk = to_clk_gfm(hw);
> unsigned int val;
> + int ret;
> +
> + ret = pm_runtime_resume_and_get(clk->priv->dev);
Doesn't the clk framework already do this? Why do we need to do it
again?
> + if (ret < 0 && ret != -EACCES) {
> + dev_err_ratelimited(clk->priv->dev,
> + "pm_runtime_resume_and_get failed in %s, ret %d\n",
> + __func__, ret);
> + return ret;
> + }
>
> val = readl(clk->gfm_mux);
>
next prev parent reply other threads:[~2023-03-21 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 17:57 [PATCH] clk: qcom: gfm-mux: use runtime pm while accessing registers Srinivas Kandagatla
2023-03-21 18:46 ` Stephen Boyd [this message]
2023-03-21 20:33 ` Srinivas Kandagatla
2023-03-21 22:48 ` Stephen Boyd
2023-03-22 10:06 ` Amit Pundir
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=c5273d67493cbb008f13d7538837828a.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.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