From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
linux-pm@lists.osdl.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: Problems with PM_FREEZE
Date: Wed, 28 Sep 2005 21:09:24 +0200 [thread overview]
Message-ID: <200509282109.25419.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0509281451010.5193-100000@iolanthe.rowland.org>
Hi,
On Wednesday, 28 of September 2005 20:54, Alan Stern wrote:
> On Wed, 28 Sep 2005, Rafael J. Wysocki wrote:
>
> > IMO if the driver is a module it should not make any assumptions
> > on the state of the device when its resume routine is called. Instead,
> > it should assume the device can be in an arbitrary state and proceed
> > in the safest way possible. Which is 3.
>
> That's what it should do when resuming from disk.
>
> But that's not what it should do when it's being resumed just after the
> memory image was created, in order to write out the image. In this case
> the device is known to be in FREEZE, not SUSPEND, and to save time we
> would like the driver not to go through a full resume procedure.
>
> The problem is that currently the driver has no way to tell the difference
> between the two types of resume. What's needed is a way for driver to
> tell, and that can be added easily enough.
Yes, I've been thinking about it for some time. It seems to me we could do
this with the help of an additional field in pm_message_t.
Greetings,
Rafael
next prev parent reply other threads:[~2005-09-28 19:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 2:09 Problems with PM_FREEZE Alan Stern
2005-09-27 12:26 ` Pavel Machek
2005-09-27 19:02 ` Alan Stern
2005-09-27 19:58 ` Pavel Machek
2005-09-27 20:25 ` Alan Stern
2005-09-27 20:32 ` Pavel Machek
2005-09-27 21:30 ` Nigel Cunningham
2005-09-27 22:01 ` Pavel Machek
2005-09-27 23:19 ` Nigel Cunningham
2005-09-28 2:58 ` Alan Stern
2005-09-28 3:27 ` Nigel Cunningham
2005-09-28 15:46 ` David Brownell
2005-09-28 16:17 ` Alan Stern
2005-09-28 20:53 ` Pavel Machek
2005-09-28 21:15 ` Alan Stern
2005-09-28 21:18 ` Pavel Machek
2005-09-28 21:20 ` David Brownell
2005-09-28 21:22 ` Pavel Machek
2005-09-28 13:03 ` Pavel Machek
2005-09-29 15:45 ` Alan Stern
2005-09-29 17:12 ` David Brownell
2005-09-29 17:31 ` Pavel Machek
2005-09-29 18:22 ` David Brownell
2005-09-29 19:01 ` Rafael J. Wysocki
2005-09-29 17:49 ` Alan Stern
2005-09-28 13:04 ` Pavel Machek
2005-09-28 13:51 ` Rafael J. Wysocki
2005-09-28 18:54 ` Alan Stern
2005-09-28 19:09 ` Rafael J. Wysocki [this message]
2005-09-28 19:31 ` Alan Stern
2005-09-28 20:51 ` Pavel Machek
2005-09-28 21:13 ` Alan Stern
2005-09-28 21:19 ` Pavel Machek
2005-09-28 21:56 ` Rafael J. Wysocki
2005-09-28 22:01 ` Pavel Machek
2005-09-28 22:14 ` Rafael J. Wysocki
2005-09-28 20:51 ` Pavel Machek
2005-09-28 21:08 ` David Brownell
2005-09-28 21:13 ` Pavel Machek
2005-09-28 21:12 ` Alan Stern
2005-09-28 15:28 ` David Brownell
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=200509282109.25419.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.osdl.org \
--cc=ncunningham@cyclades.com \
--cc=pavel@ucw.cz \
--cc=stern@rowland.harvard.edu \
/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