> From: Russell King - ARM Linux [mailto:linux@xxxxxxxxxxxxxxxx] > Sent: Saturday, January 15, 2011 5:38 PM > Why does OMAP initialize its clock sources soo late, outside of > the timer initialization? This means you have no counter in place > (except for the jiffies counter) during early boot. > > Is there a reason why OMAP uniquely does this? Not any good reason. I'm aware of historic porting issue and the missed/hidden need for early init for some time services. 1st attempts to do really early init (like 7 years back) were messed as not all kernel services used to be available when the time early time init functions happened. It was hidden because u-boot had already turned on the same clock the kernel level driver used. So there was no failure (until the kernel used something else). Recurring breaks & fixes happened to out of trees as owners changed. The mainline never enabled driver till recently. Regards, Richard W. -- 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
