From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ARM: shmobile: r8a7740: add CMT1 clock support for DT
Date: Thu, 24 Jul 2014 10:57:41 +0900 [thread overview]
Message-ID: <2e11179da78a56c2a44fc3fe097f2af8dc18f9d6.1406164563.git.horms+renesas@verge.net.au> (raw)
In-Reply-To: <cover.1406164563.git.horms+renesas@verge.net.au>
This will be used when initialising CMT1 device using DT
until common clock framework support is added.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/mach-shmobile/clock-r8a7740.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-shmobile/clock-r8a7740.c b/arch/arm/mach-shmobile/clock-r8a7740.c
index 3f34b3f..2ffb560 100644
--- a/arch/arm/mach-shmobile/clock-r8a7740.c
+++ b/arch/arm/mach-shmobile/clock-r8a7740.c
@@ -602,6 +602,7 @@ static struct clk_lookup lookups[] = {
CLKDEV_ICK_ID("fck", "sh-tmu.0", &mstp_clks[MSTP125]),
CLKDEV_ICK_ID("fck", "fff80000.timer", &mstp_clks[MSTP125]),
CLKDEV_ICK_ID("fck", "sh-cmt-48.1", &mstp_clks[MSTP329]),
+ CLKDEV_ICK_ID("fck", "e6138000.timer", &mstp_clks[MSTP329]),
CLKDEV_ICK_ID("host", "renesas_usbhs", &mstp_clks[MSTP416]),
CLKDEV_ICK_ID("func", "renesas_usbhs", &mstp_clks[MSTP407]),
CLKDEV_ICK_ID("phy", "renesas_usbhs", &mstp_clks[MSTP406]),
--
2.0.1
next prev parent reply other threads:[~2014-07-24 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 1:57 [GIT PULL] Third Round of Renesas ARM Based SoC Clock Updates for v3.17 Simon Horman
2014-07-24 1:57 ` [PATCH 1/5] ARM: shmobile: r8a7778: add TMU clock support for DT Simon Horman
2014-07-24 1:57 ` [PATCH 2/5] ARM: shmobile: r8a7740: " Simon Horman
2014-07-24 1:57 ` [PATCH 3/5] ARM: shmobile: r8a73a4: add CMT1 " Simon Horman
2014-07-24 1:57 ` Simon Horman [this message]
2014-07-24 1:57 ` [PATCH 5/5] ARM: shmobile: sh73a0: " Simon Horman
2014-07-30 19:43 ` [GIT PULL] Third Round of Renesas ARM Based SoC Clock Updates for v3.17 Olof Johansson
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=2e11179da78a56c2a44fc3fe097f2af8dc18f9d6.1406164563.git.horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--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).