On Mon, Dec 12, 2011 at 11:47:30AM +0200, Felipe Balbi wrote:
> Yeah, but what I meant by that is that struct usb_phy would have a
> struct usb_otg field, not just a pointer to struct usb_otg. Something
> like:
>
> struct usb_otg {
> unsigned a,b,c;
> };
>
> struct usb_phy {
> struct usb_otg otg;
> };
Uh.. We should have talked about this earlier. My fault. You want
the phy to be always available. I would prefer to have the chance to be
able to use otg even if there is no phy driver at all. When we have
USB2 with UTMI+ controller, there is no need to have phy driver. This
configuration is however completely OTG capable. The "otg driver" will
only deal with the controller.
This would mean that the events would again be part of OTG, not PHY.
--
heikki
--
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
