From: Dmitry Fleytman <dmitry.fleytman@gmail.com>
To: JackStocker <jackstocker.93@gmail.com>
Cc: 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>,
Stefan Bader <stefan.bader@canonical.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Devin Heitmueller <dheitmueller@kernellabs.com>,
Sandeep Singh <sandeep.singh@amd.com>, dmitry <dmitry@daynix.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add delay-init quirk for Corsair K70 RGB keyboards
Date: Fri, 2 Feb 2018 20:19:23 +0200 [thread overview]
Message-ID: <596D3B57-74E7-4038-85CA-2F48F0130EFE@gmail.com> (raw)
In-Reply-To: <1517586717-6209-1-git-send-email-jackstocker.93@gmail.com>
> On 2 Feb 2018, at 17:51, JackStocker <jackstocker.93@gmail.com> wrote:
>
> From: Jack Stocker <jackstocker.93@gmail.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
Reviewed-by: Dmitry Fleytman <dmitry.fleytman@gmail.com>
>
> Signed-off-by: Jack Stocker <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..9eb92dc 100644
> --- a/drivers/usb/core/quirks.c
> +++ b/drivers/usb/core/quirks.c
> @@ -221,6 +221,9 @@ static const struct usb_device_id usb_quirk_list[] = {
> /* Corsair Strafe RGB */
> { USB_DEVICE(0x1b1c, 0x1b20), .driver_info = USB_QUIRK_DELAY_INIT },
>
> + /* Corsair K70 RGB */
> + { USB_DEVICE(0x1b1c, 0x1b13), .driver_info = USB_QUIRK_DELAY_INIT },
> +
> /* MIDI keyboard WORLDE MINI */
> { USB_DEVICE(0x1c75, 0x0204), .driver_info =
> USB_QUIRK_CONFIG_INTF_STRINGS },
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-02-02 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 15:51 JackStocker
2018-02-02 18:19 ` Dmitry Fleytman [this message]
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 ` [PATCH v4] " 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=596D3B57-74E7-4038-85CA-2F48F0130EFE@gmail.com \
--to=dmitry.fleytman@gmail.com \
--cc=dheitmueller@kernellabs.com \
--cc=dmitry@daynix.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jackstocker.93@gmail.com \
--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 \
--cc=stefan.bader@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
all inboxes | Powered by JetHome®