From: Nigel Cunningham <ncunningham@cyclades.com>
To: Felix Kuehling <fkuehlin@ati.com>
Cc: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>,
"Yu, Luming" <luming.yu@intel.com>,
linux-acpi@vger.kernel.org, Matthew Tippett <mtippett@ati.com>,
Chang-Hwa Lee <changl@ati.com>, Samuel Li <samli@ati.com>
Subject: Re: Power-button event after resume from S3
Date: Fri, 14 Apr 2006 15:33:32 +1000 [thread overview]
Message-ID: <200604141533.40747.ncunningham@cyclades.com> (raw)
In-Reply-To: <1144938518.1936.8.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Hi.
On Friday 14 April 2006 00:28, Felix Kuehling wrote:
> On Tue, 2006-11-04 at 14:14 +1000, Nigel Cunningham wrote:
> > Hi.
> >
> > On Tuesday 11 April 2006 12:35, Sanjoy Mahajan wrote:
> > > > if(acpi_during_suspend_resume)
> > > > don't generate power button event to confuse user space daemon
> > >
> > > This patch might be useful useful in setting and unsetting
> > > acpi_during_suspend_resume (and also using it, but you should ignore
> > > those as they are hacks for a different problem). The equivalent
> > > variable in the patch below is acpi_in_suspend.
> >
> > If you want this to get wider testing, I'll be happy to include it in the
> > Suspend2 patchset.
>
> Just to clarify, software suspend is not affected by this problem. Only
> S3, possibly S1 and maybe S4BIOS are affected, though I've never seen
> the latter on any real system.
Thanks. I still think it would be worth including, because Suspend2 (and now
uswsusp, I believe) lets you choose what to do after writing the image. One
of the options is suspending to ram, so that you effectively get disk-backed
suspend to ram. It might be useful in this situation.
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-04-14 5:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 1:11 Power-button event after resume from S3 Yu, Luming
2006-04-11 2:35 ` Sanjoy Mahajan
2006-04-11 4:14 ` Nigel Cunningham
2006-04-13 14:28 ` Felix Kuehling
2006-04-14 5:33 ` Nigel Cunningham [this message]
2006-04-14 9:29 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2006-04-07 2:49 Yu, Luming
2006-04-10 20:47 ` Felix Kuehling
2006-04-06 20:12 Felix Kuehling
2006-04-06 22:15 ` Sanjoy Mahajan
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=200604141533.40747.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=changl@ati.com \
--cc=fkuehlin@ati.com \
--cc=linux-acpi@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=mtippett@ati.com \
--cc=samli@ati.com \
--cc=sanjoy@mrao.cam.ac.uk \
/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