From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Giridhar Pemmasani <giri@lmc.cs.sunysb.edu>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
swsusp-devel@lists.sourceforge.net
Subject: Re: pmdisk suspend patch
Date: Mon, 15 Mar 2004 20:36:08 +1100 [thread overview]
Message-ID: <1079343368.2348.156.camel@gaston> (raw)
In-Reply-To: <20040315081323.37D3E7831D@mail.lmc.cs.sunysb.edu>
On Mon, 2004-03-15 at 19:13, Giridhar Pemmasani wrote:
> On Mon, 15 Mar 2004 17:35:07 +1100, Benjamin Herrenschmidt <benh@kernel.crashing.org> said:
>
> Benjamin> I agree that it would be nice to be able to resume only
> Benjamin> one "branch" of the PM tree like that, it's just not
> Benjamin> possible at this point.
>
> Thanks for your reply.
>
> My understanding was that although it is a specific device that is
> being resumed, actual resume method is for the bus and that should
> power up the whole IDE subsystem. Am I wrong?
No. The bus "type" handler gets the resume and passes it along to the
device straight. You really need to walk the PM tree and wake up all
parents first, starting from the top of tree.
> I see that there is dependency branch information in
> dpm_active/dpm_off/dpm_off_irq. Isn't it possible to traverse these
> lists and power up parents for a device? What are the issues involved?
>
> Cheers,
> Giri
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
prev parent reply other threads:[~2004-03-15 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 15:19 pmdisk suspend patch Giridhar Pemmasani
2004-03-15 6:35 ` Benjamin Herrenschmidt
2004-03-15 8:13 ` Giridhar Pemmasani
2004-03-15 9:36 ` Benjamin Herrenschmidt [this message]
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=1079343368.2348.156.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=giri@lmc.cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=swsusp-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.