On Mon, 2011-06-06 at 14:56 +0200, Cousson, Benoit wrote: > That terminology in the PRCM just means that an opt clock will not be > handled automatically by the PRCM and will require SW control. > This is not the case for mandatory clock. Upon module enable the PRCM > will ensure that all mandatory clocks (functional and interface) are > enabled automagically. If the clock is marked as optional it means that > the SW will have to enable it explicitly before enabling the module. Is that correct? This would mean that whenever a hwmod has opt clock, it needs to implement similar hack functions that are present in this patch, to be able to enable the opt clock before enabling the hwmod, and to disable the opt clock after disabling the hwmod. I'd rather hope the optional clock could be enabled whenever the driver needs it, between enabling and disabling the hwmod. If it's required that the opt clocks are enabled before enabling the hwmod, what is the point of having them as optional and driver controlled? The hwmod fmwk could as well handle the opt clocks in that case. Tomi -- 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
