From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Subtle semantic issue with sleep callbacks in drivers
Date: 16 Apr 2003 21:29:52 +0200 [thread overview]
Message-ID: <1050521391.644.5.camel@debian> (raw)
In-Reply-To: <Pine.LNX.4.44.0304161124400.912-100000@cherise>
On Wed, 2003-04-16 at 20:31, Patrick Mochel wrote:
> This is not necessarily a slot-by-slot question, but whether the entire
> PCI/AGP buses will lose power during the sleep state, right?
This is really per-slot. Especially on embedded or laptops, you really
don't know how each slot is wired regarding the power planes.
> There are a couple of things to note.
>
> This is only an issue when doing suspend-to-RAM. Suspend-to-disk, and
> power-on suspend will definitely lose power and definitely not lose any
> power, respectively. So, you need a mechanism to determine what state the
> system is entering.
Yes.
> Next, once you determine that we're entering suspend-to-RAM, you need to
> know if the buses will lose power. In order to have a generic suspend
> sequence, there must be a set of platform-specific methods to do all the
> fun platform things that must be done. In that object, we can easily add a
> flag that specifies whether or not the platform will lose power. This flag
> can be initialized based on platform knowledge on startup.
It's individual to each device though. And we must also have a flag the
platform can use to indicate it can/will re-POST the card (by re-running
the BIOS or whatever firmware)...
> In short, there should be no problems. Hopefully, I should have something
> within the week to review/test. (Yeah yeah, talk is cheap, but I'm getting
> there).
Good :) I'm getting there too for the pmac implementation finally...
Ben.
next prev parent reply other threads:[~2003-04-16 19:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 10:00 Subtle semantic issue with sleep callbacks in drivers Benjamin Herrenschmidt
2003-04-14 10:11 ` Benjamin Herrenschmidt
2003-04-16 18:31 ` Patrick Mochel
2003-04-16 19:29 ` Benjamin Herrenschmidt [this message]
2003-04-23 15:32 ` Pavel Machek
2003-04-14 17:09 Grover, Andrew
2003-04-14 17:40 ` Benjamin Herrenschmidt
2003-04-23 15:29 ` Pavel Machek
2003-04-14 19:07 Grover, Andrew
2003-04-14 19:18 ` Benjamin Herrenschmidt
2003-04-14 19:56 ` Alan Cox
2003-04-23 15:34 ` Pavel Machek
2003-04-14 21:09 Grover, Andrew
2003-04-16 18:39 ` Patrick Mochel
2003-04-16 19:36 ` Benjamin Herrenschmidt
2003-04-17 13:35 ` Alan Cox
2003-04-17 14:48 ` Jeff Garzik
2003-04-17 15:09 ` John Bradford
2003-04-17 15:09 ` Jeff Garzik
2003-04-17 15:47 ` John Bradford
2003-04-17 15:56 ` Jeff Garzik
2003-04-17 16:24 ` Alan Cox
2003-04-18 7:37 ` Greg KH
2003-04-18 7:51 ` John Bradford
2003-04-18 9:10 ` Russell King
2003-04-18 11:18 ` Alan Cox
2003-04-18 11:30 ` Alan Cox
2003-04-29 8:28 ` Pavel Machek
2003-04-17 14:59 ` John Bradford
2003-04-17 15:04 ` Alan Cox
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=1050521391.644.5.camel@debian \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).