From: sashiko-bot@kernel.org
To: "Shawn Guo" <shengchao.guo@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 3/7] arm64: dts: qcom: nord-rrd: Enable ADSP and CDSPs
Date: Tue, 29 Sep 2026 16:01:34 +0000 [thread overview]
Message-ID: <20260929160135.72EDB1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260929155152.1898666-4-shengchao.guo@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] dts: identical firmware-name for multiple distinct DSP cores
--
commit bd06b63b7bb11c940c1decfb487bb0de89250712
Author: Shawn Guo <shengchao.guo@oss.qualcomm.com>
arm64: dts: qcom: nord-rrd: Enable ADSP and CDSPs
This commit enables ADSP and CDSP remoteproc cores on the Nord RRD board.
It configures the firmware names and sets the status to okay for adsp,
cdsp0, cdsp1, cdsp2, and cdsp3.
> diff --git a/arch/arm64/boot/dts/qcom/nord-rrd.dts b/arch/arm64/boot/dts/qcom/nord-rrd.dts
> index 3673003c8b213..0b0acd33a2e19 100644
> --- a/arch/arm64/boot/dts/qcom/nord-rrd.dts
> +++ b/arch/arm64/boot/dts/qcom/nord-rrd.dts
[ ... ]
> +&remoteproc_cdsp0 {
> + firmware-name = "qcom/nord/cdsp.mbn",
> + "qcom/nord/cdsp_dtb.mbn";
> +
> + status = "okay";
> +};
> +
> +&remoteproc_cdsp1 {
> + firmware-name = "qcom/nord/cdsp.mbn",
> + "qcom/nord/cdsp_dtb.mbn";
> +
> + status = "okay";
> +};
> +
> +&remoteproc_cdsp2 {
> + firmware-name = "qcom/nord/cdsp.mbn",
> + "qcom/nord/cdsp_dtb.mbn";
> +
> + status = "okay";
> +};
> +
> +&remoteproc_cdsp3 {
> + firmware-name = "qcom/nord/cdsp.mbn",
> + "qcom/nord/cdsp_dtb.mbn";
[Severity: High]
Will cdsp1, cdsp2, and cdsp3 fail to load their firmware during boot?
In Qualcomm platforms, distinct remoteproc instances are backed by
different TrustZone Peripheral Authentication Service (PAS) IDs and are
assigned disjoint reserved physical memory regions.
Reusing cdsp.mbn and cdsp_dtb.mbn across all four cores means that cdsp1,
cdsp2, and cdsp3 will likely fail either the ELF segment physical address
checks in qcom_mdt_load() (because the ELF p_paddr will fall outside the
core's reserved memory region) or TrustZone signature verification.
Should these nodes use core-specific names (e.g., cdsp1.mbn, cdsp2.mbn)
matching standard multi-DSP firmware naming conventions instead?
> +
> + status = "okay";
> +};
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260929155152.1898666-1-shengchao.guo@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-09-29 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 15:51 [PATCH v4 0/7] arm64: dts: qcom: nord: Add remoteproc and PMIC support Shawn Guo
2026-09-29 15:51 ` [PATCH v4 1/7] dt-bindings: rtc: qcom-pm8xxx: Document PMM8654AU RTC Shawn Guo
2026-09-29 15:51 ` [PATCH v4 2/7] arm64: dts: qcom: nord: Add support for ADSP and CDSPs Shawn Guo
2026-10-01 14:44 ` Bartosz Golaszewski
2026-09-29 15:51 ` [PATCH v4 3/7] arm64: dts: qcom: nord-rrd: Enable " Shawn Guo
2026-09-29 16:01 ` sashiko-bot [this message]
2026-10-01 14:44 ` Bartosz Golaszewski
2026-09-29 15:51 ` [PATCH v4 4/7] arm64: dts: qcom: nord: Add the SPMI PMIC arbiter Shawn Guo
2026-09-29 15:51 ` [PATCH v4 5/7] arm64: dts: qcom: nord: Add PMAU0102 and PMM8650AU PMIC support Shawn Guo
2026-10-01 14:44 ` Bartosz Golaszewski
2026-09-29 15:51 ` [PATCH v4 6/7] dt-bindings: arm: qcom: Document Nord Ride Embedded board Shawn Guo
2026-09-29 15:51 ` [PATCH v4 7/7] arm64: dts: qcom: Add initial support for " 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=20260929160135.72EDB1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=shengchao.guo@oss.qualcomm.com \
/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;
as well as URLs for NNTP newsgroup(s).