From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
Pavel Machek <pavel@suse.cz>, "Brown, Len" <len.brown@intel.com>
Subject: Re: Runtime GPEs not saved over suspend/resume if type != "platform"
Date: Wed, 25 Oct 2006 17:07:45 +0200 [thread overview]
Message-ID: <200610251707.46333.rjw@sisk.pl> (raw)
In-Reply-To: <453F77D4.2080706@linux.intel.com>
Hi,
On Wednesday, 25 October 2006 16:42, Alexey Starikovskiy wrote:
> Hi,
>
> There is a problem with swsuspend and GPE events.
> Now they are restored from acpi_pm_finish(), which is called only if we
> suspend with "platform" option, what means that if we suspended to disk
> with the default "shutdown" option after resume all the GPEs will be disabled.
> This presents us with the overheating problem after resume at very least.
> I see two solutions: one is to make "platform" to be default option if ACPI is enabled,
> and second -- enable GPE events from some other function, which will be called in any case.
>
> What do you think?
Obviously we can "fix" that in the short run by causing "platform" to be the
default. Still, I think swsusp should work regardless of whether "platform"
or "shutdown" is used.
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
next prev parent reply other threads:[~2006-10-25 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 14:42 Runtime GPEs not saved over suspend/resume if type != "platform" Alexey Starikovskiy
2006-10-25 15:07 ` Rafael J. Wysocki [this message]
2006-10-27 5:22 ` Len Brown
2006-10-27 8:40 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-10-25 15:15 Yu, Luming
2006-10-25 16:35 ` Alexey Starikovskiy
2006-10-25 18:54 ` Rafael J. Wysocki
2006-10-26 13:21 ` Alexey Starikovskiy
2006-10-26 15:01 ` Rafael J. Wysocki
2006-10-26 15:05 ` Alexey Starikovskiy
2006-10-25 15:18 Yu, Luming
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=200610251707.46333.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=alexey_y_starikovskiy@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=pavel@suse.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