From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs
Date: Sat, 20 Aug 2016 02:55:12 +0900 [thread overview]
Message-ID: <CAK7LNAROCdE4tomp6jg4p5Ep-koPjWSchNEXH01Qn0Wn3q-f2g@mail.gmail.com> (raw)
In-Reply-To: <20160819002826.GT361@codeaurora.org>
Hi Stephen,
2016-08-19 9:28 GMT+09:00 Stephen Boyd <sboyd@codeaurora.org>:
>> +
>> +
>> +System clock
>> +------------
>> +
>> +Required properties:
>> +- compatible: should be one of the following:
>> + "socionext,uniphier-sld3-clock" - for PH1-sLD3 SoC.
>> + "socionext,uniphier-ld4-clock" - for PH1-LD4 SoC.
>> + "socionext,uniphier-pro4-clock" - for PH1-Pro4 SoC.
>> + "socionext,uniphier-sld8-clock" - for PH1-sLD8 SoC.
>> + "socionext,uniphier-pro5-clock" - for PH1-Pro5 SoC.
>> + "socionext,uniphier-pxs2-clock" - for ProXstream2/PH1-LD6b SoC.
>> + "socionext,uniphier-ld11-clock" - for PH1-LD11 SoC.
>> + "socionext,uniphier-ld20-clock" - for PH1-LD20 SoC.
>> +- #clock-cells: should be 1.
>> +
>> +Example:
>> +
>> + sysctrl@61840000 {
>> + compatible = "socionext,uniphier-ld20-sysctrl",
>> + "simple-mfd", "syscon";
>> + reg = <0x61840000 0x4000>;
>> +
>> + clock {
>> + compatible = "socionext,uniphier-ld20-clock";
>> + #clock-cells = <1>;
>> + };
>> +
>> + other nodes ...
>
> What are the other nodes? Is there a document for the rest of the
> MFD?
At lease there are "clock" and "reset" in this MFD at this point.
Perhaps, I may want to add more in the future.
That's why I do not want to list all of the sibling nodes.
The reset node is documented in its binding document,
added by the following patch:
https://patchwork.kernel.org/patch/9255101/
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2016-08-19 17:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 4:30 [PATCH v6 0/2] clk: uniphier: add clock drivers for UniPhier SoCs Masahiro Yamada
2016-08-02 4:30 ` [PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver Masahiro Yamada
2016-08-19 0:25 ` Stephen Boyd
2016-08-19 17:46 ` Masahiro Yamada
2016-08-19 19:16 ` Stephen Boyd
2016-08-29 2:21 ` Masahiro Yamada
2016-08-29 18:22 ` Stephen Boyd
2016-09-05 4:02 ` Masahiro Yamada
2016-09-07 0:32 ` Stephen Boyd
2016-09-16 7:41 ` Masahiro Yamada
2016-08-02 4:30 ` [PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs Masahiro Yamada
2016-08-19 0:28 ` Stephen Boyd
2016-08-19 17:55 ` Masahiro Yamada [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-02 4:28 [PATCH v6 0/2] clk: uniphier: add clock drivers " Masahiro Yamada
2016-08-02 4:28 ` [PATCH v6 2/2] clk: uniphier: add clock data " Masahiro Yamada
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=CAK7LNAROCdE4tomp6jg4p5Ep-koPjWSchNEXH01Qn0Wn3q-f2g@mail.gmail.com \
--to=yamada.masahiro@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=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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).