On Mon, Jan 28, 2013 at 07:37:55PM +0100, Stephen Warren wrote: > On 01/27/2013 03:17 PM, Lucas Stach wrote: > > The USB clocks are just clock gates, so no need to set a specific clock. > > In fact trying to set a specific clock is just a NOP if the requested > > clockrate is the same as those of the parent (clk_m) or will trigger a > > WARN_ON() if rates don't match up. > > > > As we are not setting a specific rate, nor activating the clocks at > > init, there is no point in keeping the the usb entries in the clock init > > table. > > I'm not convinced here; aren't the USB clocks supposed to be driven by > PLL U? > > Prashant, Peter, Venu, can you please comment here. According to our downstream code, they are indeed just clockgates with clk_m as the parent. I couldn't find any confirmation in the TRM though. Cheers, Peter. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
