From: Adam Belay <abelay@novell.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: Suspend "core": what to do now ?
Date: Mon, 27 Jun 2005 18:55:18 -0400 [thread overview]
Message-ID: <1119912918.30369.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1119851395.5133.112.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Mon, 2005-06-27 at 15:49 +1000, Benjamin Herrenschmidt wrote:
> Hi !
>
> So I'm still sitting on that rewrite of the pmac suspend code including
> suspend to disk consolidation etc... that I would really like to get
> upstream. However, I'm still having a problem:
>
> - I'm still adding all those callbacks to pm_ops, Patrick wants to get
> the stuff out of the core, which I agree, but I don't feel like "fixing"
> x86 neither :) Pavel wants to keep the existing stuff.
I'd like to move it out of the core and use the pm functions as a
library.
>
> - If I keep my callbacks addition, we need to consolidate
> kernel/power/disk.c with kernel/power/main.c. I need all callbacks in
> both cases. The current inconsistency makes little sense.
>
> - I want that in 2.6.13 final, so please, let's decide something :)
>
> Ben.
I'm familiar with the ACPI code. If you'd like, I could work on the x86
pm_ops.
Let's discuss how we would change the existing PM code...
I was thinking each arch could provide a table of system power states
with an ->enter() function for each. We would then show the names of
these states in "/sys/power/state", and the user could select one. Did
you have something else in mind?
Thanks,
Adam
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-06-27 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 5:49 Suspend "core": what to do now ? Benjamin Herrenschmidt
2005-06-27 21:23 ` Pavel Machek
2005-06-27 22:39 ` Rafael J. Wysocki
2005-06-27 22:55 ` Adam Belay [this message]
2005-06-27 23:49 ` Benjamin Herrenschmidt
2005-06-28 4:06 ` Benjamin Herrenschmidt
2005-06-28 4:58 ` Pavel Machek
2005-06-28 5:02 ` Benjamin Herrenschmidt
2005-06-28 12:44 ` Pavel Machek
2005-06-28 6:37 ` Nigel Cunningham
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=1119912918.30369.7.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=benh@kernel.crashing.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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.