From: Oliver Neukum Subject: Re: [patch update] Re: [linux-pm] Run-time PM idea (was: Re: [RFC][PATCH 0/2] PM: Rearrange core suspend code) Date: Wed, 10 Jun 2009 16:20:26 +0200 Message-ID: <200906101620.26559.oliver@neukum.org> References: <200906100057.04473.rjw@sisk.pl> <200906101029.27529.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp-out003.kontent.com ([81.88.40.217]:38119 "EHLO smtp-out003.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756146AbZFJOTj (ORCPT ); Wed, 10 Jun 2009 10:19:39 -0400 In-Reply-To: <200906101029.27529.rjw@sisk.pl> Content-Disposition: inline Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Rafael J. Wysocki" Cc: Alan Stern , linux-pm@lists.linux-foundation.org, ACPI Devel Maling List , LKML Am Mittwoch, 10. Juni 2009 10:29:26 schrieb Rafael J. Wysocki: > Argh, I forgot about some important things. > > First, there are devices with no parent (actually, it would be much easier > if they had a default dummy parent, but that's a separate issue). > > Second, the parent has to be taken into account in the asynchronous resume > path too (which BTW is more complicated). What happens if the parent's parent is also suspended? It seems to me that you must code this recursively. Regards Oliver