> > >
> > > What happens if you start putting a different PHY on the board, one
> > > that takes longer to enter low-power mode?
> >
> > A little difficult to change a PHY on the board.
> >
> > Just like I said above, it depends on when the hardware enables wake on
> > disconnect, full-speed idle
On Wed, 29 Jan 2014, Peter Chen wrote:
> On Tue, Jan 28, 2014 at 11:32:28AM -0500, Alan Stern wrote:
> > On Tue, 28 Jan 2014, Peter Chen wrote:
> >
> > > > It sounds like this is a bug in your EHCI hardware. The
> > > > wake-on-disconnect logic should never take effect until after the port
> > >
On Tue, Jan 28, 2014 at 11:32:28AM -0500, Alan Stern wrote:
> On Tue, 28 Jan 2014, Peter Chen wrote:
>
> > > It sounds like this is a bug in your EHCI hardware. The
> > > wake-on-disconnect logic should never take effect until after the port
> > > goes into full-speed idle.
> >
> > Where EHCI sp
On Tue, 28 Jan 2014, Peter Chen wrote:
> > It sounds like this is a bug in your EHCI hardware. The
> > wake-on-disconnect logic should never take effect until after the port
> > goes into full-speed idle.
>
> Where EHCI spec said that? I can't find it at 2.3.9 and 4.3.
It doesn't say that. Not
On Mon, Jan 27, 2014 at 10:52:48AM -0500, Alan Stern wrote:
> On Mon, 27 Jan 2014, Peter Chen wrote:
>
> > If the high-speed device does not enter full-speed idle after
> > wakeup on disconnect logic has effected, there will be an
> > unexpected disconnect wakeup interrupt due to the bus is still
On Mon, 27 Jan 2014, Peter Chen wrote:
> If the high-speed device does not enter full-speed idle after
> wakeup on disconnect logic has effected, there will be an
> unexpected disconnect wakeup interrupt due to the bus is still SE0.
I think you mean "If the high-speed device does not enter full-s
