From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev, robh@kernel.org,
conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: remoteproc: imx_rproc: document memory-region-names to avoid hidden ABI
Date: Thu, 15 Oct 2026 14:49:34 +0000 [thread overview]
Message-ID: <sashiko-outbox-172996@kernel.org> (raw)
In-Reply-To: <20261015-memory-region-name-v5-1-abc358b39a96@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: imx-rproc: strict regex rejects valid memory-region-names
--
commit 6408464abda5d8740cc2d4f521608bce19b964e6
Author: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
dt-bindings: remoteproc: imx_rproc: document memory-region-names to avoid hidden ABI
Document the optional memory-region-names property explicitly to identify the
expected memory regions. This avoids relying on memory node names as a hidden
DT ABI, which previously allowed incorrect names to silently pass validation.
Link: https://lore.kernel.org/imx/a3602ef8-2b77-4cc3-adef-2c4cba08a5d9@nabladev.com/ [1]
Link: https://lore.kernel.org/imx/alexXTYQHUs76J7v@SMW015318/T/#mb9dc709ff3adc24d9db6d30c973f37b580f6f1f9 [2]
> diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> index c18f71b648890..f87036299a7b6 100644
> --- a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> @@ -62,6 +62,15 @@ properties:
> minItems: 1
> maxItems: 32
>
> + memory-region-names:
> + minItems: 1
> + maxItems: 32
> + items:
> + anyOf:
> + - const: rsc-table
> + - pattern: "^vdev[0-9]+(buffer|vring[0-9]+)$"
> + - pattern: "^m(4|7|33)-reserved(-[a-z0-9-]+)+$"
[Severity: Low]
Does this regular expression structurally exclude the valid base names
themselves?
Because of the + quantifier at the end of the pattern, it requires at least
one suffix. If a device tree author attempts to add memory-region-names =
"m7-reserved" to match an existing node label like m7_reserved (e.g., in
imx95-19x19-evk.dts), dtbs_check will throw a validation error.
Should the + be changed to * to allow "m4-reserved", "m7-reserved", and
"m33-reserved" without requiring a suffix?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261015-memory-region-name-v5-0-abc358b39a96@nxp.com?part=1
next prev parent reply other threads:[~2026-10-15 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 14:39 [PATCH v5 0/3] remoteproc: imx_rpoc: use memory-region-names to avoid hidden ABI Frank.Li
2026-10-15 14:39 ` [PATCH v5 1/3] dt-bindings: remoteproc: imx_rproc: document " Frank.Li
2026-10-15 14:49 ` sashiko-bot [this message]
2026-10-15 20:08 ` Rob Herring (Arm)
2026-10-15 14:39 ` [PATCH v5 2/3] remoteproc: imx_rpoc: use " Frank.Li
2026-10-15 20:26 ` Francesco Valla
2026-10-15 21:22 ` Frank Li
2026-10-15 14:39 ` [PATCH v5 3/3] arm64: dts: freescale: add DT overlay for MX95-15x15-FRDM RPMSG usage Frank.Li
2026-10-15 14:47 ` 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=sashiko-outbox-172996@kernel.org \
--to=sashiko-bot@kernel.org \
--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