Hi,
On Friday 13 April 2012 02:09 PM, Paul Walmsley wrote:
Hi Archit,
On Fri, 13 Apr 2012, Archit Taneja wrote:
There were still some issues related to this, particularly on OMAP4, I have
posted a patch set to fix this just a while back.
Was looking at those. The first one, removing the OCPIF_SWSUP_IDLE flags,
makes sense to me. But as far as the second one goes, it would be nice if
we could use interface clocks again for interfaces, rather than functional
clocks. That's the root cause of the problem... Looks like this was added
in commit da7cdfac1b0c58d6863532dd3b432c3fbc034978. Maybe this is needed
because we don't properly enable parent hwmods before the dependent child
hwmods?
Yes, you are right. As you and Benoit in the other thread explained, if
we get the parent-child dependency right, we could switch back to using
l3_div interface clock.
Thanks,
Archit
- Paul
--
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
