From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>

Hi all,

This patch series addresses three issues in the RZV2H RSPI driver:
1. The max_speed_hz field was advertising a prohibited bit rate, which
   could lead to incorrect behavior when userspace applications attempt
   to set the SPI clock speed.
2. The clock configuration logic allowed for an invalid combination of
   SPR=0 and BRDV=0, which is not supported by the hardware.
3. Simplified  the clock rate search function as min/max speed parameters
   are not needed.

Note, patches apply on top of next-20260409.

Cheers,
Prabhakar

Lad Prabhakar (3):
  spi: rzv2h-rspi: Fix max_speed_hz advertising prohibited bit rate
  spi: rzv2h-rspi: Fix invalid SPR=0/BRDV=0 clock configuration
  spi: rzv2h-rspi: Simplify clock rate search function signatures

 drivers/spi/spi-rzv2h-rspi.c | 52 +++++++++++++++++-------------------
 1 file changed, 25 insertions(+), 27 deletions(-)

-- 
2.53.0

On Fri, 10 Apr 2026 09:05:14 +0100, Prabhakar wrote:
> spi: rzv2h-rspi: Fix max_speed_hz and clock configuration issues
> 
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> 
> Hi all,
> 
> This patch series addresses three issues in the RZV2H RSPI driver:
> 1. The max_speed_hz field was advertising a prohibited bit rate, which
>    could lead to incorrect behavior when userspace applications attempt
>    to set the SPI clock speed.
> 2. The clock configuration logic allowed for an invalid combination of
>    SPR=0 and BRDV=0, which is not supported by the hardware.
> 3. Simplified  the clock rate search function as min/max speed parameters
>    are not needed.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: rzv2h-rspi: Fix max_speed_hz advertising prohibited bit rate
      https://git.kernel.org/broonie/spi/c/4e292cbf3890
[2/3] spi: rzv2h-rspi: Fix invalid SPR=0/BRDV=0 clock configuration
      https://git.kernel.org/broonie/spi/c/0335767dd8e7
[3/3] spi: rzv2h-rspi: Simplify clock rate search function signatures
      https://git.kernel.org/broonie/spi/c/c958bb67b2df

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