From: David Brownell <david-b@pacbell.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
pm list <linux-pm@lists.linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC][PATCH] PM: Separate suspend and hibernation callbacks (highest level) - updated
Date: Wed, 12 Mar 2008 01:37:24 -0800 [thread overview]
Message-ID: <200803120237.24857.david-b@pacbell.net> (raw)
In-Reply-To: <200803101758.01826.rjw@sisk.pl>
On Monday 10 March 2008, Rafael J. Wysocki wrote:
> + * @poweroff: Hibernation-specific, executed after saving a hibernation image.
> + * Quiesce the device, put it into a low power state appropriate for the
> + * upcoming system state (such as PCI_D3hot), and enable wakeup events as
> + * appropriate.
This seems uncomfortably similar to device_driver.shutdown().
The only obvious difference is wakeup event handling, and even
that is already a function of the target system state.
Are both methods needed?
Shouldn't this be more generic, not "hibernation-specific"?
--
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-12 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 1:20 [RFC][PATCH] PM: Separate suspend and hibernation callbacks (highest level) - updated Rafael J. Wysocki
2008-03-09 4:13 ` Alan Stern
2008-03-09 13:28 ` Rafael J. Wysocki
2008-03-09 19:56 ` Alan Stern
2008-03-09 20:50 ` Rafael J. Wysocki
2008-03-10 2:52 ` Alan Stern
2008-03-10 16:58 ` Rafael J. Wysocki
2008-03-10 18:54 ` Alan Stern
2008-03-12 9:37 ` David Brownell [this message]
2008-03-12 21:22 ` 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=200803120237.24857.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=astarikovskiy@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--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