LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu> To: Julius Werner <jwerner@chromium.org> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>, Dan Williams <dan.j.williams@intel.com>, Douglas Anderson <dianders@chromium.org>, Tomasz Figa <tfiga@chromium.org>, Wu Liang feng <wulf@rock-chips.com> Subject: Re: [PATCH v2] usb: Retry port status check on resume to work around RH bugs Date: Tue, 27 Jan 2015 11:17:02 -0500 (EST) [thread overview] Message-ID: <Pine.LNX.4.44L0.1501271107290.28374-100000@netrider.rowland.org> (raw) In-Reply-To: <1422307602-30466-1-git-send-email-jwerner@chromium.org> On Mon, 26 Jan 2015, Julius Werner wrote: > The EHCI controller on the RK3288 SoC is violating basic parts of the > USB spec and thereby unable to properly resume a suspended port. It does > not start SOF generation within 3ms of finishing resume signaling, so > the attached device will drop off the bus again. This is a particular > problem with runtime PM, where accessing the device will trigger a > resume that immediately makes it unavailabe (and reenumerate with a new Typo: "unavailabe" > handle). > > Thankfully, the persist feature is generally able to work around stuff > like that. Unfortunately, it doesn't quite work in this particular case > because the controller will turn off the CurrentConnectStatus bit for an > instant while the device is reconnecting, which causes the kernel to > conclude that it permanently disappeared. This patch adds a tiny retry > mechanism to the core port resume code which will catch this case and > shouldn't have any notable impact on other controllers. > > Signed-off-by: Julius Werner <jwerner@chromium.org> > --- > drivers/usb/core/hub.c | 13 +++++++++++-- > 1 file changed, 11 insertions(+), 2 deletions(-) > > diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c > index aeb50bb..d1d0a66 100644 > --- a/drivers/usb/core/hub.c > +++ b/drivers/usb/core/hub.c > @@ -2896,10 +2896,12 @@ static int port_is_suspended(struct usb_hub *hub, unsigned portstatus) > */ > static int check_port_resume_type(struct usb_device *udev, > struct usb_hub *hub, int port1, > - int status, unsigned portchange, unsigned portstatus) > + int status, u16 portchange, u16 portstatus) > { > struct usb_port *port_dev = hub->ports[port1 - 1]; > + int retries = 3; > > +retry: I prefer to indent statement labels by one space, so that diff doesn't see them as function declarations. > /* Is a warm reset needed to recover the connection? */ > if (status == 0 && udev->reset_resume > && hub_port_warm_reset_required(hub, port1, portstatus)) { > @@ -2909,8 +2911,15 @@ static int check_port_resume_type(struct usb_device *udev, > else if (status || port_is_suspended(hub, portstatus) || > !port_is_power_on(hub, portstatus) || > !(portstatus & USB_PORT_STAT_CONNECTION)) { > - if (status >= 0) > + if (status >= 0) { Thinking about this more carefully, it looks like the only thing you care about here is the !(portstatus & USB_PORT_STAT_CONNECTION) case. For everything else, you don't need to retry. So why not separate out that one case? else if (status || port_is_suspended(hub, portstatus) || !port_is_power_on(hub, portstatus)) { if (status >= 0) status = -ENODEV; } else if (!(portstatus & USB_PORT_STAT_CONNECTION)) { retry stuff... } > + if (retries--) { > + usleep_range(200, 300); > + status = hub_port_status(hub, port1, > + &portstatus, &portchange); > + goto retry; > + } > status = -ENODEV; > + } > } > > /* Can't do a normal resume if the port isn't enabled, Alan Stern
next prev parent reply other threads:[~2015-01-27 16:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-24 0:01 [PATCH] usb: Retry port status check on resume to work around RH bugs Julius Werner 2015-01-24 15:49 ` Alan Stern 2015-01-26 21:24 ` Julius Werner 2015-01-26 21:26 ` [PATCH v2] " Julius Werner 2015-01-27 16:17 ` Alan Stern [this message] 2015-01-27 21:20 ` [PATCH v3] " Julius Werner 2015-01-28 15:33 ` Alan Stern
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=Pine.LNX.4.44L0.1501271107290.28374-100000@netrider.rowland.org \ --to=stern@rowland.harvard.edu \ --cc=dan.j.williams@intel.com \ --cc=dianders@chromium.org \ --cc=gregkh@linuxfoundation.org \ --cc=jwerner@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-usb@vger.kernel.org \ --cc=tfiga@chromium.org \ --cc=wulf@rock-chips.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).