From: Stephen Boyd <sboyd@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
heiko@sntech.de
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
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: Re: [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt to YAML
Date: Thu, 31 Mar 2022 15:37:57 -0700 [thread overview]
Message-ID: <20220331223759.B8B12C340ED@smtp.kernel.org> (raw)
In-Reply-To: <bf438af8-5969-73e4-009d-cb7d93095a5e@kernel.org>
Quoting Krzysztof Kozlowski (2022-03-25 00:31:25)
> On 25/03/2022 01:51, Stephen Boyd wrote:
> > Quoting Johan Jonker (2022-03-24 12:51:36)
> >> Hi Heiko, Krzysztof,
> >>
> >> Question for the Rockchip clock maintainer:
> >> What clock should be used here and other SoCs with several clock parents
> >> in the tree?
> >>
> >> The clock.yaml produces a lot off notifications like:
> >>
> >> /arch/arm/boot/dts/rk3036-evb.dtb: clock-controller@20000000: 'clocks'
> >> is a dependency of 'assigned-clocks'
> >
> > 'clocks' is not a dependency of 'assigned-clocks'. The dt-schema should
> > be fixed to remove that requirement.
>
> If the driver does not have any clock inputs ("clocks" property), why
> does it care about some clock frequencies and parents?
Because it's a clock provider itself. In this case I suspect because
this is a clock-controller node it was skipping describing some crystal
input though. Maybe it wants to configure the various PLLs in the
clock-controller for a particular board. I can imagine some node with
#clock-cells may want to configure the frequency of the clock outputs or
configure the clk parents for a certain board/SoC. In that case there
may not be any clocks property, but we still want to configure things.
>
> The clocks is the logical dependency of assigned-clocks, because
> otherwise hardware description is not complete.
Sure, but also #clock-cells indicating that this is a clock-controller
itself means something. The existing bindings are what they are so
forcing bindings to be updated to comply with having a 'clocks' property
doesn't seem very nice.
>
> What should be here for Rockhip? We had similar cases like this for many
> drivers, I was fixing some of Exynos as well. In my case usually the
> root/external clock was missing, so I supplied is as input clock to the
> clock controller.
>
Can the schema consider either #clock-cells or clocks? I think that will
work for most cases. It would also be good to have a comment in the
schema or more detail around the definition of assigned-clocks in
bindings/clock/clock-bindings.txt that clocks or #clock-cells are
required. It would be super cool if assigned-clocks only applied if
#clock-cells was present, otherwise clocks property applies, but I doubt
we can do that anymore given how long the binding has been around.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
heiko@sntech.de
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
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: Re: [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt to YAML
Date: Thu, 31 Mar 2022 15:37:57 -0700 [thread overview]
Message-ID: <20220331223759.B8B12C340ED@smtp.kernel.org> (raw)
In-Reply-To: <bf438af8-5969-73e4-009d-cb7d93095a5e@kernel.org>
Quoting Krzysztof Kozlowski (2022-03-25 00:31:25)
> On 25/03/2022 01:51, Stephen Boyd wrote:
> > Quoting Johan Jonker (2022-03-24 12:51:36)
> >> Hi Heiko, Krzysztof,
> >>
> >> Question for the Rockchip clock maintainer:
> >> What clock should be used here and other SoCs with several clock parents
> >> in the tree?
> >>
> >> The clock.yaml produces a lot off notifications like:
> >>
> >> /arch/arm/boot/dts/rk3036-evb.dtb: clock-controller@20000000: 'clocks'
> >> is a dependency of 'assigned-clocks'
> >
> > 'clocks' is not a dependency of 'assigned-clocks'. The dt-schema should
> > be fixed to remove that requirement.
>
> If the driver does not have any clock inputs ("clocks" property), why
> does it care about some clock frequencies and parents?
Because it's a clock provider itself. In this case I suspect because
this is a clock-controller node it was skipping describing some crystal
input though. Maybe it wants to configure the various PLLs in the
clock-controller for a particular board. I can imagine some node with
#clock-cells may want to configure the frequency of the clock outputs or
configure the clk parents for a certain board/SoC. In that case there
may not be any clocks property, but we still want to configure things.
>
> The clocks is the logical dependency of assigned-clocks, because
> otherwise hardware description is not complete.
Sure, but also #clock-cells indicating that this is a clock-controller
itself means something. The existing bindings are what they are so
forcing bindings to be updated to comply with having a 'clocks' property
doesn't seem very nice.
>
> What should be here for Rockhip? We had similar cases like this for many
> drivers, I was fixing some of Exynos as well. In my case usually the
> root/external clock was missing, so I supplied is as input clock to the
> clock controller.
>
Can the schema consider either #clock-cells or clocks? I think that will
work for most cases. It would also be good to have a comment in the
schema or more detail around the definition of assigned-clocks in
bindings/clock/clock-bindings.txt that clocks or #clock-cells are
required. It would be super cool if assigned-clocks only applied if
#clock-cells was present, otherwise clocks property applies, but I doubt
we can do that anymore given how long the binding has been around.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
heiko@sntech.de
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
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: Re: [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt to YAML
Date: Thu, 31 Mar 2022 15:37:57 -0700 [thread overview]
Message-ID: <20220331223759.B8B12C340ED@smtp.kernel.org> (raw)
In-Reply-To: <bf438af8-5969-73e4-009d-cb7d93095a5e@kernel.org>
Quoting Krzysztof Kozlowski (2022-03-25 00:31:25)
> On 25/03/2022 01:51, Stephen Boyd wrote:
> > Quoting Johan Jonker (2022-03-24 12:51:36)
> >> Hi Heiko, Krzysztof,
> >>
> >> Question for the Rockchip clock maintainer:
> >> What clock should be used here and other SoCs with several clock parents
> >> in the tree?
> >>
> >> The clock.yaml produces a lot off notifications like:
> >>
> >> /arch/arm/boot/dts/rk3036-evb.dtb: clock-controller@20000000: 'clocks'
> >> is a dependency of 'assigned-clocks'
> >
> > 'clocks' is not a dependency of 'assigned-clocks'. The dt-schema should
> > be fixed to remove that requirement.
>
> If the driver does not have any clock inputs ("clocks" property), why
> does it care about some clock frequencies and parents?
Because it's a clock provider itself. In this case I suspect because
this is a clock-controller node it was skipping describing some crystal
input though. Maybe it wants to configure the various PLLs in the
clock-controller for a particular board. I can imagine some node with
#clock-cells may want to configure the frequency of the clock outputs or
configure the clk parents for a certain board/SoC. In that case there
may not be any clocks property, but we still want to configure things.
>
> The clocks is the logical dependency of assigned-clocks, because
> otherwise hardware description is not complete.
Sure, but also #clock-cells indicating that this is a clock-controller
itself means something. The existing bindings are what they are so
forcing bindings to be updated to comply with having a 'clocks' property
doesn't seem very nice.
>
> What should be here for Rockhip? We had similar cases like this for many
> drivers, I was fixing some of Exynos as well. In my case usually the
> root/external clock was missing, so I supplied is as input clock to the
> clock controller.
>
Can the schema consider either #clock-cells or clocks? I think that will
work for most cases. It would also be good to have a comment in the
schema or more detail around the definition of assigned-clocks in
bindings/clock/clock-bindings.txt that clocks or #clock-cells are
required. It would be super cool if assigned-clocks only applied if
#clock-cells was present, otherwise clocks property applies, but I doubt
we can do that anymore given how long the binding has been around.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-31 22:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 13:32 [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt to YAML Johan Jonker
2022-03-24 13:32 ` [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt " Johan Jonker
2022-03-24 13:32 ` Johan Jonker
2022-03-24 14:28 ` [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt " Krzysztof Kozlowski
2022-03-24 14:28 ` [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt " Krzysztof Kozlowski
2022-03-24 14:28 ` Krzysztof Kozlowski
2022-03-24 19:51 ` [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt " Johan Jonker
2022-03-24 19:51 ` [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt " Johan Jonker
2022-03-24 19:51 ` Johan Jonker
2022-03-25 0:51 ` [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt " Stephen Boyd
2022-03-25 0:51 ` [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt " Stephen Boyd
2022-03-25 0:51 ` Stephen Boyd
2022-03-25 7:31 ` [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt " Krzysztof Kozlowski
2022-03-25 7:31 ` [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt " Krzysztof Kozlowski
2022-03-25 7:31 ` Krzysztof Kozlowski
2022-03-31 22:37 ` Stephen Boyd [this message]
2022-03-31 22:37 ` Stephen Boyd
2022-03-31 22:37 ` Stephen Boyd
2022-04-13 21:44 ` [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt " Rob Herring
2022-04-13 21:44 ` [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt " Rob Herring
2022-04-13 21:44 ` Rob Herring
2022-03-25 7:36 ` [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt " Krzysztof Kozlowski
2022-03-25 7:36 ` [PATCH v1] dt-bindings: clock: convert rockchip, rk3188-cru.txt " Krzysztof Kozlowski
2022-03-25 7:36 ` Krzysztof Kozlowski
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=20220331223759.B8B12C340ED@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.