Devicetree
 help / color / mirror / Atom feed
From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
	Harshal Dev <harshal.dev@oss.qualcomm.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 RESEND 3/5] arm64: dts: qcom: Add device tree for Nord SA8797P SoC
Date: Sat, 4 Jul 2026 09:32:55 +0800	[thread overview]
Message-ID: <akhix2qrSBp4elR3@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <0355cf52-b9ca-443e-88e7-2e7457e4b576@oss.qualcomm.com>

On Tue, Jun 16, 2026 at 01:00:32PM +0200, Konrad Dybcio wrote:
> On 5/26/26 7:12 AM, Shawn Guo wrote:
> > From: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
> > 
> > Add SoC-level device tree include for SA8797P, an automotive variant
> > of the Nord SoC family. The dtsi covers:
> > 
> >  - 64 SCMI shared memory regions reserved at 0xd7600000-0xd763f000
> >    for SMC-based firmware communication channels
> >  - Three QUPV3 GENI SE QUP blocks (qupv3_0/1/2) with UART controllers
> >    using SCMI power and performance domains via scmi11
> >  - UFS host controller with SCMI power domain via scmi3
> > 
> > Also introduce scmi-common.dtsi providing the firmware-level SCMI
> > channel nodes shared across SCMI based SoCs.
> 
> "across SoCs with GearVM firmware that utilize SCMI for resource
> management"

Sure!

> Is the scmi-common.dtsi actually any common? Are e.g. the interrupt
> numbers going to be stable?

Yes, from what I can see, it's completely common for Lemans and Nord
GearVM variant.

Shawn

  reply	other threads:[~2026-07-04  1:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  5:12 [PATCH v3 RESEND 0/5] Add initial device trees for Nord SA8797P Shawn Guo
2026-05-26  5:12 ` [PATCH v3 RESEND 1/5] dt-bindings: crypto: qcom,inline-crypto-engine: Document Nord ICE Shawn Guo
2026-05-26  5:12 ` [PATCH v3 RESEND 2/5] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-05-26  5:44   ` sashiko-bot
2026-06-16 10:57   ` Konrad Dybcio
2026-07-04  1:05     ` Shawn Guo
2026-06-16 10:58   ` Konrad Dybcio
2026-07-04  1:06     ` Shawn Guo
2026-05-26  5:12 ` [PATCH v3 RESEND 3/5] arm64: dts: qcom: Add device tree for Nord SA8797P SoC Shawn Guo
2026-05-26  6:01   ` sashiko-bot
2026-06-16 11:00   ` Konrad Dybcio
2026-07-04  1:32     ` Shawn Guo [this message]
2026-05-26  5:12 ` [PATCH v3 RESEND 4/5] dt-bindings: arm: qcom: Document SA8797P Ride board Shawn Guo
2026-05-26  6:11   ` sashiko-bot
2026-05-26  5:13 ` [PATCH v3 RESEND 5/5] arm64: dts: qcom: Add device tree for " Shawn Guo
2026-05-26  6:29   ` sashiko-bot
2026-06-16 11:02   ` Konrad Dybcio
2026-07-04  3:03     ` 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=akhix2qrSBp4elR3@QCOM-aGQu4IUr3Y \
    --to=shengchao.guo@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=deepti.jaggi@oss.qualcomm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=harshal.dev@oss.qualcomm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=robh@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