On Thu, 13 Sep 2012, Benoit Cousson wrote: > In this case, the ocp2scp IP is just the *bus controller* to access the > real USB_UTMI_PHY IP. > > The TRM diagram does not show that level of detail unfortunately. You > can check the PRCM spec (Figure 78 : CD_L3_INIT_USB clock scheme) to see > the two modules. > > So considering phy_48m as the main clock is still correct for the > ocp2scp IP. > > The INIT_960M_FCLK will be a fck associated with the child of the > ocp2scp nodes which is the usb_phy. > > Upgrading the opt_clk to fck does make sense as soon as we don't have > any other functional clock and as soon as this clock is *mandatory*. The > optional aspect in that case is just a wrong PRCM naming for a clock > that is mandatory. It is similar to the DSS case that does have only > optional clocks that are mandatory. > > I do agree that we must stick to the HW definition as far as we can. But > the optional attribute is something that is wrong/inaccurate for a > couple of IPs. HW folks agreed on that point and will fix that in the > future. Okay so is this an Acked-by for this patch? :-) If so I'll take it. - 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
