Hi Laurent, On Thu, Jun 18, 2015 at 4:14 PM, Laurent Pinchart <[email protected]> wrote: > On Thursday 18 June 2015 12:22:33 Geert Uytterhoeven wrote: >> Currently the sh_cmt clocksource timer is disabled or enabled >> unconditionally on clocksource suspend resp. resume, even if a better >> clocksource is present (e.g. arch_sys_counter) and the sh_cmt >> clocksource is not enabled.
>> Signed-off-by: Geert Uytterhoeven <[email protected]> > > Good catch. The patch looks good to me. While the solution was simple, it was hard to catch (engineers and lightbulbs... euh timers ;-) > Acked-by: Laurent Pinchart <[email protected]> Thanks! > I've quickly checked the MTU2 and TMU timer drivers and they should be immune > to the issue, but I'd appreciate if you could confirm that. I had concluded the same, thanks for verifying! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
