From: Alan Stern <stern@rowland.harvard.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
"open list:USB HID/HIDBP DRIVERS \[USB KEYBOARDS, MICE,
REM..." <linux-usb@vger.kernel.org>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Richard Gong <richard.gong@amd.com>
Subject: Re: [PATCH v2] HID: usbhid: set mouse as a wakeup resource
Date: Fri, 17 Jun 2022 11:05:06 -0400 [thread overview]
Message-ID: <YqyYIt2MLmoCRSA9@rowland.harvard.edu> (raw)
In-Reply-To: <YqugZQiDu35Y8lTu@kroah.com>
On Thu, Jun 16, 2022 at 11:28:05PM +0200, Greg KH wrote:
> On Thu, Jun 16, 2022 at 01:31:42PM -0500, Mario Limonciello wrote:
> > The USB HID transport layer doesn't set mice for wakeup by default so users
> > can not wake system from s2idle using wired USB mouse. However, users can
> > wake the same system from Modern Standby on Windows with the same wired
> > USB mouse.
> >
> > Microsoft documentation indicates that all USB mice and touchpads should
> > be waking the system from Modern Standby. To align expectations from users
> > make this behavior the same when the system is configured by the OEM and
> > the user to use s2idle in Linux.
> >
> > Link: https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/modern-standby-wake-sources#input-devices-1
> > Link: https://lore.kernel.org/linux-usb/20220404214557.3329796-1-richard.gong@amd.com/
> > Suggested-by: Richard Gong <richard.gong@amd.com>
> > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> > ---
> > More people keep coming to us confused that they couldn't wake a Linux system
> > up from sleep using a mouse, so this patch is being revived.
>
> How many different devices did you test this on?
Another issue is whether wakeup for a mouse means pressing a button or
just moving the mouse. For a mouse that uses LEDs to sense motion,
moving it won't generate a wakeup request -- USB suspend does not allow
the mouse to use enough current to keep the LEDs illuminated. On the
other hand, there's no reason why wakeup by pressing a button shouldn't
always work.
Also, the patch description doesn't seem to appreciate the difference
between the default value for the wakeup setting and actually supporting
wakeup. As long as the hardware supports it, the default wakeup setting
doesn't matter all that much, because the user can change the setting
during system startup or whenever he wants. But if the hardware doesn't
support wakeup then the default setting makes no difference at all.
Alan Stern
next prev parent reply other threads:[~2022-06-17 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 18:31 [PATCH v2] HID: usbhid: set mouse as a wakeup resource Mario Limonciello
2022-06-16 21:28 ` Greg KH
2022-06-16 21:47 ` Limonciello, Mario
2022-06-17 15:05 ` Alan Stern [this message]
2022-06-17 15:39 ` David Laight
2022-06-17 16:06 ` Limonciello, Mario
2022-06-17 17:39 ` 'Alan Stern'
2022-06-17 17:44 ` Limonciello, Mario
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=YqyYIt2MLmoCRSA9@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=benjamin.tissoires@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=richard.gong@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