From: Dinh Nguyen <dinguyen@kernel.org>
To: adrianhoyin.ng@altera.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, Eugeniy.Paltsev@synopsys.com,
vkoul@kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Matthew Gerlach <matthew.gerlach@altrera.com>
Subject: Re: [PATCH v3 1/4] dt-bindings: dma: snps,dw-axi-dmac: Add iommus dma-coherent and dma-addressable-bits property
Date: Thu, 26 Jun 2025 07:19:28 -0500 [thread overview]
Message-ID: <e3ac4f22-e19c-407f-a448-c54b2ca34428@kernel.org> (raw)
In-Reply-To: <144d2070c7b2f69f034b6f16bc938a538afa9f15.1750084527.git.adrianhoyin.ng@altera.com>
On 6/16/25 09:40, adrianhoyin.ng@altera.com wrote:
> From: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
>
> Intel Agilex5 address bus only supports up to 40 bits. Add
> dma-addressable-bits property to allow configuration of number of dma
> addressable bits.Add iommu property for SMMU support. Add dma-coherent
> property for cache coherent support.
>
> Signed-off-by: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
> Reviewed-by: Matthew Gerlach <matthew.gerlach@altrera.com>
>
Add a '---' above to signify the version history..
Applies to all of your patches.
Dinh
next prev parent reply other threads:[~2025-06-26 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 14:40 [PATCH v3 0/4] agilex5: Update agilex5 device tree and device tree bindings adrianhoyin.ng
2025-06-16 14:40 ` [PATCH v3 1/4] dt-bindings: dma: snps,dw-axi-dmac: Add iommus dma-coherent and dma-addressable-bits property adrianhoyin.ng
2025-06-17 6:25 ` Krzysztof Kozlowski
2025-06-26 12:19 ` Dinh Nguyen [this message]
2025-06-16 14:40 ` [PATCH v3 2/4] dt-bindings: mtd: cadence: Add iommus and dma-coherent properties adrianhoyin.ng
2025-06-17 7:19 ` Krzysztof Kozlowski
2025-06-16 14:40 ` [PATCH v3 3/4] arm64: dts: socfpga: agilex5: Update Agilex5 DTSI and DTS adrianhoyin.ng
2025-06-16 14:40 ` [PATCH v3 4/4] dma: dw-axi-dmac: Add support for dma-bit-mask property adrianhoyin.ng
2025-06-20 7:15 ` 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=e3ac4f22-e19c-407f-a448-c54b2ca34428@kernel.org \
--to=dinguyen@kernel.org \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=adrianhoyin.ng@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=matthew.gerlach@altrera.com \
--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 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.