linux-kernel - Re: (subset) [PATCH 00/13] Add DMA support for RZ/T2H RSPI

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: <176580717199.161463.3915595459908387302.b4-ty@kernel.org>
Date: Mon, 15 Dec 2025 22:59:31 +0900
From: Mark Brown <broonie@...nel.org>
To: Fabrizio Castro <fabrizio.castro.jz@...esas.com>, 
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, 
 Geert Uytterhoeven <geert+renesas@...der.be>, 
 Magnus Damm <magnus.damm@...il.com>, Philipp Zabel <p.zabel@...gutronix.de>, 
 Cosmin Tanislav <cosmin-gabriel.tanislav.xa@...esas.com>
Cc: linux-spi@...r.kernel.org, linux-renesas-soc@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 00/13] Add DMA support for RZ/T2H RSPI

On Mon, 01 Dec 2025 15:42:16 +0200, Cosmin Tanislav wrote:
> The DMA controller can be used to transfer data to and from the SPI
> controller without involving the CPU for each word of a SPI transfer.
> 
> Add support for DMA mode, and do some other cleanups while touching the
> same code.
> 
> The dts changes in this series depend on the DMA series [1].
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[01/13] spi: rzv2h-rspi: fix rzv2h_rspi_transfer_one() indentation
        commit: fb0140774aff45b8dc326987cc1da89484ecb081
[02/13] spi: rzv2h-rspi: remove call to spi_finalize_current_transfer()
        commit: 9e4830b35dc0d522f45e1ec3ee5b1ff1648afe1b
[03/13] spi: rzv2h-rspi: do not set SPI_TRANS_FAIL_IO
        commit: 218917659df165cff72439480929e68a6e127b55
[04/13] spi: rzv2h-rspi: use device-managed APIs
        commit: b73ac782828f27c2217a17bd26aa8710769f032d
[05/13] spi: rzv2h-rspi: store RX interrupt in state
        commit: 28b590bd4c6a051ec61cf286a46a8b14846e6fcf
[06/13] spi: rzv2h-rspi: set MUST_RX/MUST_TX
        commit: 6f9026b5a18acdf190d1622831b100aacfca0eb3
[07/13] spi: rzv2h-rspi: set TX FIFO threshold to 0
        commit: a886baaaa6e12a9b7d5a9687d11d3b895f1b87c9
[08/13] spi: rzv2h-rspi: enable TX buffer empty interrupt
        commit: d49eea07de5851e1b8941ad6b6179be7ec36a986
[09/13] spi: rzv2h-rspi: split out PIO transfer
        commit: 1e5e10df8b9be71ca64435cbe7c96b189e5ee293
[10/13] dt-bindings: spi: renesas,rzv2h-rspi: document optional support for DMA
        commit: 163345e356722e98ba57cd120787d6e991da7b1d
[11/13] spi: rzv2h-rspi: add support for DMA mode
        commit: fa08b566860bca8ebf9300090b85174c34de7ca5

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark