public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@suse.cz>,
	pm list <linux-pm@lists.linux-foundation.org>,
	Thomas Renninger <trenn@suse.de>,
	Romano Giannetti <romano.giannetti@gmail.com>
Subject: Re: [PATCH] ACPI Suspend: Enable ACPI during resume if SCI_EN is not set
Date: Mon, 6 Oct 2008 14:45:32 +0200	[thread overview]
Message-ID: <200810061445.33151.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.1.10.0810060034050.2973@localhost.localdomain>

On Monday, 6 of October 2008, Len Brown wrote:
> applied to acpi-test.

Thanks!

Actually, it appears to fix a recent regression for Romano
(http://bugzilla.kernel.org/show_bug.cgi?id=11634).  If that's verified, it
would be -stable material.

[I guess the regression was caused by the Linus' patch we were discussing on
IRC.]

It also evidently fixes my resume problem on the MSI Wind.  Both machines
(the Wind and the Romano's box) have the problem with ACPI not being enabled
by the BIOS on resume from S3.

Thanks,
Rafael


> On Sat, 4 Oct 2008, Rafael J. Wysocki wrote:
> 
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> > 
> > ACPI Suspend: Enable ACPI during resume if SCI_EN is not set
> > 
> > On some machines, like for example MSI Wind U100, the BIOS doesn't
> > enable ACPI before returning control to the OS, which sometimes
> > causes resume to fail.  This is against the ACPI specification,
> > which clearly states that "When the platform is waking from an S1, S2
> > or S3 state, OSPM assumes the hardware is already in the ACPI mode
> > and will not issue an ACPI_ENABLE", but it won't hurt to check the
> > SCI_EN bit and enable ACPI during resume from S3 if this bit is not
> > set.
> > 
> > Fortunately, we already have acpi_enable() for that, so use it in the
> > resume code path, before executing _BFS, in analogy with the
> > resume-from-hibernation code path.
> > 
> > NOTE: We aren't supposed to set SCI_EN directly, because it's owned
> > by the hardware.
> > 
> > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> > ---
> >  drivers/acpi/sleep/main.c |    2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > Index: linux-2.6/drivers/acpi/sleep/main.c
> > ===================================================================
> > --- linux-2.6.orig/drivers/acpi/sleep/main.c
> > +++ linux-2.6/drivers/acpi/sleep/main.c
> > @@ -200,6 +200,8 @@ static int acpi_suspend_enter(suspend_st
> >  		break;
> >  	}
> >  
> > +	/* If ACPI is not enabled by the BIOS, we need to enable it here. */
> > +	acpi_enable();
> >  	/* Reprogram control registers and execute _BFS */
> >  	acpi_leave_sleep_state_prep(acpi_state);
> >  
> > 
> 
> 

  reply	other threads:[~2008-10-06 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 22:05 [PATCH] ACPI Suspend: Enable ACPI during resume if SCI_EN is not set Rafael J. Wysocki
2008-10-06  4:34 ` Len Brown
2008-10-06 12:45   ` Rafael J. Wysocki [this message]
2008-10-08 11:39 ` 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=200810061445.33151.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@suse.cz \
    --cc=romano.giannetti@gmail.com \
    --cc=trenn@suse.de \
    /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