From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linusw@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] pinctrl: qcom: lpass-lpi: Enable runtime PM hooks on LPASS LPI SoCs
Date: Fri, 22 May 2026 13:13:13 +0200 [thread overview]
Message-ID: <d0259627-bdda-4533-9051-a40546241e89@oss.qualcomm.com> (raw)
In-Reply-To: <20260513140009.3841770-2-ajay.nandam@oss.qualcomm.com>
On 5/13/26 4:00 PM, Ajay Kumar Nandam wrote:
> The LPASS LPI core conversion to PM clock framework relies on variant
> drivers wiring runtime PM callbacks.
>
> Hook up runtime PM callbacks for the LPASS LPI variant drivers touched
> in this patch so they are prepared for the shared core conversion.
> sc7280 wiring is completed in the following patch.
>
> This commit is a preparatory NOP on its own, as runtime PM is still
> disabled on these devices until the following core conversion patch.
>
> This is a mechanical per-variant driver update that relies on the
> same generic PM clock flow (of_pm_clk_add_clks() + pm_clk_suspend/
> pm_clk_resume()) and DT-provided clocks.
>
> Runtime behavior was validated on Kodiak (sc7280).
>
> Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
> ---
> drivers/pinctrl/qcom/pinctrl-milos-lpass-lpi.c | 7 +++++++
> drivers/pinctrl/qcom/pinctrl-sc8280xp-lpass-lpi.c | 15 +++++++++++----
> drivers/pinctrl/qcom/pinctrl-sdm660-lpass-lpi.c | 7 +++++++
> drivers/pinctrl/qcom/pinctrl-sdm670-lpass-lpi.c | 7 +++++++
> drivers/pinctrl/qcom/pinctrl-sm4250-lpass-lpi.c | 7 +++++++
> drivers/pinctrl/qcom/pinctrl-sm6115-lpass-lpi.c | 7 +++++++
> drivers/pinctrl/qcom/pinctrl-sm8250-lpass-lpi.c | 15 +++++++++++----
> drivers/pinctrl/qcom/pinctrl-sm8450-lpass-lpi.c | 15 +++++++++++----
> drivers/pinctrl/qcom/pinctrl-sm8550-lpass-lpi.c | 15 +++++++++++----
> drivers/pinctrl/qcom/pinctrl-sm8650-lpass-lpi.c | 15 +++++++++++----
I don't understand why the 7280 change is in patch 2, please move
it here too
and you still need to adjust
drivers/pinctrl/qcom/pinctrl-sm6350-lpass-lpi.c
Konrad
next prev parent reply other threads:[~2026-05-22 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 14:00 [PATCH v5 0/2] pinctrl: qcom: lpass-lpi: Switch to PM clock framework Ajay Kumar Nandam
2026-05-13 14:00 ` [PATCH v5 1/2] pinctrl: qcom: lpass-lpi: Enable runtime PM hooks on LPASS LPI SoCs Ajay Kumar Nandam
2026-05-22 11:13 ` Konrad Dybcio [this message]
2026-05-13 14:00 ` [PATCH v5 2/2] pinctrl: qcom: lpass-lpi: Switch to PM clock framework for runtime PM Ajay Kumar Nandam
2026-05-22 11:15 ` Konrad Dybcio
2026-05-22 20:33 ` [PATCH v6 0/2] pinctrl: qcom: lpass-lpi: Switch to PM clock framework Ajay Kumar Nandam
2026-05-22 20:33 ` [PATCH v6 1/2] pinctrl: qcom: lpass-lpi: Enable runtime PM hooks on LPASS LPI SoCs Ajay Kumar Nandam
2026-05-22 20:33 ` [PATCH v6 2/2] pinctrl: qcom: lpass-lpi: Switch to PM clock framework for runtime PM Ajay Kumar Nandam
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=d0259627-bdda-4533-9051-a40546241e89@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=ajay.nandam@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®