spi: orion: yield to scheduler in transfer wait loop
PATCH 1/1 spi: orion: yield to scheduler in transfer wait loop
orion_spi_wait_till_ready() busy-waits in a tight udelay(1) loop, up to 2000 iterations, and is called per byte from the polled, byte-at-a-time transfer path. On SoCs such as the Armada 388 (e.g. SolidRun Helios4), which also run SATA over the shared internal MBus fabric, this stalls the CPU for the whole transfer and delays servicing of SATA interrupts. Under sustained activity this can cause SATA timeouts and link resets (sometimes renegotiating down to SATA II, 3 Gbps).
Add cond_resched() to the wait loop so the scheduler can run pending IRQs between polls. This is a no-op at runtime unless the kernel is built with CONFIG_PREEMPT enabled, where it lets other peripheral interrupts be serviced during SPI transfers.
Built with LLVM=1 ARCH=powerpc; passes checkpatch --strict.
--- drivers/spi/spi-orion.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/spi/spi-orion.c +9 -0
@@ -370,7 +370,16 @@ static inline int orion_spi_wait_till_ready(struct orion_spi *orion_spi)if (readl (spi_reg (orion_spi,ORION_SPI_INT_CAUSE_REG )))return 1 ; +/* +* This is a polled, byte-at-a-time transfer loop. Each +* iteration busy-waits in a tight udelay() loop, which can +* starve other time-sensitive peripherals (e.g. SATA) of CPU +* time and interfere with them if they run on this SoC. +* Yield to the scheduler between polls so pending IRQs can +* be serviced. +*/ udelay (1 ); +cond_resched (); }return -1 ;
Signature · 1 line
2.55.0
Mark Brown
maintainerQuoted 1 line · Rosen Penev
spi: orion: yield to scheduler in transfer wait loop
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.4
Thanks!
[1/1] spi: orion: yield to scheduler in transfer wait loop
https://git.kernel.org/broonie/spi/c/23ea08ca607c
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