mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Dmitry Fleytman <dmitry@daynix.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Johan Hovold <johan@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Eugene Korenevsky <ekorenevsky@gmail.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: Increase quirk delay for USB devices
Date: Tue, 5 Sep 2017 13:22:25 -0700	[thread overview]
Message-ID: <20170905202225.GC16996@roeck-us.net> (raw)
In-Reply-To: <20170905084059.28816-1-dmitry@daynix.com>

On Tue, Sep 05, 2017 at 11:40:56AM +0300, Dmitry Fleytman wrote:
> Commit e0429362ab15
> ("usb: Add device quirk for Logitech HD Pro Webcams C920 and C930e")
> introduced quirk to workaround an issue with some Logitech webcams.
> 
> The workaround is introducing delay for some USB operations.
> 
> According to our testing, delay introduced by original commit
> is not long enough and in rare cases we still see issues described
> by the aforementioned commit.
> 
> This patch increases delays introduced by original commit.
> Having this patch applied we do not see those problems anymore.
> 
> Signed-off-by: Dmitry Fleytman <dmitry@daynix.com>
> ---
>  drivers/usb/core/config.c | 2 +-
>  drivers/usb/core/hub.c    | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/usb/core/config.c b/drivers/usb/core/config.c
> index 4be52c6..854c8d6 100644
> --- a/drivers/usb/core/config.c
> +++ b/drivers/usb/core/config.c
> @@ -852,7 +852,7 @@ int usb_get_configuration(struct usb_device *dev)
>  		}
>  
>  		if (dev->quirks & USB_QUIRK_DELAY_INIT)
> -			msleep(100);
> +			msleep(200);

How did you determine the new delays ? Was it discussed with the vendor,
or is it based on trial and error ?

Either case, did you confirm that you need to increase both delays
for the problem to disappear ?

Thanks,
Guenter

>  
>  		result = usb_get_descriptor(dev, USB_DT_CONFIG, cfgno,
>  		    bigbuffer, length);
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> index 822f8c5..78c2aca 100644
> --- a/drivers/usb/core/hub.c
> +++ b/drivers/usb/core/hub.c
> @@ -4825,7 +4825,7 @@ static void hub_port_connect(struct usb_hub *hub, int port1, u16 portstatus,
>  			goto loop;
>  
>  		if (udev->quirks & USB_QUIRK_DELAY_INIT)
> -			msleep(1000);
> +			msleep(2000);
>  
>  		/* consecutive bus-powered hubs aren't reliable; they can
>  		 * violate the voltage drop budget.  if the new child has
> -- 
> 2.7.4
> 

  reply	other threads:[~2017-09-05 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05  8:40 Dmitry Fleytman
2017-09-05 20:22 ` Guenter Roeck [this message]
2017-09-06 12:34   ` Dmitry Fleytman

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=20170905202225.GC16996@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dmitry@daynix.com \
    --cc=ekorenevsky@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=samuel.thibault@ens-lyon.org \
    --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®