From: Jon Hunter <jonathanh@nvidia.com>
To: Kartik Rajput <kkartik@nvidia.com>,
ldewangan@nvidia.com, akhilrajeev@nvidia.com, vkoul@kernel.org,
Frank.Li@kernel.org, thierry.reding@kernel.org, digetx@gmail.com,
pkunapuli@nvidia.com, dmaengine@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH RESEND] dmaengine: tegra: Fix burst size calculation
Date: Wed, 22 Apr 2026 10:26:47 +0100 [thread overview]
Message-ID: <98255b77-dcef-40c8-8851-91e723b82ea1@nvidia.com> (raw)
In-Reply-To: <20260422064134.1323610-1-kkartik@nvidia.com>
On 22/04/2026 07:41, Kartik Rajput wrote:
> Currently, the Tegra GPC DMA hardware requires the transfer length to
> be a multiple of the max burst size configured for the channel. When a
> client requests a transfer where the length is not evenly divisible by
> the configured max burst size, the DMA hangs with partial burst at
> the end.
>
> Fix this by reducing the burst size to the largest power-of-2 value
> that evenly divides the transfer length. For example, a 40-byte
> transfer with a 16-byte max burst will now use an 8-byte burst
> (40 / 8 = 5 complete bursts) instead of causing a hang.
>
> This issue was observed with the PL011 UART driver where TX DMA
> transfers of arbitrary lengths were stuck.
>
> Fixes: ee17028009d4 ("dmaengine: tegra: Add tegra gpcdma driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> drivers/dma/tegra186-gpc-dma.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/dma/tegra186-gpc-dma.c b/drivers/dma/tegra186-gpc-dma.c
> index 5948fbf32c21..0aa3a02b2277 100644
> --- a/drivers/dma/tegra186-gpc-dma.c
> +++ b/drivers/dma/tegra186-gpc-dma.c
> @@ -825,6 +825,13 @@ static unsigned int get_burst_size(struct tegra_dma_channel *tdc,
> * len to calculate the optimum burst size
> */
> burst_byte = burst_size ? burst_size * slave_bw : len;
> +
> + /*
> + * Find the largest burst size that evenly divides the transfer length.
> + * The hardware requires the transfer length to be a multiple of the
> + * burst size - partial bursts are not supported.
> + */
> + burst_byte = min(burst_byte, 1U << __ffs(len));
> burst_mmio_width = burst_byte / 4;
>
> if (burst_mmio_width < TEGRA_GPCDMA_MMIOSEQ_BURST_MIN)
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Thanks
Jon
--
nvpublic
prev parent reply other threads:[~2026-04-22 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 6:41 [PATCH RESEND] dmaengine: tegra: Fix burst size calculation Kartik Rajput
2026-04-22 9:26 ` Jon Hunter [this message]
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=98255b77-dcef-40c8-8851-91e723b82ea1@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=akhilrajeev@nvidia.com \
--cc=digetx@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=kkartik@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pkunapuli@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@kernel.org \
--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