From: "Romli, Khairul Anuar" <khairul.anuar.romli@altera.com>
To: Vinod Koul <vkoul@kernel.org>, Dinh Nguyen <dinguyen@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: (subset) [PATCH v5 0/2] Add Agilex5 AXI DMA support
Date: Thu, 1 Jan 2026 23:20:59 +0000 [thread overview]
Message-ID: <7fc74327-a589-462c-91eb-53475c60eb59@altera.com> (raw)
In-Reply-To: <176728930288.239406.12362948217259379016.b4-ty@kernel.org>
On 2/1/2026 1:41 am, Vinod Koul wrote:
>
> On Mon, 29 Dec 2025 11:49:00 +0800, Khairul Anuar Romli wrote:
>> This series introduces support for Agilex5 SoC in the Synopsys DesignWare
>> AXI DMA binding and updates the device tree to use the platform-specific
>> compatible string.
>>
>> The Agilex5 only has 40-bit DMA addressable bit instead of 64-bit. Hence,
>> this specific addition will enable driver to handle this limitation.
>>
>> [...]
>
> Applied, thanks!
>
> [1/2] dt-bindings: dma: snps,dw-axi-dmac: Add compatible string for Agilex5
> commit: 0a6946644f0d1151d31212820497e1a49fe1a0a6
>
> Best regards,
Thank you so much for getting this patch series reviewed and accepted.
Regards,
Khairul
prev parent reply other threads:[~2026-01-01 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 3:49 Khairul Anuar Romli
2025-12-29 3:49 ` [PATCH v5 1/2] dt-bindings: dma: snps,dw-axi-dmac: Add compatible string for Agilex5 Khairul Anuar Romli
2025-12-30 18:02 ` Rob Herring (Arm)
2025-12-29 3:49 ` [PATCH v5 2/2] arm64: dts: intel: agilex5: Add simple-bus node on top of dma controller node Khairul Anuar Romli
2026-01-02 13:52 ` Dinh Nguyen
2026-01-01 17:41 ` (subset) [PATCH v5 0/2] Add Agilex5 AXI DMA support Vinod Koul
2026-01-01 23:20 ` Romli, Khairul Anuar [this message]
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=7fc74327-a589-462c-91eb-53475c60eb59@altera.com \
--to=khairul.anuar.romli@altera.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--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®