mbox series

[v1,0/2] Export the spi-sc18is602's max transfer len limit to SPI slave drivers

Message ID 20210520131238.2903024-1-olteanv@gmail.com (mailing list archive)
Headers show
Series Export the spi-sc18is602's max transfer len limit to SPI slave drivers | expand

Message

Vladimir Oltean May 20, 2021, 1:12 p.m. UTC
From: Vladimir Oltean <vladimir.oltean@nxp.com>

These 2 patches make it possible for a SPI device driver which uses
large transfer sizes (256 bytes) to limit itself to the maximum length
supported by the spi-sc18is602 hardware.

Tested with 200 byte buffers on the SC18IS602B.

Vladimir Oltean (2):
  spi: sc18is602: don't consider the chip select byte in
    sc18is602_check_transfer
  spi: sc18is602: implement .max_{transfer,message}_size() for the
    controller

 drivers/spi/spi-sc18is602.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

Comments

Mark Brown May 21, 2021, 3:07 p.m. UTC | #1
On Thu, 20 May 2021 16:12:36 +0300, Vladimir Oltean wrote:
> These 2 patches make it possible for a SPI device driver which uses
> large transfer sizes (256 bytes) to limit itself to the maximum length
> supported by the spi-sc18is602 hardware.
> 
> Tested with 200 byte buffers on the SC18IS602B.
> 
> Vladimir Oltean (2):
>   spi: sc18is602: don't consider the chip select byte in
>     sc18is602_check_transfer
>   spi: sc18is602: implement .max_{transfer,message}_size() for the
>     controller
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: sc18is602: don't consider the chip select byte in sc18is602_check_transfer
      commit: bda7db1d952c3ff7c24c11bc295aa72aaeb98451
[2/2] spi: sc18is602: implement .max_{transfer,message}_size() for the controller
      commit: b4e46c9954ad55092502e1e8c44ceb9b6744bade

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