From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Oliver Neukum <oliver@neukum.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
linux-pm@lists.linux-foundation.org,
Alexey Starikovskiy <astarikovskiy@suse.de>,
Johannes Berg <johannes@sipsolutions.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [RFC][PATCH] PM: Introduce new top level suspend and hibernation callbacks (rev. 2)
Date: Tue, 25 Mar 2008 21:56:11 +0100 [thread overview]
Message-ID: <200803252156.12185.rjw@sisk.pl> (raw)
In-Reply-To: <200803252149.37552.oliver@neukum.org>
On Tuesday, 25 of March 2008, Oliver Neukum wrote:
> Am Dienstag, 25. März 2008 21:41:48 schrieb Rafael J. Wysocki:
> > On Tuesday, 25 of March 2008, Oliver Neukum wrote:
> > > Am Dienstag, 25. März 2008 15:33:22 schrieb Alan Stern:
> > > > > so I'd say a
> > > > > failure to resume is just a limited subcase of a device vanishing during
> > > > > sleep.
> > > >
> > > > I'll go along with that. If a device vanishes during sleep, the PM
> > > > core isn't responsible for unregistering it -- the device's subsystem
> > > > is.
> > >
> > > Yes, that makes sense. You are right.
> >
> > Still, if ->resume() returns an error, does it make sense, from the PM core's
> > point of view, to execute ->complete() for that device, for example?
>
> IMO you must always keep the ordering invariant. If a parent returns an error
> the PM core must not wake its children.
I'm agreeing here, but one of the previous Alan's comments suggests he has a
differing opinion. Alan?
I'm considering to make the PM core skip the resuming of the children of
devices that failed to resume and skip calling ->complete() for that devices
and their children.
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-25 20:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 0:01 [RFC][PATCH] PM: Introduce new top level suspend and hibernation callbacks (rev. 2) Rafael J. Wysocki
2008-03-21 0:21 ` [linux-pm] " Johannes Berg
2008-03-21 0:26 ` Rafael J. Wysocki
2008-03-25 9:49 ` Oliver Neukum
2008-03-25 13:06 ` Rafael J. Wysocki
2008-03-25 13:15 ` Oliver Neukum
2008-03-25 14:19 ` Alan Stern
2008-03-25 14:24 ` Oliver Neukum
2008-03-25 14:33 ` Alan Stern
2008-03-25 19:48 ` Oliver Neukum
2008-03-25 20:41 ` Rafael J. Wysocki
2008-03-25 20:49 ` Oliver Neukum
2008-03-25 20:56 ` Rafael J. Wysocki [this message]
2008-03-26 14:10 ` Alan Stern
2008-03-26 14:24 ` Oliver Neukum
2008-03-26 14:40 ` Alan Stern
2008-03-26 15:42 ` Oliver Neukum
2008-03-26 16:36 ` Alan Stern
2008-03-26 20:46 ` Rafael J. Wysocki
2008-03-27 2:48 ` Alan Stern
2008-03-21 1:21 ` Alan Stern
2008-03-21 2:14 ` Rafael J. Wysocki
2008-03-21 2:53 ` Alan Stern
2008-03-22 22:17 ` Rafael J. Wysocki
2008-03-22 23:28 ` Alan Stern
2008-03-22 23:44 ` Rafael J. Wysocki
2008-03-23 2:07 ` Alan Stern
2008-03-23 18:41 ` Rafael J. Wysocki
2008-03-21 8:15 ` Sam Ravnborg
2008-03-23 21:16 ` Rafael J. Wysocki
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=200803252156.12185.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=astarikovskiy@suse.de \
--cc=johannes@sipsolutions.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=oliver@neukum.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