From: Alexey Starikovskiy <aystarik@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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: Wed, 23 May 2007 00:10:20 +0400 [thread overview]
Message-ID: <46534E2C.60808@gmail.com> (raw)
In-Reply-To: <200705222203.48568.rjw@sisk.pl>
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.
Regards,
Alex.
next prev parent reply other threads:[~2007-05-22 20:10 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 [this message]
2007-05-22 20:30 ` Rafael J. Wysocki
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=46534E2C.60808@gmail.com \
--to=aystarik@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox