diff options
| author | Rob Herring (Arm) <robh@kernel.org> | 2025-07-15 15:27:10 -0500 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2025-07-15 22:18:07 +0100 |
| commit | d5255ae7ec48ac1f702e95b472801dbb7bf1e97f (patch) | |
| tree | 40ef4f910141bd1b4cd169a0a437bd7014b790d8 | |
| parent | 6f8584a4826f01a55d3d0c4bbad5961f1de52fc9 (diff) | |
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) <robh@kernel.org>
Reviewed-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Link: https://patch.msgid.link/20250715202711.1882103-1-robh@kernel.org
Signed-off-by: Mark Brown <broonie@kernel.org>
| -rw-r--r-- | Documentation/devicetree/bindings/spi/spi-mux.yaml | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/spi/spi-mux.yaml b/Documentation/devicetree/bindings/spi/spi-mux.yaml index fb2a6039928c4..b1e2a97be6995 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 |