Date: Wed, 11 Jun 2003 22:59:24 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: marks@ripe.net Cc: orion@freebsd.org Subject: Re: Correct PCI suspend and resume operations Message-ID: <20030611.225924.52165341.imp@bsdimp.com> In-Reply-To: <20030610194132.GA4287@laptop.6bone.nl> References: <200306101644.h5AGiawR066527@puma.icir.org> <20030610191504.GA8927@laptop.6bone.nl> <20030610194132.GA4287@laptop.6bone.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20030610194132.GA4287@laptop.6bone.nl>
Mark Santcroos <marks@ripe.net> writes:
: On Tue, Jun 10, 2003 at 09:15:05PM +0200, Mark Santcroos wrote:
: > > AFAICT, we don't common code for handling this and maybe there should
: > > be some rather than have each driver replicate this behaviour.
: >
: > In general, that would of course be better. However, I don't know if the
: > PCI layer (in this case) always knows enough.
: > On the other side, if the device itself has to do some special things, the
: > PCI layer could at least do the generic stuff.
:
: To be more precise, the suspend function should know the powerstate it is
: transitioning to. If it keeps context (D0-D2) it doesn't need to do much
: special, if it will loose context (D3) it should save the state at
: suspend, and restore the state at resume.
Sadly, in the current scheme, the device driver has no way of knowing
what the new power state is going to be.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030611.225924.52165341.imp>