mbox series

[0/2] spi: sh-msiof: Advertize bit rate limits and actual speed

Message ID 20210113101916.1147695-1-geert+renesas@glider.be (mailing list archive)
Headers show
Series spi: sh-msiof: Advertize bit rate limits and actual speed | expand

Message

Geert Uytterhoeven Jan. 13, 2021, 10:19 a.m. UTC
Hi Mark,

This patch series makes the Renesas MSIOF SPI driver fill in actual
transfer speeds and controller limits, so the SPI core can take them
into account.

This has been tested on R-Car Gen2 and Gen3.
Thanks!

Geert Uytterhoeven (2):
  spi: sh-msiof: Fill in spi_transfer.effective_speed_hz
  spi: sh-msiof: Fill in controller speed limits

 drivers/spi/spi-sh-msiof.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

Comments

Mark Brown Jan. 13, 2021, 3:28 p.m. UTC | #1
On Wed, 13 Jan 2021 11:19:14 +0100, Geert Uytterhoeven wrote:
> 	Hi Mark,
> 
> This patch series makes the Renesas MSIOF SPI driver fill in actual
> transfer speeds and controller limits, so the SPI core can take them
> into account.
> 
> This has been tested on R-Car Gen2 and Gen3.
> Thanks!
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: sh-msiof: Fill in spi_transfer.effective_speed_hz
      commit: 9a133f7b72f0b8d8896cbc7e4149c763b59168bb
[2/2] spi: sh-msiof: Fill in controller speed limits
      commit: 81f68479ec4ec91c0b0d7fb20db433be28e00497

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