From: David Laight <David.Laight@ACULAB.COM>
To: 'Alan Stern' <stern@rowland.harvard.edu>,
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 15:39:10 +0000 [thread overview]
Message-ID: <419f8edc2a7744ecbfaa0728227db180@AcuMS.aculab.com> (raw)
In-Reply-To: <YqyYIt2MLmoCRSA9@rowland.harvard.edu>
From: Alan Stern
> Sent: 17 June 2022 16:05
...
> 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.
I'm not even sure I want a system to wake up because it's mouse
gets knocked.
I guess a mouse could include accelerometers so that you can shake it!
I've an idea that one of my systems manages to boot if the mouse
is knocked (and it was last shutdown from windows).
At least, that it why I think it is sometimes booting up.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-06-17 15:39 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
2022-06-17 15:39 ` David Laight [this message]
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=419f8edc2a7744ecbfaa0728227db180@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--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 \
--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