On Fri, 15 Jun 2012, Jon Hunter wrote: > On 06/14/2012 03:31 PM, Paul Walmsley wrote: > > > Sorry to make you change this, but how about adding the optional clock > > aliases to the hwmod data instead? > > Yes, we can do. However, technically these are not optional clocks but > parents clocks. So if you are ok with that we can.
OK. The hwmod optional clocks weren't intended to map directly to the OMAP4 notion of optional clocks. But sounds like this would require a bit more thought. So let's go with your original patch. Will ack it after sending this. > Ok, but what it not clear to me is how I retrieve the clock handle from > the driver. Is there an API I can use to retrieve the optional clocks > using the device structure? In other words, similar to clk_get()? It works via clk_get(), so using the hwmod optional clocks would require no driver changes. - Paul -- 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
