[PATCH v1 0/9] spi: spi-imx: cleanups and performance improvements

[Mark Brown]

On Mon, 2 May 2022 19:54:48 +0200, Marc Kleine-Budde wrote:
> this patch series first cleans up several sparse and checkpatch
> warnings, then finished master -< controller conversion. Then PIO
> based polling support is added. It's activated by default for
> transfers smaller than 30 µs (like in the raspi SPI drivers). The last
> patch optimized setup of the MX51_ECSPI_CONFIG register.
> 
> Changes since RFC:
> - rebased to broonie/spi.git for-5.19 (thanks Baruch)
> - 4/9: use swab32s instead of swab32
> - 5/9: use swahw32s instead of swahw32
> - 7/9: removed "select SPI_BITBANG" from Kconfig
> 
> [...]

Applied to

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

Thanks!

[1/9] spi: spi-imx: fix sparse warning: add identifier name to function definition
      commit: f7b8787164551a09fca287b1dea15d0c4d646e4a
[2/9] spi: spi-imx: avoid unnecessary line continuations
      commit: a8c785c1e75538876b524247a3738db53b1f78b8
[3/9] spi: spi-imx: mx51_ecspi_intctrl(): prefer 'unsigned int' to bare use of 'unsigned'
      commit: 1a23461a8a08c4a32972dec31a394eee3302511d
[4/9] spi: spi-imx: spi_imx_buf_rx_swap_u32(): fix sparse warning: use swab32s() instead of cpu_to_be32()
      commit: dae336d0dca669143e0fdf6b82c333bf6a8d9e0a
[5/9] spi: spi-imx: spi_imx_buf_rx_swap_u32(): replace open coded swahw32s()
      commit: baaadffe8854ea14eed1a5f3c09f2136c3aa4427
[6/9] spi: spi-imx: complete conversion from master -> controller
      commit: 63cd96b70f9366f67048fbc07294ce5823001ded
[7/9] spi: spi-imx: replace struct spi_imx_data::bitbang by pointer to struct spi_controller
      commit: 307c897db762d1e0feee9477276b08f6deca4a5b
[8/9] spi: spi-imx: add PIO polling support
      commit: 07e7593877882fbd07c55b26b7dcf88760449323
[9/9] spi: spi-imx: mx51_ecspi_prepare_message(): skip writing MX51_ECSPI_CONFIG register if unchanged
      commit: 184434fcd6177b76f929570348935d7c9f22d296

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