On Tue, 18 Jan 2011 12:36:26 -0700 (MST) Paul Walmsley <paul@xxxxxxxxx> wrote: > This is due to the recent ARM init_sched_clock() changes and the late > initialization of the counter_32k clock source. More information here: > > http://marc.info/?l=linux-omap&m=129513468605208&w=2 > > Fix by initializing the counter_32k clocksource during the machine timer > initialization. > > Reported-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> > Tested-by: Thomas Weber <weber@xxxxxxxxxxxxx> > Signed-off-by: Paul Walmsley <paul@xxxxxxxxx> > --- Thanks Paul. My tested-by is late as this in already in your pull request but wanted to comment that this makes the mainline working on omap3 after commit 211baa7 "ARM: sched_clock: allow init_sched_clock() to be called early" -- Jarkko -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
