Re: [PATCH v2] spi: spi-ti-qspi: Support per-transfer and per-slave speed_hz settings

[Mark Brown <broonie@xxxxxxxxxx>]

On Thu, 19 May 2022 08:46:04 +0900 (JST), Atsushi Nemoto wrote:
> The spi-ti-qspi driver initializes its spi clock by the
> spi-max-frequency property from the controller node, and ignores
> per-transfer (and per-slave) speed_hz settings.
> 
> Isolate clock settings out from ti_qspi_setup() and call it from
> ti_qspi_start_transfer_one() and ti_qspi_exec_mem_op(), using
> per-transfer speed_hz and per-slave max_speed_hz settings.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-ti-qspi: Support per-transfer and per-slave speed_hz settings
      commit: 8d0b512844fdee83b6299647aa178828a4ebfc3b

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