On Wed, 3 Sep 2014, Felipe Balbi wrote:
> > > On the other hand, core.c:dwc3_remove() doesn't call
> > > dwc3_core_exit_mode() until after doing a lot of other things.
> > > Shouldn't it call dwc3_core_exit_mode() first?
> >
> > yup. At least the PHYs still need to the be alive for as long as
HI,
On Wed, Sep 03, 2014 at 03:47:16PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Wed, Sep 03, 2014 at 04:41:34PM -0400, Alan Stern wrote:
> > On Wed, 3 Sep 2014, Felipe Balbi wrote:
> >
> > > Hi,
> > >
> > > I've been tracking down two issues and one of them seems to be a problem
> > > with eithe
Hi,
On Wed, Sep 03, 2014 at 04:41:34PM -0400, Alan Stern wrote:
> On Wed, 3 Sep 2014, Felipe Balbi wrote:
>
> > Hi,
> >
> > I've been tracking down two issues and one of them seems to be a problem
> > with either usbcore or xhci.
> >
> > DWC3, when acting as host, instantiates an xhci platform-
On Wed, 3 Sep 2014, Felipe Balbi wrote:
> Hi,
>
> I've been tracking down two issues and one of them seems to be a problem
> with either usbcore or xhci.
>
> DWC3, when acting as host, instantiates an xhci platform-device and sets
> itself as the parent of that. That's all fine and dandy until I
