| 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
| ||
|
Message-ID: <3385264.aeNJFYEL58@jernej-laptop> Date: Sun, 21 Dec 2025 16:57:07 +0100 From: Jernej Škrabec <jernej.skrabec@...il.com> To: Vinod Koul <vkoul@...nel.org>, Chen-Yu Tsai <wens@...nel.org>, 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 Dne nedelja, 21. december 2025 ob 09:04:48 Srednjeevropski standardni čas je Chen-Yu Tsai napisal(a): > 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. > > Signed-off-by: Chen-Yu Tsai <wens@...nel.org> Reviewed-by: Jernej Skrabec <jernej.skrabec@...il.com> Best regards, Jernej
Powered by blists - more mailing lists