From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFC][PATCH 3/4] swsusp: Introduce restore platform operations
Date: Tue, 22 May 2007 22:30:34 +0200 [thread overview]
Message-ID: <200705222230.35078.rjw@sisk.pl> (raw)
In-Reply-To: <46534E2C.60808@gmail.com>
On Tuesday, 22 May 2007 22:10, Alexey Starikovskiy wrote:
> Rafael J. Wysocki ?????:
> > On Tuesday, 22 May 2007 01:55, Rafael J. Wysocki wrote:
> > Moreover, I'm not quite certain in which points the GPEs should actually be
> >
> > disabled and enabled. For example, there are some testing data indicating that
> > the enabling of GPEs should be done after all of the device drivers' .resume()
> > callbacks have run.
> Opposite, ACPI devices require enabled GPEs to do their resume, so
> enabling of GPEs
> should happen at least before .resume() of ACPI devices is called.
Theoretically, that surely is correct, and which is what the patch actually
does. :-)
Still, we have users for whom hibernation was broken by moving the execution
of acpi_leave_sleep_state() before enable_nonboot_cpus(). At least on one
of these systems the hibernation can be fixed by removing the execution of
acpi_leave_sleep_state() from before enable_nonboot_cpus() and adding a
simplified version of it that only executes _WAK and enables the GPEs *after*
device_resume(). Unfortunately, I was unable to check if _WAK was necessary
for this (I hope it wasn't).
Greetings,
Rafael
next prev parent reply other threads:[~2007-05-22 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 22:19 [RFC][PATCH 0/4] swsusp: Fix hibernation/restore code ordering Rafael J. Wysocki
2007-05-17 22:21 ` [RFC][PATCH 1/4] swsusp: Remove incorrect code from user.c Rafael J. Wysocki
2007-05-21 23:29 ` Pavel Machek
2007-05-17 22:22 ` [RFC][PATCH 2/4] swsusp: Remove code duplication between disk.c and user.c Rafael J. Wysocki
2007-05-21 23:30 ` Pavel Machek
2007-05-17 22:24 ` [RFC][PATCH 3/4] swsusp: Introduce restore platform operations Rafael J. Wysocki
2007-05-21 23:38 ` Pavel Machek
2007-05-21 23:55 ` Rafael J. Wysocki
2007-05-22 20:03 ` Rafael J. Wysocki
2007-05-22 20:10 ` Alexey Starikovskiy
2007-05-22 20:30 ` Rafael J. Wysocki [this message]
2007-05-17 22:26 ` [RFC][PATCH 4/4] swsusp: Fix hibernation code ordering Rafael J. Wysocki
2007-05-19 8:36 ` [RFC][PATCH 4/4] swsusp: Fix hibernation code ordering (updated) Rafael J. Wysocki
2007-05-21 23:31 ` 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=200705222230.35078.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=aystarik@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
/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