linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Moseychuk <franchesko.salias.hudro.pedros@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, gregkh@linuxfoundation.org,
	mathias.nyman@linux.intel.com
Subject: usb: do not reset if a low-speed device timed out
Date: Thu, 04 Jan 2018 20:21:12 +0300	[thread overview]
Message-ID: <1515086472.7389.2.camel@gmail.com> (raw)

В Чт, 04/01/2018 в 11:57 -0500, Alan Stern пишет:
> On Thu, 4 Jan 2018, Maxim Moseychuk wrote:
> 
> > Some low-speed devices (for example, bluetooth) do not have
> > time to initialize. For them, ETIMEDOUT is a valid error.
> > We need to give them another try. Otherwise, they will
> > never be initialized correctly and in dmesg will be messages
> > "Bluetooth: hci0 command 0x1002 tx timeout" or similars.
> 
> Your patch description talks about low-speed devices...
> 
> > Fixes: 264904ccc33c ("usb: retry reset if a device times out")
> > Signed-off-by: Maxim Moseychuk <franchesko.salias.hudro.pedros@gmai
> l.com>
> > ---
> >  drivers/usb/core/hub.c | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> > index cf7bbcb9a63c..46366c73f0df 100644
> > --- a/drivers/usb/core/hub.c
> > +++ b/drivers/usb/core/hub.c
> > @@ -4524,7 +4524,10 @@ hub_port_init(struct usb_hub *hub, struct
> usb_device *udev, int port1,
> >                                * reset. But only on the first
> attempt,
> >                                * lest we get into a time out/reset
> loop
> >                                */
> > -                             if (r == 0  || (r == -ETIMEDOUT &&
> retries == 0))
> > +                             if (r == 0 ||
> > +                                             r == -ETIMEDOUT
> > +                                             && retries == 0
> > +                                             && udev->speed >
> USB_SPEED_FULL)
> 
> but the patch itself affects both low-speed and full-speed devices.
> 
> Also, I would keep the parens around the && expressions, and there's
> no
> need for the first line break you added.  (For that matter, it looks
> strange to break the first line _after_ the || operator and then to
> break the later lines _before_ the && operators -- try to copy the 
> style used elsewhere in that source file.)
> 
> Alan Stern
> 

I probably chose the wrong term. We are talking about devices running
at speeds of usb 1.1 (Low-speed and Full-speed).
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-01-04 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 17:21 Maxim Moseychuk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-04 16:57 usb: do not reset if a low-speed device timed out Alan Stern
2018-01-04  1:29 Maxim Moseychuk

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=1515086472.7389.2.camel@gmail.com \
    --to=franchesko.salias.hudro.pedros@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.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;
as well as URLs for NNTP newsgroup(s).