From: Pavel Machek <pavel@ucw.cz>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Arjan van de Ven <arjan@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH 2/8] introduce the device async action mechanism
Date: Mon, 20 Jul 2009 00:16:58 +0200 [thread overview]
Message-ID: <20090719221658.GL26511@elf.ucw.cz> (raw)
In-Reply-To: <1247798643.26272.275.camel@rzhang-dt>
Hi!
> > During suspend-resume we know dependencies between
> > devices beforehand, at least in theory, so we can use them.
> >
> that's why I use multiple async domains. :)
> One domain for a device group.
>
> > In particular, we have to make sure that parent devices will not be suspended
> > until all of their children have been suspended and children devices will not
> > be resumed before the parents.
>
> that's not enough.
> ???For examples,
> ACPI battery and EC are independent devices, but EC must be resumed
> before battery because battery driver may access some EC address space
> during resume time.
Yes, but those dependencies should be pulled from driver tree, not
adding separate dependencies infrastructure.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-07-19 22:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 7:38 [PATCH 2/8] introduce the device async action mechanism Zhang Rui
2009-07-15 0:31 ` [linux-pm] " Pavel Machek
2009-07-15 13:00 ` Arjan van de Ven
2009-07-16 2:05 ` Zhang Rui
2009-07-17 1:11 ` Rafael J. Wysocki
2009-07-17 2:44 ` Zhang Rui
2009-07-19 22:16 ` Pavel Machek [this message]
2009-07-20 3:09 ` Zhang Rui
2009-07-20 16:24 ` Rafael J. Wysocki
2009-07-17 4:31 ` Arjan van de Ven
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=20090719221658.GL26511@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=arjan@infradead.org \
--cc=arjan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
/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