linux-kernel - Re: System suspend states and device driver suspend() callback

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]

Date:	Fri, 16 Aug 2013 17:13:42 +0000
From:	Li Yang-R58472 <r58472@...escale.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: System suspend states and device driver suspend() callback

在 2013-8-16，下午7:22，"Rafael J. Wysocki" <rjw@...k.pl> 写道：

> On Friday, August 16, 2013 04:06:26 PM Li Yang wrote:
>> Hi Guys,
>> 
>> Is there a standard way for the device drivers to know if the system
>> is going to “standby” mode or “mem” mode when the suspend() callbacks
>> are called?
> 
> No, there's none.
> 
> What do you need that for?

Some chips like ours are putting the on-chip devices into different low power states when entering different system low power states.  When we enter system standby, on-chip devices are clock gated.  While entering suspend to ram, on-chip devices are power gated.  We want to driver to act differently too when entering different suspend states.

- Leo

> 
> Rafael
> 
>