Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <4086b017d678f2edaea3a87b8eae18a85cc8e89d.camel@suse.com>
Subject: Re: Re: [PATCH] HID: usbhid: enable remote wakeup for mouse
From:   Oliver Neukum <oneukum@suse.com>
To:     =?UTF-8?Q?=E9=A9=AC=E5=BC=BA?= <maqianga@uniontech.com>,
        Alan Stern <stern@rowland.harvard.edu>
Cc:     jikos <jikos@kernel.org>,
        "benjamin.tissoires" <benjamin.tissoires@redhat.com>,
        linux-usb <linux-usb@vger.kernel.org>,
        linux-input <linux-input@vger.kernel.org>,
        linux-kernel <linux-kernel@vger.kernel.org>
Date:   Tue, 25 May 2021 11:55:46 +0200
In-Reply-To: <1209199573.51584.1621492845444.JavaMail.xmail@bj-wm-cp-1>
References: <20210517060145.32359-1-maqianga@uniontech.com>
         <1327a9251c74587670970baa0f662cd61006f576.camel@suse.com>
        , <20210517133247.GB1083813@rowland.harvard.edu>
         <1209199573.51584.1621492845444.JavaMail.xmail@bj-wm-cp-1>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.4 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Am Donnerstag, den 20.05.2021, 14:40 +0800 schrieb 马强:
> This is caused by external reasons, as the kernel cannot sense 
> whether it is accidentally triggered or actively triggered. 
> If this kind of unintentional situation is avoided, 
> the keyboard should also be disabled wakeup by default. 
> Otherwise, the normally used computer may be awakened 
> by someone else accidentally pressing the keyboard on standby.
> 

The kernel has to manage keyboards. There just is no genuine
keyboard device user space could open, nor could we do sysrq
or sak if we left the keyboard fully to user space.

Hence keyboards are a special case unfortunately. We will
have to live with two classes of wakeup, keyboards and power
buttons on the one hand, versus everything else.

	Regards
		Oliver