> Virtual clocks should soon be eliminated from the OMAP clock tree. ( > "Virtual clocks" is here used to refer a clock that does not have a > referent in the hardware; the usage of the term in the code is loose.) > So far as I know, all of the OMAP virtual clocks have either turned out to > be superfluous (and prone to spinlock recursion bugs), or to be better > implemented outside of the clock framework (such as the virtual OPP > clocks). We've eliminated the former. We should be able to eliminate the > latter in a few months.
What is your idea for replacement of virtual OPPs? Especially on OMAP2 they were useful with tightly coupled clock sets. Some later versions of 2420 were characterized such that some of the dependencies could be ignored but that is not the case for all of them. The centerline design as I understand it wasn't for this. It just happened that enough margin was there in some binn'ed lots to do this. Regards, Richard W. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
