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: conor+dt@kernel.org, imx@lists.linux.dev,
	devicetree@vger.kernel.org, Frank.Li@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 2/4] arm64: dts: imx952-evk: Add CM7 node and related memory nodes
Date: Thu, 23 Jul 2026 13:11:08 +0000	[thread overview]
Message-ID: <20260723131111.180EB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260723-imx-rproc-dts-v2-2-a5f5cf2eb55a@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The vdev buffer memory region bypasses the name check in `imx_rproc_prepare()`, causing it to be incorrectly mapped as a general carveout.
--

--- Patch [2]: [PATCH v2 2/4] arm64: dts: imx952-evk: Add CM7 node and related memory nodes ---
commit 22a3bbe540374b7f9198ab38657f1b8b84d70816
Author: Peng Fan <peng.fan@nxp.com>

arm64: dts: imx952-evk: Add CM7 node and related memory nodes

This commit adds the remoteproc CM7 node and reserved memory regions for the
Cortex-M7 remote processor. The reserved memory includes firmware memory,
vring buffers, and a resource table.

> diff --git a/arch/arm64/boot/dts/freescale/imx952-evk.dts b/arch/arm64/boot/dts/freescale/imx952-evk.dts
> index 62d1c1c7c5013..fec851544fb11 100644
> --- a/arch/arm64/boot/dts/freescale/imx952-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx952-evk.dts
[ ... ]
> @@ -82,6 +82,42 @@ linux_cma: linux,cma {
[ ... ]
> +		vdev1vring1: vdev1vring1@88018000 {
> +			reg = <0 0x88018000 0 0x8000>;
> +			no-map;
> +		};
> +
> +		vdevbuffer: vdevbuffer@88020000 {

[Severity: Medium]
Should this node be named vdev0buffer instead of vdevbuffer?

Because this node is named vdevbuffer, it bypasses the driver's hardcoded
skip check strstarts(res.name, "vdev0buffer") in imx_rproc_prepare().

Will this cause the memory region to be incorrectly mapped as a general
carveout during rproc_start()?

This unnecessarily consumes 1MB of vmalloc space via ioremap_wc and
double-maps the memory since it is simultaneously initialized as a DMA
coherent pool.

> +			compatible = "shared-dma-pool";
> +			reg = <0 0x88020000 0 0x100000>;
> +			no-map;
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260723-imx-rproc-dts-v2-0-a5f5cf2eb55a@nxp.com?part=2

  reply	other threads:[~2026-07-23 13:11 UTC|newest]

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

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=20260723131111.180EB1F000E9@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.