mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jack Stocker <jackstocker.93@gmail.com>
Cc: Jack Stocker <jackstocker.93@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Seth Forshee <seth.forshee@canonical.com>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Dmitry Fleytman <dmitry@daynix.com>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4] Add delay-init quirk for Corsair K70 RGB keyboards
Date: Thu, 15 Feb 2018 18:24:10 +0000	[thread overview]
Message-ID: <1518719051-9644-1-git-send-email-jackstocker.93@gmail.com> (raw)
In-Reply-To: <20180215180205.GA15170@kroah.com>

Following on from this patch: https://lkml.org/lkml/2017/11/3/516,
Corsair K70 RGB keyboards also require the DELAY_INIT quirk to
start correctly at boot.

Device ids found here:
usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b13
usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-3: Product: Corsair K70 RGB Gaming Keyboard

Signed-off-by: Jack Stocker <jackstocker.93@gmail.com>
Cc: stable <stable@vger.kernel.org>
---
Changes in v4:
  - Corrected 'real' name.
Changes in v3:
  - Added correct v1 commit message.
Changes in v2:
  - Moved K70 entry above Strafe to preserve ascending order.

 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 },
 
-- 
2.7.4

      reply	other threads:[~2018-02-15 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02 15:51 [PATCH] " JackStocker
2018-02-02 18:19 ` Dmitry Fleytman
2018-02-04 13:35 ` Kai Heng Feng
2018-02-04 16:18   ` [PATCH v2] " JackStocker
2018-02-04 16:38     ` Kai Heng Feng
2018-02-04 16:50       ` [PATCH v3] " JackStocker
2018-02-15 17:35         ` Greg Kroah-Hartman
2018-02-15 17:59           ` Jack
2018-02-15 18:02             ` Greg Kroah-Hartman
2018-02-15 18:24               ` Jack Stocker [this message]

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=1518719051-9644-1-git-send-email-jackstocker.93@gmail.com \
    --to=jackstocker.93@gmail.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=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