From: sashiko-bot@kernel.org
To: "Golla Nagendra" <nagendra.golla@amd.com>
Cc: conor+dt@kernel.org, dmaengine@vger.kernel.org,
Frank.Li@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
vkoul@kernel.org
Subject: Re: [PATCH V3 4/6] dt-bindings: dma: xlnx,zynqmp-dma: Add Versal Net compatible support
Date: Mon, 10 Aug 2026 10:20:09 +0000 [thread overview]
Message-ID: <20260810102010.215D71F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260810100452.426320-5-nagendra.golla@amd.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Invalid fallback compatible string `xlnx,zynqmp-dma-1.0` for `amd,versal-net-dma-1.0`.
--
--- Patch [4]: [PATCH V3 4/6] dt-bindings: dma: xlnx,zynqmp-dma: Add Versal Net compatible support ---
commit c94f71cbb3b4d274afbe8968d6bb108158803292
Author: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
dt-bindings: dma: xlnx,zynqmp-dma: Add Versal Net compatible support
This commit introduces the amd,versal-net-dma-1.0 compatible string with a
fallback to xlnx,zynqmp-dma-1.0. It also adds a required per-channel reset
property for Versal Gen2 and Versal Net because the DMA channel must be
reset to clear the state left by firmware.
> diff --git a/Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml b/Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml
> index 2da86037ad79e..87c65aef5c7d3 100644
> --- a/Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml
> +++ b/Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml
[ ... ]
> @@ -18,15 +18,31 @@ maintainers:
> properties:
> "#dma-cells":
> const: 1
>
> compatible:
> - enum:
> - - amd,versal2-dma-1.0
> - - xlnx,zynqmp-dma-1.0
> + oneOf:
> + - const: amd,versal2-dma-1.0
> + - const: xlnx,zynqmp-dma-1.0
> + - items:
> + - const: amd,versal-net-dma-1.0
> + - const: xlnx,zynqmp-dma-1.0
[Severity: Medium]
Is this fallback compatible string appropriate here?
The commit message explicitly states that a DMA channel reset is essential
because the device is left in a bad state by firmware, and DMA functionality
fails without it.
If a device tree is parsed by an older OS using the fallback
xlnx,zynqmp-dma-1.0 driver, it will attempt to operate the hardware without
knowing about the new resets property. Since the older driver cannot perform
the required channel reset, won't the DMA functionality fail just as
described?
Should the fallback be removed if the older driver cannot reliably operate
the device?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260810100452.426320-1-nagendra.golla@amd.com?part=4
next prev parent reply other threads:[~2026-08-10 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 10:04 [PATCH V3 0/6] dmaengine: zynqmp_dma: Per-channel reset, IRQ guard improvements, and PM fixes Golla Nagendra
2026-08-10 10:04 ` [PATCH V3 1/6] dmaengine: zynqmp_dma: Fix PM usage count handling in probe error path Golla Nagendra
2026-08-10 10:28 ` sashiko-bot
2026-08-10 10:04 ` [PATCH V3 2/6] PM: runtime: Add pm_runtime_if_active guard and conditional variant Golla Nagendra
2026-08-10 10:25 ` sashiko-bot
2026-08-10 10:04 ` [PATCH V3 3/6] dmaengine: zynqmp_dma: Guard IRQ handler against spurious interrupts Golla Nagendra
2026-08-10 10:04 ` [PATCH V3 4/6] dt-bindings: dma: xlnx,zynqmp-dma: Add Versal Net compatible support Golla Nagendra
2026-08-10 10:20 ` sashiko-bot [this message]
2026-08-10 10:04 ` [PATCH V3 5/6] dmaengine: zynqmp_dma: Add new compatible string for Versal Net Golla Nagendra
2026-08-10 10:20 ` sashiko-bot
2026-08-10 10:04 ` [PATCH V3 6/6] dmaengine: zynqmp_dma: Add per-channel reset support Golla Nagendra
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=20260810102010.215D71F00A3A@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=nagendra.golla@amd.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 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.