linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: JackStocker <jackstocker.93@gmail.com>
Cc: JackStocker <jackstocker.93@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Seth Forshee <seth.forshee@canonical.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
	Sandeep Singh <sandeep.singh@amd.com>,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	Dmitry Fleytman <dmitry@daynix.com>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [v2] Add delay-init quirk for Corsair K70 RGB keyboards
Date: Sun,  4 Feb 2018 16:18:21 +0000	[thread overview]
Message-ID: <1517761102-6849-1-git-send-email-jackstocker.93@gmail.com> (raw)

Do you mean like this?

Signed-off-by: JackStocker <jackstocker.93@gmail.com>
---
 drivers/usb/core/quirks.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index a6aaf2f..0405d68 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -218,6 +218,9 @@ static const struct usb_device_id usb_quirk_list[] = {
 	{ USB_DEVICE(0x1a0a, 0x0200), .driver_info =
 			USB_QUIRK_LINEAR_UFRAME_INTR_BINTERVAL },
 
+	/* Corsair K70 RGB */
+	{ USB_DEVICE(0x1b1c, 0x1b13), .driver_info = USB_QUIRK_DELAY_INIT },
+
 	/* Corsair Strafe RGB */
 	{ USB_DEVICE(0x1b1c, 0x1b20), .driver_info = USB_QUIRK_DELAY_INIT },
 

             reply	other threads:[~2018-02-04 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 16:18 JackStocker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-04 16:38 [v2] Add delay-init quirk for Corsair K70 RGB keyboards Kai-Heng Feng

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=1517761102-6849-1-git-send-email-jackstocker.93@gmail.com \
    --to=jackstocker.93@gmail.com \
    --cc=cascardo@canonical.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=dmitry@daynix.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=sandeep.singh@amd.com \
    --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;
as well as URLs for NNTP newsgroup(s).