devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-clk@vger.kernel.org
Cc: bcm-kernel-feedback-list@broadcom.com,
	devicetree@vger.kernel.org, jonmason@broadcom.com,
	sboyd@codeaurora.org, mturquette@baylibre.com,
	linux@arm.linux.org.uk, sbranden@broadcom.com, rjui@broadcom.com
Subject: Re: [PATCH v4 0/3] clk: Broadcom BCM63138 support
Date: Thu, 19 Nov 2015 17:02:36 -0800	[thread overview]
Message-ID: <564E712C.50309@gmail.com> (raw)
In-Reply-To: <564E70A4.8060001@gmail.com>

On 19/11/15 17:00, Florian Fainelli wrote:
> On 29/10/15 18:23, Florian Fainelli wrote:
>> This patch series adds support for the Broadcom BCM63138 DSL SoCs
>> clocking framework.
>>
>> Since the HW is identical to the one found in Broadcom iProc SoCs, but the
>> integration is different (obviously), there is still a new compatible string
>> introduced just in case we happen to find issues in the future.
>>
>> Stephen, could you stage the two patches in a clk-bcm63xx branch that I could
>> later utilize while doing the arm-soc DT pull request?
> 
> Stephen, can you queue the first two patches in a topic branch for me to
> merge as part of the commit adding the DTS changes?

Well, now that I look back at the changes, you can actually merge the
two patches in clk-next, and the DTS changes can come in before or
after, it does not really matter, this would not cause breakage or
anything. Sorry for the noise.

> 
> Thanks!
> 
>>
>> Thank you!
>>
>> Florian Fainelli (3):
>>   clk: iproc: Extend binding to cover BCM63138
>>   clk: bcm: Add BCM63138 clock support
>>   ARM: dts: BCM63xx: Add ARMPLL device tree nodes
>>
>>  .../bindings/clock/brcm,iproc-clocks.txt           |  5 +++
>>  arch/arm/boot/dts/bcm63138.dtsi                    | 36 +++++++++++++++++-----
>>  drivers/clk/bcm/Kconfig                            | 10 ++++++
>>  drivers/clk/bcm/Makefile                           |  1 +
>>  drivers/clk/bcm/clk-bcm63xx.c                      | 22 +++++++++++++
>>  5 files changed, 66 insertions(+), 8 deletions(-)
>>  create mode 100644 drivers/clk/bcm/clk-bcm63xx.c
>>
> 
> 


-- 
Florian

  reply	other threads:[~2015-11-20  1:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30  1:23 [PATCH v4 0/3] clk: Broadcom BCM63138 support Florian Fainelli
2015-10-30  1:23 ` [PATCH v4 1/3] clk: iproc: Extend binding to cover BCM63138 Florian Fainelli
2015-11-20 23:48   ` Stephen Boyd
2015-10-30  1:23 ` [PATCH v4 2/3] clk: bcm: Add BCM63138 clock support Florian Fainelli
2015-11-20 23:48   ` Stephen Boyd
2015-10-30  1:23 ` [PATCH v4 3/3] ARM: dts: BCM63xx: Add ARMPLL device tree nodes Florian Fainelli
     [not found]   ` <1446168199-5959-4-git-send-email-f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-11-23 18:40     ` Florian Fainelli
2015-11-20  1:00 ` [PATCH v4 0/3] clk: Broadcom BCM63138 support Florian Fainelli
2015-11-20  1:02   ` Florian Fainelli [this message]
2015-11-20 18:46     ` Stephen Boyd
2015-11-20 18:47       ` Florian Fainelli
2015-11-20 23:49         ` Stephen Boyd

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=564E712C.50309@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonmason@broadcom.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mturquette@baylibre.com \
    --cc=rjui@broadcom.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 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).