On Fri, Nov 15, 2013 at 02:21:36AM +0000, Peter Chen wrote:
> > 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?
> >
>
> It is not a USB controller's clock, it is one USB device's clock which
> uses SoC clock at one specific board. Currently, there is only one general
> USB HUB driver, no any special board information in it.
>
> You can also put this special board control at arch/arm/mach-imx/mach-imx6q.c
> if shawn also agree it.
Hmm, I would argue if it can be done in bootloader before kernel has a
proper little driver for it.
Shawn
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
