From: sashiko-bot@kernel.org
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
dmaengine@vger.kernel.org, imx@lists.linux.dev, vkoul@kernel.org,
robh@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: dma: fsl,edma: add per-channel child node support
Date: Wed, 30 Sep 2026 06:34:34 +0000 [thread overview]
Message-ID: <20260930063434.93FF41F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930-edma-iommu-v2-1-72a62bf44c74@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: fsl,edma: missing required interrupts property validation
--
commit 4f1b5be8631d1a7b37208c50010390f6dfaf3925
Author: Peng Fan <peng.fan@nxp.com>
dt-bindings: dma: fsl,edma: add per-channel child node support
Add support for optional per-channel child nodes to the fsl,edma binding
to describe real per-channel MMIO regions. The interrupts property is
removed from the required list to accommodate these child nodes.
> diff --git a/Documentation/devicetree/bindings/dma/fsl,edma.yaml b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> index f609038e35ae1..19a103baccaf4 100644
> --- a/Documentation/devicetree/bindings/dma/fsl,edma.yaml
> +++ b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
[ ... ]
> +patternProperties:
> + "^dma-channel@[0-9a-f]+$":
> + type: object
> + additionalProperties: false
> +
> + properties:
> + reg:
> + maxItems: 1
> + description: Per-channel register region within the eDMA block.
> +
> + interrupts:
> + maxItems: 1
> +
> + iommus:
> + maxItems: 1
> +
> + power-domains:
> + maxItems: 1
> +
> + required:
> + - reg
[Severity: Medium]
Does this required list fail to enforce the interrupts property when the
new child node approach is used?
> required:
> - "#dma-cells"
> - compatible
> - reg
> - - interrupts
> - dma-channels
[Severity: Medium]
Does removing the interrupts property from the global required list break
schema validation for legacy device trees (e.g., fsl,vf610-edma or
fsl,imx7ulp-edma)?
Without this enforcement, invalid device trees that completely omit
interrupts might silently pass make dtbs_check. This could result in
incomplete device trees failing at runtime during driver probe. Is it
possible to preserve this in a conditional enforcement block for legacy
hardware instead of dropping it entirely?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930-edma-iommu-v2-0-72a62bf44c74@nxp.com?part=1
next prev parent reply other threads:[~2026-09-30 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 6:26 [PATCH v2 0/3] dmaengine: fsl-edma: per-channel IOMMU support via DT child nodes Peng Fan (OSS)
2026-09-30 6:26 ` [PATCH v2 1/3] dt-bindings: dma: fsl,edma: add per-channel child node support Peng Fan (OSS)
2026-09-30 6:34 ` sashiko-bot [this message]
2026-09-30 16:00 ` Frank Li
2026-09-30 6:26 ` [PATCH v2 2/3] dmaengine: fsl-edma: support per-channel DT child nodes Peng Fan (OSS)
2026-09-30 6:42 ` sashiko-bot
2026-09-30 6:26 ` [PATCH v2 3/3] arm64: dts: imx95: convert eDMA to per-channel " 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=20260930063434.93FF41F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=peng.fan@oss.nxp.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
/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