Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: "Vinod Koul" <vkoul@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Christoph Hellwig" <hch@lst.de>,
	"Sagi Grimberg" <sagi@grimberg.me>,
	"Chaitanya Kulkarni" <kch@nvidia.com>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	"Nicolas Ferre" <nicolas.ferre@microchip.com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
	"Koichiro Den" <den@valinux.co.jp>,
	"Niklas Cassel" <cassel@kernel.org>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org,
	mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
	linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
	Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v3 0/9] dmaengine: Add new API to combine configuration and descriptor preparation
Date: Fri, 30 Jan 2026 14:19:58 -0500	[thread overview]
Message-ID: <aX0EXjM4LlO3Hygd@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <aXD/EYqhhRJEN8oy@lizhi-Precision-Tower-5810>

On Wed, Jan 21, 2026 at 11:30:09AM -0500, Frank Li wrote:
> On Mon, Jan 05, 2026 at 05:46:50PM -0500, Frank Li wrote:
> > Previously, configuration and preparation required two separate calls. This
> > works well when configuration is done only once during initialization.
> >
> > However, in cases where the burst length or source/destination address must
> > be adjusted for each transfer, calling two functions is verbose.
> >
> > 	if (dmaengine_slave_config(chan, &sconf)) {
> > 		dev_err(dev, "DMA slave config fail\n");
> > 		return -EIO;
> > 	}
> >
> > 	tx = dmaengine_prep_slave_single(chan, dma_local, len, dir, flags);
> >
> > After new API added
> >
> > 	tx = dmaengine_prep_config_single(chan, dma_local, len, dir, flags, &sconf);
> >
> > Additional, prevous two calls requires additional locking to ensure both
> > steps complete atomically.
> >
> >     mutex_lock()
> >     dmaengine_slave_config()
> >     dmaengine_prep_slave_single()
> >     mutex_unlock()
> >
> > after new API added, mutex lock can be moved. See patch
> >      nvmet: pci-epf: Use dmaengine_prep_config_single_safe() API
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
>
> Vinod:
> 	Can you take care these patches? At least first 2 patches! So
> I can did more clean up at next kernel release.

Vinod Koul:

	Do you have chance to pick up (at least first 2 patches) for 6.20?
So I can start do more cleanup work.

	There are two serial depend on this one

https://lore.kernel.org/dmaengine/20251212-edma_ll-v1-0-fc863d9f5ca3@nxp.com/
https://lore.kernel.org/dmaengine/aWT4p7RnFykJnuOz@ryzen/

Frank

>
> Frank
>
> > Changes in v3:
> > - collect review tags
> > - create safe version in framework
> > - Link to v2: https://lore.kernel.org/r/20251218-dma_prep_config-v2-0-c07079836128@nxp.com
> >
> > Changes in v2:
> > - Use name dmaengine_prep_config_single() and dmaengine_prep_config_sg()
> > - Add _safe version to avoid confuse, which needn't additional mutex.
> > - Update document/
> > - Update commit message. add () for function name. Use upcase for subject.
> > - Add more explain for remove lock.
> > - Link to v1: https://lore.kernel.org/r/20251208-dma_prep_config-v1-0-53490c5e1e2a@nxp.com
> >
> > ---
> > Frank Li (9):
> >       dmaengine: Add API to combine configuration and preparation (sg and single)
> >       dmaengine: Add safe API to combine configuration and preparation
> >       PCI: endpoint: pci-epf-test: Use dmaenigne_prep_config_single() to simplify code
> >       dmaengine: dw-edma: Use new .device_prep_config_sg() callback
> >       dmaengine: dw-edma: Pass dma_slave_config to dw_edma_device_transfer()
> >       nvmet: pci-epf: Remove unnecessary dmaengine_terminate_sync() on each DMA transfer
> >       nvmet: pci-epf: Use dmaengine_prep_config_single_safe() API
> >       PCI: epf-mhi: Use dmaengine_prep_config_single() to simplify code
> >       crypto: atmel: Use dmaengine_prep_config_single() API
> >
> >  Documentation/driver-api/dmaengine/client.rst |   9 ++
> >  drivers/crypto/atmel-aes.c                    |  10 +--
> >  drivers/dma/dmaengine.c                       |   3 +
> >  drivers/dma/dw-edma/dw-edma-core.c            |  41 ++++++---
> >  drivers/nvme/target/pci-epf.c                 |  21 ++---
> >  drivers/pci/endpoint/functions/pci-epf-mhi.c  |  52 ++++--------
> >  drivers/pci/endpoint/functions/pci-epf-test.c |   8 +-
> >  include/linux/dmaengine.h                     | 117 ++++++++++++++++++++++++--
> >  8 files changed, 177 insertions(+), 84 deletions(-)
> > ---
> > base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
> > change-id: 20251204-dma_prep_config-654170d245a2
> >
> > Best regards,
> > --
> > Frank Li <Frank.Li@nxp.com>
> >


  reply	other threads:[~2026-01-30 19:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 22:46 [PATCH v3 0/9] dmaengine: Add new API to combine configuration and descriptor preparation Frank Li
2026-01-05 22:46 ` [PATCH v3 1/9] dmaengine: Add API to combine configuration and preparation (sg and single) Frank Li
2026-01-05 22:46 ` [PATCH v3 2/9] dmaengine: Add safe API to combine configuration and preparation Frank Li
2026-01-05 22:46 ` [PATCH v3 3/9] PCI: endpoint: pci-epf-test: Use dmaenigne_prep_config_single() to simplify code Frank Li
2026-01-17 10:57   ` Manivannan Sadhasivam
2026-01-05 22:46 ` [PATCH v3 4/9] dmaengine: dw-edma: Use new .device_prep_config_sg() callback Frank Li
2026-01-05 22:46 ` [PATCH v3 5/9] dmaengine: dw-edma: Pass dma_slave_config to dw_edma_device_transfer() Frank Li
2026-01-05 22:46 ` [PATCH v3 6/9] nvmet: pci-epf: Remove unnecessary dmaengine_terminate_sync() on each DMA transfer Frank Li
2026-01-05 22:46 ` [PATCH v3 7/9] nvmet: pci-epf: Use dmaengine_prep_config_single_safe() API Frank Li
2026-01-05 22:46 ` [PATCH v3 8/9] PCI: epf-mhi: Use dmaengine_prep_config_single() to simplify code Frank Li
2026-01-17 11:03   ` Manivannan Sadhasivam
2026-01-05 22:46 ` [PATCH v3 9/9] crypto: atmel: Use dmaengine_prep_config_single() API Frank Li
2026-01-19  9:26   ` Nicolas Ferre
2026-01-12 13:01 ` [PATCH v3 0/9] dmaengine: Add new API to combine configuration and descriptor preparation Niklas Cassel
2026-01-17 11:05   ` Manivannan Sadhasivam
2026-01-21 16:30 ` Frank Li
2026-01-30 19:19   ` Frank Li [this message]
2026-02-25 22:49     ` Niklas Cassel

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=aX0EXjM4LlO3Hygd@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=davem@davemloft.net \
    --cc=den@valinux.co.jp \
    --cc=dlemoal@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=imx@lists.linux.dev \
    --cc=kch@nvidia.com \
    --cc=kishon@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=mhi@lists.linux.dev \
    --cc=nicolas.ferre@microchip.com \
    --cc=sagi@grimberg.me \
    --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