spi: dt-bindings: Fix unevaluatedProperties warnings in examples

The 'unevaluatedProperties' schema checks is not fully working and doesn't catch some cases where there's a $ref to another schema. A fix is pending, but results in new warnings in examples.

'spi-max-frequency' is supposed to be a per SPI peripheral device property, not a SPI controller property, so drop it.

Signed-off-by Rob Herring <[email protected]>

EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe

The 'unevaluatedProperties' schema checks is not fully working and doesn't catch some cases where there's a $ref to another schema. A fix is pending, but results in new warnings in examples.

'spi-max-frequency' is supposed to be a per SPI peripheral device property, not a SPI controller property, so drop it.

Signed-off-by Rob Herring <[email protected]>

---
  Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml | 1 -
  Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.yaml | 1 -
  2 files changed, 2 deletions(-)

Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml +0 -1

index ece261b8e963..7326c0a28d16 100644
@@ -47,6 +47,5 @@ examples:
          clocks = <&clkcfg CLK_SPI0>;
          interrupt-parent = <&plic>;
          interrupts = <54>;
-        spi-max-frequency = <25000000>;
      };
...

Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.yaml +0 -2

index e2c7b934c50d..78ceb9d67754 100644
@@ -110,7 +110,6 @@ examples:
          pinctrl-names = "default";
          pinctrl-0 = <&qup_spi1_default>;
          interrupts = <GIC_SPI 602 IRQ_TYPE_LEVEL_HIGH>;
-        spi-max-frequency = <50000000>;
          #address-cells = <1>;
          #size-cells = <0>;
      };
--

2.34.1

Quoted 6 lines · Rob Herring

EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe

The 'unevaluatedProperties' schema checks is not fully working and doesn't catch some cases where there's a $ref to another schema. A fix is pending, but results in new warnings in examples.

Quoted 2 lines

'spi-max-frequency' is supposed to be a per SPI peripheral device property, not a SPI controller property, so drop it.

Reviewed-by Conor Dooley <[email protected]>

As this property is in the mpfs devicetree & I'll need to fix it, is this patch targeted at 5.19? (I assume given the window is open and there's no fixes tag that it isn't).

EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe

Quoted 10 lines · On Thu, May 26, 2022 at 06:52:23AM +0000, [email protected] wrote:

Quoted 8 lines · Rob Herring

EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe

The 'unevaluatedProperties' schema checks is not fully working and doesn't catch some cases where there's a $ref to another schema. A fix is pending, but results in new warnings in examples.

'spi-max-frequency' is supposed to be a per SPI peripheral device property, not a SPI controller property, so drop it.

Quoted 5 lines

Reviewed-by Conor Dooley <[email protected]>

As this property is in the mpfs devicetree & I'll need to fix it, is this patch targeted at 5.19? (I assume given the window is open and there's no fixes tag that it isn't).

5.18 ideally because warnings are going to appear when I push the

dtschema fix for 'unevaluatedProperties'.

Rob

The 'unevaluatedProperties' schema checks is not fully working and doesn't catch some cases where there's a $ref to another schema. A fix is pending, but results in new warnings in examples.

'spi-max-frequency' is supposed to be a per SPI peripheral device property, not a SPI controller property, so drop it.

[...]