Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760336AbZFLT4S (ORCPT ); Fri, 12 Jun 2009 15:56:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753972AbZFLT4I (ORCPT ); Fri, 12 Jun 2009 15:56:08 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:59537 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752964AbZFLT4H (ORCPT ); Fri, 12 Jun 2009 15:56:07 -0400 From: "Rafael J. Wysocki" To: Alan Stern Subject: Re: [patch update] Re: [linux-pm] Run-time PM idea (was: Re: [RFC][PATCH 0/2] PM: Rearrange core suspend code) Date: Fri, 12 Jun 2009 21:56:14 +0200 User-Agent: KMail/1.11.2 (Linux/2.6.30-rc8-rjw; KDE/4.2.4; x86_64; ; ) Cc: Oliver Neukum , "Linux-pm mailing list" , ACPI Devel Maling List , LKML References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906122156.14873.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 929 Lines: 23 On Friday 12 June 2009, Alan Stern wrote: > On Fri, 12 Jun 2009, Rafael J. Wysocki wrote: > > > So, are you suggesting that the core should only check the "all children > > suspended" condition if special flag is set in dev_pm_info? > > Or rather, check it only if the special flag _isn't_ set. Where the default is unset, I guess? But then, what about the resuming of the parents before the device is resumed? Should the parents be resumed regardless of the flag state? And if so, what's the condition for breaking the recurrence? Surely it's not sufficient to check if the parent is active, because its parent need not be active if it has this special flag set. Best, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/