From: Mike Turquette <mturquette@linaro.org>
To: Alex Elder <alex.elder@linaro.org>,
Christian Daudt <bcm@fixthebug.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <Pawel.Moll@arm.com>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
Russell King <linux@arm.linux.org.uk>,
Stephen Warren <swarren@wwwdotorg.org>
Cc: "bcm-kernel-feedback-list@broadcom.com"
<bcm-kernel-feedback-list@broadcom.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] clk: initial support for Broadcom Kona clocks
Date: Thu, 26 Dec 2013 14:50:59 -0800 [thread overview]
Message-ID: <20131226225059.28468.61907@quantum> (raw)
In-Reply-To: <52AF1BA5.6000902@linaro.org>
Quoting Alex Elder (2013-12-16 07:26:29)
> Mike, please pull the following for 3.14. It adds clock support
> for Broadcom SoCs having "Kona" clock control units. Thanks.
Pulled into clk-next.
Thanks!
Mike
>
> -Alex
>
> The following changes since commit 1459c837036a44e2dcf14a9452ed330201fb23b5:
>
> clk: si570: Add a driver for SI570 oscillators (2013-12-14 21:01:35 -0800)
>
> are available in the git repository at:
>
> git://git.linaro.org/landing-teams/working/broadcom/kernel.git
> pull/mturquette-kona-clocks
>
> for you to fetch changes up to 143522e704d105bd2b3cbbca6e8fb2d217866ec0:
>
> clk: bcm281xx: add initial clock framework support (2013-12-16
> 07:34:52 -0600)
>
> ----------------------------------------------------------------
> Alex Elder (2):
> clk: bcm281xx: define kona clock binding
> clk: bcm281xx: add initial clock framework support
>
> .../devicetree/bindings/clock/bcm-kona-clock.txt | 93 ++
> drivers/clk/Kconfig | 1 +
> drivers/clk/Makefile | 1 +
> drivers/clk/bcm/Kconfig | 8 +
> drivers/clk/bcm/Makefile | 3 +
> drivers/clk/bcm/clk-bcm281xx.c | 416 ++++++++
> drivers/clk/bcm/clk-kona-setup.c | 769 +++++++++++++++
> drivers/clk/bcm/clk-kona.c | 1033
> ++++++++++++++++++++
> drivers/clk/bcm/clk-kona.h | 414 ++++++++
> include/dt-bindings/clock/bcm281xx.h | 65 ++
> 10 files changed, 2803 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/clock/bcm-kona-clock.txt
> create mode 100644 drivers/clk/bcm/Kconfig
> create mode 100644 drivers/clk/bcm/Makefile
> create mode 100644 drivers/clk/bcm/clk-bcm281xx.c
> create mode 100644 drivers/clk/bcm/clk-kona-setup.c
> create mode 100644 drivers/clk/bcm/clk-kona.c
> create mode 100644 drivers/clk/bcm/clk-kona.h
> create mode 100644 include/dt-bindings/clock/bcm281xx.h
prev parent reply other threads:[~2013-12-26 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 15:26 [GIT PULL] clk: initial support for Broadcom Kona clocks Alex Elder
2013-12-26 22:50 ` Mike Turquette [this message]
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=20131226225059.28468.61907@quantum \
--to=mturquette@linaro.org \
--cc=Pawel.Moll@arm.com \
--cc=alex.elder@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bcm@fixthebug.org \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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).