linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Mochel <mochel@osdl.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Russell King <rmk@arm.linux.org.uk>, Greg KH <greg@kroah.com>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: PCI PM & compatibility
Date: Wed, 27 Aug 2003 16:29:24 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0308271628060.4140-100000@cherise> (raw)
In-Reply-To: <1061988185.1293.57.camel@gaston>


> > - When a device is suspended, the pm_users count of its pm_parent is 
> >   decremented, and incremented when the device is resumed. 
> > 
> > - device_suspend() makes multiple passes over the device list, in case
> >   power dependencies cause some devices to be deferred. It fails with an 
> >   error (and resumes all suspended devices) if a pass was made in which 
> >   no devicse were suspended, but there are still devices with a positive
> >   pm_users count. 
> 
> How do you intend to deal with the childs of the device that has
> pm_users non null ?
> 
> If you don't suspend it, you must also postpone all of it's childs.
> That makes the list walking slightly more tricky, or you finally go
> to a real tree structure ? (Which you may have to do to implement
> the set_parent() thing too, no ?

I don't understand. We suspend the children before we suspend the device, 
so as long as all the children go done, so will the parent device.


	Pat


  reply	other threads:[~2003-08-27 23:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 14:39 PCI PM & compatibility Benjamin Herrenschmidt
2003-08-23 17:08 ` Russell King
2003-08-23 17:28   ` Benjamin Herrenschmidt
2003-08-23 17:48     ` Russell King
2003-08-26 15:31       ` Patrick Mochel
2003-08-26 17:51         ` Russell King
2003-08-27 22:57           ` Patrick Mochel
2003-08-28 21:45             ` Russell King
2003-08-27 12:43         ` Benjamin Herrenschmidt
2003-08-27 23:29           ` Patrick Mochel [this message]
2003-08-28  8:39             ` Benjamin Herrenschmidt

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=Pine.LNX.4.44.0308271628060.4140-100000@cherise \
    --to=mochel@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).