Date: Tue, 10 Jun 2003 21:41:32 +0200 From: Mark Santcroos <marks@ripe.net> To: Orion Hodson <orion@freebsd.org> Cc: current@freebsd.org Subject: Re: Correct PCI suspend and resume operations [ was Re: cirrus ich3 doesn't work after suspend to disk ] Message-ID: <20030610194132.GA4287@laptop.6bone.nl> In-Reply-To: <20030610191504.GA8927@laptop.6bone.nl> References: <20030609035127.GA36909@laptop.6bone.nl> <200306101644.h5AGiawR066527@puma.icir.org> <20030610191504.GA8927@laptop.6bone.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030610194132.GA4287>