From: Ray Jui <rjui@broadcom.com>
To: Jon Mason <jonmason@broadcom.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
Scott Branden <sbranden@broadcom.com>,
<linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [RFC 1/5] clk: iproc: define Broadcom NSP iProc clock binding
Date: Tue, 13 Oct 2015 15:17:36 -0700 [thread overview]
Message-ID: <561D8300.3040804@broadcom.com> (raw)
In-Reply-To: <1444771347-11382-2-git-send-email-jonmason@broadcom.com>
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@broadcom.com>
> ---
> .../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?
> +
> +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
>
WARNING: multiple messages have this Message-ID (diff)
From: rjui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/5] clk: iproc: define Broadcom NSP iProc clock binding
Date: Tue, 13 Oct 2015 15:17:36 -0700 [thread overview]
Message-ID: <561D8300.3040804@broadcom.com> (raw)
In-Reply-To: <1444771347-11382-2-git-send-email-jonmason@broadcom.com>
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@broadcom.com>
> ---
> .../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?
> +
> +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
>
WARNING: multiple messages have this Message-ID (diff)
From: Ray Jui <rjui@broadcom.com>
To: Jon Mason <jonmason@broadcom.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
Scott Branden <sbranden@broadcom.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [RFC 1/5] clk: iproc: define Broadcom NSP iProc clock binding
Date: Tue, 13 Oct 2015 15:17:36 -0700 [thread overview]
Message-ID: <561D8300.3040804@broadcom.com> (raw)
In-Reply-To: <1444771347-11382-2-git-send-email-jonmason@broadcom.com>
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@broadcom.com>
> ---
> .../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?
> +
> +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
>
next prev parent reply other threads:[~2015-10-13 22:17 UTC|newest]
Thread overview: 38+ 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 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` [RFC 1/5] clk: iproc: define Broadcom NSP iProc clock binding Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 22:17 ` Ray Jui [this message]
2015-10-13 22:17 ` Ray Jui
2015-10-13 22:17 ` Ray Jui
2015-10-14 15:40 ` Jon Mason
2015-10-14 15:40 ` Jon Mason
2015-10-14 15:40 ` Jon Mason
2015-10-13 21:22 ` [RFC 2/5] ARM: dts: enable clock support for Broadcom NSP Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` [RFC 3/5] ARM: dts: enable clock support for BCM5301X Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-18 22:34 ` Hauke Mehrtens
2015-10-18 22:34 ` Hauke Mehrtens
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
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` Jon Mason
2015-10-13 22:24 ` Ray Jui
2015-10-13 22:24 ` Ray Jui
2015-10-13 22:24 ` Ray Jui
2015-10-14 15:44 ` Jon Mason
2015-10-14 15:44 ` Jon Mason
2015-10-14 15:44 ` Jon Mason
2015-10-14 16:53 ` Ray Jui
2015-10-14 16:53 ` Ray Jui
2015-10-14 16:53 ` Ray Jui
2015-10-16 22:11 ` Stephen Boyd
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
2015-10-13 21:22 ` Jon Mason
2015-10-13 21:22 ` 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=561D8300.3040804@broadcom.com \
--to=rjui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jonmason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=sbranden@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.