From: Thomas Gleixner <tglx@linutronix.de>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
johnstul@us.ibm.com, lethal@linux-sh.org, mingo@redhat.com
Subject: Re: [RESEND][PATCH] clockevent: let set_mode() setup delta information
Date: Fri, 16 Jan 2009 12:28:09 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0901161227480.3400@localhost.localdomain> (raw)
In-Reply-To: <20090116081438.12388.15130.sendpatchset@rx1.opensource.se>
On Fri, 16 Jan 2009, Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
>
> Allow the set_mode() clockevent callback to decide and fill in delta
> details such as shift, mult, max_delta_ns and min_delta_ns.
>
> With this change the clockevent can be registered without delta details
> which allows us to keep the parent clock disabled until the clockevent
> gets setup using set_mode().
>
> Letting set_mode() fill in or update delta details allows us to save
> power by disabling the parent clock while the clockevent is unused.
> This may however make the parent clock rate change, so next time the
> clockevent gets enabled we need let set_mode() to update the detla
> details accordingly. Doing it at registration time is not enough.
>
> Furthermore, the delta details seem unused in the case of periodic-only
> clockevent drivers, so this change also allows registration of such
> drivers without the delta details filled in.
>
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
Applied to tip/timers/clockevents
Thanks,
tglx
prev parent reply other threads:[~2009-01-16 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 8:14 Magnus Damm
2009-01-16 11:28 ` Thomas Gleixner [this message]
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=alpine.LFD.2.00.0901161227480.3400@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome