From: <Conor.Dooley@microchip.com>
To: <robh@kernel.org>, <broonie@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <agross@kernel.org>,
<bjorn.andersson@linaro.org>
Cc: <krzysztof.kozlowski@linaro.org>, <linux-spi@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] spi: dt-bindings: Fix unevaluatedProperties warnings in examples
Date: Thu, 26 May 2022 06:52:23 +0000 [thread overview]
Message-ID: <13a92f37-2491-9daa-05a7-f831d9bbb0e0@microchip.com> (raw)
In-Reply-To: <20220526014141.2872567-1-robh@kernel.org>
On 26/05/2022 02:41, Rob Herring wrote:
> 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.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
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).
As an aside, I meant to send the driver once the merge window closes, so
thanks for spotting a problem with the driver before I even sent it :)
Thanks,
Conor.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml | 1 -
> Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.yaml | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml b/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> index ece261b8e963..7326c0a28d16 100644
> --- a/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> +++ b/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> @@ -47,6 +47,5 @@ examples:
> clocks = <&clkcfg CLK_SPI0>;
> interrupt-parent = <&plic>;
> interrupts = <54>;
> - spi-max-frequency = <25000000>;
> };
> ...
> diff --git a/Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.yaml b/Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.yaml
> index e2c7b934c50d..78ceb9d67754 100644
> --- a/Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.yaml
> +++ b/Documentation/devicetree/bindings/spi/qcom,spi-geni-qcom.yaml
> @@ -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
>
next prev parent reply other threads:[~2022-05-26 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 1:41 [PATCH] spi: dt-bindings: Fix unevaluatedProperties warnings in examples Rob Herring
2022-05-26 6:49 ` Krzysztof Kozlowski
2022-05-26 6:52 ` Conor.Dooley [this message]
2022-05-26 14:01 ` Rob Herring
2022-05-26 14:08 ` Conor.Dooley
2022-06-06 16:13 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13a92f37-2491-9daa-05a7-f831d9bbb0e0@microchip.com \
--to=conor.dooley@microchip.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox