DMA Engine development
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: "Frank Li" <Frank.Li@nxp.com>, "Benoît Monin" <benoit.monin@bootlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Frank Li <Frank.Li@kernel.org>,
	imx@lists.linux.dev,  dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 0/2] dmaengine: fsl-edma: Scatter/gather improvements
Date: Mon, 05 Oct 2026 17:42:48 +0200	[thread overview]
Message-ID: <179121496809.358863.5036968996455847544.b4-ty@kernel.org> (raw)
In-Reply-To: <20260911-fsl-edma-dyn-sg-v10-0-700eb72def57@bootlin.com>


On Fri, 11 Sep 2026 15:11:35 +0200, Benoît Monin wrote:
> This series adds support for scatter/gather DMA transfers via dma_vec
> and dynamic descriptor chaining to the Freescale eDMA controller driver.
> 
> The first patch implements the .device_prep_peripheral_dma_vec() callback,
> enabling the DMA engine to accept an array of dma_vec structures. This
> callback supports both regular and cyclic transfer modes.
> 
> [...]

Applied, thanks!

[1/2] dmaengine: fsl-edma: Implement device_prep_peripheral_dma_vec
      commit: e2174129ddb293552ab7832439606848348f0370
[2/2] dmaengine: fsl-edma: Support dynamic scatter/gather chaining
      commit: 2c9f5e95f41898b506b132d7698d270ed6a13583

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2026-10-05 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 13:11 [PATCH v10 0/2] dmaengine: fsl-edma: Scatter/gather improvements Benoît Monin
2026-09-11 13:11 ` [PATCH v10 1/2] dmaengine: fsl-edma: Implement device_prep_peripheral_dma_vec Benoît Monin
2026-09-11 13:27   ` sashiko-bot
2026-09-11 13:11 ` [PATCH v10 2/2] dmaengine: fsl-edma: Support dynamic scatter/gather chaining Benoît Monin
2026-09-11 13:23   ` sashiko-bot
2026-09-11 14:14   ` Frank Li
2026-09-15 17:31 ` [PATCH v10 0/2] dmaengine: fsl-edma: Scatter/gather improvements Vinod Koul
2026-10-05 15:42 ` 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=179121496809.358863.5036968996455847544.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=benoit.monin@bootlin.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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