From: Jon Mason <jonmason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: Ray Jui <rjui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Cc: Michael Turquette
<mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Florian Fainelli
<f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>,
Scott Branden <sbranden-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org
Subject: Re: [RFC 1/5] clk: iproc: define Broadcom NSP iProc clock binding
Date: Wed, 14 Oct 2015 11:40:51 -0400 [thread overview]
Message-ID: <20151014154051.GE15160@broadcom.com> (raw)
In-Reply-To: <561D8300.3040804-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
On Tue, Oct 13, 2015 at 03:17:36PM -0700, Ray Jui wrote:
> Shouldn't the device tree binding document go with the other patch
> series since both the binding document and drivers are merged by Michael
> or Stephen?
>
> On 10/13/2015 2:22 PM, Jon Mason wrote:
> > Document the device tree bindings for Broadcom Northstar Plus
> > architecture based clock controller
> >
> > Signed-off-by: Jon Mason <jonmason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
> > ---
> > .../bindings/clock/brcm,iproc-clocks.txt | 30 ++++++++++++++++++++++
> > 1 file changed, 30 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/clock/brcm,iproc-clocks.txt b/Documentation/devicetree/bindings/clock/brcm,iproc-clocks.txt
> > index da8d9bb..b3c3e9d 100644
> > --- a/Documentation/devicetree/bindings/clock/brcm,iproc-clocks.txt
> > +++ b/Documentation/devicetree/bindings/clock/brcm,iproc-clocks.txt
> > @@ -130,3 +130,33 @@ These clock IDs are defined in:
> > ch3_unused mipipll 4 BCM_CYGNUS_MIPIPLL_CH3_UNUSED
> > ch4_unused mipipll 5 BCM_CYGNUS_MIPIPLL_CH4_UNUSED
> > ch5_unused mipipll 6 BCM_CYGNUS_MIPIPLL_CH5_UNUSED
> > +
> > +Northstar and Northstar Plus
> > +------
> > +PLL and leaf clock compatible strings for Northstar and Northstar Plus are:
> > + "brcm,nsp-armpll"
> > + "brcm,nsp-genpll"
> > + "brcm,nsp-lcpll0"
>
> So the current clock driver also supports NS? That will be nice and that
> indicates all the clock related registers/offsets are exactly the same
> between NS and NSP?
Yes. The register offsets are different, but everything else is
identical.
>
> > +
> > +The following table defines the set of PLL/clock index and ID for Northstar and
> > +Northstar Plus. These clock IDs are defined in:
> > + "include/dt-bindings/clock/bcm-nsp.h"
> > +
> > + Clock Source Index ID
> > + --- ----- ----- ---------
> > + crystal N/A N/A N/A
> > +
> > + armpll crystal N/A N/A
> > +
> > + genpll crystal 0 BCM_NSP_GENPLL
> > + phy genpll 1 BCM_NSP_GENPLL_PHY_CLK
> > + ethernetclk genpll 2 BCM_NSP_GENPLL_ENET_SW_CLK
> > + usbclk genpll 3 BCM_NSP_GENPLL_USB_PHY_REF_CLK
> > + iprocfast genpll 4 BCM_NSP_GENPLL_IPROCFAST_CLK
> > + sata1 genpll 5 BCM_NSP_GENPLL_SATA1_CLK
> > + sata2 genpll 6 BCM_NSP_GENPLL_SATA2_CLK
> > +
> > + lcpll0 crystal 0 BCM_NSP_LCPLL0
> > + pcie_phy lcpll0 1 BCM_NSP_LCPLL0_PCIE_PHY_REF_CLK
> > + sdio lcpll0 2 BCM_NSP_LCPLL0_SDIO_CLK
> > + ddr_phy lcpll0 3 BCM_NSP_LCPLL0_DDR_PHY_CLK
> >
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-14 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 21:22 [PATCH 0/5] ARM: dts: add device tree support for NS, NSP, and NS2 clocks Jon Mason
2015-10-13 21:22 ` [RFC 1/5] clk: iproc: define Broadcom NSP iProc clock binding Jon Mason
2015-10-13 22:17 ` Ray Jui
[not found] ` <561D8300.3040804-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-10-14 15:40 ` Jon Mason [this message]
2015-10-13 21:22 ` [RFC 2/5] ARM: dts: enable clock support for Broadcom NSP Jon Mason
2015-10-13 21:22 ` [RFC 3/5] ARM: dts: enable clock support for BCM5301X Jon Mason
2015-10-18 22:34 ` Hauke Mehrtens
2015-10-13 21:22 ` [RFC 4/5] clk: iproc: define Broadcom NS2 iProc clock binding Jon Mason
[not found] ` <1444771347-11382-5-git-send-email-jonmason-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-10-13 22:24 ` Ray Jui
[not found] ` <561D84B4.4000002-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-10-14 15:44 ` Jon Mason
[not found] ` <20151014154410.GF15160-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-10-14 16:53 ` Ray Jui
2015-10-16 22:11 ` Stephen Boyd
2015-10-13 21:22 ` [RFC 5/5] ARM: dts: enable clock support for Broadcom NS2 Jon Mason
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=20151014154051.GE15160@broadcom.com \
--to=jonmason-dy08kvg/lbpwk0htik3j/w@public.gmane.org \
--cc=bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=rjui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=sbranden-dY08KVG/lbpWk0Htik3J/w@public.gmane.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).