From: "Rafael J. Wysocki" Subject: Re: [RFC][PATCH 0/7] PM: Asynchronous suspend and resume (updated) Date: Tue, 18 Aug 2009 22:01:11 +0200 Message-ID: <200908182201.11489.rjw@sisk.pl> References: <200908122218.13975.rjw@sisk.pl> <200908170215.21173.rjw@sisk.pl> <1250579793.5351.79.camel@rzhang-dt> Mime-Version: 1.0 Content-Type: Text/Plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:55724 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751007AbZHRUA2 convert rfc822-to-8bit (ORCPT ); Tue, 18 Aug 2009 16:00:28 -0400 In-Reply-To: <1250579793.5351.79.camel@rzhang-dt> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Zhang Rui Cc: linux-pm , linux-acpi , Linux Kernel Mailing List , Len Brown , Alan Stern , Arjan van de Ven , Greg KH On Tuesday 18 August 2009, Zhang Rui wrote: > On Mon, 2009-08-17 at 08:15 +0800, Rafael J. Wysocki wrote: > > On Wednesday 12 August 2009, Rafael J. Wysocki wrote: > > > Hi, > > >=20 > > > The following patches introduce a mechanism allowing us to execut= e device > > > drivers' suspend and resume callbacks asynchronously during syste= m sleep > > > transitions, such as suspend to RAM. The idea is explained in th= e [1/1] patch > > > message. > >=20 > > Changes: > >=20 > > * Added [1/7] that fixes kerneldoc comments in drivers/base/power/m= ain.c > > (this is a 2.6.32 candidate). > >=20 > > * Added [2/7] adding a framework for representing PM link (idea des= cribed > > in the patch message). > >=20 > > * [3/7] is the async resume patch (idea described in the patch mess= age). > >=20 > > * [4/7] is the async suspend patch. > >=20 > > * [5/7] - [7/7] set async_suspend for devices in a few selected sub= systems. > >=20 > > The patches have been tested on HP nx6325. > >=20 > I tried this patch set and it does work. :) > But unfortunately it doesn't save too much time. >=20 > I still think that the child device should inherit its parent's > async_suspend flag to do the asynchronous resume more efficiently. >=20 > or at least we should provide such an interface > in =EF=BB=BFdrivers/base/power/common.c, so that device can tell the = device core > to inherit this flag if there is no off-tree dependency. Well, I'd prefer to identify all of the off-tree dependencies that have= to be taken into account and handle all devices asynchronously. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html