Hi Paul, On 2/23/2011 8:11 AM, Paul Walmsley wrote: > Hello, > > This series adds the ability to late-initialize individual > hwmods. The goal here is for clockevent (and eventually > clocksource) hwmods to be late-initialized individually, and > right before they are needed, in the timer init code. Then > omap_hwmod_late_init(), which late-inits the rest of the hwmods, > is intended to run as an initcall -- much later in the boot > process. > > This series includes the OMAP2/3 hwmod data for the GPTIMERs that > Tarun posted earlier. This data is necessary for this new code > to avoid warnings during boot. > > Boot-tested on N800, OMAP34xx Beagleboard and OMAP4430ES2 Panda. I'm testing it on 4430sdp, and I have the following warning: [ 0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck. [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: at arch/arm/mach-omap2/timer-gp.c:157 omap2_gp_timer_init+0x80/0x190() [ 0.000000] timer-gp: omap_dm_timer_set_source() failed [ 0.000000] Modules linked in: [ 0.000000] [<c0062a6c>] (unwind_backtrace+0x0/0xec) from [<c009422c>] (warn_slowpath_common+0x4c/0x64) [ 0.000000] [<c009422c>] (warn_slowpath_common+0x4c/0x64) from [<c00942c4>] (warn_slowpath_fmt+0x2c/0x3c) [ 0.000000] [<c00942c4>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0010e30>] (omap2_gp_timer_init+0x80/0x190) [ 0.000000] [<c0010e30>] (omap2_gp_timer_init+0x80/0x190) from [<c000c0dc>] (time_init+0x20/0x30) [ 0.000000] [<c000c0dc>] (time_init+0x20/0x30) from [<c0008cbc>] (start_kernel+0x1a4/0x30c) [ 0.000000] [<c0008cbc>] (start_kernel+0x1a4/0x30c) from [<80008038>] (0x80008038) [ 0.000000] ---[ end trace 1b75b31a2719ed1c ]--- [ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz Regards, Benoit -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
