There's little reason to require the SPI mux to define a maximum bus
frequency as the muxing is just the chip select and devices still define
their maximum freq. In fact, several users don't set "spi-max-frequency"
which caused warnings.

Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
 Documentation/devicetree/bindings/spi/spi-mux.yaml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/spi/spi-mux.yaml b/Documentation/devicetree/bindings/spi/spi-mux.yaml
index fb2a6039928c..b1e2a97be699 100644
--- a/Documentation/devicetree/bindings/spi/spi-mux.yaml
+++ b/Documentation/devicetree/bindings/spi/spi-mux.yaml
@@ -46,7 +46,6 @@ properties:
 required:
   - compatible
   - reg
-  - spi-max-frequency
   - mux-controls
 
 unevaluatedProperties: false
-- 
2.47.2

On Tue, 15 Jul 2025 15:27:10 -0500, Rob Herring (Arm) wrote:
> There's little reason to require the SPI mux to define a maximum bus
> frequency as the muxing is just the chip select and devices still define
> their maximum freq. In fact, several users don't set "spi-max-frequency"
> which caused warnings.
> 
> 

Applied to

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

Thanks!

[1/1] spi: dt-bindings: spi-mux: Drop "spi-max-frequency" as required
      commit: d5255ae7ec48ac1f702e95b472801dbb7bf1e97f

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

Hi Rob,

On 16/07/2025 08:27, Rob Herring (Arm) wrote:
> There's little reason to require the SPI mux to define a maximum bus
> frequency as the muxing is just the chip select and devices still define
> their maximum freq. In fact, several users don't set "spi-max-frequency"
> which caused warnings.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Reviewed-by: Chris Packham <chris.packham@alliedtelesis.co.nz>

> ---
>   Documentation/devicetree/bindings/spi/spi-mux.yaml | 1 -
>   1 file changed, 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/spi/spi-mux.yaml b/Documentation/devicetree/bindings/spi/spi-mux.yaml
> index fb2a6039928c..b1e2a97be699 100644
> --- a/Documentation/devicetree/bindings/spi/spi-mux.yaml
> +++ b/Documentation/devicetree/bindings/spi/spi-mux.yaml
> @@ -46,7 +46,6 @@ properties:
>   required:
>     - compatible
>     - reg
> -  - spi-max-frequency
>     - mux-controls
>   
>   unevaluatedProperties: false