From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Highbank clock support using DT
Date: Wed, 16 May 2012 21:02:15 -0500 [thread overview]
Message-ID: <1337220137-31666-1-git-send-email-robherring2@gmail.com> (raw)
From: Rob Herring <rob.herring@calxeda.com>
This series adds clock support to highbank using common clock
infrastructure and DT clock bindings. The DT clock bindings were previously
posted here:
https://lkml.org/lkml/2012/4/9/322
Changes in this version:
- add Documentation for bindings
- rebase to clk-next
- add A9 periphclk divider handling instead of hardcoding
- a fix to the PLL relock sequence
Mike, It's getting a bit late, but I could not get back to this sooner. I
intend to send this and the DT patches by the end of the week.
Rob
Rob Herring (2):
dt: add clock binding doc to primecell bindings
clk: add highbank clock support
.../devicetree/bindings/arm/primecell.txt | 6 +
.../devicetree/bindings/clock/calxeda.txt | 17 +
arch/arm/Kconfig | 1 +
arch/arm/boot/dts/highbank.dts | 91 +++++-
arch/arm/mach-highbank/Makefile | 2 +-
arch/arm/mach-highbank/clock.c | 62 ----
arch/arm/mach-highbank/highbank.c | 7 +
drivers/clk/Makefile | 4 +-
drivers/clk/clk-highbank.c | 345 ++++++++++++++++++++
9 files changed, 470 insertions(+), 65 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/calxeda.txt
delete mode 100644 arch/arm/mach-highbank/clock.c
create mode 100644 drivers/clk/clk-highbank.c
--
1.7.9.5
next reply other threads:[~2012-05-17 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 2:02 Rob Herring [this message]
2012-05-17 2:02 ` [PATCH v2 1/2] dt: add clock binding doc to primecell bindings Rob Herring
2012-05-17 2:02 ` [PATCH v2 2/2] clk: add highbank clock support Rob Herring
2012-05-22 9:45 ` Ben Dooks
2012-05-22 14:04 ` Rob Herring
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=1337220137-31666-1-git-send-email-robherring2@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).