From: Pavel Machek <pavel@suse.cz>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Andrew Grover <andrew.grover@intel.com>,
kernel list <linux-kernel@vger.kernel.org>,
ACPI mailing list <acpi-devel@lists.sourceforge.net>
Subject: Re: Ask devices to powerdown before S3 sleep
Date: Tue, 21 Jan 2003 12:03:58 +0100 [thread overview]
Message-ID: <20030121110358.GE24349@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0301210554050.2653-100000@montezuma.mastecende.com>
Hi!
> > > > SUSPEND_RESUME phase is needed for turning off IO-APIC. [I believe
> > > > SUSPEND_DISABLE should be so simple that errors just should not be
> > > > there, and besides we would not know how to safely enable devices from
> > > > such weird state, anyway]. Please apply,
> > >
> > > panic() is a bit on the extreme side no? I know diddly about ACPI and
> > > the current code, but can't you check for _PS3 methods or _S3D mappings
> > > for your devices before hand to be certain that the system can even go
> > > down to S3 somewhat reliably?
> >
> > At this point, you already DISABLED half of devices, and you don't
> > even know *which* ones. You can't just send them ENABLE and hope it
> > works.
>
> I meant checking before you even attempt starting the process of doing S3.
All devices should support that -- BIOS should not advertise S3 if it
can not do that, and kernel should be fixed to work.
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
prev parent reply other threads:[~2003-01-21 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 21:46 Pavel Machek
2003-01-21 1:27 ` Andre Hedrick
2003-01-21 10:47 ` Pavel Machek
2003-01-21 11:38 ` Andre Hedrick
2003-01-21 7:56 ` Zwane Mwaikambo
2003-01-21 10:46 ` Pavel Machek
2003-01-21 10:55 ` Zwane Mwaikambo
2003-01-21 11:03 ` Pavel Machek [this message]
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=20030121110358.GE24349@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@holomorphy.com \
/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
all inboxes | Powered by JetHome®