From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.osdl.org, Nigel Cunningham <ncunningham@cyclades.com>
Subject: Re: Problems with PM_FREEZE
Date: Thu, 29 Sep 2005 00:01:38 +0200 [thread overview]
Message-ID: <20050928220138.GL2506@elf.ucw.cz> (raw)
In-Reply-To: <200509282356.07108.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Hi!
> > > 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.
> >
> > The problem that no pm_message_t is passed to resume routines.
>
> Yes, shame on me (I desperately need some sleep).
>
> How about calling *_suspend() twice, first before the image is created
> and second after it has been created but before *_resume() are called,
> with the second call only telling the driver the next resume will be
> resume-during-suspend?
Could we do it properly and pass pm_message_t to resume()? Yes, it is
more work, but no, we don't need hacks there.
Pavel
--
if you have sharp zaurus hardware you don't need... you know my address
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-09-28 22:01 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
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 [this message]
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=20050928220138.GL2506@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-pm@lists.osdl.org \
--cc=ncunningham@cyclades.com \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.