public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: "Frank Li" <Frank.Li@nxp.com>, "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>,
	"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>
Subject: Re: [PATCH v3 9/9] crypto: atmel: Use dmaengine_prep_config_single() API
Date: Mon, 19 Jan 2026 10:26:39 +0100	[thread overview]
Message-ID: <bc019bd8-34d3-420e-8519-09700437fb01@microchip.com> (raw)
In-Reply-To: <20260105-dma_prep_config-v3-9-a8480362fd42@nxp.com>

On 05/01/2026 at 23:46, Frank Li wrote:
> Using new API dmaengine_prep_config_single() to simple code.
> 
> No functional change.
> 
> Tested-by: Niklas Cassel <cassel@kernel.org>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>

Looks good to me:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>

Thanks, best regards,
   Nicolas

> ---
>   drivers/crypto/atmel-aes.c | 10 +++-------
>   1 file changed, 3 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/crypto/atmel-aes.c b/drivers/crypto/atmel-aes.c
> index 3a2684208dda9ee45d71b4bc2958be293a4fb6fe..e300672ffd7185b0f5bf356c2376681537047def 100644
> --- a/drivers/crypto/atmel-aes.c
> +++ b/drivers/crypto/atmel-aes.c
> @@ -795,7 +795,6 @@ static int atmel_aes_dma_transfer_start(struct atmel_aes_dev *dd,
>          struct dma_slave_config config;
>          dma_async_tx_callback callback;
>          struct atmel_aes_dma *dma;
> -       int err;
> 
>          memset(&config, 0, sizeof(config));
>          config.src_addr_width = addr_width;
> @@ -820,12 +819,9 @@ static int atmel_aes_dma_transfer_start(struct atmel_aes_dev *dd,
>                  return -EINVAL;
>          }
> 
> -       err = dmaengine_slave_config(dma->chan, &config);
> -       if (err)
> -               return err;
> -
> -       desc = dmaengine_prep_slave_sg(dma->chan, dma->sg, dma->sg_len, dir,
> -                                      DMA_PREP_INTERRUPT | DMA_CTRL_ACK);
> +       desc = dmaengine_prep_config_sg(dma->chan, dma->sg, dma->sg_len, dir,
> +                                       DMA_PREP_INTERRUPT | DMA_CTRL_ACK,
> +                                       &config);
>          if (!desc)
>                  return -ENOMEM;
> 
> 
> --
> 2.34.1
> 



  reply	other threads:[~2026-01-19  9:27 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 [this message]
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
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=bc019bd8-34d3-420e-8519-09700437fb01@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=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=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=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