From: Vinod Koul <vkoul@kernel.org>
To: lizhi.hou@amd.com, brian.xu@amd.com, raj.kumar.rampelli@amd.com,
michal.simek@amd.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, miquel.raynal@bootlin.com,
Jan Kuliga <jankul@alatek.krakow.pl>
Subject: Re: [PATCH v5 0/8] Miscellaneous xdma driver enhancements
Date: Thu, 21 Dec 2023 22:00:23 +0530 [thread overview]
Message-ID: <170317622335.683420.15291981209572271704.b4-ty@kernel.org> (raw)
In-Reply-To: <20231218113904.9071-1-jankul@alatek.krakow.pl>
On Mon, 18 Dec 2023 12:39:04 +0100, Jan Kuliga wrote:
> 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.
>
> [...]
Applied, thanks!
[1/8] dmaengine: xilinx: xdma: Get rid of unused code
commit: 6e2387183312cdfce6326b2626c0b801c2ffe686
[2/8] dmaengine: xilinx: xdma: Add necessary macro definitions
commit: 7a9c7f46bd0abea214d96f00f78622f24c798ad8
[3/8] dmaengine: xilinx: xdma: Ease dma_pool alignment requirements
commit: e5bc76b0e1c54906ca744ed1a7872f4f407d5d2e
[4/8] dmaengine: xilinx: xdma: Rework xdma_terminate_all()
commit: 2e142cebb1645ac18db1e66f0c30a8d720d00c0b
[5/8] dmaengine: xilinx: xdma: Add error checking in xdma_channel_isr()
commit: c38d055a7c021145ab3a07cf69992d287440c4cb
[6/8] dmaengine: xilinx: xdma: Add transfer error reporting
commit: c3fcb6f5575fcfd240baa339319d2a42d137cd8e
[7/8] dmaengine: xilinx: xdma: Prepare the introduction of interleaved DMA transfers
commit: fa88abfd0d03fea8b800ff1df4f161c804d24c8a
[8/8] dmaengine: xilinx: xdma: Implement interleaved DMA transfers
commit: 01e6d907656134949c4126e7fd64984d4daa4c1e
Best regards,
--
~Vinod
prev parent reply other threads:[~2023-12-21 16:30 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 ` [PATCH v5 0/8] Miscellaneous xdma driver enhancements Lizhi Hou
2023-12-21 16:30 ` Vinod Koul [this message]
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=170317622335.683420.15291981209572271704.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=brian.xu@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=jankul@alatek.krakow.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=michal.simek@amd.com \
--cc=miquel.raynal@bootlin.com \
--cc=raj.kumar.rampelli@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