Re: [PATCH 0/5] spi: tegra114: chip-select fixes and PIO-only probe
From: Mark Brown
Date: Thu Nov 05 2026 - 08:46:07 EST
On Wed, 21 Oct 2026 10:14:06 +0000, Vishwaroop A wrote:
> spi: tegra114: chip-select fixes and PIO-only probe
>
> Tegra114 SPI sends each transfer as its own packet, and hardware CS
> follows that packet. The driver implements transfer_one_message(), so
> it has to do the per-transfer delay and cs_change itself. It gets
> both wrong.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.5
Thanks!
[1/5] spi: tegra114: Allow PIO fallback when DMA is unavailable
https://git.kernel.org/broonie/spi/c/04eebd439d91
[2/5] spi: tegra114: Run per-transfer delay before ending the transfer
https://git.kernel.org/broonie/spi/c/5b4ed7580ece
[3/5] spi: tegra114: Assert CS between transfers when cs_change is set
https://git.kernel.org/broonie/spi/c/679565d314db
[4/5] spi: tegra114: Decide the chip-select mode once per message
https://git.kernel.org/broonie/spi/c/d9dfcbf274d5
[5/5] spi: tegra114: Keep software CS across bus-locked messages
https://git.kernel.org/broonie/spi/c/881e4ef23286
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