From: sashiko-bot@kernel.org
To: "Ananthu C V" <ananthu.cv@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v5 3/3] arm64: dts: qcom: add SoCCP DT node for Glymur
Date: Tue, 07 Jul 2026 10:25:35 +0000 [thread overview]
Message-ID: <20260707102536.0055F1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260707-glymur-soccp-v5-3-053993f0c6fe@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] The 'qcom,glymur-soccp-pas' compatible string incorrectly falls back to 'qcom,kaanapali-soccp-pas', which lacks required TrustZone memory configuration.
- [Medium] The `remoteproc_soccp` node is missing `status = "disabled";` in the base SoC `.dtsi` file.
--
--- Patch [3]: [PATCH v5 3/3] arm64: dts: qcom: add SoCCP DT node for Glymur ---
commit ba22e521690a1cf89042171dd1def802f653ee49
Author: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
arm64: dts: qcom: add SoCCP DT node for Glymur
This commit adds the device tree nodes required to enable the SoC Control
Processor (SoCCP) on Qualcomm Glymur/Mahua SoCs.
> diff --git a/arch/arm64/boot/dts/qcom/glymur.dtsi b/arch/arm64/boot/dts/qcom/glymur.dtsi
> --- a/arch/arm64/boot/dts/qcom/glymur.dtsi
> +++ b/arch/arm64/boot/dts/qcom/glymur.dtsi
[ ... ]
> + remoteproc_soccp: remoteproc@d00000 {
[Severity: Medium]
Should this remoteproc node include status = "disabled"?
Any board including glymur.dtsi that does not actively use the SoCCP or
provide firmware for it will default to status = "okay". The driver will
attempt to load firmware and boot the remoteproc, potentially causing
spurious driver probe errors and kernel log pollution.
> + compatible = "qcom,glymur-soccp-pas", "qcom,kaanapali-soccp-pas";
[Severity: High]
Is it safe to use "qcom,kaanapali-soccp-pas" as a fallback here?
If an older kernel lacking the Glymur-specific match binds to this node via
the fallback, it will use the kaanapali_soccp_resource which does not set
.needs_tzmem = true.
Since Glymur requires TrustZone memory configuration to prevent faults, the
Kaanapali driver cannot safely run Glymur hardware and may cause a fatal
SMMU or TrustZone panic during remote processor boot.
> + reg = <0x0 0x00d00000 0x0 0x200000>;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260707-glymur-soccp-v5-0-053993f0c6fe@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-07-07 10:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 10:12 [PATCH v5 0/3] Add remoteproc PAS loader for SoCCP on Glymur DT Ananthu C V
2026-07-07 10:12 ` [PATCH v5 1/3] remoteproc: qcom: pas: add needs_tzmem flag to trigger shmbridge creation Ananthu C V
2026-07-09 7:11 ` Mukesh Ojha
2026-07-07 10:12 ` [PATCH v5 2/3] arm64: dts: qcom: fix SoCCP memory mappings for Glymur Ananthu C V
2026-07-09 7:14 ` Mukesh Ojha
2026-07-09 12:01 ` Ananthu C V
2026-07-07 10:12 ` [PATCH v5 3/3] arm64: dts: qcom: add SoCCP DT node " Ananthu C V
2026-07-07 10:25 ` sashiko-bot [this message]
2026-07-09 7:18 ` Dmitry Baryshkov
2026-07-09 12:15 ` Ananthu C V
2026-07-09 12:11 ` Ananthu C V
2026-07-10 18:07 ` (subset) [PATCH v5 0/3] Add remoteproc PAS loader for SoCCP on Glymur DT Bjorn Andersson
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=20260707102536.0055F1F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ananthu.cv@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