On Thu, Jan 22, 2009 at 05:17:28PM -0800, Tony Lindgren wrote: > Basically we currently cannot use virtual clocks because of this > and the fact that the parent of the virtual clock may not be known > as pointed out by Paul Walmsley. One other thing I'd like to confirm is how the kernel treats the OMAP5912. OMAP5912 is interesting to me at the moment because it seems that all the information on it is freely available. I don't know about the others. However, it would be useful to know how the kernel treats this - iow, which of the four categories for OMAP1 SoCs - 310, 730, 1510, 1610. Of course, if someone knows (or can send me, maybe Richard W?) where there's a similar document to spru751a for the clock architecture for these other CPUs (and OMAP2420, OMAP2430, OMAP3430, etc) it would be most useful. -- 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
