Re: [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later

* Kevin Hilman khil...@ti.com [110623 09:56]: Tony Lindgren t...@atomide.com writes: There's no need to initialize the dmtimer framework early. Actually, there is, because it's being used from the early code. The sys_timer.init functions are called before arch_initcalls, so before

Re: [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later

* Kevin Hilman khil...@ti.com [110623 10:08]: Tony Lindgren t...@atomide.com writes: There's no need to initialize the dmtimer framework early. Just mark the clocksource and timesource as reserved, and initialize dmtimer with an arch_initcall. Signed-off-by: Tony Lindgren

Re: [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later

* Tony Lindgren t...@atomide.com [110627 00:46]: * Kevin Hilman khil...@ti.com [110623 10:08]: Tony Lindgren t...@atomide.com writes: There's no need to initialize the dmtimer framework early. Just mark the clocksource and timesource as reserved, and initialize dmtimer with an

Re: [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later

Tony Lindgren t...@atomide.com writes: * Kevin Hilman khil...@ti.com [110623 09:56]: Tony Lindgren t...@atomide.com writes: There's no need to initialize the dmtimer framework early. Actually, there is, because it's being used from the early code. The sys_timer.init functions are

Re: [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later

Tony Lindgren t...@atomide.com writes: There's no need to initialize the dmtimer framework early. Actually, there is, because it's being used from the early code. The sys_timer.init functions are called before arch_initcalls, so before omap_dm_timer_init() is called, you have:

Re: [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later

Tony Lindgren t...@atomide.com writes: There's no need to initialize the dmtimer framework early. Just mark the clocksource and timesource as reserved, and initialize dmtimer with an arch_initcall. Signed-off-by: Tony Lindgren t...@atomide.com Reviewed-by: Kevin Hilman khil...@ti.com Also,

[PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later

There's no need to initialize the dmtimer framework early. Just mark the clocksource and timesource as reserved, and initialize dmtimer with an arch_initcall. Signed-off-by: Tony Lindgren t...@atomide.com Reviewed-by: Kevin Hilman khil...@ti.com --- arch/arm/mach-omap1/timer32k.c|

[PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later

There's no need to initialize the dmtimer framework early. Just mark the clocksource and timesource as reserved, and initialize dmtimer with an arch_initcall. Signed-off-by: Tony Lindgren t...@atomide.com --- arch/arm/mach-omap1/timer32k.c|4 arch/arm/mach-omap2/timer-gp.c