On Thu, Nov 14, 2013 at 3:10 PM, Michael Grzeschik <[email protected]> wrote:
> So, what I see is an regular Hub that usually got driven by an external
> Crystal of 24MHz. That the boarddesigner did change that to be driven
> by the SoC clock makes your dependency here. We need an location for this,
> but obviously not in the glue.
>
> I could think of an simple bus driver that has i2c, regulator and clock
> dependency in the device tree. But where this got implemented is currently
> undefined.
If on the board file I just do this:
+&usbh1 {
+ vbus-supply = <®_usb_h1_vbus>;
+ clocks = <&clks 201>; /* USB2514 clock comes from mx6 clko2 pin */
+ status = "okay";
+};
+
without touching any kernel code, then the USB hub clock is turned on
and the USB host is functional.
Does this make sense?
Regards,
Fabio Estevam
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
