Re: USB resume issue

2015-12-02 Thread Alan Stern
On Tue, 1 Dec 2015, Alan Cooper wrote: > I agree that for USB suspend modes, VBUS must be on, and our hardware > behaves that way for runtime suspend. The question is for system wide > suspend (S3/STR) can the system shut down the USB hardware entirely. Oh, okay, I misunderstood. > The ACPI

Re: USB resume issue

2015-12-01 Thread Alan Stern
On Tue, 1 Dec 2015, Alan Cooper wrote: > On Tue, Dec 1, 2015 at 2:35 PM, Alan Stern wrote: > >> I'm now sure the host in "non-compliant". > > > > It is non-compliant if it turns off Vbus power during suspend. But > > that may be caused by the platform more than by the

Re: USB resume issue

2015-12-01 Thread Alan Cooper
On Tue, Dec 1, 2015 at 2:35 PM, Alan Stern wrote: >> I'm now sure the host in "non-compliant". > > It is non-compliant if it turns off Vbus power during suspend. But > that may be caused by the platform more than by the controller itself. > I wasn't able to find any

Re: USB resume issue

2015-12-01 Thread Alan Cooper
On Tue, Dec 1, 2015 at 4:48 PM, Alan Stern wrote: > On Tue, 1 Dec 2015, Alan Cooper wrote: > >> On Tue, Dec 1, 2015 at 2:35 PM, Alan Stern wrote: >> >> I'm now sure the host in "non-compliant". >> > >> > It is non-compliant if it turns off

Re: USB resume issue

2015-12-01 Thread Alan Cooper
On Tue, Dec 1, 2015 at 11:07 AM, Alan Stern wrote: > On Tue, 1 Dec 2015, Oliver Neukum wrote: > >> On Tue, 2015-12-01 at 10:41 -0500, Alan Stern wrote: >> > > A recent patch, 7fa40910e0bf5ef32eca49595d950cb24f6402bf, added a >> > > CONNECTED retry for a different reason

Re: USB resume issue

2015-12-01 Thread Alan Cooper
On Tue, Dec 1, 2015 at 12:12 PM, Alan Cooper wrote: > On Tue, Dec 1, 2015 at 11:07 AM, Alan Stern wrote: >> On Tue, 1 Dec 2015, Oliver Neukum wrote: >> >>> On Tue, 2015-12-01 at 10:41 -0500, Alan Stern wrote: >>> > > A recent patch,

Re: USB resume issue

2015-12-01 Thread Alan Stern
On Tue, 1 Dec 2015, Alan Cooper wrote: > On Tue, Dec 1, 2015 at 11:07 AM, Alan Stern wrote: > > On Tue, 1 Dec 2015, Oliver Neukum wrote: > > > >> On Tue, 2015-12-01 at 10:41 -0500, Alan Stern wrote: > >> > > A recent patch, 7fa40910e0bf5ef32eca49595d950cb24f6402bf,

Re: USB resume issue

2015-12-01 Thread Alan Stern
On Mon, 30 Nov 2015, Alan Cooper wrote: > I'm seeing a problem that looks like an issue in the USB-Persist > feature. I'm finding that all my 3.0 thumb drives are torn down and > brought back up (fail USB-Persist) during resume from "suspend to > memory" if they are plugged into a 2.0 EHCI/OHCI

Re: USB resume issue

2015-12-01 Thread Oliver Neukum
On Tue, 2015-12-01 at 10:41 -0500, Alan Stern wrote: > > A recent patch, 7fa40910e0bf5ef32eca49595d950cb24f6402bf, added a > > CONNECTED retry for a different reason and I could simply increase > > this retry time. Any thoughts? > > I don't know. You've got a non-compliant host combined with an

Re: USB resume issue

2015-12-01 Thread Alan Stern
On Tue, 1 Dec 2015, Oliver Neukum wrote: > On Tue, 2015-12-01 at 10:41 -0500, Alan Stern wrote: > > > A recent patch, 7fa40910e0bf5ef32eca49595d950cb24f6402bf, added a > > > CONNECTED retry for a different reason and I could simply increase > > > this retry time. Any thoughts? > > > > I don't

USB resume issue

2015-11-30 Thread Alan Cooper
I'm seeing a problem that looks like an issue in the USB-Persist feature. I'm finding that all my 3.0 thumb drives are torn down and brought back up (fail USB-Persist) during resume from "suspend to memory" if they are plugged into a 2.0 EHCI/OHCI only port on my embedded system. This embedded