mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Fleytman <dmitry@daynix.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "Dmitry Fleytman" <dmitry@daynix.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Sandeep Singh" <sandeep.singh@amd.com>,
	"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
	"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
	"Devin Heitmueller" <dheitmueller@kernellabs.com>,
	"Lukáš Lalinský" <lukas@oxygene.sk>,
	"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] usb: Add device quirk for Logitech HD Pro Webcam C920-C
Date: Mon, 21 Aug 2017 13:03:31 +0300	[thread overview]
Message-ID: <20170821100333.3538-1-dmitry@daynix.com> (raw)

Commit e0429362ab15
("usb: Add device quirk for Logitech HD Pro Webcams C920 and C930e")
introduced quirk to workaround an issue with some Logitech webcams.

Apparently model C920-C has the same issue so applying
the same quirk as well.

See aforementioned commit message for detailed explanation of the problem.

Signed-off-by: Dmitry Fleytman <dmitry@daynix.com>
---
 drivers/usb/core/quirks.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 574da2b..36d4841 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -59,6 +59,7 @@ static const struct usb_device_id usb_quirk_list[] = {
 
 	/* Logitech HD Pro Webcams C920 and C930e */
 	{ USB_DEVICE(0x046d, 0x082d), .driver_info = USB_QUIRK_DELAY_INIT },
+	{ USB_DEVICE(0x046d, 0x0841), .driver_info = USB_QUIRK_DELAY_INIT },
 	{ USB_DEVICE(0x046d, 0x0843), .driver_info = USB_QUIRK_DELAY_INIT },
 
 	/* Logitech ConferenceCam CC3000e */
-- 
2.7.4

             reply	other threads:[~2017-08-21 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 10:03 Dmitry Fleytman [this message]
2017-08-24  7:58 ` Kai-Heng Feng
2017-08-25  7:41   ` Dmitry Fleytman

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=20170821100333.3538-1-dmitry@daynix.com \
    --to=dmitry@daynix.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@oxygene.sk \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=sandeep.singh@amd.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®