Devicetree
 help / color / mirror / Atom feed
From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Ulf Hansson <ulf.hansson@oss.qualcomm.com>
Cc: Ulf Hansson <ulfh@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Abel Vesa <abel.vesa@oss.qualcomm.com>,
	Bartosz Golaszewski <brgl@kernel.org>,
	Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add NMXC power domain for Nord SoC
Date: Wed, 2 Sep 2026 15:52:29 +0800	[thread overview]
Message-ID: <apfVvXLAW0j7g3pD@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <CAPx+jO8RVUv=mqDZ-GeJa=dEYdNCK9L8Vi=UCDY9GqQ1TefCsQ@mail.gmail.com>

On Tue, Sep 01, 2026 at 05:46:09PM +0200, Ulf Hansson wrote:
> On Wed, Aug 26, 2026 at 3:55 PM Shawn Guo
> <shengchao.guo@oss.qualcomm.com> wrote:
> >
> > The Nord CDSP subsystems do not take their memory rail from the shared
> > MX rail like all other Qualcomm SoCs, but from a dedicated NMXC RPMh
> > resource. Add the nmxc.lvl RPMh resource and register it in the Nord
> > power domain table.
> >
> > Changes for v2:
> > - Drop remoteproc changes since "mx" of remoteproc is just the name of
> >   memory rail input which can be wired up to NMXC power domain in DT
> > - Link to v1: https://lore.kernel.org/all/20260826102746.633076-1-shengchao.guo@oss.qualcomm.com/
> >
> > Anurag Pateriya (2):
> >   dt-bindings: power: qcom,rpmhpd: Add NMXC power domain index
> >   pmdomain: qcom: rpmhpd: Add NMXC power domain for Nord
> >
> >  drivers/pmdomain/qcom/rpmhpd.c          | 6 ++++++
> >  include/dt-bindings/power/qcom,rpmhpd.h | 1 +
> >  2 files changed, 7 insertions(+)
> >
> 
> Applied for next, thanks!

Thank you, Ulf!

Could you maintain a immutable branch for qcom,rpmhpd.h patch? I have
dependant DTS patches planned, so an immutable branch would help Bjorn
to resolve the dependency.

Shawn

  reply	other threads:[~2026-09-02  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 13:54 [PATCH v2 0/2] Add NMXC power domain for Nord SoC Shawn Guo
2026-08-26 13:54 ` [PATCH v2 1/2] dt-bindings: power: qcom,rpmhpd: Add NMXC power domain index Shawn Guo
2026-08-26 13:54 ` [PATCH v2 2/2] pmdomain: qcom: rpmhpd: Add NMXC power domain for Nord Shawn Guo
2026-09-01 15:46 ` [PATCH v2 0/2] Add NMXC power domain for Nord SoC Ulf Hansson
2026-09-02  7:52   ` Shawn Guo [this message]
2026-09-02  9:42     ` Ulf Hansson
2026-09-02 10:05       ` Shawn Guo

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=apfVvXLAW0j7g3pD@QCOM-aGQu4IUr3Y \
    --to=shengchao.guo@oss.qualcomm.com \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=anurag.pateriya@oss.qualcomm.com \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=ulf.hansson@oss.qualcomm.com \
    --cc=ulfh@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