From: Nigel Cunningham <ncunningham@cyclades.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: Problems with PM_FREEZE
Date: Wed, 28 Sep 2005 07:30:34 +1000 [thread overview]
Message-ID: <1127855345.4802.13.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0509271455140.636-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]
Hi Alan.
On Wed, 2005-09-28 at 05:02, Alan Stern wrote:
> On Tue, 27 Sep 2005, Pavel Machek wrote:
>
> > Hi!
> >
> > > A problem with the PM_FREEZE state has surfaced recently.
> > >
> > > It has to do with the device state recorded in the memory image. When the
> > > image is made, devices are in the FREEZE state, and that's what gets
> > > recorded. But then the image is written to disk and devices are put into
> > > SUSPEND.
> > >
> > > Later on, when the system wakes up and the image is restored, drivers are
> > > asked to resume the devices. The problem is that now the drivers think
> > > the devices are in FREEZE when in fact they are really in SUSPEND. The
> > > difference is significant and it can cause errors in the resume procedure.
> >
> > No; devices are in FREEZE if their driver was in kernel, and in some kind
> > of power up state when not. Drivers should just handle both.
>
> For USB, that "some kind of power up state" will in fact be SUSPEND.
Excuse me taking a step back, but I think you guys might be solving a
problem that doesn't exist...
How do USB drivers get into a suspend state? At suspend time, before the
atomic copy is made they have been told to FREEZE. At resume time, prior
to the atomic restore, they have been told to FREEZE. The state they're
told to enter when we powerdown should be irrelevant, because after that
we have powered down the whole system and then powered it back up like
we would for a normal boot. The "some kind of powered up state" should
be ON, unless the usb drivers are managing to retain power and state
across a power down and reboot (I suppose you're going to tell me they
are!).
Regards,
Nigel
>
> ______________________________________________________________________
> _______________________________________________
> linux-pm mailing list
> linux-pm@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/linux-pm
--
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-09-27 21:30 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 [this message]
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
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=1127855345.4802.13.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=linux-pm@lists.osdl.org \
--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