Chirantan, On Tue, Jun 3, 2014 at 11:48 AM, Chirantan Ekbote <chirantan@xxxxxxxxxxxx> wrote: > Unfortunately on some exynos systems, resetting the mct counter also > resets the architected timer counter. This can cause problems if the > architected timer driver has already been initialized because the kernel > will think that the counter has wrapped around, causing a big jump in > printk timestamps and delaying any scheduled clock events until the > counter reaches the value it had before it was reset. > > The kernel code makes no assumptions about the initial value of the mct > counter so there is no reason from a software perspective to clear the > counter before starting it. This also fixes the problems described in > the previous paragraph. > > Cc: Olof Johansson <olof@xxxxxxxxx> > Cc: Doug Anderson <dianders@xxxxxxxxxxxx> > Cc: Kukjin Kim <kgene.kim@xxxxxxxxxxx> > Cc: Tomasz Figa <tomasz.figa@xxxxxxxxx> > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Cc: linux-samsung-soc@xxxxxxxxxxxxxxx > Signed-off-by: Chirantan Ekbote <chirantan@xxxxxxxxxxxx> > --- > drivers/clocksource/exynos_mct.c | 9 +++------ > 1 file changed, 3 insertions(+), 6 deletions(-) I can confirm that this fixes problems I described in <http://www.spinics.net/lists/linux-samsung-soc/msg29085.html>. Now when I boot there's no mysterious delay and there's no big jump in time. I'd love to see this in 3.16 so we can get rid of this annoying delay. Reviewed-by: Doug Anderson <dianders@xxxxxxxxxxxx> Tested-by: Doug Anderson <dianders@xxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |