Re: [PATCH v2 0/3] spi: tegra210-quad: Fix timeout path status handling and DMA leak

[Mark Brown]

On Mon, 26 Oct 2026 11:14:09 +0000, Vishwaroop A wrote:
> spi: tegra210-quad: Fix timeout path status handling and DMA leak
> 
> Three fixes in the Tegra QSPI transfer timeout path: the two from v1, plus
> one new patch out of Mark's review.
> 
> Patch 1 fixes a regression from commit 1ff82c13ea94 ("spi: tegra210-quad:
> Cache TRANS_STATUS in ISR for timeout handler"), currently in linux-next
> only. When tegra_qspi_handle_timeout() observes a real ISR completion
> after draining the workqueue, it still publishes the pre-drain lost-IRQ
> FIFO snapshot. That snapshot can hold zeroed error bits if the ISR W1C-ed
> the hardware between the two reads, which makes the manual completion
> handler downstream accept a transfer that actually reported a FIFO
> underflow or overflow. No stable backport is needed because the offending
> commit has not been released.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: tegra210-quad: don't overwrite refreshed status with lost-IRQ snapshot
      https://git.kernel.org/broonie/spi/c/543a83912fed
[2/3] spi: tegra210-quad: Track DMA mapping state
      https://git.kernel.org/broonie/spi/c/7b9e6f7bc13c
[3/3] spi: tegra210-quad: Unmap DMA buffers on transfer timeout
      https://git.kernel.org/broonie/spi/c/d04ad85dd801

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