Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1465709 > unrolled thread

Re: [PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs

Started byStephen Boyd <sboyd@codeaurora.org>
First post2016-08-19 03:10 +0200
Last post2016-08-19 20:00 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs Stephen Boyd <sboyd@codeaurora.org> - 2016-08-19 03:10 +0200
    Re: [PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs Masahiro Yamada <yamada.masahiro@socionext.com> - 2016-08-19 20:00 +0200

#1465709 — Re: [PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs

FromStephen Boyd <sboyd@codeaurora.org>
Date2016-08-19 03:10 +0200
SubjectRe: [PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs
Message-ID<s7GtQ-7go-37@gated-at.bofh.it>
On 08/02, Masahiro Yamada wrote:
> diff --git a/Documentation/devicetree/bindings/clock/uniphier-clock.txt b/Documentation/devicetree/bindings/clock/uniphier-clock.txt
> new file mode 100644
> index 0000000..1a4db8b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/uniphier-clock.txt
> @@ -0,0 +1,134 @@
> +UniPhier clock controller
> +
> +
> +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?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

[toc] | [next] | [standalone]


#1466589

FromMasahiro Yamada <yamada.masahiro@socionext.com>
Date2016-08-19 20:00 +0200
Message-ID<s7Wff-e9-7@gated-at.bofh.it>
In reply to#1465709
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

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web