* Joel Fernandes <[email protected]> [140422 18:27]: > Add a comment describing the state of system timer clock parenting. The code > following the comment should be deleted once all platforms can do DT boot, and > specially should not be executed for DT platforms once we can specify default > clock parents through DT.
I think we can do it already for DT based booting? Regards, Tony > Signed-off-by: Joel Fernandes <[email protected]> > --- > arch/arm/mach-omap2/timer.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/arch/arm/mach-omap2/timer.c b/arch/arm/mach-omap2/timer.c > index f192a41..9fdff5b 100644 > --- a/arch/arm/mach-omap2/timer.c > +++ b/arch/arm/mach-omap2/timer.c > @@ -313,6 +313,10 @@ static int __init omap_dm_timer_init_one(struct > omap_dm_timer *timer, > if (IS_ERR(timer->fclk)) > return PTR_ERR(timer->fclk); > > + /* > + * Clock reparenting code, goes away for DT-boot atleast, > + * once clock layer can do it through DT. > + */ > src = clk_get(NULL, fck_source); > if (IS_ERR(src)) > return PTR_ERR(src); > -- > 1.7.9.5 > -- 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/
