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: Thu, 11 Jun 2009 15:57:48 +0200 Message-ID: <200906111557.49490.oliver@neukum.org> References: <200906111548.33751.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp-out002.kontent.com ([81.88.40.216]:39265 "EHLO smtp-out002.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751230AbZFKN5C (ORCPT ); Thu, 11 Jun 2009 09:57:02 -0400 In-Reply-To: <200906111548.33751.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 Donnerstag, 11. Juni 2009 15:48:33 schrieb Rafael J. Wysocki: > > > But after pm_request_resume() returns there's no means to make sure > > > nothing alters it back to RPM_SUSPENDED. The workqueue doesn't help > > > you because you've scheduled nothing by that time. The suspension will > > > work because C is still in RPM_SUSPENDED. > > > > This is an example where usage counters come in handy. > > Do you mean we can count suspend/resume requests for a device? No, we count reasons a device cannot be suspended. Drivers are allowed to add their own reasons. The core uses that mechanism to indicate that an ongoing resumption lower down is also a reason. The count going to zero is equivalent to a request to suspend. Regards Oliver