From: Adam Belay <abelay@novell.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
Karsten Keil <kkeil@suse.de>
Subject: Re: [PATCH] fix tulip suspend/resume
Date: Mon, 06 Jun 2005 23:42:31 -0400 [thread overview]
Message-ID: <1118115751.3245.31.camel@localhost.localdomain> (raw)
In-Reply-To: <1118115123.6850.43.camel@gaston>
On Tue, 2005-06-07 at 13:32 +1000, Benjamin Herrenschmidt wrote:
> > > It should probably test for message state, it's not worth doing
> > > pci_set_power_state(D3) if PMSG_FREEZE is passed... (just slows down
> > > suspend to disk)
> >
> > Yeah, I added pci_choose_state in my last email. This will at least help
> > avoid powering off. Still, I agree this needs to be handled specifically.
> > Currently, I don't think many drivers support PMSG_FREEZE.
>
> Nope, but I've been improving swsusp support on macs lately and have
> already a bunch of driver fixes waiting.
>
> Now I need to get Pavel, Patrick and I to agree about the PM toplevel
> core changes before I can send all that stuff to Andrew :)
>
> Ben.
What PM toplevel core changes are you referring to? I've look over the
changes to pm_ops and they seem to make sense. Still I almost wonder if
we should make the entire thing arch specific code, and then have this
code call things like device_suspend(). If mac hardware required that
many new hooks, then other platforms might require even more.
Thanks,
Adam
next prev parent reply other threads:[~2005-06-07 3:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 22:46 [PATCH] fix tulip suspend/resume Karsten Keil
2005-06-07 0:04 ` Linus Torvalds
2005-06-07 2:50 ` Adam Belay
2005-06-07 3:34 ` Benjamin Herrenschmidt
2005-06-07 3:58 ` Adam Belay
2005-06-07 4:26 ` Benjamin Herrenschmidt
2005-06-07 5:34 ` Adam Belay
2005-06-07 5:50 ` Benjamin Herrenschmidt
2005-06-07 10:55 ` Karsten Keil
2005-06-07 20:58 ` Adam Belay
2005-06-08 0:26 ` Benjamin Herrenschmidt
2005-06-08 2:16 ` Adam Belay
2005-06-08 12:23 ` Pavel Machek
2005-06-08 23:00 ` Benjamin Herrenschmidt
2005-06-09 0:04 ` Pavel Machek
2005-06-09 0:38 ` Adam Belay
2005-06-09 10:51 ` Pavel Machek
2005-06-09 2:49 ` Nigel Cunningham
2005-06-09 8:27 ` Karsten Keil
2005-06-08 12:19 ` Pavel Machek
2005-06-08 6:39 ` Karsten Keil
2005-06-08 18:11 ` Davide Rossetti
2005-06-09 1:48 ` Adam Belay
2005-06-07 11:52 ` Stefan Seyfried
2005-06-07 2:15 ` Benjamin Herrenschmidt
2005-06-07 2:57 ` Adam Belay
2005-06-07 3:32 ` Benjamin Herrenschmidt
2005-06-07 3:42 ` Adam Belay [this message]
2005-06-07 4:29 ` Benjamin Herrenschmidt
2005-06-07 5:03 ` Adam Belay
2005-06-07 5:51 ` Nigel Cunningham
2005-06-07 5:55 ` Benjamin Herrenschmidt
2005-06-07 15:10 ` Pavel Machek
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=1118115751.3245.31.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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.