linux-kernel - Re: [PATCH] spi: dt-bindings: spi-mux: Drop "spi-max-frequency" as required

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6ed8defc-0e3c-469e-be16-9d337d08f994@alliedtelesis.co.nz>
Date: Wed, 16 Jul 2025 08:50:07 +1200
From: Chris Packham <chris.packham@...iedtelesis.co.nz>
To: "Rob Herring (Arm)" <robh@...nel.org>, Mark Brown <broonie@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Cc: linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: dt-bindings: spi-mux: Drop "spi-max-frequency" as
 required

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@...nel.org>
Reviewed-by: Chris Packham <chris.packham@...iedtelesis.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