From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Mark Brown <broonie@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH 2/2] dt-bindings: spi: Update clock-names property for ARM pl022
Date: Tue, 8 Mar 2022 02:07:45 +0530 [thread overview]
Message-ID: <20220307203745.65210-2-singh.kuldeep87k@gmail.com> (raw)
In-Reply-To: <20220307203745.65210-1-singh.kuldeep87k@gmail.com>
Pl022 clock-names can be one of following:
['apb_pclk'] or ['sspclk', 'apb_pclk']
The current schema refers to second case only. Make necessary changes to
incorporate both the cases and resolve below dtc warnings:
clock-names: 'apb_pclk' is not one of ['sspclk']
Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
---
Documentation/devicetree/bindings/spi/spi-pl022.yaml | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/spi/spi-pl022.yaml b/Documentation/devicetree/bindings/spi/spi-pl022.yaml
index 7d36e15db5b3..6cfab948624e 100644
--- a/Documentation/devicetree/bindings/spi/spi-pl022.yaml
+++ b/Documentation/devicetree/bindings/spi/spi-pl022.yaml
@@ -38,11 +38,13 @@ properties:
maxItems: 2
clock-names:
- items:
+ oneOf:
- enum:
- - SSPCLK
- - sspclk
- - const: apb_pclk
+ - apb_pclk
+ - items:
+ - enum:
+ - sspclk
+ - const: apb_pclk
pl022,autosuspend-delay:
description: delay in ms following transfer completion before the
--
2.25.1
next prev parent reply other threads:[~2022-03-07 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 20:37 [PATCH 1/2] dt-bindings: spi: Update clocks property for ARM pl022 Kuldeep Singh
2022-03-07 20:37 ` Kuldeep Singh [this message]
2022-03-07 21:55 ` Krzysztof Kozlowski
2022-03-08 5:21 ` 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=20220307203745.65210-2-singh.kuldeep87k@gmail.com \
--to=singh.kuldeep87k@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).