From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>,
ryan <ryanzhou54@gmail.com>,
jikos@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hid: usbhid: Enable remote wake-up based on device configuration
Date: Thu, 11 Jul 2024 09:41:45 +0200 [thread overview]
Message-ID: <2024071104-rental-bleak-b273@gregkh> (raw)
In-Reply-To: <f0c789d8-8ae0-4a46-a5b3-aa9a5a758915@rowland.harvard.edu>
On Wed, Jul 10, 2024 at 09:47:39PM -0400, Alan Stern wrote:
> On Thu, Jul 11, 2024 at 07:16:06AM +0800, ryan wrote:
> > According to the USB protocol, the host should automatically
> > adapt the remote wake-up function based on the configuration
> > descriptor reported by the device, rather than only the default
> > keyboard support. Therefore, it's necessary to support other hid
> > devices, such as digital headsets,mice,etc.
>
> It's true that the host shouldn't try to enable remote wakeup if the
> configuration descriptor shows that the device doesn't support it.
>
> However, it's not true that the host should try to enable remote wakeup
> for devices other than keyboards with boot-protocol support. History
> has shown that quite a few HID devices don't handle remote wakeup
> properly; the decision about whether to enable it should be left to the
> user.
I agree, this patch isn't acceptable. Ryan, why do you want this
applied? What userspace control is missing to allow you to do this
today on your systems with no kernel changes for devices that you know
will work properly?
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-11 7:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 23:16 [PATCH] hid: usbhid: Enable remote wake-up based on device configuration ryan
2024-07-11 1:47 ` Alan Stern
2024-07-11 7:41 ` Greg KH [this message]
2024-07-15 15:36 ` ryan zhou
2024-07-15 15:43 ` Greg KH
2024-07-15 17:45 ` Alan Stern
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=2024071104-rental-bleak-b273@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ryanzhou54@gmail.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