From: Paul Mundt <lethal@linux-sh.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] clocksource: sh_tmu: __clocksource_updatefreq_hz() update
Date: Mon, 23 May 2011 05:38:09 +0000 [thread overview]
Message-ID: <20110523053808.GG5206@linux-sh.org> (raw)
In-Reply-To: <1304024143.2971.106.camel@work-vm>
On Thu, Apr 28, 2011 at 01:55:43PM -0700, john stultz wrote:
> On Mon, 2011-04-25 at 22:38 +0900, Magnus Damm wrote:
> > From: Magnus Damm <damm@opensource.se>
> >
> > This patch updates the clocksource part of the TMU driver
> > to make use of the __clocksource_updatefreq_hz() function.
> >
> > Without this patch the old code uses clocksource_register()
> > together with a hack that assumes a never changing clock rate
> > (see clk_enable(), clk_get_rate() and clk_disable()).
> >
> > The patch uses clocksource_register_hz() with 1 Hz as initial
> > value, then lets the ->enable() callback update the value
> > with __clocksource_updatefreq_hz() once the struct clk has
> > been enabled and the frequency is stable.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Acked-by: John Stultz <johnstul@us.ibm.com>
>
> If these don't get picked up for 2.6.40, I'll queue them myself.
>
I've queued them all now, with your Acks, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] clocksource: sh_tmu: __clocksource_updatefreq_hz() update
Date: Mon, 23 May 2011 14:38:09 +0900 [thread overview]
Message-ID: <20110523053808.GG5206@linux-sh.org> (raw)
In-Reply-To: <1304024143.2971.106.camel@work-vm>
On Thu, Apr 28, 2011 at 01:55:43PM -0700, john stultz wrote:
> On Mon, 2011-04-25 at 22:38 +0900, Magnus Damm wrote:
> > From: Magnus Damm <damm@opensource.se>
> >
> > This patch updates the clocksource part of the TMU driver
> > to make use of the __clocksource_updatefreq_hz() function.
> >
> > Without this patch the old code uses clocksource_register()
> > together with a hack that assumes a never changing clock rate
> > (see clk_enable(), clk_get_rate() and clk_disable()).
> >
> > The patch uses clocksource_register_hz() with 1 Hz as initial
> > value, then lets the ->enable() callback update the value
> > with __clocksource_updatefreq_hz() once the struct clk has
> > been enabled and the frequency is stable.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Acked-by: John Stultz <johnstul@us.ibm.com>
>
> If these don't get picked up for 2.6.40, I'll queue them myself.
>
I've queued them all now, with your Acks, thanks.
next prev parent reply other threads:[~2011-05-23 5:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 13:38 [PATCH] clocksource: sh_tmu: __clocksource_updatefreq_hz() update Magnus Damm
2011-04-25 13:38 ` Magnus Damm
2011-04-28 20:55 ` [PATCH] clocksource: sh_tmu: __clocksource_updatefreq_hz() john stultz
2011-04-28 20:55 ` [PATCH] clocksource: sh_tmu: __clocksource_updatefreq_hz() update john stultz
2011-05-23 5:38 ` Paul Mundt [this message]
2011-05-23 5:38 ` Paul Mundt
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=20110523053808.GG5206@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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.