From: Alex Elder <elder@linaro.org>
To: mturquette@linaro.org, bcm@fixthebug.org, mporter@linaro.org,
devicetree@vger.kernel.org
Cc: linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] clk: bcm21664: add common clock support
Date: Fri, 28 Feb 2014 07:49:26 -0600 [thread overview]
Message-ID: <1393595371-3789-1-git-send-email-elder@linaro.org> (raw)
This is series has two parts. The first two patches are changes
to the existing Broadcom Kona family clock code to prepare for the
addition of support for another SoC bcm21664.
The remaining three define the binding and code for bcm21664, and
replace the use of "fake" clocks in the device tree with the real
ones. This ends up being a fairly straightforward definition of
the clocks on this SoC; the rest of the clock code is shared with
other SoCs that use the Kona style clock system.
This series depends on a number of other things that are
currently queued for Linux 3.15 or have already been sent
out for review:
- Clock support for bcm281xx (code and DT file, queued for 3.15)
https://github.com/broadcom/mach-bcm/
armsoc/for-3.15/drivers
armsoc/for-3.15/dt
- Additional fixes and features for bcm281xx (out for review)
https://lkml.org/lkml/2014/2/25/614
- Initial BCM21664 support (from Markus Mayer, out for review)
https://lkml.org/lkml/2014/2/27/615
This prerequisite code appears in the branch (below) as merges from
other publicly-available git branches.
This code is available in the "review/bcm21664-clock" branch of
the git repository here:
http://git.linaro.org/git/landing-teams/working/broadcom/kernel.git
-Alex
Alex Elder (5):
clk: bcm281xx: move compatible string definitions
ARM: dts: revise kona clock binding document
Cleanup and prepare existing code for addition of new SoC.
ARM: dts: define clock binding for bcm21664
clk: bcm21664: use common clock framework
ARM: dts: use real clocks for bcm21664
Add support for the bcm21664 SoC.
.../devicetree/bindings/clock/bcm-kona-clock.txt | 116 +++++---
arch/arm/boot/dts/bcm21664.dtsi | 190 ++++++++-----
drivers/clk/bcm/Kconfig | 2 +-
drivers/clk/bcm/Makefile | 1 +
drivers/clk/bcm/clk-bcm21664.c | 290 ++++++++++++++++++++
drivers/clk/bcm/clk-bcm281xx.c | 12 -
include/dt-bindings/clock/bcm21664.h | 62 +++++
include/dt-bindings/clock/bcm281xx.h | 12 +
8 files changed, 565 insertions(+), 120 deletions(-)
create mode 100644 drivers/clk/bcm/clk-bcm21664.c
create mode 100644 include/dt-bindings/clock/bcm21664.h
--
1.7.9.5
next reply other threads:[~2014-02-28 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 13:49 Alex Elder [this message]
2014-02-28 13:49 ` [PATCH 1/5] clk: bcm281xx: move compatible string definitions Alex Elder
2014-02-28 13:49 ` [PATCH 2/5] ARM: dts: revise kona clock binding document Alex Elder
2014-02-28 13:49 ` [PATCH 3/5] ARM: dts: define clock binding for bcm21664 Alex Elder
2014-02-28 13:49 ` [PATCH 4/5] clk: bcm21664: use common clock framework Alex Elder
2014-02-28 13:49 ` [PATCH 5/5] ARM: dts: use real clocks for bcm21664 Alex Elder
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=1393595371-3789-1-git-send-email-elder@linaro.org \
--to=elder@linaro.org \
--cc=bcm@fixthebug.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@linaro.org \
--cc=mturquette@linaro.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).