Messages in this thread | | | Date | Sun, 22 May 2011 22:18:01 -0700 | Subject | Re: [PATCH v2] ARM: smp_twd: Reconfigure clockevents after cpufreq change | From | Colin Cross <> |
| |
On Fri, May 20, 2011 at 11:29 PM, Santosh Shilimkar <santosh.shilimkar@ti.com> wrote: > 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. >> >> Change-Id: I413b5cd07fb2b79bc9fad8b4bf257332d1da7bcd >> Signed-off-by: Colin Cross<ccross@android.com> >> Cc: Thomas Gleixner<tglx@linutronix.de> >> Cc: Russell King<linux@arm.linux.org.uk> >> Cc: Santosh Shilimkar<santosh.shilimkar@ti.com> >> Cc: Rob Herring<robherring2@gmail.com> >> Tested-by: Linus Walleij<linus.walleij@linaro.org> >> --- > > Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com> > > 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |