From: Johan Jonker <jbx6244@gmail.com>
To: heiko@sntech.de, zhangqing@rock-chips.com
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 4/6] dt-bindings: clock: fix rk3399 cru clock issues
Date: Tue, 29 Mar 2022 17:07:40 +0200 [thread overview]
Message-ID: <20220329150742.22093-4-jbx6244@gmail.com> (raw)
In-Reply-To: <20220329150742.22093-1-jbx6244@gmail.com>
The current rk3399 cru DT node gives warnings like:
'clocks' is a dependency of 'assigned-clocks'.
With the YAML conversion somehow "assigned-xxx" properties where added.
If a proper clock is added to the cru node these properties are no longer
needed, so removed them. Currently only one clock will be added, so limit
the clock maxItems to 1. Add a clock name to be able to differentiate
and filter bogus entries.
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
.../bindings/clock/rockchip,rk3399-cru.yaml | 15 +++------------
1 file changed, 3 insertions(+), 12 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.yaml b/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.yaml
index 18a009311..54da1e31e 100644
--- a/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.yaml
+++ b/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.yaml
@@ -46,19 +46,10 @@ properties:
const: 1
clocks:
- minItems: 1
-
- assigned-clocks:
- minItems: 1
- maxItems: 64
-
- assigned-clock-parents:
- minItems: 1
- maxItems: 64
+ maxItems: 1
- assigned-clock-rates:
- minItems: 1
- maxItems: 64
+ clock-names:
+ const: xin24m
rockchip,grf:
$ref: /schemas/types.yaml#/definitions/phandle
--
2.20.1
next prev parent reply other threads:[~2022-03-29 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 15:07 [PATCH v2 1/6] dt-bindings: clock: fix some conversion style issues for rockchip,rk3399-cru.yaml Johan Jonker
2022-03-29 15:07 ` [PATCH v2 2/6] dt-bindings: clock: replace a maintainer " Johan Jonker
2022-03-29 15:07 ` [PATCH v2 3/6] dt-bindings: clock: use generic node name for pmucru example in rockchip,rk3399-cru.yaml Johan Jonker
2022-03-29 15:29 ` [PATCH v2 3/6] dt-bindings: clock: use generic node name for pmucru example in rockchip, rk3399-cru.yaml Krzysztof Kozlowski
2022-03-29 15:07 ` Johan Jonker [this message]
2022-03-29 15:30 ` [PATCH v2 4/6] dt-bindings: clock: fix rk3399 cru clock issues Krzysztof Kozlowski
2022-03-29 15:07 ` [PATCH v2 5/6] arm64: dts: rockchip: rk3399: use generic node name for pmucru Johan Jonker
2022-03-29 15:07 ` [PATCH v2 6/6] arm64: dts: rockchip: add clocks property to cru nodes rk3399 Johan Jonker
2022-03-29 15:31 ` [PATCH v2 1/6] dt-bindings: clock: fix some conversion style issues for rockchip, rk3399-cru.yaml Krzysztof Kozlowski
2022-04-10 17:12 ` [PATCH v2 1/6] dt-bindings: clock: fix some conversion style issues for rockchip,rk3399-cru.yaml Heiko Stuebner
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=20220329150742.22093-4-jbx6244@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=zhangqing@rock-chips.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