Devicetree
 help / color / mirror / Atom feed
From: Marek Vasut <marex@nabladev.com>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: sashiko-reviews@lists.linux.dev, devicetree@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org, Frank.Li@kernel.org,
	imx@lists.linux.dev
Subject: Re: [PATCH v4 4/6] arm64: dts: imx8mm: imx8mp: Add CM DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
Date: Wed, 15 Jul 2026 00:51:26 +0200	[thread overview]
Message-ID: <a3602ef8-2b77-4cc3-adef-2c4cba08a5d9@nabladev.com> (raw)
In-Reply-To: <alWR66rjt-9jGEOV@SMW015318>

On 7/14/26 3:33 AM, Frank Li wrote:

>>>> [Severity: Medium]
>>>> Will this node name bypass the driver's carveout exclusion logic?
>>>>
>>>> Looking at imx_rproc_prepare(), it iterates over memory-regions and checks
>>>> specifically for the name "vdev0buffer" to skip processing the vdev buffer:
>>>>
>>>> 	if (!strcmp(it.node->name, "rsc-table") ||
>>>> 	    !strcmp(it.node->name, "vdev0vring0") ||
>>>> 	    !strcmp(it.node->name, "vdev0vring1") ||
>>>> 	    strstarts(res.name, "vdev0buffer"))
>>>> 		continue;
>>>>
>>>> Because this node is named "vdevbuffer" instead of "vdev0buffer", it appears
>>>> it will be mapped as a generic carveout via ioremap_wc() and unintentionally
>>>> included in the remoteproc coredump.
>>>>
>>>> Could this node be renamed to "vdev0buffer" to avoid wasting vmalloc space
>>>> and bloating the coredump?
>>>
>>> Look like make sense, please check it.
>>>
>>> It is not good to use node-name as ABI. Laurentiu is working on use
>>> memory-region-namses.
>> The memory regionss are referenced from imx8mm-cm4 { } node via the
>> memory-region property:
>>
>> memory-region = <&vdevbuffer>, <&vdev0vring0>, <&vdev0vring1>, <&rsc_table>;
> 
> I known, but now code parser node-name, At your case, it.node->name is
> vdevbuffer, but driver expected vdev0buffer.  so above check will be failure.
> 
> suppose it should be
> 
>   vdevbuffer: vdev0buffer@b8400000
>               ^^^^^^^^^^^
> 
> I know it is bad, but waiting for Laurentiu to fix it.
Actually, if I look at "git log -p drivers/remoteproc/imx_rproc.c" in 
current linux-next 20260714 , which has the entire history of 
imx_rproc.c and the latest content, the code cited by the AI:

"
	if (!strcmp(it.node->name, "rsc-table") ||
	    !strcmp(it.node->name, "vdev0vring0") ||
	    !strcmp(it.node->name, "vdev0vring1") ||
	    strstarts(res.name, "vdev0buffer"))
		continue;
"

never existed in imx_rproc.c:

"
$ git log --follow -p next/master -- drivers/remoteproc/imx_rproc.c | 
grep vdev0vring1
     vdev regions are vdev0vring0, vdev0vring1, vdevbuffer and similar.
"

It seems the AI hallucinated something which is not based in reality ?

  reply	other threads:[~2026-07-14 22:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 20:05 [PATCH v4 1/6] arm64: dts: imx8mm: imx8mp: Add LVDS DTOs for Data Modul i.MX8M Mini and Plus eDM SBC Marek Vasut
2026-07-05 20:05 ` [PATCH v4 2/6] arm64: dts: imx8mm: imx8mp: Add legacy board " Marek Vasut
2026-07-05 20:05 ` [PATCH v4 3/6] arm64: dts: imx8mm: imx8mp: Add HDMI " Marek Vasut
2026-07-05 20:05 ` [PATCH v4 4/6] arm64: dts: imx8mm: imx8mp: Add CM " Marek Vasut
2026-07-05 20:24   ` sashiko-bot
2026-07-13 15:45     ` Frank Li
2026-07-13 16:33       ` Marek Vasut
2026-07-14  1:33         ` Frank Li
2026-07-14 22:51           ` Marek Vasut [this message]
2026-07-05 20:05 ` [PATCH v4 5/6] arm64: dts: imx8mm: imx8mp: Add FIO1 " Marek Vasut
2026-07-05 20:20   ` sashiko-bot
2026-07-05 20:05 ` [PATCH v4 6/6] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio " Marek Vasut
2026-07-05 20:22   ` sashiko-bot
2026-07-13 15:49     ` Frank Li
2026-07-13 16:41       ` Marek Vasut
2026-07-05 20:22 ` [PATCH v4 1/6] arm64: dts: imx8mm: imx8mp: Add LVDS " 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=a3602ef8-2b77-4cc3-adef-2c4cba08a5d9@nabladev.com \
    --to=marex@nabladev.com \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.li@oss.nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --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