From: Jack Stocker <jackstocker.93@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Jack Stocker <jackstocker.93@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Seth Forshee <seth.forshee@canonical.com>,
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
Harry Pan <harry.pan@intel.com>,
Kamil Lulko <kamilx.lulko@intel.com>,
Danilo Krummrich <danilokrummrich@dk-develop.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Add USB_QUIRK_DELAY_CTRL_MSG quirk for Corsair K70 RGB
Date: Wed, 2 Jan 2019 18:37:44 +0000 [thread overview]
Message-ID: <1546454264-11561-1-git-send-email-jackstocker.93@gmail.com> (raw)
To match the Corsair Strafe RGB, the Corsair K70 RGB also requires
USB_QUIRK_DELAY_CTRL_MSG to completely resolve boot connection issues
discussed here: https://github.com/ckb-next/ckb-next/issues/42.
Otherwise roughly 1 in 10 boots the keyboard will fail to be detected.
Signed-off-by: Jack Stocker <jackstocker.93@gmail.com>
---
drivers/usb/core/quirks.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 7909262..4a9267d 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -377,7 +377,8 @@ static const struct usb_device_id usb_quirk_list[] = {
USB_QUIRK_LINEAR_UFRAME_INTR_BINTERVAL },
/* Corsair K70 RGB */
- { USB_DEVICE(0x1b1c, 0x1b13), .driver_info = USB_QUIRK_DELAY_INIT },
+ { USB_DEVICE(0x1b1c, 0x1b13), .driver_info = USB_QUIRK_DELAY_INIT |
+ USB_QUIRK_DELAY_CTRL_MSG },
/* Corsair Strafe RGB */
{ USB_DEVICE(0x1b1c, 0x1b20), .driver_info = USB_QUIRK_DELAY_INIT |
--
2.7.4
next reply other threads:[~2019-01-02 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 18:37 Jack Stocker [this message]
2019-01-02 20:57 ` Danilo Krummrich
2019-01-03 21:56 ` [PATCH v2] " Jack Stocker
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=1546454264-11561-1-git-send-email-jackstocker.93@gmail.com \
--to=jackstocker.93@gmail.com \
--cc=cascardo@canonical.com \
--cc=danilokrummrich@dk-develop.de \
--cc=gregkh@linuxfoundation.org \
--cc=harry.pan@intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kamilx.lulko@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=seth.forshee@canonical.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: 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
Powered by JetHome