From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Luca Weiss <luca@lucaweiss.eu>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
"Bjorn Andersson" <andersson@kernel.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Stephan Gerhold" <stephan@gerhold.net>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Matti Lehtimäki" <matti.lehtimaki@gmail.com>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/9] remoteproc: qcom_q6v5_mss: Handle platforms with one power domain
Date: Mon, 27 Jan 2025 09:58:45 +0100 [thread overview]
Message-ID: <Z5dKxZ-fri8RaTPo@linaro.org> (raw)
In-Reply-To: <20250126-msm8226-modem-v2-3-e88d76d6daff@lucaweiss.eu>
On Sun, Jan 26, 2025 at 09:57:22PM +0100, Luca Weiss wrote:
> For example MSM8974 has mx voltage rail exposed as regulator and only cx
> voltage rail is exposed as power domain. This power domain (cx) is
> attached internally in power domain and cannot be attached in this driver.
>
> Fixes: 8750cf392394 ("remoteproc: qcom_q6v5_mss: Allow replacing regulators with power domains")
> Co-developed-by: Matti Lehtimäki <matti.lehtimaki@gmail.com>
> Signed-off-by: Matti Lehtimäki <matti.lehtimaki@gmail.com>
> Signed-off-by: Luca Weiss <luca@lucaweiss.eu>
> ---
> Changes in v2:
> - Move MSM8974 mx-supply from "fallback_proxy_supply" to
> "proxy_supply" to match updated DT schema
> - Add fixes tag
> ---
> drivers/remoteproc/qcom_q6v5_mss.c | 20 +++++++++++++++++---
> 1 file changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/remoteproc/qcom_q6v5_mss.c b/drivers/remoteproc/qcom_q6v5_mss.c
> index e78bd986dc3f256effce4470222c0a5faeea86ec..e2523b01febf393abfe50740a68b85a04011293c 100644
> --- a/drivers/remoteproc/qcom_q6v5_mss.c
> +++ b/drivers/remoteproc/qcom_q6v5_mss.c
> @@ -1828,6 +1828,13 @@ static int q6v5_pds_attach(struct device *dev, struct device **devs,
> if (!pd_names)
> return 0;
>
> + /* Handle single power domain */
> + if (dev->pm_domain) {
> + devs[0] = dev;
> + pm_runtime_enable(dev);
> + return 1;
> + }
> +
> while (pd_names[num_pds])
> num_pds++;
Hmm, I think you should put the above if condition below this loop and
verify that num_pds == 1. Otherwise this would hide the error condition
if the platform needs multple PDs, but someone only specifies one of
them in the DT. i.e.
if (num_pds == 1 && dev->pm_domain) {
// ...
}
>
> @@ -1851,8 +1858,15 @@ static int q6v5_pds_attach(struct device *dev, struct device **devs,
> static void q6v5_pds_detach(struct q6v5 *qproc, struct device **pds,
> size_t pd_count)
> {
> + struct device *dev = qproc->dev;
> int i;
>
> + /* Handle single power domain */
> + if (dev->pm_domain && pd_count) {
Maybe if (pd_count == 1 && dev->pm_domain) for consistency with the
above then.
> + pm_runtime_disable(dev);
I'm guessing it does, but just to make sure: Have you verified that the
power domain is indeed voted for off after this call to
pm_runtime_disable()? Start the remoteproc and when it's booted inspect
/sys/kernel/debug/pm_genpd/pm_genpd_summary to see if the PD/remoteproc
dev is suspended.
Thanks,
Stephan
next prev parent reply other threads:[~2025-01-27 8:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 20:57 [PATCH v2 0/9] Modem support for MSM8226 Luca Weiss
2025-01-26 20:57 ` [PATCH v2 1/9] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Support platforms with one power domain Luca Weiss
2025-01-27 7:48 ` Krzysztof Kozlowski
2025-01-26 20:57 ` [PATCH v2 2/9] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8226 Luca Weiss
2025-01-27 7:48 ` Krzysztof Kozlowski
2025-01-26 20:57 ` [PATCH v2 3/9] remoteproc: qcom_q6v5_mss: Handle platforms with one power domain Luca Weiss
2025-01-27 8:58 ` Stephan Gerhold [this message]
2025-01-27 22:21 ` Luca Weiss
2025-01-28 7:30 ` Stephan Gerhold
2025-01-28 22:02 ` Luca Weiss
2025-01-26 20:57 ` [PATCH v2 4/9] remoteproc: qcom_q6v5_mss: Add modem support on MSM8226 Luca Weiss
2025-01-27 9:06 ` Stephan Gerhold
2025-01-26 20:57 ` [PATCH v2 5/9] ARM: dts: qcom: msm8226: Add node for TCSR halt regs Luca Weiss
2025-01-28 11:27 ` Konrad Dybcio
2025-01-26 20:57 ` [PATCH v2 6/9] ARM: dts: qcom: msm8226: Add smsm node Luca Weiss
2025-01-27 9:28 ` Stephan Gerhold
2025-01-26 20:57 ` [PATCH v2 7/9] ARM: dts: qcom: msm8226: Add modem remoteproc node Luca Weiss
2025-01-27 9:19 ` Stephan Gerhold
2025-01-27 13:27 ` Luca Weiss
2025-01-26 20:57 ` [PATCH v2 8/9] ARM: dts: qcom: msm8226: Add BAM DMUX Ethernet/IP device Luca Weiss
2025-01-27 9:25 ` Stephan Gerhold
2025-01-26 20:57 ` [PATCH v2 9/9] ARM: dts: qcom: msm8226-samsung-matisse-common: Enable modem Luca Weiss
2025-01-27 9:44 ` Stephan Gerhold
2025-01-27 13:34 ` Luca Weiss
2025-01-27 13:44 ` Stephan Gerhold
2025-01-27 15:09 ` Konrad Dybcio
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=Z5dKxZ-fri8RaTPo@linaro.org \
--to=stephan.gerhold@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=luca@lucaweiss.eu \
--cc=mathieu.poirier@linaro.org \
--cc=matti.lehtimaki@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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