All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Adam Belay <abelay@novell.com>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: Suspend "core": what to do now ?
Date: Tue, 28 Jun 2005 15:02:35 +1000	[thread overview]
Message-ID: <1119934956.5133.192.camel@gaston> (raw)
In-Reply-To: <20050628045846.GA10735@atrey.karlin.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

On Tue, 2005-06-28 at 06:58 +0200, Pavel Machek wrote:
> Hi!
> 
> > However, PM_DISK_PLATFORM and PM_DISK_FIRMWARE sort-of abuse the pm_ops
> > that I have killed to call into arch code... it's all crap as it exposes
> > to all archs some behaviours that may not be supported by those archs.
> 
> Feel free to kill PM_DISK_FIRMWARE. PM_DISK_PLATFORM looks like the
> "right way" to do swsusp on acpi-enabled systems, so it should stay...

No, not in this form. It will be under arch control too. Makes no sense
to aim to remove the pm_ops callbacks and just add new ones for
PM_DISK_FIRMWARE :) Instead, ACPI systems will expose an S4 state that
does the right thing and calls swsusp_* library routines to do the job.

What I'll do is that I'll keep the "shutdown" case and will rename the
file generic_disk.c. It will be a "drop in" implementation that
architectures can use if they have no callbacks need at all. PPC won't
use it though. And I suspect x86 neither.

Ben.



[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2005-06-28  5:02 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
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 [this message]
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=1119934956.5133.192.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=abelay@novell.com \
    --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.