From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: Problems with PM_FREEZE Date: Wed, 28 Sep 2005 23:13:15 +0200 Message-ID: <20050928211315.GD2506@elf.ucw.cz> References: <200509281551.30587.rjw@sisk.pl> <20050928205106.GA2506@elf.ucw.cz> <20050928210837.02F19E3727@adsl-69-107-32-110.dsl.pltn13.pacbell.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============23627820713141734==" Return-path: In-Reply-To: <20050928210837.02F19E3727@adsl-69-107-32-110.dsl.pltn13.pacbell.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: David Brownell Cc: linux-pm@lists.osdl.org, ncunningham@cyclades.com List-Id: linux-pm@vger.kernel.org --===============23627820713141734== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! > > > But that's not what it should do when it's being resumed just after the > > > memory image was created, in order to write out the image. In this case > > > the device is known to be in FREEZE, not SUSPEND, and to save time we > > > would like the driver not to go through a full resume procedure. > > > > Do you have any driver which can save some significant ammount of time > > that way? > > If there is no such driver, then there's no need for the FREEZE state. Wrong. IDE can avoid spinning down disk when *entering* FREEZE state. No difference during *exiting* it. Pavel -- if you have sharp zaurus hardware you don't need... you know my address --===============23627820713141734== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============23627820713141734==--