From: sashiko-bot@kernel.org
To: pankaj.gupta@oss.nxp.com
Cc: Frank.Li@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, conor+dt@kernel.org
Subject: Re: [PATCH v29 6/7] arm64: dts: imx8ulp: add secure enclave node
Date: Tue, 21 Jul 2026 10:57:07 +0000 [thread overview]
Message-ID: <20260721105707.C9FFE1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260721-imx-se-if-v29-6-04a362f4fcca@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The `secure-enclave` node is missing the required `memory-region` property, violating the DT binding and causing the `se_ctrl` driver to fail probe unconditionally with `-ENODEV`.
--
--- Patch [6]: [PATCH v29 6/7] arm64: dts: imx8ulp: add secure enclave node ---
commit 2de8edbeb186b1bf74b55f8e1113a94023d98cce
Author: Pankaj Gupta <pankaj.gupta@nxp.com>
arm64: dts: imx8ulp: add secure enclave node
This commit adds support for the NXP EdgeLock Enclave firmware (se-fw)
on imx8ulp-evk by defining the secure-enclave node in the device tree.
> diff --git a/arch/arm64/boot/dts/freescale/imx8ulp.dtsi b/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> index c6d1bb9edf388..182f1444b6434 100644
> --- a/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
[ ... ]
> @@ -185,6 +185,13 @@ scmi_sensor: protocol@15 {
> #thermal-sensor-cells = <1>;
> };
> };
> +
> + hsm0: secure-enclave {
> + compatible = "fsl,imx8ulp-se-ele-hsm";
> + mbox-names = "tx", "rx";
> + mboxes = <&s4muap 0 0>, <&s4muap 1 0>;
> + sram = <&sram0>;
> + };
[Severity: High]
Does this node need a memory-region property?
Looking at the driver side in drivers/firmware/imx/se_ctrl.c, when the
hardware matches and sets reserved_dma_ranges = true, se_if_probe() executes
this logic:
drivers/firmware/imx/se_ctrl.c:se_if_probe() {
...
if (if_node->reserved_dma_ranges) {
ret = of_reserved_mem_device_init(dev);
if (ret)
return dev_err_probe(dev, ret,
"Failed to init reserved memory region.");
}
...
}
Since the memory-region property is missing from the device tree node here,
will of_reserved_mem_device_init() fail to parse the phandle and return
-ENODEV, causing the probe to unconditionally fail?
> };
>
> cm33: remoteproc-cm33 {
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260721-imx-se-if-v29-0-04a362f4fcca@nxp.com?part=6
next prev parent reply other threads:[~2026-07-21 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 11:23 [PATCH v29 0/7] firmware: imx: driver for NXP secure-enclave pankaj.gupta
2026-07-21 11:23 ` [PATCH v29 1/7] Documentation/firmware: add imx/se to other_interfaces pankaj.gupta
2026-07-21 10:37 ` sashiko-bot
2026-07-21 11:23 ` [PATCH v29 2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc pankaj.gupta
2026-07-21 11:23 ` [PATCH v29 3/7] firmware: imx: add driver for NXP EdgeLock Enclave pankaj.gupta
2026-07-21 10:49 ` sashiko-bot
2026-07-21 10:50 ` Frieder Schrempf
2026-07-21 11:23 ` [PATCH v29 4/7] firmware: imx: device context dedicated to priv pankaj.gupta
2026-07-21 10:51 ` sashiko-bot
2026-07-21 11:23 ` [PATCH v29 5/7] firmware: drivers: imx: adds miscdev pankaj.gupta
2026-07-21 10:54 ` sashiko-bot
2026-07-21 11:23 ` [PATCH v29 6/7] arm64: dts: imx8ulp: add secure enclave node pankaj.gupta
2026-07-21 10:57 ` sashiko-bot [this message]
2026-07-21 11:23 ` [PATCH v29 7/7] arm64: dts: imx8ulp-evk: add reserved memory property pankaj.gupta
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=20260721105707.C9FFE1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=pankaj.gupta@oss.nxp.com \
--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