[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20221104191918.D5A5BC433C1@smtp.kernel.org>
Date: Fri, 04 Nov 2022 12:19:16 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
patches@...ts.linux.dev, Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
linux-arm-msm@...r.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Johan Hovold <johan+linaro@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Taniya Das <quic_tdas@...cinc.com>,
Satya Priya <quic_c_skakit@...cinc.com>,
Douglas Anderson <dianders@...omium.org>,
Matthias Kaehlcke <mka@...omium.org>
Subject: Re: [PATCH v3] clk: qcom: gdsc: Remove direct runtime PM calls
Quoting Stephen Boyd (2022-11-03 11:30:30)
> 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[1] 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
Applied to clk-fixes
Powered by blists - more mailing lists