All of lore.kernel.org
 help / color / mirror / Atom feed
From: "han.xu" <han.xu@oss.nxp.com>
To: Frank.Li@oss.nxp.com
Cc: Han Xu <han.xu@nxp.com>, Haibo Chen <haibo.chen@nxp.com>,
	 Mark Brown <broonie@kernel.org>,
	"open list:NXP XSPI DRIVER" <linux-spi@vger.kernel.org>,
	 "open list:NXP XSPI DRIVER" <imx@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>,
	 Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH 1/1] spi: nxp-xspi: use dmaengine_get_copy_align() API
Date: Wed, 11 Nov 2026 16:06:15 -0600	[thread overview]
Message-ID: <avTmsgHPAi_SDonX@cozumel> (raw)
In-Reply-To: <20261111202741.3866239-1-Frank.Li@oss.nxp.com>

On 26/11/11 03:27PM, Frank.Li@oss.nxp.com wrote:
> From: Frank Li <Frank.Li@nxp.com>
> 
> Use the dmaengine_get_copy_align() API function instead of directly
> accessing rx->device->copy_align.
> 
> No functional change and prepare to move struct dma_device to private.
> 
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
>  drivers/spi/spi-nxp-xspi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/spi/spi-nxp-xspi.c b/drivers/spi/spi-nxp-xspi.c
> index e532b2da54835..e8383fed461e5 100644
> --- a/drivers/spi/spi-nxp-xspi.c
> +++ b/drivers/spi/spi-nxp-xspi.c
> @@ -824,7 +824,7 @@ static int nxp_xspi_dma_init(struct device *dev, struct nxp_xspi *xspi)
>  
>  	xspi->dma_rx = rx;
>  	init_completion(&xspi->dma_rx_c);
> -	xspi->dma_copy_align = 1 << rx->device->copy_align;
> +	xspi->dma_copy_align = 1 << dmaengine_get_copy_align(rx);

Acked-by: Han Xu <han.xu@nxp.com>

>  
>  	return 0;
>  }
> -- 
> 2.43.0
> 

  reply	other threads:[~2026-11-11 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 20:27 [PATCH 1/1] spi: nxp-xspi: use dmaengine_get_copy_align() API Frank.Li
2026-11-11 22:06 ` han.xu [this message]
2026-11-12  6:28 ` Daniel Baluta
2026-11-12 17:52 ` Mark Brown

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=avTmsgHPAi_SDonX@cozumel \
    --to=han.xu@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=Frank.Li@oss.nxp.com \
    --cc=broonie@kernel.org \
    --cc=haibo.chen@nxp.com \
    --cc=han.xu@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.