lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d444c3e5-79b1-f6a6-10e9-e597b3227434@amd.com>
Date:   Fri, 1 Jul 2022 13:00:17 -0500
From:   Mario Limonciello <mario.limonciello@....com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Jiri Kosina <jikos@...nel.org>,
        Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        linux-pm@...r.kernel.org, Richard Gong <richard.gong@....com>,
        linux-usb@...r.kernel.org, linux-input@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 10/10] HID: usbhid: Set USB mice as s2idle wakeup
 resources

(FYI - combined both of Greg's responses in this message rather than 
responding to them separately)

 > Note, this is very different than older versions of Windows.  Any idea
when this behavior and prescription changed?

Older versions of Windows also didn't support Modern Standby, so I would 
hypothesize it's either Windows 8 or Windows 10 that changed it.

 > Where are patches 1-9 of this series?

Patch 1 was based on your comment in v2 that there was no helper (it 
introduces a helper).

Patches 2-9 are just changes across the kernel to use this helper.

The entire series was submitted to LKML, but individual patches only to 
the relevant maintainers for the subsystem.  If there is a v4 patch I'll 
CC everyone on everything.

Here is a lore link to the whole series:
https://lore.kernel.org/lkml/20220701023328.2783-1-mario.limonciello@amd.com/

On 7/1/22 01:58, Greg KH wrote:
> On Thu, Jun 30, 2022 at 09:33:28PM -0500, Mario Limonciello wrote:
>> The USB HID transport layer doesn't configure mice for wakeup by default.
>> Thus users can not wake system from s2idle via USB mouse. However, users
>> can wake the same system from Modern Standby on Windows with the same USB
>> mouse.
>>
>> Microsoft documentation indicates that all USB mice and touchpads should
>> be waking the system from Modern Standby.
> 
> As I said before, their documentation indicates that all _EXTERNAL_ mice
> and touchpads.  You forgot about internally connected mice and touchpads
> here, you wouldn't want them to wake up a device asleep, right?
> 

Is this actually a thing?  I've been in the PC industry a while but 
never seen a design that supported Modern Standby/s2idle that opted to 
use USB to connect an "internal" touchpad/mouse.  Microsoft's own 
documentation in the same link advises against it at least too.

"We recommend using HIDI2C for input peripherals whenever possible for 
better power efficiency, but this is not a requirement".

But in any case - wakeup from this type of device is a grey area.  They 
require that internal touchpads connected to I2C be a wake source and 
also USB touchpads.
There is nothing on that page prescribing the behavior for an "internal" 
USB touchpad.

Reading between the lines given the intent, I would argue if such a 
design is created or exists internal USB mice and touchpads should also 
be a wake up.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ