Devicetree
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: Marek Vasut <marex@nabladev.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 16:37:42 -0500	[thread overview]
Message-ID: <alf9pp3c_zI4rwC0@SMW015318> (raw)
In-Reply-To: <c9a67cbd-fda8-4016-9cff-9125f3191b74@nabladev.com>

On Wed, Jul 15, 2026 at 06:38:32PM +0200, Marek Vasut wrote:
> On 7/15/26 6:22 PM, Frank Li wrote:
>
> Hello Frank,
>
> > > > > > > [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:
> > > > > > >
...
> > >
> > > never existed in imx_rproc.c:
> >
> > AI refer old version code, but problem is the same
>
> No, sorry, the aforementioned piece of code never existed in imx_rproc.c
> according to git log. There is no old version of the code that looked
> anything like what the AI produced above.
>
> > if (strstarts(res.name, "vdev0buffer"))
> >
> > >
> > > "
> > > $ git log --follow -p next/master -- drivers/remoteproc/imx_rproc.c | grep
> > > vdev0vring1
> >    ^^^^^^^^^^
> >
> > vdev0buffer
>
> The AI generated review content above does refer to vdev0vring1 , which is a

No, AI talk about "vdev0buffer" at beginning, never said vdev0vring1 at all.

"   Looking at imx_rproc_prepare(), it iterates over memory-regions and checks
   specifically for the name "vdev0buffer" to skip processing the vdev buffer:
"

> unique identifier, but that unique identifier exists only once is the entire
> history of drivers/remoteproc/imx_rproc.c and that is as a code comment .
> That proves my point that the aforementioned AI generated review feedback is
> not based on code that ever existed in the kernel.
>
> > >      vdev regions are vdev0vring0, vdev0vring1, vdevbuffer and similar.
> > > "
> > >
> > > It seems the AI hallucinated something which is not based in reality ?
> >
> > git log --follow -p linux-next/master -- drivers/remoteproc/imx_rproc.c | grep vdev0buffer
> > -		if (!strcmp(it.node->name, "vdev0buffer"))
> > +		if (strstarts(res.name, "vdev0buffer"))
>
> "
> if (strstarts(res.name, "vdev0buffer"))
> "
>
> and
>
> "
> 	    strstarts(res.name, "vdev0buffer"))
> "
>
> looks like different code , and the AI reported "strstarts(res.name,
> "vdev0buffer"))" which never existed in drivers/remoteproc/imx_rproc.c as is
> clearly visible from the command output you shared above.
>
> So, what exactly is the problem here , can you please clarify it without
> referencing the AI generated content above ?

The problem is simple, node name should use

	vdevbuffer: vdev0buffer@b8400000
                        ^

Frank

>
> Thank you for your help !

  reply	other threads:[~2026-07-15 21:37 UTC|newest]

Thread overview: 21+ 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
2026-07-15 16:22             ` Frank Li
2026-07-15 16:38               ` Marek Vasut
2026-07-15 21:37                 ` Frank Li [this message]
2026-07-15 23:30                   ` Marek Vasut
2026-07-16 14:26                     ` Frank Li
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=alf9pp3c_zI4rwC0@SMW015318 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=marex@nabladev.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