linux-kernel - Re: [PATCH] dmaengine: sun6i: Choose appropriate burst length under maxburst

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176648929819.697163.12733277039569161505.b4-ty@kernel.org>
Date: Tue, 23 Dec 2025 16:58:18 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Jernej Skrabec <jernej@...nel.org>, 
 Samuel Holland <samuel@...lland.org>, Chen-Yu Tsai <wens@...nel.org>
Cc: Andre Przywara <andre.przywara@....com>, dmaengine@...r.kernel.org, 
 linux-sunxi@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dmaengine: sun6i: Choose appropriate burst length
 under maxburst


On Sun, 21 Dec 2025 16:04:48 +0800, Chen-Yu Tsai wrote:
> maxburst, as provided by the client, specifies the largest amount of
> data that is allowed to be transferred in one burst. This limit is
> normally provided to avoid a data burst overflowing the target FIFO.
> It does not mean that the DMA engine can only do bursts in that size.
> 
> Let the driver pick the largest supported burst length within the
> given limit. This lets the driver work correctly with some clients that
> give a large maxburst value. In particular, the 8250_dw driver will give
> a quarter of the UART's FIFO size as maxburst. On some systems the FIFO
> size is 256 bytes, giving a maxburst of 64 bytes, while the hardware
> only supports bursts of up to 16 bytes.
> 
> [...]

Applied, thanks!

[1/1] dmaengine: sun6i: Choose appropriate burst length under maxburst
      commit: 7178c3586ab42693b28bb81014320a7783e5c435

Best regards,
-- 
~Vinod