From: Hamza Mahfooz <someguy@effective-light.com>
To: linux-usb@vger.kernel.org
Cc: "Hamza Mahfooz" <someguy@effective-light.com>,
stable@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
"Bastien Nocera" <hadess@hadess.net>,
"Hans de Goede" <hdegoede@redhat.com>,
"Łukasz Bartosik" <lb@semihalf.com>,
"Nicolas Dumazet" <ndumazet@google.com>,
"Jean-Francois Le Fillatre" <jflf_kernel@gmx.com>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
"Hannu Hartikainen" <hannu@hrtk.in>,
linux-kernel@vger.kernel.org
Subject: [PATCH] USB: add ignore remote wakeup quirk for one of Logitech's receivers
Date: Sun, 10 Sep 2023 12:37:48 -0400 [thread overview]
Message-ID: <20230910163751.4210-1-someguy@effective-light.com> (raw)
This device causes the system to wake up from suspend, as soon as it
enters it (even if the device attached to the receiver is powered off).
So, ignore remote wakeup events from it.
Cc: stable@vger.kernel.org
Signed-off-by: Hamza Mahfooz <someguy@effective-light.com>
---
drivers/usb/core/quirks.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 15e9bd180a1d..d2e2a2873f34 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -264,6 +264,10 @@ static const struct usb_device_id usb_quirk_list[] = {
/* Logitech Harmony 700-series */
{ USB_DEVICE(0x046d, 0xc122), .driver_info = USB_QUIRK_DELAY_INIT },
+ /* Logitech lightspeed receiver (0xc547) */
+ { USB_DEVICE(0x046d, 0xc547), .driver_info =
+ USB_QUIRK_IGNORE_REMOTE_WAKEUP },
+
/* Philips PSC805 audio device */
{ USB_DEVICE(0x0471, 0x0155), .driver_info = USB_QUIRK_RESET_RESUME },
--
2.42.0
next reply other threads:[~2023-09-10 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 16:37 Hamza Mahfooz [this message]
2023-09-11 7:32 ` [PATCH] USB: add ignore remote wakeup quirk for one of Logitech's receivers Hans de Goede
2023-09-11 15:19 ` Hamza Mahfooz
2023-09-11 15:29 ` Hans de Goede
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=20230910163751.4210-1-someguy@effective-light.com \
--to=someguy@effective-light.com \
--cc=benjamin.tissoires@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=hannu@hrtk.in \
--cc=hdegoede@redhat.com \
--cc=jflf_kernel@gmx.com \
--cc=lb@semihalf.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=ndumazet@google.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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