mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Pavel Machek <pavel@ucw.cz>
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 11:09:36 +0800	[thread overview]
Message-ID: <1248059376.26272.311.camel@rzhang-dt> (raw)
In-Reply-To: <20090719221658.GL26511@elf.ucw.cz>

On Mon, 2009-07-20 at 06:16 +0800, Pavel Machek wrote:
> Hi!
> 
> > 
> > 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.
> 
Sorry, the problem I described above is wrong.
We just disable the EC interrupt mode in S3, but it still works.
Battery can access EC address space before EC resumed, in low speed.


> 
> > > 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.
> > 
this is right.

thanks,
rui


  reply	other threads:[~2009-07-20  3:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  7:38 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
2009-07-20  3:09           ` Zhang Rui [this message]
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=1248059376.26272.311.camel@rzhang-dt \
    --to=rui.zhang@intel.com \
    --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=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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
all inboxes | Powered by JetHome®