On Fri, May 20, 2011 at 11:29 PM, Santosh ShilimkarYep. That should be ok.
On 5/20/2011 5:54 AM, Colin Cross wrote:
The localtimer's clock changes with the cpu clock. After a
cpufreq transition, update the clockevent's frequency and
reprogram the next clock event.
Adds a clock called "smp_twd" that is used to determine the
twd frequency, which can also be used at init time to
avoid calibrating the twd frequency.
Clock changes are based on Rob Herring's work.
Signed-off-by: Colin Cross<ccross@xxxxxxxxxxx>
Cc: Thomas Gleixner<tglx@xxxxxxxxxxxxx>
Cc: Russell King<linux@xxxxxxxxxxxxxxxx>
Cc: Santosh Shilimkar<santosh.shilimkar@xxxxxx>
Cc: Rob Herring<robherring2@xxxxxxxxx>
Tested-by: Linus Walleij<linus.walleij@xxxxxxxxxx>
Acked-by: Santosh Shilimkar<santosh.shilimkar@xxxxxx>
What about the clock-node patches?
Do you want those to get merged via sub-arch tree's once this
patch + Thomas's new API gets merged ?
The clock-node patches can be merged independently - twd scaling just
won't work until they are both merged.