From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] imx6q clk device tree lookup
Date: Tue, 11 Sep 2012 20:02:48 +0800 [thread overview]
Message-ID: <1347364968-27496-3-git-send-email-shawn.guo@linaro.org> (raw)
In-Reply-To: <1347364968-27496-1-git-send-email-shawn.guo@linaro.org>
The following changes since commit fea7a08acb13524b47711625eebea40a0ede69a0:
Linux 3.6-rc3 (2012-08-22 13:29:06 -0700)
are available in the git repository at:
git://git.linaro.org/people/shawnguo/linux-2.6.git tags/imx-clk-dt-lookup
for you to fetch changes up to 0e87e0436c0cc3954eb62181a96d7217ca955a4f:
ARM: imx6q: replace clk_register_clkdev with clock DT lookup (2012-09-11 19:16:14 +0800)
----------------------------------------------------------------
imx-clk-dt-lookup
It replaces the clk_register_clkdev in imx6q clock driver with DT
lookup. It depends on Mike's clk-3.7 branch.
When it gets merged together with imx-dt-3.7, there is a trivial
conflict on arch/arm/boot/dts/imx6q.dtsi.
----------------------------------------------------------------
Shawn Guo (1):
ARM: imx6q: replace clk_register_clkdev with clock DT lookup
.../devicetree/bindings/clock/imx6q-clock.txt | 222 ++++++++++++++++++++
arch/arm/boot/dts/imx6q-sabrelite.dts | 1 +
arch/arm/boot/dts/imx6q.dtsi | 73 ++++++-
arch/arm/mach-imx/clk-imx6q.c | 44 +---
arch/arm/mach-imx/mach-imx6q.c | 1 -
5 files changed, 291 insertions(+), 50 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/imx6q-clock.txt
next prev parent reply other threads:[~2012-09-11 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 12:02 [GIT PULL 0/2] imx device tree changes for 3.7 Shawn Guo
2012-09-11 12:02 ` [GIT PULL 1/2] imx device tree changes Shawn Guo
2012-09-13 6:22 ` Olof Johansson
2012-09-13 6:37 ` Shawn Guo
2012-09-11 12:02 ` Shawn Guo [this message]
2012-09-13 6:23 ` [GIT PULL 2/2] imx6q clk device tree lookup Olof Johansson
2012-09-13 6:38 ` Shawn Guo
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=1347364968-27496-3-git-send-email-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--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).