From: Conor Dooley <conor@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: Eugeniy.Paltsev@synopsys.com, vkoul@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: Re: [PATCH] dt-bindings: dma: snps,dw-axi-dmac: add dma-coherent property
Date: Mon, 2 Feb 2026 18:45:49 +0000 [thread overview]
Message-ID: <20260202-stylishly-chaffing-0aab46b244d8@spud> (raw)
In-Reply-To: <f5183a72-6ea4-4d68-b136-f6d83a36493d@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
On Sun, Feb 01, 2026 at 01:30:59PM -0600, Dinh Nguyen wrote:
>
>
> On 1/31/26 14:27, Conor Dooley wrote:
> > On Sat, Jan 31, 2026 at 11:28:56AM -0600, Dinh Nguyen wrote:
> > > 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>
> >
> > Why does this v1 have an ack?
> >
>
> I respun this patch based on the dmaengine tree so that the dma engine
> maintainer can take it. I had originally applied it to my tree, but avoid
> potential merge conflicts, I'm going to submit it through dma. This patch is
> the same as this[1].
In the future, please note this or carry on the version number from the
series it was originally in.
>
> Sorry for any confusion.
>
> Dinh
> [1] https://lore.kernel.org/linux-devicetree/176488420978.2206697.11201292177123636920.robh@kernel.org/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-02 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 17:28 Dinh Nguyen
2026-01-31 20:27 ` Conor Dooley
2026-02-01 19:30 ` Dinh Nguyen
2026-02-02 18:45 ` Conor Dooley [this message]
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=20260202-stylishly-chaffing-0aab46b244d8@spud \
--to=conor@kernel.org \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@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
all inboxes | Powered by JetHome®