From: Dinh Nguyen <dinguyen@kernel.org>
To: Eugeniy.Paltsev@synopsys.com, vkoul@kernel.org
Cc: dinguyen@kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Khairul Anuar Romli <khairul.anuar.romli@altera.com>,
Rob Herring <robh@kernel.org>
Subject: [PATCH] dt-bindings: dma: snps,dw-axi-dmac: add dma-coherent property
Date: Sat, 31 Jan 2026 11:28:56 -0600 [thread overview]
Message-ID: <20260131172856.29227-1-dinguyen@kernel.org> (raw)
From: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
The Synopsys DesignWare AXI DMA Controller on Agilex5, the controller
operates on a cache-coherent AXI interface, where DMA transactions are
automatically kept coherent with the CPU caches. In previous generations
SoC (Stratix10 and Agilex) the interconnect was non-coherent, hence there
is no need for dma-coherent property to be presence. In Agilex 5, the
architecture has changed. It introduced a coherent interconnect that
supports cache-coherent DMA.
Signed-off-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
---
Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml b/Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml
index 216cda21c538..e12a48a12ea4 100644
--- a/Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml
+++ b/Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml
@@ -68,6 +68,8 @@ properties:
dma-noncoherent: true
+ dma-coherent: true
+
resets:
minItems: 1
maxItems: 2
--
2.42.0.411.g813d9a9188
next reply other threads:[~2026-01-31 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 17:28 Dinh Nguyen [this message]
2026-01-31 20:27 ` [PATCH] dt-bindings: dma: snps,dw-axi-dmac: add dma-coherent property Conor Dooley
2026-02-01 19:30 ` Dinh Nguyen
2026-02-02 18:45 ` Conor Dooley
2026-02-25 11:24 ` Vinod Koul
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=20260131172856.29227-1-dinguyen@kernel.org \
--to=dinguyen@kernel.org \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=khairul.anuar.romli@altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--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