On Mon, 21 Oct 2013, Mike Turquette wrote: > Quoting Paul Walmsley (2013-10-19 10:16:50) > > On Fri, 11 Oct 2013, Tero Kristo wrote: > > > > > Some drivers require direct access to the autoidle functionality of the > > > interface clocks. Added clock APIs for these, so that the drivers do not > > > need to access CM registers directly. > > > > > > Signed-off-by: Tero Kristo <t-kristo@xxxxxx> > > > > Thanks, queued. Please coordinate with Mike to get > > allow_idle/deny_idle-type interfaces into the Common Clock Framework, so > > these can be replaced with standard CCF-type allow_idle() & deny_idle() > > functions. That interface should include use-counting so multiple callers > > can use allow_idle() and deny_idle() without stomping on each other. > > Where and when are these functions called? IIRC these are only accessed > at boot/init time, though I may be wrong. If they are a boot-time thing > then the .init callback provided in struct clk may be sufficient. They are called dynamically at runtime when the McBSP goes active and inactive. It's in the next patch in this series. I'm fairly sure at least one other IP block needs this workaround also. - 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
