Re: [RESEND][PATCH] clockevent: let set_mode() setup deltainformation

From: Thomas Gleixner
Date: Fri Jan 16 2009 - 06:28:53 EST

On Fri, 16 Jan 2009, Magnus Damm wrote:
> From: Magnus Damm <damm@xxxxxxxxxx>
> 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@xxxxxxxxxx>

Applied to tip/timers/clockevents


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at