From: Jiri Slaby <jirislaby@kernel.org>
To: Thomas Fourier <fourier.thomas@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] pch_uart: Fix dma_sync_sg_for_device() nents value
Date: Mon, 30 Jun 2025 15:01:01 +0200 [thread overview]
Message-ID: <624ba0b2-afe0-4111-96b9-8b678b6472fe@kernel.org> (raw)
In-Reply-To: <20250630121021.106643-2-fourier.thomas@gmail.com>
On 30. 06. 25, 14:10, Thomas Fourier wrote:
> The dma_sync_sg_for_device() functions should be called with the same
> nents as the dma_map_sg(), not the value the map function returned.
Care to explain why do you intend to sync more than mapped? "should be
called" is way to vague.
> Fixes: da3564ee027e ("pch_uart: add multi-scatter processing")
> Signed-off-by: Thomas Fourier <fourier.thomas@gmail.com>
> ---
> drivers/tty/serial/pch_uart.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/pch_uart.c b/drivers/tty/serial/pch_uart.c
> index 508e8c6f01d4..884fefbfd5a1 100644
> --- a/drivers/tty/serial/pch_uart.c
> +++ b/drivers/tty/serial/pch_uart.c
> @@ -954,7 +954,7 @@ static unsigned int dma_handle_tx(struct eg20t_port *priv)
> __func__);
> return 0;
> }
> - dma_sync_sg_for_device(port->dev, priv->sg_tx_p, nent, DMA_TO_DEVICE);
> + dma_sync_sg_for_device(port->dev, priv->sg_tx_p, num, DMA_TO_DEVICE);
> priv->desc_tx = desc;
> desc->callback = pch_dma_tx_complete;
> desc->callback_param = priv;
--
js
suse labs
next prev parent reply other threads:[~2025-06-30 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 12:10 [PATCH v2] pch_uart: Fix dma_sync_sg_for_device() nents value Thomas Fourier
2025-06-30 12:49 ` Greg KH
2025-06-30 13:01 ` Jiri Slaby [this message]
2025-06-30 13:13 ` Andy Shevchenko
2025-07-01 5:15 ` Jiri Slaby
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=624ba0b2-afe0-4111-96b9-8b678b6472fe@kernel.org \
--to=jirislaby@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fourier.thomas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=tomoya-linux@dsn.okisemi.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