From: Johan Hovold <johan@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: qcom: edp: Add runtime PM support
Date: Wed, 18 Sep 2024 12:05:59 +0200 [thread overview]
Message-ID: <ZuqmB3Cn7mGfA2PU@hovoldconsulting.com> (raw)
In-Reply-To: <20240907-phy-qcom-edp-enable-runtime-pm-v1-1-8b9ee4210e1e@linaro.org>
On Sat, Sep 07, 2024 at 06:25:21PM +0300, Abel Vesa wrote:
> Enable runtime PM support by adding proper ops which will handle the
Avoid words like 'proper' here (what are non-proper runtime PM ops?).
> clocks and regulators. These resources will now be handled on power_on and
> power_off instead of init and exit PHY ops.
No, this is simply a false claim and indicates that you haven't reviewed
how PHY runtime PM works. Core will increment the usage count on init()
and decrement it on exit().
> Also enable these resources on
> probe in order to balance out the disabling that is happening right after.
> Prevent runtime PM from being ON by default as well.
And here you just regressed all current systems that do not have udev
rules to enable runtime PM, and which will now be stuck with these
resources always-on (e.g. during DPMS off and system suspend).
In fact, you are even regressing systems that would enable runtime PM,
as the runtime suspend callback would not currently be called when you
enter system suspend so the regulators and clocks will be left on.
This clearly hasn't been tested and analysed properly.
> +static int __maybe_unused qcom_edp_runtime_suspend(struct device *dev)
> +{
> + struct qcom_edp *edp = dev_get_drvdata(dev);
> +
> + dev_err(dev, "Suspending DP phy\n");
You forgot to drop your development printks (same below).
Johan
next prev parent reply other threads:[~2024-09-18 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 15:25 [PATCH] phy: qcom: edp: Add runtime PM support Abel Vesa
2024-09-07 17:52 ` Dmitry Baryshkov
2024-09-08 18:12 ` Abel Vesa
2024-09-08 18:43 ` Dmitry Baryshkov
2024-09-08 18:55 ` Abel Vesa
2024-09-08 3:19 ` Bjorn Andersson
2024-09-08 18:22 ` Abel Vesa
2024-09-18 10:05 ` Johan Hovold [this message]
2024-09-18 13:10 ` Abel Vesa
2024-09-20 8:40 ` Johan Hovold
2024-09-20 9:02 ` Abel Vesa
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=ZuqmB3Cn7mGfA2PU@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=srinivas.kandagatla@linaro.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