Hello,

while developing a virtio-spi device, I noticed that the spi-virtio
driver in not honoring the indication on the maximum transfer frequency
supported by the device that this one indicates using the config space.
Patch 1 contains a fix for that.

While at it, I did a minor cleanup inside the function parsing the
config space, where a value was stored into the driver's private data
without a further usage, wasting (a very tiny amount of) memory.

This was tested against a (still unreleased) virtio device running on
a Cortex-M33, with remoteproc as virtio transport.

Regards,
Francesco

Signed-off-by: Francesco Valla <francesco@valla.it>
---
Francesco Valla (2):
      spi: virtio: fix max frequency setting
      spi: virtio: drop unused field from private data

 drivers/spi/spi-virtio.c | 20 ++++++++------------
 1 file changed, 8 insertions(+), 12 deletions(-)
---
base-commit: 9b87fdc9af2fbfcdb5c24a64139685ef80f6573f
change-id: 20260915-virtio-spi-fix2-ed832a0c069e

Best regards,
--  
Francesco Valla <francesco@valla.it>

On Tue, 15 Sep 2026 22:24:35 +0200, Francesco Valla wrote:
> spi: virtio: fix max frequency setting plus minor cleanup
> 
> Hello,
> 
> while developing a virtio-spi device, I noticed that the spi-virtio
> driver in not honoring the indication on the maximum transfer frequency
> supported by the device that this one indicates using the config space.
> Patch 1 contains a fix for that.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: virtio: fix max frequency setting
      https://git.kernel.org/broonie/spi/c/26f42ca8becd
[2/2] spi: virtio: drop unused field from private data
      https://git.kernel.org/broonie/spi/c/62b223cf4334

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