Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: "Benoît Monin" <benoit.monin@bootlin.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	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 RFC 2/2] dmaengine: fsl-edma: Support dynamic scatter/gather chaining
Date: Wed, 6 May 2026 10:48:02 -0400	[thread overview]
Message-ID: <aftUorBAXzTD1BBD@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <43uRGEDfSHihWPAxby2EOg@bootlin.com>

On Wed, May 06, 2026 at 04:01:37PM +0200, Benoît Monin wrote:
> On Tuesday, 5 May 2026 at 17:07:48 CEST, Frank Li wrote:
> > > >         how do you test it? and how much preformance improved?
> > > I did my tests by doing SPI transfers with the LPSPI controllers, doing DMA
> > > transactions with different number of buffers and different buffer sizes.
> > > Without chaining, interruptions on the SPI bus occur between each DMA
> > > transaction. With chaining, the activity on the SPI bus is continuous as
> > > long as DMA transactions are issued before the end of the current
> > > transaction.
> >
> > Does SPI support issue new transfers without wait for previous transfer
> > complete, or SPI transfer already support async queue?
> >
> This is done with a local version of fsl-lpspi driver adding a simple
> offload support by borrowing the DMA channels allocated to the SPI
> controller. I can then issue multiple DMA transactions with the dma_buf API
> of the IIO subsystem and trigger SG chaining.

Can you include these patches to reference?

Frank
>
> Best regards,
> --
> Benoît Monin, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
>

  reply	other threads:[~2026-05-06 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  9:49 [PATCH RFC 0/2] dmaengine: fsl-edma: Scatter/gather improvements Benoît Monin
2026-04-30  9:49 ` [PATCH RFC 1/2] dmaengine: fsl-edma: Implement device_prep_peripheral_dma_vec Benoît Monin
2026-05-04 15:58   ` Frank Li
2026-05-05 13:51     ` Benoît Monin
2026-04-30  9:49 ` [PATCH RFC 2/2] dmaengine: fsl-edma: Support dynamic scatter/gather chaining Benoît Monin
2026-05-04 16:04   ` Frank Li
2026-05-05 13:51     ` Benoît Monin
2026-05-05 15:07       ` Frank Li
2026-05-06 14:01         ` Benoît Monin
2026-05-06 14:48           ` Frank Li [this message]
2026-05-07 14:15             ` Benoît Monin

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=aftUorBAXzTD1BBD@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=Frank.Li@kernel.org \
    --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 \
    --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