From: Pavel Machek <pavel@ucw.cz>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] swsusp: allow drivers to determine between write-resume and actual wakeup
Date: Mon, 5 Jun 2006 11:23:42 +0200 [thread overview]
Message-ID: <20060605092342.GI5540@elf.ucw.cz> (raw)
In-Reply-To: <20060605091131.GE8106@htj.dyndns.org>
On Po 05-06-06 18:11:31, Tejun Heo wrote:
> Currently, there is no way to tell whether a device is resuming to
> write swsusp image or waking up from actual software suspend. FREEZE
> and SUSPEND are different operations for some devices (e.g. disks
> don't spin down for FREEZE) and the resume operation for each is also
> different.
>
> This patch makes swsusp change device power state from PMSG_FREEZE to
> PMSG_SUSPEND on resume from software suspend. A driver can determine
> whether it's getting thawed or resuming by looking at device power
> state - if FREEZE, it's getting thawed to write image; if SUSPEND,
> resuming from software suspend. This patch doesn't affect drivers
> which don't update device power state. Only drivers which set power
> state to FREEZE after freezing are affected.
No, sorry.
If driver is interested if previous operation was FREEZE or
SUSPEND... just store that information locally.
If you want to know if you RESUME was after normal FREEZE or if it is
after reboot, there's better patch floating around to do that.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-06-05 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 9:11 [PATCH] swsusp: allow drivers to determine between write-resume and actual wakeup Tejun Heo
2006-06-05 9:23 ` Pavel Machek [this message]
2006-06-05 11:50 ` Tejun Heo
2006-06-05 12:43 ` Tejun Heo
2006-06-05 13:15 ` Pavel Machek
2006-06-05 13:17 ` Pavel Machek
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=20060605092342.GI5540@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).