From: Scott Wood <scottwood@freescale.com>
To: "Igal.Liberman" <igal.liberman@freescale.com>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [v3] dt/bindings: qoriq-clock: Add binding for FMan clock mux
Date: Wed, 15 Apr 2015 12:35:57 -0500 [thread overview]
Message-ID: <1429119357.22867.724.camel@freescale.com> (raw)
In-Reply-To: <1429008968-24707-1-git-send-email-igal.liberman@freescale.com>
On Tue, 2015-04-14 at 13:56 +0300, Igal.Liberman wrote:
> From: Igal Liberman <Igal.Liberman@freescale.com>
>
> v3: Addressed feedback from Scott:
> - Removed clock specifier description.
>
> v2: Addressed feedback from Scott:
> - Moved the "fman-clk-mux" clock provider details
> under "clocks" property.
>
> Signed-off-by: Igal Liberman <Igal.Liberman@freescale.com>
> ---
> .../devicetree/bindings/clock/qoriq-clock.txt | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/qoriq-clock.txt b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
> index b0d7b73..2bb3b38 100644
> --- a/Documentation/devicetree/bindings/clock/qoriq-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
> @@ -65,9 +65,10 @@ Required properties:
> It takes parent's clock-frequency as its clock.
> * "fsl,qoriq-platform-pll-1.0" for the platform PLL clock (v1.0)
> * "fsl,qoriq-platform-pll-2.0" for the platform PLL clock (v2.0)
> + * "fsl,fman-clk-mux" for the Frame Manager clock.
> - #clock-cells: From common clock binding. The number of cells in a
> - clock-specifier. Should be <0> for "fsl,qoriq-sysclk-[1,2].0"
> - clocks, or <1> for "fsl,qoriq-core-pll-[1,2].0" clocks.
> + clock-specifier. Should be <0> for "fsl,qoriq-sysclk-[1,2].0" and
> + "fsl,fman-clk-mux" clocks or <1> for "fsl,qoriq-core-pll-[1,2].0".
> For "fsl,qoriq-core-pll-1.0" clocks, the single
> clock-specifier cell may take the following values:
> * 0 - equal to the PLL frequency
> @@ -145,6 +146,18 @@ Example for clock block and clock provider:
> clocks = <&sysclk>;
> clock-output-names = "platform-pll", "platform-pll-div2";
> };
> +
> + fm0clk: fm0-clk-mux {
> + #clock-cells = <0>;
> + reg = <0x10 4>
> + compatible = "fsl,fman-clk-mux";
> + clocks = <&pll0 0>, <&pll0 1>, <&pll0 2>, <&pll0 3>,
> + <&platform_pll 0>, <&pll1 1>, <&pll1 2>;
> + clock-names = "pll0", "pll0-div2", "pll0-div3",
> + "pll0-div4", "platform-pll", "pll1-div2",
> + "pll1-div3";
> + clock-output-names = "fm0-clk";
> + };
> };
> };
>
I don't see this register in the manuals for older DPAA chips, such as
p4080 or p3041. Is it present but undocumented? Should I be looking
somewhere other than "Clocking Memory Map"?
-Scott
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2015-04-15 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 10:56 [v3] dt/bindings: qoriq-clock: Add binding for FMan clock mux Igal.Liberman
2015-04-15 17:35 ` Scott Wood [this message]
[not found] ` <1429119357.22867.724.camel-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-04-16 6:11 ` Igal.Liberman-KZfg59tc24xl57MIdRCFDg
[not found] ` <DM2PR03MB38330DBBFFD1BC45D58F447E6E40-ufbTtyGzTTRJonC5hhDUuuO6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-04-17 5:41 ` Scott Wood
[not found] ` <1429249281.32545.52.camel-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-04-20 11:07 ` Igal.Liberman-KZfg59tc24xl57MIdRCFDg
2015-04-20 11:40 ` Igal.Liberman-KZfg59tc24xl57MIdRCFDg
[not found] ` <DM2PR03MB383E5F67C358CCE2E38EA71E6E00-ufbTtyGzTTRJonC5hhDUuuO6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-04-21 0:51 ` Scott Wood
[not found] ` <1429577504.4352.67.camel-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-04-22 10:47 ` Igal.Liberman-KZfg59tc24xl57MIdRCFDg
[not found] ` <DM2PR03MB383C35FA5959662DD48D00BE6EE0-ufbTtyGzTTRJonC5hhDUuuO6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-04-30 0:30 ` Scott Wood
[not found] ` <1430353832.16357.138.camel-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-04-30 14:28 ` Igal.Liberman-KZfg59tc24xl57MIdRCFDg
[not found] ` <DM2PR03MB3839C9D3FDFD7978C1A3497E6D60-ufbTtyGzTTRJonC5hhDUuuO6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-05-01 23:42 ` Scott Wood
[not found] ` <1430523775.16357.177.camel-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-05-05 21:02 ` Igal.Liberman-KZfg59tc24xl57MIdRCFDg
[not found] ` <BY2PR03MB3794413FB3FF795DF520D23E6D10-+7O3WWA3DPtn35zppGJRk+O6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-05-05 21:16 ` Scott Wood
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=1429119357.22867.724.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=igal.liberman@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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).