From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kelvin Cheung <keguang.zhang@gmail.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: clock: Add binding for Loongson-1 clock driver
Date: Tue, 17 Jan 2023 11:47:32 +0100 [thread overview]
Message-ID: <4f56e6b3-c698-0909-17a0-ec8c39b6c25d@linaro.org> (raw)
In-Reply-To: <CAJhJPsV5wC_fNgP9iSi1bUp+HFY=dgyh4-x0OueZ8fQO=p7r8w@mail.gmail.com>
On 17/01/2023 11:31, Kelvin Cheung wrote:
>>> + "#clock-cells":
>>> + const: 0
>>> +
>>> + compatible:
>>> + enum:
>>> + - loongson,ls1b-clk-pll
>>> + - loongson,ls1b-clk-cpu
>>> + - loongson,ls1b-clk-ahb
>>> + - loongson,ls1c-clk-pll
>>> + - loongson,ls1c-clk-cpu
>>> + - loongson,ls1c-clk-ahb
>>
>> Are you registering single clocks? It looks like. No, make a proper
>> clock controller.
>
> This binding contains two types of clock, pll-clk and div-clk.
> Should I split the binding to two bindings files?
No, you should register rather one clock controller. Why this have to be
3 separate clock controllers?
>>
>>> +
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + clocks:
>>> + maxItems: 1
>>> +
>>> +required:
>>> + - "#clock-cells"
>>> + - compatible
>>> + - clocks
>>> + - reg
>>> +
>>> +additionalProperties: false
>>> +
>>> +examples:
>>> + - |
>>> + clocks {
>>
>> No, not really related to the binding.
>
> Should I remove the "clocks" section?
Yes.
>>
>>> + #address-cells = <1>;
>>> + #size-cells = <1>;
>>> + ranges;
>>> +
>>> + xtal: xtal {
>>
>> Incorrect in this context. Missing unit address.
>
> XTAL doesn't have reg property.
Yeah, but DTS is not correct now, is it? If you doubt, build your DTB
with W=1.
>>
>>> + compatible = "fixed-clock";
>>> + #clock-cells = <0>;
>>> + clock-frequency = <33000000>;
>>> + };
>>> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-17 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 11:07 [PATCH 0/2] Devicetree support for Loongson-1 clock Keguang Zhang
2023-01-13 11:07 ` [PATCH 1/2] dt-bindings: clock: Add binding for Loongson-1 clock driver Keguang Zhang
2023-01-13 11:17 ` Krzysztof Kozlowski
2023-01-17 10:31 ` Kelvin Cheung
2023-01-17 10:47 ` Krzysztof Kozlowski [this message]
2023-01-18 11:16 ` Kelvin Cheung
2023-01-18 11:28 ` Krzysztof Kozlowski
2023-01-13 15:26 ` Rob Herring
2023-01-17 10:54 ` Kelvin Cheung
2023-01-17 11:08 ` Krzysztof Kozlowski
2023-01-13 11:07 ` [PATCH 2/2] clk: loongson1: Refactor to add devicetree support Keguang Zhang
2023-01-13 11:19 ` Krzysztof Kozlowski
2023-01-19 11:13 ` kernel test robot
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=4f56e6b3-c698-0909-17a0-ec8c39b6c25d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=keguang.zhang@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).