Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: pankaj.gupta@oss.nxp.com
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
	Frank.Li@kernel.org, imx@lists.linux.dev, robh@kernel.org
Subject: Re: [PATCH v30 6/7] arm64: dts: imx8ulp: add secure enclave node
Date: Fri, 24 Jul 2026 08:31:10 +0000	[thread overview]
Message-ID: <20260724083110.C0A9B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260724-imx-se-if-v30-6-ce8ba256692c@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing 'memory-region' DT property causes EdgeLock Enclave driver probe failure
--

--- Patch [6]: [PATCH v30 6/7] arm64: dts: imx8ulp: add secure enclave node ---
commit dd89141b9b11f1e2b0130369e668c9487347c666
Author: Pankaj Gupta <pankaj.gupta@nxp.com>

arm64: dts: imx8ulp: add secure enclave node

This commit adds support for the NXP secure enclave called EdgeLock Enclave
firmware for imx8ulp-evk. It adds the sram0 label and a new secure-enclave
device tree node.

> 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]
Will this node cause the EdgeLock Enclave driver probe to fail?

Looking at se_if_probe() in drivers/firmware/imx/se_ctrl.c, the driver requires
reserved memory initialization when reserved_dma_ranges is set (which is true
for the fsl,imx8ulp-se-ele-hsm compatibility string):

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 this new device tree node,
of_reserved_mem_device_init() will return an error, causing the probe to
unconditionally abort. Should a memory-region property be included here to
prevent the probe failure?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260724-imx-se-if-v30-0-ce8ba256692c@nxp.com?part=6

  reply	other threads:[~2026-07-24  8:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  9:05 [PATCH v30 0/7] firmware: imx: driver for NXP secure-enclave pankaj.gupta
2026-07-24  9:05 ` [PATCH v30 1/7] Documentation/firmware: add imx/se to other_interfaces pankaj.gupta
2026-07-24  8:18   ` sashiko-bot
2026-07-24  9:05 ` [PATCH v30 2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc pankaj.gupta
2026-07-24  9:05 ` [PATCH v30 3/7] firmware: imx: add driver for NXP EdgeLock Enclave pankaj.gupta
2026-07-24  8:28   ` sashiko-bot
2026-07-24  9:05 ` [PATCH v30 4/7] firmware: imx: device context dedicated to priv pankaj.gupta
2026-07-24  8:30   ` sashiko-bot
2026-07-24  9:05 ` [PATCH v30 5/7] firmware: drivers: imx: adds miscdev pankaj.gupta
2026-07-24  8:32   ` sashiko-bot
2026-07-24  9:05 ` [PATCH v30 6/7] arm64: dts: imx8ulp: add secure enclave node pankaj.gupta
2026-07-24  8:31   ` sashiko-bot [this message]
2026-07-24  9:05 ` [PATCH v30 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=20260724083110.C0A9B1F000E9@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