From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Trimarchi Subject: Re: [RFC Add no_suspend attribute V2] Let the driver know if it's in use Date: Fri, 01 May 2009 01:42:04 +0200 Message-ID: <49FA374C.8000501@gandalf.sssup.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Alan Stern Cc: Greg KH , linux-pm@lists.linux-foundation.org, len.brown@intel.com List-Id: linux-pm@vger.kernel.org Hi, Alan Stern wrote: > On Sat, 25 Apr 2009, Michael Trimarchi wrote: > > >> Ok, I understand, so how to know the devices dependences? There is a way >> to express >> this relation? Because if it is not possible a single flag can be used >> > > Nobody knows all the device dependencies. That's why we're afraid that > if you change the list, something will break. > > But this happen for broken device? The list is a sufficient condition for correct suspend phase but is not necesarry, because all the dependence are not registerd. But just to understand: What are the typical situation, because I suppose that we are not talking about broken device. >>> This will set the dont_suspend flag for all devices in the subtree >>> starting at topdev. >>> >>> >> Yes this is possible, but you walk all list twice. >> > > So what? Walking the list is very quick, and you're not on a > time-critical path. > > Yes, you are right, I will submit a new patch with all the necessary fixes > Alan Stern > > > Thanks