From: Krzysztof Kozlowski <krzk@kernel.org>
To: Abin Joseph <abin.joseph@amd.com>,
vkoul@kernel.org, michal.simek@amd.com, robh@kernel.org,
u.kleine-koenig@pengutronix.de, krzk+dt@kernel.org,
conor+dt@kernel.org, radhey.shyam.pandey@amd.com,
harini.katakam@amd.com
Cc: git@amd.com, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: dmaengine: zynqmp_dma: Add a new compatible string
Date: Fri, 26 Jul 2024 11:13:21 +0200 [thread overview]
Message-ID: <c36db187-0779-4424-b3e9-2b96c4076d29@kernel.org> (raw)
In-Reply-To: <20240726062639.2609974-2-abin.joseph@amd.com>
On 26/07/2024 08:26, Abin Joseph wrote:
> Add compatible string "amd,versal2-dma-1.0" to support AMD Versal Gen 2
> platform.
>
> AMD Versal Gen 2 has 8 LPD DMA IPs in PS that can be used as general
> purpose DMAs which is designed to support memory to memory and memory to
> IO buffer transfer. Versal Gen 2 DMA IP has different interrupt register
> offset. Add example binding documentation for the newly added compatible
> string.
>
> Signed-off-by: Abin Joseph <abin.joseph@amd.com>
> ---
> .../dma/xilinx/xlnx,zynqmp-dma-1.0.yaml | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml b/Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml
> index 769ce23aaac2..17f16ae7e42b 100644
> --- a/Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml
> +++ b/Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dma-1.0.yaml
> @@ -24,7 +24,9 @@ properties:
> const: 1
>
> compatible:
> - const: xlnx,zynqmp-dma-1.0
> + enum:
> + - xlnx,zynqmp-dma-1.0
> + - amd,versal2-dma-1.0
Keep the list ordered.
>
> reg:
> description: memory map for gdma/adma module access
> @@ -74,6 +76,7 @@ additionalProperties: false
> examples:
> - |
> #include <dt-bindings/clock/xlnx-zynqmp-clk.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>
> fpd_dma_chan1: dma-controller@fd500000 {
> compatible = "xlnx,zynqmp-dma-1.0";
> @@ -86,3 +89,15 @@ examples:
> xlnx,bus-width = <128>;
> dma-coherent;
> };
> +
> + fpd_dma_chan2: dma-controller@ebd00000 {
That's the same example. Xilinx already received such comments, so
finally please learn them. Drop the example.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-26 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 6:26 [PATCH 0/2] Add support for ADMA Abin Joseph
2024-07-26 6:26 ` [PATCH 1/2] dt-bindings: dmaengine: zynqmp_dma: Add a new compatible string Abin Joseph
2024-07-26 9:13 ` Krzysztof Kozlowski [this message]
2024-07-26 6:26 ` [PATCH 2/2] dmaengine: zynqmp_dma: Add support for AMD Versal Gen 2 DMA IP Abin Joseph
2024-07-26 9:12 ` Krzysztof Kozlowski
2024-08-05 16:53 ` 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=c36db187-0779-4424-b3e9-2b96c4076d29@kernel.org \
--to=krzk@kernel.org \
--cc=abin.joseph@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).