From: sashiko-bot@kernel.org
To: "Anurag Pateriya" <anurag.pateriya@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord
Date: Thu, 12 Nov 2026 08:15:24 +0000 [thread overview]
Message-ID: <sashiko-outbox-210682@kernel.org> (raw)
In-Reply-To: <20261112-nord-soccp-dt-v4-1-af6e44e9f397@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Medium] arm64: dts: qcom: nord: undocumented qcom,nord-soccp-pas
compatible
- [Low] arm64: dts: qcom: nord: commit message describes moving new
compatible
--
commit 368cfee1a2a184e173c7b4c22c268cf4858fda12
Author: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord
This commit adds the SoCCP remoteproc and SMP2P nodes in nord.dtsi and
enables the compatible, clock, and power domains in nord-embedded.dtsi.
> Move the SoCCP compatible to nord-embedded.dtsi to fix binding
> errors reported for the Ride board.
[Severity: Low]
This isn't a bug, but this sentence reads like a changelog note between
patch revisions. Prior to this commit, neither remoteproc_soccp nor a
SoCCP compatible existed in nord.dtsi, so the compatible is being added in
nord-embedded.dtsi rather than moved from nord.dtsi.
> diff --git a/arch/arm64/boot/dts/qcom/nord-embedded.dtsi b/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
> index 5a1520e436c64..2211171b8c4c0 100644
> --- a/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
> +++ b/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
> @@ -464,6 +464,16 @@ &remoteproc_cdsp3 {
> "nsp";
> };
>
> +&remoteproc_soccp {
> + compatible = "qcom,nord-soccp-pas";
[Severity: Medium]
Is "qcom,nord-soccp-pas" documented in a Devicetree binding schema or
supported by the PAS driver yet?
Neither Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml
nor Documentation/devicetree/bindings/remoteproc/qcom,nord-pas.yaml lists
"qcom,nord-soccp-pas", and qcom_pas_of_match[] in
drivers/remoteproc/qcom_q6v5_pas.c only matches the Nord ADSP and CDSP0..3
compatibles. This causes dtbs_check to fail on the Nord embedded device
trees and prevents remoteproc_soccp from binding at runtime.
In addition, remoteproc_soccp in nord.dtsi specifies a single
memory-region = <&soccp_mem>, whereas the existing SoCCP and Nord PAS
binding schemas require two memory-region items.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112-nord-soccp-dt-v4-0-af6e44e9f397@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-11-12 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:02 [PATCH v4 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya
2026-11-12 8:02 ` [PATCH v4 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya
2026-11-12 8:15 ` sashiko-bot [this message]
2026-11-12 8:02 ` [PATCH v4 2/3] arm64: dts: qcom: nord: Add SoCCP on RRD board Anurag Pateriya
2026-11-12 8:02 ` [PATCH v4 3/3] arm64: dts: qcom: nord: Add SoCCP on Ride-Embedded board Anurag Pateriya
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=sashiko-outbox-210682@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=anurag.pateriya@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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