[PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later
From: tony@atomide.com (Tony Lindgren)
Date: 2011-06-27 07:51:02
Also in:
linux-omap
Possibly related (same subject, not in this thread)
- 2011-06-27 · [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later · Kevin Hilman <hidden>
- 2011-06-27 · [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later · tony@atomide.com (Tony Lindgren)
- 2011-06-23 · [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later · Kevin Hilman <hidden>
- 2011-06-20 · [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later · tony@atomide.com (Tony Lindgren)
- 2011-03-28 · [PATCH 07/10] omap2+: Reserve clocksource and timesource and initialize dmtimer later · tony@atomide.com (Tony Lindgren)
* Kevin Hilman [off-list ref] [110623 10:08]:
Tony Lindgren [off-list ref] writes:quoted
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 <tony@atomide.com> Reviewed-by: Kevin Hilman <redacted>Also, when you are able to fully get rid of omap_dm_timer_init(), you can probably remove it from dmtimer.h and make it static in dmtimer.c
Good catch. That can be made static now. Tony