From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Rob Herring <robh@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
devicetree@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] dt-bindings: clock: uniphier: Add clock binding for SoC-glue
Date: Mon, 11 Oct 2021 08:55:33 +0900 [thread overview]
Message-ID: <1fe99277-10e0-0149-cef5-e839bd2515bb@socionext.com> (raw)
In-Reply-To: <CAL_JsqL8N+h7bciDt=4fMHyAP=DL=YikpaTh2v4q383XVXH2AA@mail.gmail.com>
On 2021/10/09 4:20, Rob Herring wrote:
> On Thu, Oct 7, 2021 at 3:50 AM Kunihiko Hayashi
> <hayashi.kunihiko@socionext.com> wrote:
>>
>> Hi Rob,
>>
>> On 2021/10/07 4:49, Rob Herring wrote:
>>> On Wed, Oct 06, 2021 at 08:09:14PM +0900, Kunihiko Hayashi wrote:
>>>> Update binding document for clocks implemented in SoC-glue.
>>>>
>>>> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
>>>> ---
>>>> .../bindings/clock/socionext,uniphier-clock.yaml | 16
>>> ++++++++++++++++
>>>> 1 file changed, 16 insertions(+)
>>>>
>>>> diff --git
>>> a/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
>>> b/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
>>>> index ee8d16a8019e..05a9d1f89756 100644
>>>> ---
>>> a/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
>>>> +++
>>> b/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
>>>> @@ -46,6 +46,9 @@ properties:
>>>> - socionext,uniphier-ld20-peri-clock
>>>> - socionext,uniphier-pxs3-peri-clock
>>>> - socionext,uniphier-nx1-peri-clock
>>>> + - description: SoC-glue clock
>>>> + enum:
>>>> + - socionext,uniphier-pro4-sg-clock
>>>>
>>>> "#clock-cells":
>>>> const: 1
>>>> @@ -95,3 +98,16 @@ examples:
>>>>
>>>> // other nodes ...
>>>> };
>>>> +
>>>> + - |
>>>> + soc-glue@5f800000 {
>>>> + compatible = "socionext,uniphier-sysctrl", "simple-mfd",
>>> "syscon";
>>>> + reg = <0x5f800000 0x2000>;
>>>> +
>>>> + clock {
>>>> + compatible = "socionext,uniphier-pro4-sg-clock";
>>>> + #clock-cells = <1>;
>>>> + };
>>>> +
>>>> + // other nodes ...
>>>> + };
>>>
>>> What's the value of this 2nd example? It's just a different compatible
>>> string.
>> Following the previous three examples in the document, it describes the
>> difference between the parent nodes that place the clock.
>>
>> They are common to be child nodes of "syscon", and the definition of the
>> parent node is not in this document.
>> Should I put them together in a common example?
>
> I'd just drop the example.
I see. I'd drop the example in next.
Thank you,
---
Best Regards
Kunihiko Hayashi
_______________________________________________
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:[~2021-10-10 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 11:09 [PATCH v2 0/5] clk: uniphier: Introduce some clock features and NX1 support Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 1/5] clk: uniphier: Add audio system and video input clock control for PXs3 Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 2/5] dt-bindings: clock: uniphier: Add NX1 clock binding Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 3/5] clk: uniphier: Add NX1 clock support Kunihiko Hayashi
2021-10-06 11:09 ` [PATCH v2 4/5] dt-bindings: clock: uniphier: Add clock binding for SoC-glue Kunihiko Hayashi
2021-10-06 19:08 ` Rob Herring
2021-10-06 19:49 ` Rob Herring
2021-10-07 8:50 ` Kunihiko Hayashi
2021-10-08 19:20 ` Rob Herring
2021-10-10 23:55 ` Kunihiko Hayashi [this message]
2021-10-06 11:09 ` [PATCH v2 5/5] clk: uniphier: Add SoC-glue clock source selector support for Pro4 Kunihiko Hayashi
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=1fe99277-10e0-0149-cef5-e839bd2515bb@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@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