Skip to contentSkip to conversation

spi: dt-bindings: spi-mux: Drop "spi-max-frequency" as required

PATCH In review Rob Herring (Arm) 3 participants 3 messages Jul 15, 2025 – Jul 16, 2025

Subsystems (2)
Device tree bindings SPI
lore
Share & tools
lore

Rob Herring (Arm)

author maintainer
#0 lore raw

PATCH 1/1 spi: dt-bindings: spi-mux: Drop "spi-max-frequency" as required

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) <[email protected]>
---
 Documentation/devicetree/bindings/spi/spi-mux.yaml | 1 -
 1 file changed, 1 deletion(-)
Documentation/devicetree/bindings/spi/spi-mux.yaml +0 -1
index fb2a6039928c..b1e2a97be699 100644
@@ -46,7 +46,6 @@ properties:
 required:
   - compatible
   - reg
-  - spi-max-frequency
   - mux-controls
 
 unevaluatedProperties: false
Signature · 1 line
2.47.2
Reviewed-by on v1 1/1
#1 lore raw

Hi Rob,

Quoted 6 lines · Rob Herring (Arm)

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) <[email protected]>
Reviewed-by Chris Packham <[email protected]>
Quoted 16 lines
---
  Documentation/devicetree/bindings/spi/spi-mux.yaml | 1 -
  1 file changed, 1 deletion(-)
Documentation/devicetree/bindings/spi/spi-mux.yaml +0 -1
index fb2a6039928c..b1e2a97be699 100644
@@ -46,7 +46,6 @@ properties:
  required:
    - compatible
    - reg
-  - spi-max-frequency
    - mux-controls
 
  unevaluatedProperties: false
maintainer
#2 lore raw
In reply to Rob Herring (Arm)
Quoted 6 lines · Rob Herring (Arm)

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