From: Greg KH <gregkh@linuxfoundation.org>
To: Danilo Krummrich <danilokrummrich@dk-develop.de>
Cc: danilokrummrich@yahoo.de, stable@vger.kernel.org
Subject: Re: [PATCH] usb: quirks: add control message delay for 1b1c:1b20
Date: Mon, 12 Mar 2018 12:09:01 +0100 [thread overview]
Message-ID: <20180312110901.GA10633@kroah.com> (raw)
In-Reply-To: <20180312001628.11046-1-danilokrummrich@dk-develop.de>
On Mon, Mar 12, 2018 at 01:16:28AM +0100, Danilo Krummrich wrote:
> Corsair Strafe RGB keyboard does not respond to usb control messages
> sometimes and hence generates timeouts.
>
> Commit de3af5bf259d ("usb: quirks: add delay init quirk for Corsair
> Strafe RGB keyboard") tried to fix those timeouts by adding
> USB_QUIRK_DELAY_INIT.
>
> Unfortunately, even with this quirk timeouts of usb_control_msg()
> can still be seen, but with a lower frequency (approx. 1 out of 15):
>
> [ 29.103520] usb 1-8: string descriptor 0 read error: -110
> [ 34.363097] usb 1-8: can't set config #1, error -110
>
> Adding further delays to different locations where usb control
> messages are issued just moves the timeouts to other locations,
> e.g.:
>
> [ 35.400533] usbhid 1-8:1.0: can't add hid device: -110
> [ 35.401014] usbhid: probe of 1-8:1.0 failed with error -110
>
> The only way to reliably avoid those issues is having a pause after
> each usb control message. In approx. 200 boot cycles no more timeouts
> were seen.
>
> Addionaly, keep USB_QUIRK_DELAY_INIT as it turned out to be necessary
> to have the delay in hub_port_connect() after hub_port_init().
>
> The overall boot time seems not to be influenced by these additional
> delays, even on fast machines and lightweight distributions.
>
> Fixes: de3af5bf259d ("usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard")
> Cc: stable@vger.kernel.org
> Signed-off-by: Danilo Krummrich <danilokrummrich@dk-develop.de>
> ---
> drivers/usb/core/message.c | 4 ++++
> drivers/usb/core/quirks.c | 3 ++-
> include/linux/usb/quirks.h | 3 +++
> 3 files changed, 9 insertions(+), 1 deletion(-)
Please use scripts/get_maintainer.pl to know who to send patches to
(hint, you forgot all of the USB developers...)
Please fix up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2018-03-12 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 0:16 [PATCH] usb: quirks: add control message delay for 1b1c:1b20 Danilo Krummrich
2018-03-12 11:09 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-22 0:46 Danilo Krummrich
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=20180312110901.GA10633@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=danilokrummrich@dk-develop.de \
--cc=danilokrummrich@yahoo.de \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.