From: Michael Trimarchi <trimarchi@gandalf.sssup.it>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
linux-pm@lists.linux-foundation.org, len.brown@intel.com
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 [thread overview]
Message-ID: <49FA374C.8000501@gandalf.sssup.it> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0904251432250.20179-100000@netrider.rowland.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
next prev parent reply other threads:[~2009-04-30 23:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 17:24 [RFC Add no_suspend attribute V2] Let the driver know if it's in use Michael Trimarchi
2009-04-24 17:31 ` Randy Dunlap
2009-04-24 17:36 ` Michael Trimarchi
2009-04-24 17:55 ` Michael Trimarchi
2009-04-24 22:55 ` Greg KH
2009-04-25 8:21 ` Michael Trimarchi
2009-04-25 9:07 ` Michael Trimarchi
2009-04-25 10:56 ` Rafael J. Wysocki
2009-04-25 12:03 ` Michael Trimarchi
2009-04-25 16:57 ` Alan Stern
2009-04-25 17:11 ` Michael Trimarchi
2009-04-25 18:33 ` Alan Stern
2009-04-30 23:42 ` Michael Trimarchi [this message]
2009-05-01 2:27 ` Alan Stern
2009-07-23 14:09 ` Michael Trimarchi
2009-07-23 14:32 ` Rafael J. Wysocki
2009-07-23 14:56 ` Alan Stern
2009-07-23 16:00 ` Michael Trimarchi
2009-07-24 15:36 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49FA374C.8000501@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox