public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham-lkml@crca.org.au>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	Len Brown <lenb@kernel.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] PM/Suspend: Introduce two new platform callbacks to avoid breakage (Re: 900af0d breaks some embedded suspend/resume)
Date: Mon, 20 Apr 2009 09:31:47 +1000	[thread overview]
Message-ID: <1240183907.8867.22.camel@nigel-laptop> (raw)
In-Reply-To: <200904182047.48009.rjw@sisk.pl>

Hi.

On Sat, 2009-04-18 at 20:47 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
> Subject: PM/Suspend: Introduce two new platform callbacks to avoid breakage
> 
> Commit 900af0d973856d6feb6fc088c2d0d3fde57707d3 (PM: Change suspend
> code ordering) changed the ordering of suspend code in such a way
> that the platform .prepare() callback is now executed after the
> device drivers' late suspend callbacks have run.  Unfortunately, this
> turns out to break ARM platforms that need to talk via I2C to power
> control devices during the .prepare() callback.
> 
> For this reason introduce two new platform suspend callbacks,
> .prepare_late() and .wake(), that will be called just prior to
> disabling non-boot CPUs and right after bringing them back on line,
> respectively, and use them instead of .prepare() and .finish() for
> ACPI suspend.  Make the PM core execute the .prepare() and .finish()
> platform suspend callbacks where they were executed previously (that
> is, right after calling the regular suspend methods provided by
> device drivers and right before executing their regular resume
> methods, respectively).
> 
> It is not necessary to make analogous changes to the hibernation
> code and data structures at the moment, because they are only used
> by ACPI platforms.
> 
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
>  drivers/acpi/sleep.c    |    8 ++++----
>  include/linux/suspend.h |   36 ++++++++++++++++++++++++++----------
>  kernel/power/main.c     |   24 +++++++++++++++++-------
>  3 files changed, 47 insertions(+), 21 deletions(-)
> 
> Index: linux-2.6/kernel/power/main.c
> ===================================================================
> --- linux-2.6.orig/kernel/power/main.c
> +++ linux-2.6/kernel/power/main.c
> @@ -291,20 +291,26 @@ static int suspend_enter(suspend_state_t
>  
>  	device_pm_lock();
>  
> +	if (suspend_ops->prepare) {
> +		error = suspend_ops->prepare();
> +		if (error)
> +			goto Done;
> +	}
> +
>  	error = device_power_down(PMSG_SUSPEND);
>  	if (error) {
>  		printk(KERN_ERR "PM: Some devices failed to power down\n");
> -		goto Done;
> +		goto Platfrom_finish;

s/Platfrom/Platform

Why retain the typo in multiple places?

>  	}
>  
> -	if (suspend_ops->prepare) {
> -		error = suspend_ops->prepare();
> +	if (suspend_ops->prepare_late) {
> +		error = suspend_ops->prepare_late();
>  		if (error)
>  			goto Power_up_devices;
>  	}

Doesn't this invalidate testing that's already been done? Drivers
implementing prepare() (arm omap1, pxa, omap2, s3c and powerpc mpc52xx
and lite5200) are now going to have it called pre device_power_down. Why
not call the new prepare() "prepare_early" and leave the current prepare
as it is in the place where it's already called?

The name is also very confusing. Prepare matches with Finish and
Prepare_late with wake. How about prepare and unprepare?

Reviewed-by: Nigel Cunningham <nigel@tuxonice.net>

Regards,

Nigel

  parent reply	other threads:[~2009-04-19 23:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090417231009.GB6900@flint.arm.linux.org.uk>
2009-04-18 13:23 ` 900af0d breaks some embedded suspend/resume Rafael J. Wysocki
2009-04-18 13:53   ` Russell King
2009-04-18 14:26     ` Rafael J. Wysocki
2009-04-18 14:41       ` Russell King
2009-04-18 15:09         ` Rafael J. Wysocki
2009-04-18 18:09           ` Russell King
2009-04-18 18:47         ` [PATCH] PM/Suspend: Introduce two new platform callbacks to avoid breakage (Re: 900af0d breaks some embedded suspend/resume) Rafael J. Wysocki
2009-04-19 17:57           ` Len Brown
2009-04-19 20:03             ` Russell King
2009-04-20  0:50               ` Rafael J. Wysocki
2009-04-20  0:56               ` [GIT PULL] PM update for 2.6.30 Rafael J. Wysocki
2009-04-19 23:31           ` Nigel Cunningham [this message]
2009-04-20  0:50             ` [PATCH] PM/Suspend: Introduce two new platform callbacks to avoid breakage (Re: 900af0d breaks some embedded suspend/resume) Rafael J. Wysocki
2009-04-20  8:35             ` Russell King
2009-04-20  8:48               ` Nigel Cunningham
2009-04-18 14:42       ` 900af0d breaks some embedded suspend/resume Rafael J. Wysocki
2009-04-18 19:06     ` Linus Torvalds
2009-04-18 22:44       ` Rafael J. Wysocki
2009-04-26  9:25         ` Pavel Machek
2009-04-18 13:59   ` Rafael J. Wysocki
2009-04-18 14:28     ` Russell King

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=1240183907.8867.22.camel@nigel-laptop \
    --to=ncunningham-lkml@crca.org.au \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox