From: Vinod Koul <vkoul@kernel.org>
To: Lizhi Hou <lizhi.hou@amd.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
nishad.saraf@amd.com, sonal.santan@amd.com, max.zhen@amd.com
Subject: Re: [PATCH V5 0/1] AMD QDMA driver
Date: Thu, 28 Sep 2023 16:35:07 +0530 [thread overview]
Message-ID: <ZRVd4yodNiwhqO9R@matsya> (raw)
In-Reply-To: <1695402939-28924-1-git-send-email-lizhi.hou@amd.com>
On 22-09-23, 10:15, Lizhi Hou wrote:
> Hello,
>
> The QDMA subsystem is used in conjunction with the PCI Express IP block
> to provide high performance data transfer between host memory and the
> card's DMA subsystem.
>
> +-------+ +-------+ +-----------+
> PCIe | | | | | |
> Tx/Rx | | | | AXI | |
> <=======> | PCIE | <===> | QDMA | <====>| User Logic|
> | | | | | |
> +-------+ +-------+ +-----------+
This should be in patch description as well
>
> Comparing to AMD/Xilinx XDMA subsystem,
> https://lore.kernel.org/lkml/Y+XeKt5yPr1nGGaq@matsya/
> the QDMA subsystem is a queue based, configurable scatter-gather DMA
> implementation which provides thousands of queues, support for multiple
> physical/virtual functions with single-root I/O virtualization (SR-IOV),
> and advanced interrupt support. In this mode the IP provides AXI4-MM and
> AXI4-Stream user interfaces which may be configured on a per-queue basis.
>
> The QDMA has been used for Xilinx Alveo PCIe devices.
> https://www.xilinx.com/applications/data-center/v70.html
>
> This patch series is to provide the platform driver for AMD QDMA subsystem
> to support AXI4-MM DMA transfers. More functions, such as AXI4-Stream
> and SR-IOV, will be supported by future patches.
>
> The device driver for any FPGA based PCIe device which leverages QDMA can
> call the standard dmaengine APIs to discover and use the QDMA subsystem
> without duplicating the QDMA driver code in its own driver.
>
> Changes since v4:
> - Convert to use platform driver callback .remove_new()
>
> Changes since v3:
> - Minor changes in Kconfig description.
>
> Changes since v2:
> - A minor change from code review comments.
>
> Changes since v1:
> - Minor changes from code review comments.
> - Fixed kernel robot warning.
>
> Nishad Saraf (1):
> dmaengine: amd: qdma: Add AMD QDMA driver
>
> MAINTAINERS | 9 +
> drivers/dma/Kconfig | 13 +
> drivers/dma/Makefile | 1 +
> drivers/dma/amd/Makefile | 8 +
> drivers/dma/amd/qdma-comm-regs.c | 66 ++
> drivers/dma/amd/qdma.c | 1187 ++++++++++++++++++++++++
> drivers/dma/amd/qdma.h | 269 ++++++
> include/linux/platform_data/amd_qdma.h | 36 +
> 8 files changed, 1589 insertions(+)
> create mode 100644 drivers/dma/amd/Makefile
> create mode 100644 drivers/dma/amd/qdma-comm-regs.c
> create mode 100644 drivers/dma/amd/qdma.c
> create mode 100644 drivers/dma/amd/qdma.h
> create mode 100644 include/linux/platform_data/amd_qdma.h
>
> --
> 2.34.1
--
~Vinod
next prev parent reply other threads:[~2023-09-28 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 17:15 [PATCH V5 0/1] AMD QDMA driver Lizhi Hou
2023-09-22 17:15 ` [PATCH V5 1/1] dmaengine: amd: qdma: Add " Lizhi Hou
2023-09-28 11:05 ` Vinod Koul [this message]
2023-09-29 15:24 ` [PATCH V5 0/1] " Lizhi Hou
2023-10-25 15:18 ` Lizhi Hou
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=ZRVd4yodNiwhqO9R@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=max.zhen@amd.com \
--cc=nishad.saraf@amd.com \
--cc=sonal.santan@amd.com \
/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