All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: imx@lists.linux.dev, Frank.Li@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: imx943-evk: Add CM7 and CM33S nodes
Date: Wed, 15 Jul 2026 07:18:28 +0000	[thread overview]
Message-ID: <20260715071828.DB05D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715-imx-rproc-dts-v1-3-d02b583c507b@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing reserved memory regions for remoteproc firmware, breaking DDR firmware loading.
--

--- Patch [3]: [PATCH 3/4] arm64: dts: imx943-evk: Add CM7 and CM33S nodes ---
commit a58e64cf15c23fbbaba6ea1a5241a2bcdda233ef
Author: Peng Fan <peng.fan@nxp.com>

arm64: dts: imx943-evk: Add CM7 and CM33S nodes

This commit adds remoteproc nodes for Cortex-M7 (CM7-0, CM7-1) and Cortex-M33S
cores on the imx943-evk. It enables mailbox units and defines reserved memory
regions for vrings, resource tables, and shared DMA pools.

> diff --git a/arch/arm64/boot/dts/freescale/imx943-evk.dts b/arch/arm64/boot/dts/freescale/imx943-evk.dts
> index 674410e541cba..da7bfbd52e312 100644
> --- a/arch/arm64/boot/dts/freescale/imx943-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx943-evk.dts
> @@ -133,6 +133,36 @@ reg_audio_pwr: regulator-wm8962-pwr {
>  		enable-active-high;
>  	};
>  
> +	remoteproc-cm70 {
> +		compatible = "fsl,imx94-cm70";
> +		mbox-names = "tx", "rx", "rxdb";
> +		mboxes = <&mu11 0 1
> +			  &mu11 1 1
> +			  &mu11 3 1>;
> +		memory-region = <&cm70_vdevbuffer>, <&cm70_vdev0vring0>, <&cm70_vdev0vring1>,
> +				<&cm70_vdev1vring0>, <&cm70_vdev1vring1>, <&cm70_rsc_table>;

[Severity: High]
The commit message mentions adding reserved memory regions for firmware, but
are those regions missing from this memory-region list?

Without the firmware memory region defined, imx_rproc_da_to_va() will fail to
translate DDR addresses, which aborts firmware loading for segments destined
for DDR.

> +	};
> +
> +	remoteproc-cm71 {
> +		compatible = "fsl,imx94-cm71";
> +		mbox-names = "tx", "rx", "rxdb";
> +		mboxes = <&mu13 0 1
> +			  &mu13 1 1
> +			  &mu13 3 1>;
> +		memory-region = <&cm71_vdevbuffer>, <&cm71_vdev0vring0>, <&cm71_vdev0vring1>,
> +				<&cm71_vdev1vring0>, <&cm71_vdev1vring1>, <&cm71_rsc_table>;

[Severity: High]
Is the firmware memory region missing here as well?

> +	};
> +
> +	remoteproc-cm33s {
> +		compatible = "fsl,imx94-cm33s";
> +		mbox-names = "tx", "rx", "rxdb";
> +		mboxes = <&mu15 0 1
> +			  &mu15 1 1
> +			  &mu15 3 1>;
> +		memory-region = <&cm33s_vdevbuffer>, <&cm33s_vdev0vring0>, <&cm33s_vdev0vring1>,
> +				<&cm33s_vdev1vring0>, <&cm33s_vdev1vring1>, <&cm33s_rsc_table>;

[Severity: High]
And similarly, is the firmware memory region missing for the CM33S core?

> +	};
> +
>  	reserved-memory {
>  		ranges;
>  		#address-cells = <2>;
> @@ -145,6 +175,99 @@ linux,cma {
>  			size = <0 0x10000000>;
>  			linux,cma-default;
>  		};
> +
> +		cm33s_vdev0vring0: vdev0vring0@20800000 {

[Severity: High]
Does this block omit the actual firmware memory regions?

The reserved memory declarations define vrings, resource tables, and shared DMA
pools, but the firmware memory regions themselves seem to be completely missing.

There appears to be a 32MB gap in the DDR addresses (e.g., 0x80000000 to
0x81FFFFFF before cm70_vdev0vring0 at 0x82000000), which suggests the firmware
regions might have been unintentionally dropped.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260715-imx-rproc-dts-v1-0-d02b583c507b@nxp.com?part=3

  reply	other threads:[~2026-07-15  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15  7:10 [PATCH 0/4] arm64: dts: freescale: Add remoteproc support for i.MX EVKs Peng Fan (OSS)
2026-07-15  7:10 ` [PATCH 1/4] arm64: dts: imx95-19x19-evk: Add CM7 node and related memory nodes Peng Fan (OSS)
2026-07-15  7:17   ` sashiko-bot
2026-07-15 16:12     ` Frank Li
2026-07-15  7:10 ` [PATCH 2/4] arm64: dts: imx952-evk: " Peng Fan (OSS)
2026-07-15  7:10 ` [PATCH 3/4] arm64: dts: imx943-evk: Add CM7 and CM33S nodes Peng Fan (OSS)
2026-07-15  7:18   ` sashiko-bot [this message]
2026-07-15  7:10 ` [PATCH 4/4] arm64: dts: imx8ulp-evk: Update rpmsg resource table address Peng Fan (OSS)

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=20260715071828.DB05D1F000E9@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=peng.fan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.