All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: sh7724 clock framework rewrite V2
Date: Tue, 09 Jun 2009 08:04:49 +0000	[thread overview]
Message-ID: <aec7e5c30906090104o59d61ef6j64e7da900fdb9026@mail.gmail.com> (raw)
In-Reply-To: <20090602103459.13411.85023.sendpatchset@rx1.opensource.se>

Hi Morimoto-san,

Thanks for checking the patch.

On Mon, Jun 8, 2009 at 7:03 PM, Kuninori
Morimoto<morimoto.kuninori@renesas.com> wrote:
>> This patch contains V2 of the sh7724 clock framework
>> rewrite. The new code makes use of the recently merged
>> div4, div6 and mstp32 helper code. Both extal and fll are
>> supported as input clocks to the pll. The div6 clocks are
>> fed through a divide-by-3 block.
>
>> -     MSTPCR("tmu1", "peripheral_clk", 0, 10, 0),
> (snip)
>> +     MSTP("flctl0", &div4_clks[DIV4_P], MSTPCR0, 10, 0, 1, 0),

Yeah, you are correct.

> I wonder your manual is old one.
> old manual is very bad, and it say lie sometimes.
>
> correct MSTP010 is "tmu1" here

I used the Japanese version of Rev 0.10 for this code, but it contains
"tmu1" for MSTP010.
So this must be my typo. Sorry about that.

I'll repost V3 in the near future. Thank you!

/ magnus

  parent reply	other threads:[~2009-06-09  8:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 10:34 [PATCH] sh: sh7724 clock framework rewrite Magnus Damm
2009-06-03  5:04 ` Kuninori Morimoto
2009-06-03  8:43 ` [PATCH] sh: sh7724 clock framework rewrite V2 Magnus Damm
2009-06-04  7:53 ` [PATCH] sh: sh7724 clock framework rewrite Magnus Damm
2009-06-04  8:08 ` Kuninori Morimoto
2009-06-08 10:03 ` [PATCH] sh: sh7724 clock framework rewrite V2 Kuninori Morimoto
2009-06-09  8:04 ` Magnus Damm [this message]
2009-06-10 11:31 ` [PATCH] sh: sh7724 clock framework rewrite V3 Magnus Damm

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=aec7e5c30906090104o59d61ef6j64e7da900fdb9026@mail.gmail.com \
    --to=magnus.damm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.