From: Yoshihiro Shimoda <shimoda.yoshihiro@renesas.com>
To: linux-sh@vger.kernel.org
Subject: [PATCH] sh: fix clock for sh7785
Date: Wed, 10 Jun 2009 05:35:22 +0000 [thread overview]
Message-ID: <4A2F461A.8080506@renesas.com> (raw)
Signed-off-by: Yoshihiro Shimoda <shimoda.yoshihiro@renesas.com>
---
Could you apply this patch to linux-2.6.30?
If impossible, this patch is not necessary because clock-sh7785.c will modify
in linux-2.6.31.
arch/sh/kernel/cpu/sh4a/clock-sh7785.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff -uprN a/arch/sh/kernel/cpu/sh4a/clock-sh7785.c b/arch/sh/kernel/cpu/sh4a/clock-sh7785.c
--- a/arch/sh/kernel/cpu/sh4a/clock-sh7785.c
+++ b/arch/sh/kernel/cpu/sh4a/clock-sh7785.c
@@ -26,7 +26,9 @@ static int pfc_divisors[] = { 1, 1, 1, 1
static void master_clk_init(struct clk *clk)
{
- clk->rate *= pfc_divisors[ctrl_inl(FRQMR1) & 0x000f];
+ unsigned long frqmr1 = ctrl_inl(FRQMR1);
+
+ clk->rate = CONFIG_SH_PCLK_FREQ * pfc_divisors[frqmr1 & 0x000f];
}
static struct clk_ops sh7785_master_clk_ops = {
next reply other threads:[~2009-06-10 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 5:35 Yoshihiro Shimoda [this message]
2009-06-10 10:55 ` [PATCH] sh: fix clock for sh7785 Magnus Damm
2009-06-11 1:37 ` Yoshihiro Shimoda
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=4A2F461A.8080506@renesas.com \
--to=shimoda.yoshihiro@renesas.com \
--cc=linux-sh@vger.kernel.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