Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Hi Laurent,
> > > Device tree clock binding document for EMMA Mobile EV2 SMU.
> > > Following nodes are defined to describe clock tree.
> > > - renesas,emev2-smu
> > > - renesas,emev2-smu-clkdiv
> > > - renesas,emev2-smu-gclk
> >
> > I realise this has been entirely consistent in the past and
> > even as recently as Linus' pre v3.12-rc2 master branch.
> > However, after some recent discussion we are now trying to make our
> > compatibility strings consistently of the form renesas,-.
> >
> > With this in mind I believe the strings should be:
> >
> > - renesas,smu-emev2
> > - renesas,smu-clkdiv-emev2
> > - renesas,smu-gclk-emev2
> >
> > To be honest I am not quite sure about the "-clkdiv" and "-gclk"
> > bits and I would appreciate some review from others.
>
> I don't have access to the EMEV2 datasheet so my ability to comment on this
> is
> somehow limited. However, given that the clock hardware is very SoC-specific,
> it might make sense to keep the names proposed by Yoshii-san. This would be
> consistent with the other clock bindings.
Just for explanation:
EM/EV2(there is "/" according to its Users Manual) might be a little difficult
one for general discussion. It stands for "EMMA Mobile EV2", and is a SoC of
"EMMA Mobile" series, they say. So, possibly, the string was
emmamobile-smu or emmamobile-smu-ev2 if it is EV2 specific variant.
But, EMEV2 is the only SoC known in EMMA Mobile series, and no document found
to tell if some other one(if any. there used to be, they say) has SMU or not.
That's why I choose "emev2-smu". This is part, and no portion.
> > > +++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
...
> > > +Example of provider:
> > > +
> > > +usia_u0_sclkdiv: usia_u0_sclkdiv {
> > > + compatible = "renesas,emev2-smu-clkdiv";
> > > + reg = <0x610 0>;
>
> Is the registers space really 0 bytes long ?
Both those are address. as
> > +- reg: Byte offset from SMU base and Bit position in the register
The outer unit (smu) does
> > > + #address-cells = <2>;
> > > + #size-cells = <0>;
and no "ranges".
These clock node is defined not as memory-mapped.
Looks strange? I think so.
This _was introduced_ to comply ePAPR that requires the node name to consist
of generic name and @address to make it unique.
So, the first version was like this.
| usia_u0_sclkdiv: clock@610,0 {
| compatible = "renesas,emev2-smu-clkdiv";
| reg = <0x610 0>;
But later, I trashed it for the consistency with clock nodes without , say
> > > + c32ki: c32ki {
> > > + compatible = "fixed-clock";
I am still not sure what the clock nodes should be. But, I think what we are
discussing is out of the scope of current ePAPR, which does not give the
answer.
> > > +
>
> There's an extra blank line at the end of the file.
Oops. Thank you.
/yoshii
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Hi Laurent,
Device tree clock binding document for EMMA Mobile EV2 SMU.
Following nodes are defined to describe clock tree.
- renesas,emev2-smu
- renesas,emev2-smu-clkdiv
- renesas,emev2-smu-gclk
I realise this has been entirely consistent in the past and
even as recently as Linus' pre v3.12-rc2 master branch.
However, after some recent discussion we are now trying to make our
compatibility strings consistently of the form renesas,unit-soc.
With this in mind I believe the strings should be:
- renesas,smu-emev2
- renesas,smu-clkdiv-emev2
- renesas,smu-gclk-emev2
To be honest I am not quite sure about the -clkdiv and -gclk
bits and I would appreciate some review from others.
I don't have access to the EMEV2 datasheet so my ability to comment on this
is
somehow limited. However, given that the clock hardware is very SoC-specific,
it might make sense to keep the names proposed by Yoshii-san. This would be
consistent with the other clock bindings.
Just for explanation:
EM/EV2(there is / according to its Users Manual) might be a little difficult
one for general discussion. It stands for EMMA Mobile EV2, and is a SoC of
EMMA Mobile series, they say. So, possibly, the string was
emmamobile-smu or emmamobile-smu-ev2 if it is EV2 specific variant.
But, EMEV2 is the only SoC known in EMMA Mobile series, and no document found
to tell if some other one(if any. there used to be, they say) has SMU or not.
That's why I choose emev2-smu. This is unit part, and no soc portion.
+++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
...
+Example of provider:
+
+usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = renesas,emev2-smu-clkdiv;
+ reg = 0x610 0;
Is the registers space really 0 bytes long ?
Both those are address. as
+- reg: Byte offset from SMU base and Bit position in the register
The outer unit (smu) does
+ #address-cells = 2;
+ #size-cells = 0;
and no ranges.
These clock node is defined not as memory-mapped.
Looks strange? I think so.
This _was introduced_ to comply ePAPR that requires the node name to consist
of generic name and @address to make it unique.
So, the first version was like this.
| usia_u0_sclkdiv: clock@610,0 {
| compatible = renesas,emev2-smu-clkdiv;
| reg = 0x610 0;
But later, I trashed it for the consistency with clock nodes without reg, say
+ c32ki: c32ki {
+ compatible = fixed-clock;
I am still not sure what the clock nodes should be. But, I think what we are
discussing is out of the scope of current ePAPR, which does not give the
answer.
+
There's an extra blank line at the end of the file.
Oops. Thank you.
/yoshii
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
On Tue, Oct 01, 2013 at 01:36:33PM +0200, Laurent Pinchart wrote: > Hi Yoshii-san and Simon, > > On Tuesday 24 September 2013 13:52:15 Simon Horman wrote: > > [ Cc Laurent ] > > > > On Tue, Sep 24, 2013 at 01:13:31PM +0900, takas...@ops.dti.ne.jp wrote: > > > Device tree clock binding document for EMMA Mobile EV2 SMU. > > > Following nodes are defined to describe clock tree. > > > - renesas,emev2-smu > > > - renesas,emev2-smu-clkdiv > > > - renesas,emev2-smu-gclk > > > > I realise this has been entirely consistent in the past and > > even as recently as Linus' pre v3.12-rc2 master branch. > > However, after some recent discussion we are now trying to make our > > compatibility strings consistently of the form renesas,-. > > > > With this in mind I believe the strings should be: > > > > - renesas,smu-emev2 > > - renesas,smu-clkdiv-emev2 > > - renesas,smu-gclk-emev2 > > > > To be honest I am not quite sure about the "-clkdiv" and "-gclk" > > bits and I would appreciate some review from others. > > I don't have access to the EMEV2 datasheet so my ability to comment on this > is > somehow limited. However, given that the clock hardware is very SoC-specific, > it might make sense to keep the names proposed by Yoshii-san. This would be > consistent with the other clock bindings. Thanks Laurent. If that seems fine by you then it is fine by me. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Hi Yoshii-san and Simon,
On Tuesday 24 September 2013 13:52:15 Simon Horman wrote:
> [ Cc Laurent ]
>
> On Tue, Sep 24, 2013 at 01:13:31PM +0900, takas...@ops.dti.ne.jp wrote:
> > Device tree clock binding document for EMMA Mobile EV2 SMU.
> > Following nodes are defined to describe clock tree.
> > - renesas,emev2-smu
> > - renesas,emev2-smu-clkdiv
> > - renesas,emev2-smu-gclk
>
> I realise this has been entirely consistent in the past and
> even as recently as Linus' pre v3.12-rc2 master branch.
> However, after some recent discussion we are now trying to make our
> compatibility strings consistently of the form renesas,-.
>
> With this in mind I believe the strings should be:
>
> - renesas,smu-emev2
> - renesas,smu-clkdiv-emev2
> - renesas,smu-gclk-emev2
>
> To be honest I am not quite sure about the "-clkdiv" and "-gclk"
> bits and I would appreciate some review from others.
I don't have access to the EMEV2 datasheet so my ability to comment on this is
somehow limited. However, given that the clock hardware is very SoC-specific,
it might make sense to keep the names proposed by Yoshii-san. This would be
consistent with the other clock bindings.
> I have CCed Laurent as he may have some advice to offer here.
>
> > These bindings are designed manually based on
> >
> > 19UH0037EJ1000_SMU : System Management Unit User's Manual
> >
> > Signed-off-by: Takashi Yoshii
> > ---
> >
> > .../devicetree/bindings/clock/emev2-clock.txt | 99 +
> > 1 file changed, 99 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/clock/emev2-clock.txt
> >
> > diff --git a/Documentation/devicetree/bindings/clock/emev2-clock.txt
> > b/Documentation/devicetree/bindings/clock/emev2-clock.txt new file mode
> > 100644
> > index 000..f8649eb
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
> > @@ -0,0 +1,99 @@
> > +Device tree Clock bindings for Renesas EMMA Mobile EV2
> > +
> > +This binding uses the common clock binding.
> > +
> > +* SMU
> > +System Management Unit described in user's manual R19UH0037EJ1000_SMU.
> > +This is not a clock provider, but clocks under SMU depend on it.
> > +
> > +Required properties:
> > +- compatible: Should be "renesas,emev2-smu"
> > +- reg: Address and Size of SMU registers
> > +
> > +* SMU_CLKDIV
> > +Function block with an input mux and a divider, which corresponds to
> > +"Serial clock generator" in fig."Clock System Overview" of the manual,
> > +and "xxx frequency division setting register" (XXXCLKDIV) registers.
> > +This makes internal (neither input nor output) clock that is provided
> > +to input of xxxGCLK block.
> > +
> > +Required properties:
> > +- compatible: Should be "renesas,emev2-smu-clkdiv"
> > +- reg: Byte offset from SMU base and Bit position in the register
> > +- clocks: Parent clocks. Input clocks as described in clock-bindings.txt
> > +- #clock-cells: Should be <0>
> > +
> > +* SMU_GCLK
> > +Clock gating node shown as "Clock stop processing block" in the
> > +fig."Clock System Overview" of the manual.
> > +Registers are "xxx clock gate control register" (XXXGCLKCTRL).
> > +
> > +Required properties:
> > +- compatible: Should be "renesas,emev2-smu-gclk"
> > +- reg: Byte offset from SMU base and Bit position in the register
> > +- clocks: Input clock as described in clock-bindings.txt
> > +- #clock-cells: Should be <0>
> > +
> > +Example of provider:
> > +
> > +usia_u0_sclkdiv: usia_u0_sclkdiv {
> > + compatible = "renesas,emev2-smu-clkdiv";
> > + reg = <0x610 0>;
Is the registers space really 0 bytes long ?
> > + clocks = <_fo>, <_fo>, <_fo>, <_fo>;
> > + #clock-cells = <0>;
> > +};
> > +
> > +usia_u0_sclk: usia_u0_sclk {
> > + compatible = "renesas,emev2-smu-gclk";
> > + reg = <0x4a0 1>;
> > + clocks = <_u0_sclkdiv>;
> > + #clock-cells = <0>;
> > +};
> > +
> > +Example of consumer:
> > +
> > +uart@e102 {
> > + compatible = "renesas,em-uart";
> > + reg = <0xe102 0x38>;
> > + interrupts = <0 8 0>;
> > + clocks = <_u0_sclk>;
> > + clock-names = "sclk";
> > +};
> > +
> > +Example of clock-tree description:
> > +
> > + This describes a clock path in the clock tree
> > + c32ki -> pll3_fo -> usia_u0_sclkdiv -> usia_u0_sclk
> > +
> > +smu {
> > + compatible = "renesas,emev2-smu";
> > + reg = <0xe011 0x1>;
> > + #address-cells = <2>;
> > + #size-cells = <0>;
> > +
> > + c32ki: c32ki {
> > + compatible = "fixed-clock";
> > + clock-frequency = <32768>;
> > + #clock-cells = <0>;
> > + };
> > + pll3_fo: pll3_fo {
> > + compatible = "fixed-factor-clock";
> > + clocks = <>;
> > + clock-div = <1>;
> > + clock-mult = <7000>;
> > + #clock-cells = <0>;
> > + };
> > + usia_u0_sclkdiv: usia_u0_sclkdiv {
> > + compatible = "renesas,emev2-smu-clkdiv";
> > + reg = <0x610 0>;
> > + clocks = <_fo>;
> > + #clock-cells = <0>;
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Hi Yoshii-san and Simon,
On Tuesday 24 September 2013 13:52:15 Simon Horman wrote:
[ Cc Laurent ]
On Tue, Sep 24, 2013 at 01:13:31PM +0900, takas...@ops.dti.ne.jp wrote:
Device tree clock binding document for EMMA Mobile EV2 SMU.
Following nodes are defined to describe clock tree.
- renesas,emev2-smu
- renesas,emev2-smu-clkdiv
- renesas,emev2-smu-gclk
I realise this has been entirely consistent in the past and
even as recently as Linus' pre v3.12-rc2 master branch.
However, after some recent discussion we are now trying to make our
compatibility strings consistently of the form renesas,unit-soc.
With this in mind I believe the strings should be:
- renesas,smu-emev2
- renesas,smu-clkdiv-emev2
- renesas,smu-gclk-emev2
To be honest I am not quite sure about the -clkdiv and -gclk
bits and I would appreciate some review from others.
I don't have access to the EMEV2 datasheet so my ability to comment on this is
somehow limited. However, given that the clock hardware is very SoC-specific,
it might make sense to keep the names proposed by Yoshii-san. This would be
consistent with the other clock bindings.
I have CCed Laurent as he may have some advice to offer here.
These bindings are designed manually based on
19UH0037EJ1000_SMU : System Management Unit User's Manual
Signed-off-by: Takashi Yoshii takashi.yoshii...@renesas.com
---
.../devicetree/bindings/clock/emev2-clock.txt | 99 +
1 file changed, 99 insertions(+)
create mode 100644
Documentation/devicetree/bindings/clock/emev2-clock.txt
diff --git a/Documentation/devicetree/bindings/clock/emev2-clock.txt
b/Documentation/devicetree/bindings/clock/emev2-clock.txt new file mode
100644
index 000..f8649eb
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
@@ -0,0 +1,99 @@
+Device tree Clock bindings for Renesas EMMA Mobile EV2
+
+This binding uses the common clock binding.
+
+* SMU
+System Management Unit described in user's manual R19UH0037EJ1000_SMU.
+This is not a clock provider, but clocks under SMU depend on it.
+
+Required properties:
+- compatible: Should be renesas,emev2-smu
+- reg: Address and Size of SMU registers
+
+* SMU_CLKDIV
+Function block with an input mux and a divider, which corresponds to
+Serial clock generator in fig.Clock System Overview of the manual,
+and xxx frequency division setting register (XXXCLKDIV) registers.
+This makes internal (neither input nor output) clock that is provided
+to input of xxxGCLK block.
+
+Required properties:
+- compatible: Should be renesas,emev2-smu-clkdiv
+- reg: Byte offset from SMU base and Bit position in the register
+- clocks: Parent clocks. Input clocks as described in clock-bindings.txt
+- #clock-cells: Should be 0
+
+* SMU_GCLK
+Clock gating node shown as Clock stop processing block in the
+fig.Clock System Overview of the manual.
+Registers are xxx clock gate control register (XXXGCLKCTRL).
+
+Required properties:
+- compatible: Should be renesas,emev2-smu-gclk
+- reg: Byte offset from SMU base and Bit position in the register
+- clocks: Input clock as described in clock-bindings.txt
+- #clock-cells: Should be 0
+
+Example of provider:
+
+usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = renesas,emev2-smu-clkdiv;
+ reg = 0x610 0;
Is the registers space really 0 bytes long ?
+ clocks = pll3_fo, pll4_fo, pll1_fo, osc1_fo;
+ #clock-cells = 0;
+};
+
+usia_u0_sclk: usia_u0_sclk {
+ compatible = renesas,emev2-smu-gclk;
+ reg = 0x4a0 1;
+ clocks = usia_u0_sclkdiv;
+ #clock-cells = 0;
+};
+
+Example of consumer:
+
+uart@e102 {
+ compatible = renesas,em-uart;
+ reg = 0xe102 0x38;
+ interrupts = 0 8 0;
+ clocks = usia_u0_sclk;
+ clock-names = sclk;
+};
+
+Example of clock-tree description:
+
+ This describes a clock path in the clock tree
+ c32ki - pll3_fo - usia_u0_sclkdiv - usia_u0_sclk
+
+smu {
+ compatible = renesas,emev2-smu;
+ reg = 0xe011 0x1;
+ #address-cells = 2;
+ #size-cells = 0;
+
+ c32ki: c32ki {
+ compatible = fixed-clock;
+ clock-frequency = 32768;
+ #clock-cells = 0;
+ };
+ pll3_fo: pll3_fo {
+ compatible = fixed-factor-clock;
+ clocks = c32ki;
+ clock-div = 1;
+ clock-mult = 7000;
+ #clock-cells = 0;
+ };
+ usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = renesas,emev2-smu-clkdiv;
+ reg = 0x610 0;
+ clocks = pll3_fo;
+ #clock-cells = 0;
+ };
+ usia_u0_sclk: usia_u0_sclk {
+ compatible = renesas,emev2-smu-gclk;
+ reg = 0x4a0 1;
+ clocks = usia_u0_sclkdiv;
+ #clock-cells = 0;
+ };
+};
+
There's an extra blank line at the end of the file.
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
On Tue, Oct 01, 2013 at 01:36:33PM +0200, Laurent Pinchart wrote: Hi Yoshii-san and Simon, On Tuesday 24 September 2013 13:52:15 Simon Horman wrote: [ Cc Laurent ] On Tue, Sep 24, 2013 at 01:13:31PM +0900, takas...@ops.dti.ne.jp wrote: Device tree clock binding document for EMMA Mobile EV2 SMU. Following nodes are defined to describe clock tree. - renesas,emev2-smu - renesas,emev2-smu-clkdiv - renesas,emev2-smu-gclk I realise this has been entirely consistent in the past and even as recently as Linus' pre v3.12-rc2 master branch. However, after some recent discussion we are now trying to make our compatibility strings consistently of the form renesas,unit-soc. With this in mind I believe the strings should be: - renesas,smu-emev2 - renesas,smu-clkdiv-emev2 - renesas,smu-gclk-emev2 To be honest I am not quite sure about the -clkdiv and -gclk bits and I would appreciate some review from others. I don't have access to the EMEV2 datasheet so my ability to comment on this is somehow limited. However, given that the clock hardware is very SoC-specific, it might make sense to keep the names proposed by Yoshii-san. This would be consistent with the other clock bindings. Thanks Laurent. If that seems fine by you then it is fine by me. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Hi Simon, # I had added wrong From:, sorry. > With this in mind I believe the strings should be: > > - renesas,smu-emev2 > - renesas,smu-clkdiv-emev2 > - renesas,smu-gclk-emev2 Thank you for pointed it out. I'll fix it in v2. > To be honest I am not quite sure about the "-clkdiv" and "-gclk" Neither am I. I'm afread there are many 'not sure' thing for me about DT. I know some part might be wrong, which does not follow ePAPR at least. But, even I don't know whether I should follow ePAPR or not. I will wait for response for a while. /yoshii -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Hi Simon, # I had added wrong From:, sorry. With this in mind I believe the strings should be: - renesas,smu-emev2 - renesas,smu-clkdiv-emev2 - renesas,smu-gclk-emev2 Thank you for pointed it out. I'll fix it in v2. To be honest I am not quite sure about the -clkdiv and -gclk Neither am I. I'm afread there are many 'not sure' thing for me about DT. I know some part might be wrong, which does not follow ePAPR at least. But, even I don't know whether I should follow ePAPR or not. I will wait for response for a while. /yoshii -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
[ Cc Laurent ]
On Tue, Sep 24, 2013 at 01:13:31PM +0900, takas...@ops.dti.ne.jp wrote:
> Device tree clock binding document for EMMA Mobile EV2 SMU.
> Following nodes are defined to describe clock tree.
> - renesas,emev2-smu
> - renesas,emev2-smu-clkdiv
> - renesas,emev2-smu-gclk
I realise this has been entirely consistent in the past and
even as recently as Linus' pre v3.12-rc2 master branch.
However, after some recent discussion we are now trying to make our
compatibility strings consistently of the form renesas,-.
With this in mind I believe the strings should be:
- renesas,smu-emev2
- renesas,smu-clkdiv-emev2
- renesas,smu-gclk-emev2
To be honest I am not quite sure about the "-clkdiv" and "-gclk"
bits and I would appreciate some review from others.
I have CCed Laurent as he may have some advice to offer here.
>
> These bindings are designed manually based on
> 19UH0037EJ1000_SMU : System Management Unit User's Manual
>
> Signed-off-by: Takashi Yoshii
> ---
> .../devicetree/bindings/clock/emev2-clock.txt | 99
> ++
> 1 file changed, 99 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/emev2-clock.txt
>
> diff --git a/Documentation/devicetree/bindings/clock/emev2-clock.txt
> b/Documentation/devicetree/bindings/clock/emev2-clock.txt
> new file mode 100644
> index 000..f8649eb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
> @@ -0,0 +1,99 @@
> +Device tree Clock bindings for Renesas EMMA Mobile EV2
> +
> +This binding uses the common clock binding.
> +
> +* SMU
> +System Management Unit described in user's manual R19UH0037EJ1000_SMU.
> +This is not a clock provider, but clocks under SMU depend on it.
> +
> +Required properties:
> +- compatible: Should be "renesas,emev2-smu"
> +- reg: Address and Size of SMU registers
> +
> +* SMU_CLKDIV
> +Function block with an input mux and a divider, which corresponds to
> +"Serial clock generator" in fig."Clock System Overview" of the manual,
> +and "xxx frequency division setting register" (XXXCLKDIV) registers.
> +This makes internal (neither input nor output) clock that is provided
> +to input of xxxGCLK block.
> +
> +Required properties:
> +- compatible: Should be "renesas,emev2-smu-clkdiv"
> +- reg: Byte offset from SMU base and Bit position in the register
> +- clocks: Parent clocks. Input clocks as described in clock-bindings.txt
> +- #clock-cells: Should be <0>
> +
> +* SMU_GCLK
> +Clock gating node shown as "Clock stop processing block" in the
> +fig."Clock System Overview" of the manual.
> +Registers are "xxx clock gate control register" (XXXGCLKCTRL).
> +
> +Required properties:
> +- compatible: Should be "renesas,emev2-smu-gclk"
> +- reg: Byte offset from SMU base and Bit position in the register
> +- clocks: Input clock as described in clock-bindings.txt
> +- #clock-cells: Should be <0>
> +
> +Example of provider:
> +
> +usia_u0_sclkdiv: usia_u0_sclkdiv {
> + compatible = "renesas,emev2-smu-clkdiv";
> + reg = <0x610 0>;
> + clocks = <_fo>, <_fo>, <_fo>, <_fo>;
> + #clock-cells = <0>;
> +};
> +
> +usia_u0_sclk: usia_u0_sclk {
> + compatible = "renesas,emev2-smu-gclk";
> + reg = <0x4a0 1>;
> + clocks = <_u0_sclkdiv>;
> + #clock-cells = <0>;
> +};
> +
> +Example of consumer:
> +
> +uart@e102 {
> + compatible = "renesas,em-uart";
> + reg = <0xe102 0x38>;
> + interrupts = <0 8 0>;
> + clocks = <_u0_sclk>;
> + clock-names = "sclk";
> +};
> +
> +Example of clock-tree description:
> +
> + This describes a clock path in the clock tree
> + c32ki -> pll3_fo -> usia_u0_sclkdiv -> usia_u0_sclk
> +
> +smu {
> + compatible = "renesas,emev2-smu";
> + reg = <0xe011 0x1>;
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + c32ki: c32ki {
> + compatible = "fixed-clock";
> + clock-frequency = <32768>;
> + #clock-cells = <0>;
> + };
> + pll3_fo: pll3_fo {
> + compatible = "fixed-factor-clock";
> + clocks = <>;
> + clock-div = <1>;
> + clock-mult = <7000>;
> + #clock-cells = <0>;
> + };
> + usia_u0_sclkdiv: usia_u0_sclkdiv {
> + compatible = "renesas,emev2-smu-clkdiv";
> + reg = <0x610 0>;
> + clocks = <_fo>;
> + #clock-cells = <0>;
> + };
> + usia_u0_sclk: usia_u0_sclk {
> + compatible = "renesas,emev2-smu-gclk";
> + reg = <0x4a0 1>;
> + clocks = <_u0_sclkdiv>;
> + #clock-cells = <0>;
> + };
> +};
> +
> --
> 1.8.1.5
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Device tree clock binding document for EMMA Mobile EV2 SMU.
Following nodes are defined to describe clock tree.
- renesas,emev2-smu
- renesas,emev2-smu-clkdiv
- renesas,emev2-smu-gclk
These bindings are designed manually based on
19UH0037EJ1000_SMU : System Management Unit User's Manual
Signed-off-by: Takashi Yoshii
---
.../devicetree/bindings/clock/emev2-clock.txt | 99 ++
1 file changed, 99 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/emev2-clock.txt
diff --git a/Documentation/devicetree/bindings/clock/emev2-clock.txt
b/Documentation/devicetree/bindings/clock/emev2-clock.txt
new file mode 100644
index 000..f8649eb
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
@@ -0,0 +1,99 @@
+Device tree Clock bindings for Renesas EMMA Mobile EV2
+
+This binding uses the common clock binding.
+
+* SMU
+System Management Unit described in user's manual R19UH0037EJ1000_SMU.
+This is not a clock provider, but clocks under SMU depend on it.
+
+Required properties:
+- compatible: Should be "renesas,emev2-smu"
+- reg: Address and Size of SMU registers
+
+* SMU_CLKDIV
+Function block with an input mux and a divider, which corresponds to
+"Serial clock generator" in fig."Clock System Overview" of the manual,
+and "xxx frequency division setting register" (XXXCLKDIV) registers.
+This makes internal (neither input nor output) clock that is provided
+to input of xxxGCLK block.
+
+Required properties:
+- compatible: Should be "renesas,emev2-smu-clkdiv"
+- reg: Byte offset from SMU base and Bit position in the register
+- clocks: Parent clocks. Input clocks as described in clock-bindings.txt
+- #clock-cells: Should be <0>
+
+* SMU_GCLK
+Clock gating node shown as "Clock stop processing block" in the
+fig."Clock System Overview" of the manual.
+Registers are "xxx clock gate control register" (XXXGCLKCTRL).
+
+Required properties:
+- compatible: Should be "renesas,emev2-smu-gclk"
+- reg: Byte offset from SMU base and Bit position in the register
+- clocks: Input clock as described in clock-bindings.txt
+- #clock-cells: Should be <0>
+
+Example of provider:
+
+usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = "renesas,emev2-smu-clkdiv";
+ reg = <0x610 0>;
+ clocks = <_fo>, <_fo>, <_fo>, <_fo>;
+ #clock-cells = <0>;
+};
+
+usia_u0_sclk: usia_u0_sclk {
+ compatible = "renesas,emev2-smu-gclk";
+ reg = <0x4a0 1>;
+ clocks = <_u0_sclkdiv>;
+ #clock-cells = <0>;
+};
+
+Example of consumer:
+
+uart@e102 {
+ compatible = "renesas,em-uart";
+ reg = <0xe102 0x38>;
+ interrupts = <0 8 0>;
+ clocks = <_u0_sclk>;
+ clock-names = "sclk";
+};
+
+Example of clock-tree description:
+
+ This describes a clock path in the clock tree
+ c32ki -> pll3_fo -> usia_u0_sclkdiv -> usia_u0_sclk
+
+smu {
+ compatible = "renesas,emev2-smu";
+ reg = <0xe011 0x1>;
+ #address-cells = <2>;
+ #size-cells = <0>;
+
+ c32ki: c32ki {
+ compatible = "fixed-clock";
+ clock-frequency = <32768>;
+ #clock-cells = <0>;
+ };
+ pll3_fo: pll3_fo {
+ compatible = "fixed-factor-clock";
+ clocks = <>;
+ clock-div = <1>;
+ clock-mult = <7000>;
+ #clock-cells = <0>;
+ };
+ usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = "renesas,emev2-smu-clkdiv";
+ reg = <0x610 0>;
+ clocks = <_fo>;
+ #clock-cells = <0>;
+ };
+ usia_u0_sclk: usia_u0_sclk {
+ compatible = "renesas,emev2-smu-gclk";
+ reg = <0x4a0 1>;
+ clocks = <_u0_sclkdiv>;
+ #clock-cells = <0>;
+ };
+};
+
--
1.8.1.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
Device tree clock binding document for EMMA Mobile EV2 SMU.
Following nodes are defined to describe clock tree.
- renesas,emev2-smu
- renesas,emev2-smu-clkdiv
- renesas,emev2-smu-gclk
These bindings are designed manually based on
19UH0037EJ1000_SMU : System Management Unit User's Manual
Signed-off-by: Takashi Yoshii takashi.yoshii...@renesas.com
---
.../devicetree/bindings/clock/emev2-clock.txt | 99 ++
1 file changed, 99 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/emev2-clock.txt
diff --git a/Documentation/devicetree/bindings/clock/emev2-clock.txt
b/Documentation/devicetree/bindings/clock/emev2-clock.txt
new file mode 100644
index 000..f8649eb
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
@@ -0,0 +1,99 @@
+Device tree Clock bindings for Renesas EMMA Mobile EV2
+
+This binding uses the common clock binding.
+
+* SMU
+System Management Unit described in user's manual R19UH0037EJ1000_SMU.
+This is not a clock provider, but clocks under SMU depend on it.
+
+Required properties:
+- compatible: Should be renesas,emev2-smu
+- reg: Address and Size of SMU registers
+
+* SMU_CLKDIV
+Function block with an input mux and a divider, which corresponds to
+Serial clock generator in fig.Clock System Overview of the manual,
+and xxx frequency division setting register (XXXCLKDIV) registers.
+This makes internal (neither input nor output) clock that is provided
+to input of xxxGCLK block.
+
+Required properties:
+- compatible: Should be renesas,emev2-smu-clkdiv
+- reg: Byte offset from SMU base and Bit position in the register
+- clocks: Parent clocks. Input clocks as described in clock-bindings.txt
+- #clock-cells: Should be 0
+
+* SMU_GCLK
+Clock gating node shown as Clock stop processing block in the
+fig.Clock System Overview of the manual.
+Registers are xxx clock gate control register (XXXGCLKCTRL).
+
+Required properties:
+- compatible: Should be renesas,emev2-smu-gclk
+- reg: Byte offset from SMU base and Bit position in the register
+- clocks: Input clock as described in clock-bindings.txt
+- #clock-cells: Should be 0
+
+Example of provider:
+
+usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = renesas,emev2-smu-clkdiv;
+ reg = 0x610 0;
+ clocks = pll3_fo, pll4_fo, pll1_fo, osc1_fo;
+ #clock-cells = 0;
+};
+
+usia_u0_sclk: usia_u0_sclk {
+ compatible = renesas,emev2-smu-gclk;
+ reg = 0x4a0 1;
+ clocks = usia_u0_sclkdiv;
+ #clock-cells = 0;
+};
+
+Example of consumer:
+
+uart@e102 {
+ compatible = renesas,em-uart;
+ reg = 0xe102 0x38;
+ interrupts = 0 8 0;
+ clocks = usia_u0_sclk;
+ clock-names = sclk;
+};
+
+Example of clock-tree description:
+
+ This describes a clock path in the clock tree
+ c32ki - pll3_fo - usia_u0_sclkdiv - usia_u0_sclk
+
+smu {
+ compatible = renesas,emev2-smu;
+ reg = 0xe011 0x1;
+ #address-cells = 2;
+ #size-cells = 0;
+
+ c32ki: c32ki {
+ compatible = fixed-clock;
+ clock-frequency = 32768;
+ #clock-cells = 0;
+ };
+ pll3_fo: pll3_fo {
+ compatible = fixed-factor-clock;
+ clocks = c32ki;
+ clock-div = 1;
+ clock-mult = 7000;
+ #clock-cells = 0;
+ };
+ usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = renesas,emev2-smu-clkdiv;
+ reg = 0x610 0;
+ clocks = pll3_fo;
+ #clock-cells = 0;
+ };
+ usia_u0_sclk: usia_u0_sclk {
+ compatible = renesas,emev2-smu-gclk;
+ reg = 0x4a0 1;
+ clocks = usia_u0_sclkdiv;
+ #clock-cells = 0;
+ };
+};
+
--
1.8.1.5
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 4/6] ARM: shmobile: emev2: Define SMU clock DT bindings
[ Cc Laurent ]
On Tue, Sep 24, 2013 at 01:13:31PM +0900, takas...@ops.dti.ne.jp wrote:
Device tree clock binding document for EMMA Mobile EV2 SMU.
Following nodes are defined to describe clock tree.
- renesas,emev2-smu
- renesas,emev2-smu-clkdiv
- renesas,emev2-smu-gclk
I realise this has been entirely consistent in the past and
even as recently as Linus' pre v3.12-rc2 master branch.
However, after some recent discussion we are now trying to make our
compatibility strings consistently of the form renesas,unit-soc.
With this in mind I believe the strings should be:
- renesas,smu-emev2
- renesas,smu-clkdiv-emev2
- renesas,smu-gclk-emev2
To be honest I am not quite sure about the -clkdiv and -gclk
bits and I would appreciate some review from others.
I have CCed Laurent as he may have some advice to offer here.
These bindings are designed manually based on
19UH0037EJ1000_SMU : System Management Unit User's Manual
Signed-off-by: Takashi Yoshii takashi.yoshii...@renesas.com
---
.../devicetree/bindings/clock/emev2-clock.txt | 99
++
1 file changed, 99 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/emev2-clock.txt
diff --git a/Documentation/devicetree/bindings/clock/emev2-clock.txt
b/Documentation/devicetree/bindings/clock/emev2-clock.txt
new file mode 100644
index 000..f8649eb
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/emev2-clock.txt
@@ -0,0 +1,99 @@
+Device tree Clock bindings for Renesas EMMA Mobile EV2
+
+This binding uses the common clock binding.
+
+* SMU
+System Management Unit described in user's manual R19UH0037EJ1000_SMU.
+This is not a clock provider, but clocks under SMU depend on it.
+
+Required properties:
+- compatible: Should be renesas,emev2-smu
+- reg: Address and Size of SMU registers
+
+* SMU_CLKDIV
+Function block with an input mux and a divider, which corresponds to
+Serial clock generator in fig.Clock System Overview of the manual,
+and xxx frequency division setting register (XXXCLKDIV) registers.
+This makes internal (neither input nor output) clock that is provided
+to input of xxxGCLK block.
+
+Required properties:
+- compatible: Should be renesas,emev2-smu-clkdiv
+- reg: Byte offset from SMU base and Bit position in the register
+- clocks: Parent clocks. Input clocks as described in clock-bindings.txt
+- #clock-cells: Should be 0
+
+* SMU_GCLK
+Clock gating node shown as Clock stop processing block in the
+fig.Clock System Overview of the manual.
+Registers are xxx clock gate control register (XXXGCLKCTRL).
+
+Required properties:
+- compatible: Should be renesas,emev2-smu-gclk
+- reg: Byte offset from SMU base and Bit position in the register
+- clocks: Input clock as described in clock-bindings.txt
+- #clock-cells: Should be 0
+
+Example of provider:
+
+usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = renesas,emev2-smu-clkdiv;
+ reg = 0x610 0;
+ clocks = pll3_fo, pll4_fo, pll1_fo, osc1_fo;
+ #clock-cells = 0;
+};
+
+usia_u0_sclk: usia_u0_sclk {
+ compatible = renesas,emev2-smu-gclk;
+ reg = 0x4a0 1;
+ clocks = usia_u0_sclkdiv;
+ #clock-cells = 0;
+};
+
+Example of consumer:
+
+uart@e102 {
+ compatible = renesas,em-uart;
+ reg = 0xe102 0x38;
+ interrupts = 0 8 0;
+ clocks = usia_u0_sclk;
+ clock-names = sclk;
+};
+
+Example of clock-tree description:
+
+ This describes a clock path in the clock tree
+ c32ki - pll3_fo - usia_u0_sclkdiv - usia_u0_sclk
+
+smu {
+ compatible = renesas,emev2-smu;
+ reg = 0xe011 0x1;
+ #address-cells = 2;
+ #size-cells = 0;
+
+ c32ki: c32ki {
+ compatible = fixed-clock;
+ clock-frequency = 32768;
+ #clock-cells = 0;
+ };
+ pll3_fo: pll3_fo {
+ compatible = fixed-factor-clock;
+ clocks = c32ki;
+ clock-div = 1;
+ clock-mult = 7000;
+ #clock-cells = 0;
+ };
+ usia_u0_sclkdiv: usia_u0_sclkdiv {
+ compatible = renesas,emev2-smu-clkdiv;
+ reg = 0x610 0;
+ clocks = pll3_fo;
+ #clock-cells = 0;
+ };
+ usia_u0_sclk: usia_u0_sclk {
+ compatible = renesas,emev2-smu-gclk;
+ reg = 0x4a0 1;
+ clocks = usia_u0_sclkdiv;
+ #clock-cells = 0;
+ };
+};
+
--
1.8.1.5
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
