From: Lizhi Hou <lizhi.hou@amd.com>
To: Jan Kuliga <jankul@alatek.krakow.pl>, <brian.xu@amd.com>,
<raj.kumar.rampelli@amd.com>, <vkoul@kernel.org>,
<michal.simek@amd.com>, <dmaengine@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v5 0/8] Miscellaneous xdma driver enhancements
Date: Wed, 20 Dec 2023 10:50:48 -0800 [thread overview]
Message-ID: <bce801b2-b2a1-8014-a84d-87a18460cd1b@amd.com> (raw)
In-Reply-To: <20231218113904.9071-1-jankul@alatek.krakow.pl>
Verified this patch series with our device (sg interface)
Thanks,
Lizhi
On 12/18/23 03:39, Jan Kuliga wrote:
> Hi,
>
> This patchset introduces a couple of xdma driver enhancements. The most
> important change is the introduction of interleaved DMA transfers
> feature, which is a big deal, as it allows DMAEngine clients to express
> DMA transfers in an arbitrary way. This is extremely useful in FPGA
> environments, where in one FPGA system there may be a need to do DMA both
> to/from FIFO at a fixed address and to/from a (non)contiguous RAM.
>
> It is a another reroll of my previous patch series [1], but it is heavily
> modified one as it is based on Miquel's patchset [2]. We agreed on doing
> it that way, as both our patchsets touched the very same piece of code.
> The discussion took place under [2] thread.
>
> I tested it with XDMA v4.1 (Rev.20) IP core, with both sg and
> interleaved DMA transfers.
>
> Jan
>
> Changes since v1:
> [PATCH 1/5]:
> Complete a terminated descriptor with dma_cookie_complete()
> Don't reinitialize temporary list head in xdma_terminate_all()
> [PATCH 4/5]:
> Fix incorrect text wrapping
>
> Changes since v2:
> [PATCH 1/5]:
> DO NOT schedule callback from within xdma_terminate_all()
>
> Changes since v3:
> Base patchset on Miquel's [2] series
> Reorganize commits` structure
> Introduce interleaved DMA transfers feature
> Implement transfer error reporting
>
> Changes since v4:
> Get rid of duplicated line of code
> Fix various coding style issues
>
> [1]:
> https://lore.kernel.org/dmaengine/20231124192524.134989-1-jankul@alatek.krakow.pl/T/#t
>
> [2]:
> https://lore.kernel.org/dmaengine/20231130111315.729430-1-miquel.raynal@bootlin.com/T/#t
>
> ---
> Jan Kuliga (8):
> dmaengine: xilinx: xdma: Get rid of unused code
> dmaengine: xilinx: xdma: Add necessary macro definitions
> dmaengine: xilinx: xdma: Ease dma_pool alignment requirements
> dmaengine: xilinx: xdma: Rework xdma_terminate_all()
> dmaengine: xilinx: xdma: Add error checking in xdma_channel_isr()
> dmaengine: xilinx: xdma: Add transfer error reporting
> dmaengine: xilinx: xdma: Prepare the introduction of interleaved DMA
> transfers
> dmaengine: xilinx: xdma: Implement interleaved DMA transfers
>
> drivers/dma/xilinx/xdma-regs.h | 30 ++--
> drivers/dma/xilinx/xdma.c | 283 +++++++++++++++++++++++----------
> 2 files changed, 210 insertions(+), 103 deletions(-)
>
next prev parent reply other threads:[~2023-12-20 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 11:39 [PATCH v5 0/8] Miscellaneous xdma driver enhancements Jan Kuliga
2023-12-18 11:39 ` [PATCH v5 1/8] dmaengine: xilinx: xdma: Get rid of unused code Jan Kuliga
2023-12-18 11:39 ` [PATCH v5 2/8] dmaengine: xilinx: xdma: Add necessary macro definitions Jan Kuliga
2023-12-18 11:39 ` [PATCH v5 3/8] dmaengine: xilinx: xdma: Ease dma_pool alignment requirements Jan Kuliga
2023-12-18 11:39 ` [PATCH v5 4/8] dmaengine: xilinx: xdma: Rework xdma_terminate_all() Jan Kuliga
2023-12-18 11:39 ` [PATCH v5 5/8] dmaengine: xilinx: xdma: Add error checking in xdma_channel_isr() Jan Kuliga
2023-12-18 11:39 ` [PATCH v5 6/8] dmaengine: xilinx: xdma: Add transfer error reporting Jan Kuliga
2023-12-18 11:39 ` [PATCH v5 7/8] dmaengine: xilinx: xdma: Prepare the introduction of interleaved DMA transfers Jan Kuliga
2023-12-18 11:39 ` [PATCH v5 8/8] dmaengine: xilinx: xdma: Implement " Jan Kuliga
2023-12-20 18:50 ` Lizhi Hou [this message]
2023-12-21 16:30 ` [PATCH v5 0/8] Miscellaneous xdma driver enhancements 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=bce801b2-b2a1-8014-a84d-87a18460cd1b@amd.com \
--to=lizhi.hou@amd.com \
--cc=brian.xu@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=jankul@alatek.krakow.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=miquel.raynal@bootlin.com \
--cc=raj.kumar.rampelli@amd.com \
--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