public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: Runtime resume of children
Date: Mon, 23 Nov 2009 23:11:49 +0100	[thread overview]
Message-ID: <200911232311.49110.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0911231556500.2958-100000@iolanthe.rowland.org>

On Monday 23 November 2009, Alan Stern wrote:
> On Mon, 23 Nov 2009, Rafael J. Wysocki wrote:
> 
> > On Sunday 22 November 2009, Alan Stern wrote:
> > > Rafael:
> > > 
> > > Here's the situation.  Device A has children B1, ..., Bn (possibly
> > > others too).  I need to guarantee that whenever A is active, so are the
> > > children.
> > 
> > But it's perfectly valid to have an inactive device under an active parent, so
> > I guess this is not a general case.
> 
> Correct.  It's a specific case that I need to handle for USB.
> 
> > > Do you have any ideas on how to approach this?  How about allowing A's
> > > runtime_resume method to set A->power.runtime_status to RPM_ACTIVE,
> > > before it tries to resume the B's?  That would avoid the deadlock.
> > 
> > I don't see a problem with that as long as the A's runtime_resume returns 0 in
> > such a case.
> 
> Should I export a routine from the PM core for doing this or just 
> implement it directly?

Please implement that directly.  If there's any other bus type needing it,
we'll move it to the core.

Thanks,
Rafael

  reply	other threads:[~2009-11-23 22:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 22:13 Runtime resume of children Alan Stern
2009-11-23 20:44 ` Rafael J. Wysocki
2009-11-23 20:59   ` Alan Stern
2009-11-23 22:11     ` Rafael J. Wysocki [this message]
2009-11-25  9:41     ` Oliver Neukum
2009-11-25 20:46       ` Alan Stern
2009-11-26 16:47         ` Oliver Neukum
2009-11-27 13:20           ` Mark Brown

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=200911232311.49110.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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