From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Dhruvin Rajpura <drajpura@qti.qualcomm.com>,
Anandu Krishnan E <anandu.e@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] arm64: dts: qcom: nord: Add support for ADSP and CDSPs
Date: Thu, 3 Sep 2026 11:03:46 +0800 [thread overview]
Message-ID: <apjjku26X87-IjZU@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <9a7cee1d-1058-4184-a915-e7e943b4791c@oss.qualcomm.com>
On Wed, Sep 02, 2026 at 03:52:37PM +0200, Konrad Dybcio wrote:
> On 8/31/26 5:20 AM, Shawn Guo wrote:
> > Add device tree nodes to support ADSP (HPASS DSP) and CDSPs remoteproc
> > on Nord SoC.
> >
> > This includes:
> > - SMEM memory reservation used by the inter-processor communication
> > infrastructure
> > - IPCC mailbox controller for inter-processor signalling
> > - AOSS QMP node for load state power management
> > - SMP2P nodes providing stop control and fault/crash interrupt signals
> > - Remoteproc nodes with a GLINK edge and FastRPC compute contexts for
> > userspace offload
> >
> > The embedded variant specific power domains, XO clock, and interconnect
> > paths are filled in nord-embedded.dtsi.
> >
> > Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
> > ---
>
> With our previous discussion at <ao5Vh_d_dAlJknpl@QCOM-aGQu4IUr3Y>
> in mind, can we reasonably assume the ADSP description is fine as-is?
Yes, ADSP0 can work independently just like the single ADSP on other
SoCs. As audio support depends on ADSP0, we would like to get it land
first and leave the cluster support as an incremental change later.
Shawn
next prev parent reply other threads:[~2026-09-03 3:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 3:20 [PATCH 0/6] arm64: dts: qcom: nord: Add remoteproc and PMIC support Shawn Guo
2026-08-31 3:20 ` [PATCH 1/6] arm64: dts: qcom: nord: Add support for ADSP and CDSPs Shawn Guo
2026-09-02 13:52 ` Konrad Dybcio
2026-09-03 3:03 ` Shawn Guo [this message]
2026-09-03 9:16 ` Konrad Dybcio
2026-08-31 3:20 ` [PATCH 2/6] arm64: dts: qcom: nord-rrd: Enable " Shawn Guo
2026-08-31 8:17 ` Abel Vesa
2026-08-31 3:21 ` [PATCH 3/6] arm64: dts: qcom: nord: Add the SPMI PMIC arbiter Shawn Guo
2026-08-31 8:16 ` Abel Vesa
2026-09-02 13:57 ` Konrad Dybcio
2026-08-31 3:21 ` [PATCH 4/6] arm64: dts: qcom: nord: Add PMAU0102 and PMM8650AU PMIC support Shawn Guo
2026-09-02 14:17 ` Konrad Dybcio
2026-09-03 6:36 ` Shawn Guo
2026-08-31 3:21 ` [PATCH 5/6] dt-bindings: arm: qcom: Document Nord Ride Embedded board Shawn Guo
2026-09-01 8:31 ` Krzysztof Kozlowski
2026-09-03 3:10 ` Shawn Guo
2026-08-31 3:21 ` [PATCH 6/6] arm64: dts: qcom: Add initial support for " Shawn Guo
2026-08-31 8:16 ` Abel Vesa
2026-09-02 14:00 ` Konrad Dybcio
2026-09-03 7:40 ` Shawn Guo
2026-09-03 7:56 ` Konrad Dybcio
2026-09-03 8:13 ` Shawn Guo
2026-09-03 8:19 ` 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=apjjku26X87-IjZU@QCOM-aGQu4IUr3Y \
--to=shengchao.guo@oss.qualcomm.com \
--cc=anandu.e@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drajpura@qti.qualcomm.com \
--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=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