From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Oliver Neukum <oneukum@suse.com>, stern@rowland.harvard.edu
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v3] usb: hub: add retry routine after intr URB submit error
Date: Tue, 20 Nov 2018 16:17:29 +0100 [thread overview]
Message-ID: <07a6b541f53a68b994f8ee6b1c864e096e1ff8cf.camel@suse.de> (raw)
In-Reply-To: <1542725830.28362.12.camel@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Hi Oliver,
On Tue, 2018-11-20 at 15:57 +0100, Oliver Neukum wrote:
> On Di, 2018-11-20 at 15:34 +0100, Nicolas Saenz Julienne wrote:
> > The hub sends hot-plug events to the host trough it's interrupt
> > URB. The
> > driver takes care of completing the URB and re-submitting it.
> > Completion
> > errors are handled in the hub_event() work, yet submission errors
> > are
> > ignored, rendering the device unresponsive. All further events are
> > lost.
> >
>
> Hi,
>
> almost. There is no point in kicking of an error handling while aq
> reset is underway. You are checking only "quiescing" but not
> "in_reset".
Anytime "in_reset" is set "quiescing" is also set:
static int hub_pre_reset(struct usb_interface *intf)
{
struct usb_hub *hub = usb_get_intfdata(intf);
hub_quiesce(hub, HUB_PRE_RESET); //sets quiesce
hub->in_reset = 1;
hub_pm_barrier_for_all_ports(hub);
return 0;
}
static int hub_post_reset(struct usb_interface *intf)
{
struct usb_hub *hub = usb_get_intfdata(intf);
hub->in_reset = 0;
hub_pm_barrier_for_all_ports(hub);
hub_activate(hub, HUB_POST_RESET); //clears quiesce
return 0;
}
I should be OK isn't it?
Regards,
Nicolas
>
> Regards
> Oliver
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-20 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 14:34 Nicolas Saenz Julienne
2018-11-20 14:57 ` Oliver Neukum
2018-11-20 15:17 ` Nicolas Saenz Julienne [this message]
2018-11-20 15:12 ` Oliver Neukum
2019-01-07 16:33 ` Greg KH
2019-01-07 18:59 ` Alan Stern
2019-01-07 21:25 ` Oliver Neukum
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=07a6b541f53a68b994f8ee6b1c864e096e1ff8cf.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
/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: link
Be 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
all inboxes | Powered by JetHome®