From: Johan Hovold <johan@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
patches@lists.linux.dev, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
linux-arm-msm@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Johan Hovold <johan+linaro@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Taniya Das <quic_tdas@quicinc.com>,
Satya Priya <quic_c_skakit@quicinc.com>,
Douglas Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH] clk: qcom: gdsc: Remove direct runtime PM calls
Date: Wed, 2 Nov 2022 11:52:39 +0100 [thread overview]
Message-ID: <Y2JL9/HFrb3E+CYY@hovoldconsulting.com> (raw)
In-Reply-To: <20221101233421.997149-1-swboyd@chromium.org>
On Tue, Nov 01, 2022 at 04:34:21PM -0700, Stephen Boyd wrote:
> We shouldn't be calling runtime PM APIs from within the genpd
> enable/disable path for a couple reasons.
>
> First, this causes an AA lockdep splat because genpd can call into genpd
> code again while holding the genpd lock.
>
> WARNING: possible recursive locking detected
> 5.19.0-rc2-lockdep+ #7 Not tainted
> --------------------------------------------
> kworker/2:1/49 is trying to acquire lock:
> ffffffeea0370788 (&genpd->mlock){+.+.}-{3:3}, at: genpd_lock_mtx+0x24/0x30
>
> but task is already holding lock:
> ffffffeea03710a8 (&genpd->mlock){+.+.}-{3:3}, at: genpd_lock_mtx+0x24/0x30
>
> other info that might help us debug this:
> Possible unsafe locking scenario:
>
> CPU0
> ----
> lock(&genpd->mlock);
> lock(&genpd->mlock);
>
> *** DEADLOCK ***
>
> May be due to missing lock nesting notation
I've seen this splat on sc8280xp as well but haven't had time to look
into it yet.
> Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Cc: Johan Hovold <johan+linaro@kernel.org>
> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> Cc: Taniya Das <quic_tdas@quicinc.com>
> Cc: Satya Priya <quic_c_skakit@quicinc.com>
> Cc: Douglas Anderson <dianders@chromium.org>
> Cc: Matthias Kaehlcke <mka@chromium.org>
> Reported-by: Stephen Boyd <swboyd@chromium.org>
We typically don't add Reported-by tags for bugs we find and fix
ourselves.
> Fixes: 1b771839de05 ("clk: qcom: gdsc: enable optional power domain support")
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> drivers/clk/qcom/gdsc.c | 64 ++++++-----------------------------------
> 1 file changed, 8 insertions(+), 56 deletions(-)
>
> diff --git a/drivers/clk/qcom/gdsc.c b/drivers/clk/qcom/gdsc.c
> index 7cf5e130e92f..a775ce1b7d8a 100644
> --- a/drivers/clk/qcom/gdsc.c
> +++ b/drivers/clk/qcom/gdsc.c
> @@ -495,14 +451,11 @@ static int gdsc_init(struct gdsc *sc)
> sc->pd.power_on = gdsc_enable;
>
> ret = pm_genpd_init(&sc->pd, NULL, !on);
> - if (ret)
> - goto err_put_rpm;
> + if (!ret)
> + goto err_disable_supply;
The logic should not be inverted here (and only happens to work
currently when you have no regulator or the gdsc was off).
> return 0;
>
> -err_put_rpm:
> - if (on)
> - gdsc_pm_runtime_put(sc);
> err_disable_supply:
> if (on && sc->rsupply)
> regulator_disable(sc->rsupply);
Johan
next prev parent reply other threads:[~2022-11-02 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 23:34 [PATCH] clk: qcom: gdsc: Remove direct runtime PM calls Stephen Boyd
2022-11-02 0:45 ` Doug Anderson
2022-11-02 3:16 ` Stephen Boyd
2022-11-14 20:11 ` Ulf Hansson
2022-11-02 2:49 ` Bjorn Andersson
2022-11-02 3:29 ` Stephen Boyd
2022-11-02 4:29 ` Bjorn Andersson
2022-11-02 18:08 ` Stephen Boyd
2022-11-02 10:52 ` Johan Hovold [this message]
2022-11-02 16:53 ` Stephen Boyd
2022-11-03 13:21 ` Johan Hovold
2022-11-03 18:19 ` Stephen Boyd
2022-11-04 10:53 ` Johan Hovold
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=Y2JL9/HFrb3E+CYY@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=mturquette@baylibre.com \
--cc=patches@lists.linux.dev \
--cc=quic_c_skakit@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=sboyd@kernel.org \
--cc=swboyd@chromium.org \
--cc=ulf.hansson@linaro.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