From: Vinod Koul <vkoul@kernel.org>
To: Frank Li <Frank.Li@kernel.org>,
Michal Simek <michal.simek@amd.com>,
Kedareswara rao Appana <appana.durga.rao@xilinx.com>,
Alex Bereza <alex@bereza.email>
Cc: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order
Date: Thu, 10 Sep 2026 19:36:49 +0530 [thread overview]
Message-ID: <178904920902.109109.8238525405953023415.b4-ty@kernel.org> (raw)
In-Reply-To: <20260817-fix-hw-buf-desc-reuse-v1-1-d79827a844c7@bereza.email>
On Mon, 17 Aug 2026 11:23:55 +0200, Alex Bereza wrote:
> xilinx_dma_alloc_chan_resources() builds a static ring of hardware
> buffer descriptors once and the driver uses this ring throughout the
> lifetime of a channel. This requires the allocation order of hardware
> buffer descriptors from chan->free_seg_list to stay in sync with the
> hardware buffer descriptor ring built at channel allocation time by
> returning oldest descriptors to chan->free_seg_list first.
>
> [...]
Applied, thanks!
[1/1] dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order
commit: cee9c863ee68cb27d66745eb03f60e357f4f8ad2
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-09-10 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 9:23 [PATCH] dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order Alex Bereza
2026-08-17 13:47 ` Frank Li
2026-08-18 10:58 ` Pandey, Radhey Shyam
2026-08-18 12:11 ` Alex Bereza
2026-08-23 11:15 ` Gupta, Suraj
2026-09-10 14:06 ` 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=178904920902.109109.8238525405953023415.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=alex@bereza.email \
--cc=appana.durga.rao@xilinx.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@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