RE: How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-14 Thread Yoshihiro Shimoda
Hi Alan, > From: Alan Stern > Sent: Wednesday, February 15, 2017 2:57 AM > > On Tue, 14 Feb 2017, Yoshihiro Shimoda wrote: > > > Hi Alan, > > > > > From: Alan Stern > > > Sent: Tuesday, February 14, 2017 1:35 AM > > > > > > On Mon, 13 Feb 2017, Yoshihiro Shimoda wrote: > > > > > > > > Hmmm.

RE: How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-14 Thread Alan Stern
On Tue, 14 Feb 2017, Yoshihiro Shimoda wrote: > Hi Alan, > > > From: Alan Stern > > Sent: Tuesday, February 14, 2017 1:35 AM > > > > On Mon, 13 Feb 2017, Yoshihiro Shimoda wrote: > > > > > > Hmmm. You're using platform drivers for OHCI and EHCI, not PCI, > > > > > > Yes, I'm using platform

RE: How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-14 Thread Yoshihiro Shimoda
Hi Alan, > From: Alan Stern > Sent: Tuesday, February 14, 2017 1:35 AM > > On Mon, 13 Feb 2017, Yoshihiro Shimoda wrote: > > > > Hmmm. You're using platform drivers for OHCI and EHCI, not PCI, > > > > Yes, I'm using platform drivers for OHCI and EHCI. > > > > > right? The resume_common()

RE: How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-13 Thread Alan Stern
On Mon, 13 Feb 2017, Yoshihiro Shimoda wrote: > > Hmmm. You're using platform drivers for OHCI and EHCI, not PCI, > > Yes, I'm using platform drivers for OHCI and EHCI. > > > right? The resume_common() routine in drivers/usb/core/hcd-pci.c is > > careful to resume things in the correct order.

RE: How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-13 Thread Yoshihiro Shimoda
Hi Alan, > From: Alan Stern > Sent: Friday, February 10, 2017 12:28 AM > > On Thu, 9 Feb 2017, Yoshihiro Shimoda wrote: > > > > > > From: Alan Stern > > > Sent: Thursday, February 09, 2017 12:39 AM > > > On Wed, 8 Feb 2017, Yoshihiro Shimoda wrote: < snip > > > I checked the

RE: How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-09 Thread Alan Stern
On Thu, 9 Feb 2017, Yoshihiro Shimoda wrote: > Hi Alan, > > Thank you for the reply! > > > From: Alan Stern > > Sent: Thursday, February 09, 2017 12:39 AM > > > > On Wed, 8 Feb 2017, Yoshihiro Shimoda wrote: > > > > > Hi, > > > > > > In my environment, it causes the following message during

RE: How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-09 Thread Yoshihiro Shimoda
Hi Alan, Thank you for the reply! > From: Alan Stern > Sent: Thursday, February 09, 2017 12:39 AM > > On Wed, 8 Feb 2017, Yoshihiro Shimoda wrote: > > > Hi, > > > > In my environment, it causes the following message during system resume if > > debug messages are enabled: > > > > usb 2-1:

Re: How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-08 Thread Alan Stern
On Wed, 8 Feb 2017, Yoshihiro Shimoda wrote: > Hi, > > In my environment, it causes the following message during system resume if > debug messages are enabled: > > usb 2-1: Waited 2000ms for CONNECT This message indicates that the port was connected to a device when the system

How to resolve "Waited 2000ms for CONNECT" in system resuming?

2017-02-07 Thread Yoshihiro Shimoda
Hi, In my environment, it causes the following message during system resume if debug messages are enabled: usb 2-1: Waited 2000ms for CONNECT < My environment > - EHCI/OHCI controllers on R-Car H3 (arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts) - Greg's usb.git / next branch