Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: pankaj.gupta@oss.nxp.com
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	Frank.Li@kernel.org, imx@lists.linux.dev, robh@kernel.org
Subject: Re: [PATCH v38 6/7] arm64: dts: imx8ulp: add secure enclave node
Date: Wed, 19 Aug 2026 13:23:37 +0000	[thread overview]
Message-ID: <20260819132337.B46501F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260820-imx-se-if-v38-6-5df4a4cff736@nxp.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The patch explicitly mentions that boards enable the enclave by including 'imx8ulp-firmware.dtsi', but this file is missing from the patch series.
- [Low] The disabled 'hsm0' node lacks the 'memory-region' property, causing an unconditional device tree schema validation warning.
--

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

arm64: dts: imx8ulp: add secure enclave node

Add the EdgeLock Enclave (ELE) secure-enclave node to the i.MX8ULP SoC dtsi.

> Keep the node disabled in the SoC dtsi so it does not impose a
> reserved-memory requirement on every board. Boards enable the enclave and
> provide its memory-region by including imx8ulp-firmware.dtsi.

[Severity: Medium]
The commit message mentions that boards enable the enclave by including
imx8ulp-firmware.dtsi, but this file appears to be missing from the patch.
Did you intend to include it in this series?

> diff --git a/arch/arm64/boot/dts/freescale/imx8ulp.dtsi b/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> index c6d1bb9edf388..38233dd74ee33 100644
> --- a/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8ulp.dtsi

[ ... ]

> @@ -185,6 +185,14 @@ 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>;
> +			status = "disabled";
> +		};
>  	};

[Severity: Low]
Does omitting the memory-region property here cause dtbs_check validation
warnings?

Even when the node is disabled, the fsl,imx-se.yaml binding schema might
unconditionally require the memory-region property for fsl,imx8ulp-se-ele-hsm.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260820-imx-se-if-v38-0-5df4a4cff736@nxp.com?part=6

  reply	other threads:[~2026-08-19 13:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 18:45 [PATCH v38 0/7] firmware: imx: driver for NXP secure-enclave pankaj.gupta
2026-08-19 18:45 ` [PATCH v38 1/7] Documentation/firmware: add imx/se to other_interfaces pankaj.gupta
2026-08-19 13:20   ` sashiko-bot
2026-08-19 18:45 ` [PATCH v38 2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc pankaj.gupta
2026-08-19 18:45 ` [PATCH v38 3/7] firmware: imx: add driver for NXP EdgeLock Enclave pankaj.gupta
2026-08-19 13:30   ` sashiko-bot
2026-08-19 18:45 ` [PATCH v38 4/7] firmware: imx: device context dedicated to priv pankaj.gupta
2026-08-19 18:46 ` [PATCH v38 5/7] firmware: imx: adds miscdev pankaj.gupta
2026-08-19 13:30   ` sashiko-bot
2026-08-19 18:46 ` [PATCH v38 6/7] arm64: dts: imx8ulp: add secure enclave node pankaj.gupta
2026-08-19 13:23   ` sashiko-bot [this message]
2026-08-19 18:46 ` [PATCH v38 7/7] arm64: dts: imx8ulp: add reserved memory for EdgeLock Enclave pankaj.gupta
2026-08-19 13:33   ` sashiko-bot

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=20260819132337.B46501F00A3A@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