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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 3 Oct 2016 17:16:19 -0700
From:   Rajat Jain <>
To:     Kalle Valo <>
Cc:     Amitkumar Karwar <>,
        Nishant Sarmukadam <>,,,
        Wei-Ning Huang <>,
        Brian Norris <>,
        Eric Caruso <>,
        Rajat Jain <>
Subject: Re: [v2] mwifiex: report wakeup for wowlan

Hello Kalie,

On Mon, Oct 3, 2016 at 6:04 AM, Kalle Valo <> wrote:
> Rajat Jain <> wrote:
>> Enable notifying wakeup source to the PM core in case of
>> a wake on wireless LAN event.
>> Signed-off-by: Wei-Ning Huang <>
>> Signed-off-by: Rajat Jain <>
>> Tested-by: Wei-Ning Huang <>
>> Reviewed-by: Eric Caruso <>
>> Acked-by: Amitkumar Karwar <>
> The commit log doesn't give any background info. Does this fix a bug or
> why is it needed?

Some of chromeos' features (called "darkresume" in chromeos
terminology) use and track the wake up sources using the wakeup
attributes in sysfs. Since the wireless device can wake up the host,
hence we wanted to add it as a wakeup source to the system, and in the
case of an actual wakeup event, trigger to the PM core that it was
indeed caused by the device and it increments the different counters
etc. In the absence of this patch,  the feature wasn't working very
well (as it was apparently confused about the cause of wake up).



Powered by blists - more mailing lists