From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [GIT PULL] PM updates for 2.6.33 Date: Sat, 5 Dec 2009 16:45:41 -0800 Message-ID: <20091205164541.5e0f209a@infradead.org> References: <200912052216.19540.rjw@sisk.pl> <200912060055.36130.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from casper.infradead.org ([85.118.1.10]:55892 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752229AbZLFAnd (ORCPT ); Sat, 5 Dec 2009 19:43:33 -0500 In-Reply-To: <200912060055.36130.rjw@sisk.pl> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Rafael J. Wysocki" Cc: Linus Torvalds , LKML , ACPI Devel Maling List , pm list , Alan Stern On Sun, 6 Dec 2009 00:55:36 +0100 "Rafael J. Wysocki" wrote: > > Disk spinup/spindown takes time, but also some ACPI devices resume > slowly, serio devices do that too and there are surprisingly many > drivers that wait (using msleep() during suspend and resume). Apart > from this, every PCI device going from D0 to D3 during suspend and > from D3 to D0 during resume requires us to sleep for 10 ms (the > sleeping is done by the PCI core, so the drivers don't even realize > its there). maybe a good step is to make a scripts/bootgraph.pl equivalent for suspend/resume (or make a debug mode that outputs in a compatible format so that the script can be used as is.. I don't mind either way, and consider this my offer to help with such a script as long as there's sufficient logging in dmesg ;-) that way we can SEE which ones are an issue.... and by how much. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org