public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Khairul Anuar Romli <khairul.anuar.romli@altera.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
	Vinod Koul <vkoul@kernel.org>,
	dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] arm64: dts: intel: agilex5: Add simple-bus node on top of dma controller node
Date: Fri, 2 Jan 2026 07:52:20 -0600	[thread overview]
Message-ID: <e10dd345-01e6-4be7-bd9d-d0a464aa679e@kernel.org> (raw)
In-Reply-To: <ef6ed8338e54c02ed9508e91bdf120580e834e17.1766966955.git.khairul.anuar.romli@altera.com>



On 12/28/25 21:49, Khairul Anuar Romli wrote:
> Move dma-controller node under simple-bus node to allow bus node specific
> property able to be properly defined. This is require to fulfill Agilex5
> bus limitation that is limited to 40-addressable-bit.
> 
> Update the compatible string for the DMA controller nodes in the Agilex5
> device tree from the generic "snps,axi-dma-1.01a" to the platform-specific
> "altr,agilex5-axi-dma". Add fallback capability to ensure driver is able
> to initialize properly.
> 
> This change enables the use of platform-specific features and constraints
> in the driver, such as setting a 40-bit DMA addressable mask through
> dma-ranges, which is required for Agilex5. It also aligns with the updated
> device tree bindings and driver support for this compatible string.
> 
> Signed-off-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
> ---
> Changes in v5:
> 	- No changes.
> Changes in v4:
> 	- No changes.
> Changes in v3:
> 	- Rename the patch  "arm64: dts: intel: agilex5: Add dma-ranges, address
> 	  and size cells to dma node"
> 	- Add simple-bus and move dmac0 and dmac1 1 level down.
> Changes in v2:
> 	- Rename the from add platform specific to add dma-ranges, address
> 	  and size cells.
> 	- Define address-cells and size-cells for dmac0 and dmac1
> 	- Add dma-ranges for agilex5 for 40-bit
> ---
>   .../arm64/boot/dts/intel/socfpga_agilex5.dtsi | 78 ++++++++++---------
>   .../arm64/boot/dts/intel/socfpga_agilex5.dtsi | 78 ++++++++++---------
>   1 file changed, 43 insertions(+), 35 deletions(-)
> 

Applied!

Thanks,
Dinh

  reply	other threads:[~2026-01-02 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29  3:49 [PATCH v5 0/2] Add Agilex5 AXI DMA support 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 [this message]
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

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=e10dd345-01e6-4be7-bd9d-d0a464aa679e@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=Eugeniy.Paltsev@synopsys.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=khairul.anuar.romli@altera.com \
    --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