From: Robin Murphy <robin.murphy@arm.com>
To: Kuldeep Singh <singh.kuldeep87k@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 1/3] dt-bindings: spi: Update clocks property for ARM pl022
Date: Mon, 28 Feb 2022 14:26:12 +0000 [thread overview]
Message-ID: <6e14bdd4-5924-dd58-41ef-5bdb5561913b@arm.com> (raw)
In-Reply-To: <20220228124345.99474-2-singh.kuldeep87k@gmail.com>
On 2022-02-28 12:43, Kuldeep Singh wrote:
> Add missing minItems property to clocks in ARM pl022 bindings.
>
> This also helps in resolving below dtc warnings:
> arch/arm64/boot/dts/amd/amd-overdrive.dt.yaml: spi@e1020000: clocks: [[4]] is too short
> From schema: Documentation/devicetree/bindings/spi/spi-pl022.yaml
> arch/arm64/boot/dts/amd/amd-overdrive.dt.yaml: spi@e1020000: clock-names: ['apb_pclk'] is too short
> From schema: Documentation/devicetree/bindings/spi/spi-pl022.yaml
Who says that minItems is missing? Looking at the PL022 TRM[1] it seems
clear that SSPCLK is pretty fundamental to useful operation. If that DT
ever worked, it must be that the same clock is wired to both inputs, and
the fact that that's how the neighbouring PL011 is described is strongly
suggestive.
If the point of schema is to find errors in DTs, doesn't it make more
sense to fix the DTs than to weaken the schema just to shut it up?
Of course in this particular case there's also the question of whether
the most humane way to "fix" the Seattle DTs is to simply delete them,
but that's orthogonal.
Robin.
[1] https://developer.arm.com/documentation/ddi0194/h/?lang=en
> Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
> ---
> Documentation/devicetree/bindings/spi/spi-pl022.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/spi/spi-pl022.yaml b/Documentation/devicetree/bindings/spi/spi-pl022.yaml
> index 6d633728fc2b..7d36e15db5b3 100644
> --- a/Documentation/devicetree/bindings/spi/spi-pl022.yaml
> +++ b/Documentation/devicetree/bindings/spi/spi-pl022.yaml
> @@ -34,6 +34,7 @@ properties:
> maxItems: 1
>
> clocks:
> + minItems: 1
> maxItems: 2
>
> clock-names:
next prev parent reply other threads:[~2022-02-28 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 12:43 [PATCH 0/3] DTC fixes for Arm pl022 bindings Kuldeep Singh
2022-02-28 12:43 ` [PATCH 1/3] dt-bindings: spi: Update clocks property for ARM pl022 Kuldeep Singh
2022-02-28 14:26 ` Robin Murphy [this message]
2022-02-28 15:11 ` Mark Brown
2022-02-28 15:27 ` Robin Murphy
2022-02-28 15:46 ` Mark Brown
2022-02-28 16:01 ` Robin Murphy
2022-02-28 12:43 ` [PATCH 2/3] dt-bindings: spi: Update clock-names " Kuldeep Singh
2022-02-28 12:43 ` [PATCH 3/3] dt-bindings: spi: Add spiclk to clock-names property in pl022 Kuldeep Singh
2022-02-28 14:36 ` Robin Murphy
2022-03-02 19:05 ` Kuldeep Singh
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=6e14bdd4-5924-dd58-41ef-5bdb5561913b@arm.com \
--to=robin.murphy@arm.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=singh.kuldeep87k@gmail.com \
/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
all inboxes | Powered by JetHome®