Re: [PATCH v3 00/11] Optimize spi_sync path

[Mark Brown <broonie@xxxxxxxxxx>]

On Tue, 21 Jun 2022 08:12:23 +0200, David Jander wrote:
> These patches optimize the spi_sync call for the common case that the
> worker thread is idle and the queue is empty. It also opens the
> possibility to potentially further optimize the async path also, since
> it doesn't need to take into account the direct sync path anymore.
> 
> As an example for the performance gain, on an i.MX8MM SoC with a SPI CAN
> controller attached (MCP2518FD), the time the interrupt line stays
> active (which corresponds roughly with the time it takes to send 3
> relatively short consecutive spi_sync messages) is reduced from 98us to
> only 72us by this patch.
> 
> [...]

Applied to

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

Thanks!

[01/11] spi: Move ctlr->cur_msg_prepared to struct spi_message
        commit: 1714582a3a087eda8786d5a1b32b2ec86ca8a303
[02/11] spi: Don't use the message queue if possible in spi_sync
        commit: ae7d2346dc89ae89a6e0aabe6037591a11e593c0
[03/11] spi: Lock controller idling transition inside the io_mutex
        commit: c1038165fbbf83967f29b3bb38872faa780b3a72
[04/11] spi: __spi_pump_messages: Consolidate spin_unlocks to goto target
        commit: 8711a2ab51dd47b2bcb3880403add25dd7fc7c13
[05/11] spi: Remove check for controller idling in spi sync path
        commit: d5256cce1f50ff4c8fad6b8eb7b4ec9e47d38925
[06/11] spi: Remove check for idling in __spi_pump_messages()
        commit: 049d6ccc4da8d34f382949ebec6d4fb318a9c7c0
[07/11] spi: Remove the now unused ctlr->idling flag
        commit: 66a221593cb26dd6aabba63bcd18173f4e69c7ab
[08/11] spi: Remove unneeded READ_ONCE for ctlr->busy flag
        commit: 1a9cafcb57b70fc1439d4a5cb28963122568967a
[09/11] spi: Set ctlr->cur_msg also in the sync transfer case
        commit: 72c5c59b659d54d0c824d0333a211f373316361d
[10/11] spi: Ensure the io_mutex is held until spi_finalize_current_message()
        commit: 69fa95905d40846756d22402690ddf5361a9d13b
[11/11] spi: opportunistically skip ctlr->cur_msg_completion
        commit: dc3029056b02414c29b6627e3dd7b16624725ae9

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