public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S5 Powerdown problem on TX150 servers
Date: Tue, 16 Sep 2003 16:15:03 +0200	[thread overview]
Message-ID: <20030916141503.GU11391@poupinou.org> (raw)
In-Reply-To: <200309161450.19600.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>

On Tue, Sep 16, 2003 at 02:50:19PM +0100, Andrew de Quincey wrote:
> 
> > Ok.  But trouble: you have at first write the desired sleep type,
> > then set SLP_EN.  Not the two at the same time.
> 
> Yup, its doing that as well. Heres a quick summary of what it does:
> 
> Clears any wake status
> Disable BM arbitration
> 
> Get current value of PM1A control (and store two copies in variables 
> PM1AControl, PM1BControl)
> 
> Clear SLP_EN and SLP_TYP fields in the above variables
> Insert the SLP_TYP bits in each variable.
> 
> Store PM1AControl into ACPI PM1A
> Store PM1BControl into ACPI PM1B
> 
> Insert the SLP_ENABLE bit in PM1AControl, PM1BControl
> Flush the CPU cache
> Store PM1AControl into ACPI PM1A
> Store PM1BControl into ACPI PM1B
> 
> At this point the machine should be in S5, but appears to be in S1.
> 
> Prior to all this, it has called the _PTS and _GTS (if present) methods as it 
> should.
> 
> 
> Should I try masking off the SLP_TYP bits when the second write to PM1A/PM1B 
> occurs?

No.  But, what contain the _S5 in the asl?  What kind of southbridge
you have?

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2003-09-16 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16  8:12 S5 Powerdown problem on TX150 servers Andrew de Quincey
     [not found] ` <200309160912.15060.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-16  8:16   ` Andrew de Quincey
2003-09-16  9:30   ` Ducrot Bruno
     [not found]     ` <20030916093032.GP11391-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-09-16 11:09       ` Andrew de Quincey
     [not found]         ` <200309161209.35760.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-16 13:19           ` Ducrot Bruno
     [not found]             ` <20030916131922.GT11391-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-09-16 13:50               ` Andrew de Quincey
     [not found]                 ` <200309161450.19600.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-16 14:15                   ` Ducrot Bruno [this message]
     [not found]                     ` <20030916141503.GU11391-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-09-16 15:50                       ` Andrew de Quincey
  -- strict thread matches above, loose matches on Subject: below --
2003-09-24  3:14 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720B38-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-09-27 11:59   ` Andrew de Quincey

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=20030916141503.GU11391@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.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