mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Willy Tarreau <willy@w.ods.org>
Cc: Len Brown <len.brown@intel.com>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>,
	ACPI Developers <acpi-devel@lists.sourceforge.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BKPATCH] ACPI for 2.4
Date: Sun, 8 Feb 2004 10:08:54 +0100	[thread overview]
Message-ID: <20040208090854.GE29363@alpha.home.local> (raw)
In-Reply-To: <20040208082059.GD29363@alpha.home.local>

Replying to myself...

On Sun, Feb 08, 2004 at 09:20:59AM +0100, Willy Tarreau wrote:
> 
> So I've added printk's into acpi_power_off(), and I see that the system
> doesn't return from acpi_enter_sleep_state_prep(S5), which itself hangs
> on the call to acpi_evaluate_object(NULL, "\\_PTS",...). If I comment
> out this line, it now goes on through the next calls, then normally leaves
> acpi_enter_sleep_state_prep(), then powers off correctly.

Searching for _PTS on google directed me to the ACPI spec. I found in
section 9 that _PTS (prepare to sleep) is only used for S1-S4, but 9.1.7
says that it should be called for S5 too. I suspect that depending on the
paragraph they read, hardware makers do or don't implement _PTS(S5) correctly
:-/ BTW, 9.1.5 says that "S5 is not a sleeping state, but a G2 state". So it
might seem logical not to call something named "prepare to sleep" in this
case.

I checked the last working version. It was acpi-030424 + the two little
patches I sent to you at this time and which were merged. This version
called _PTS and _GTS in acpi_enter_sleep_state_prep(), while now we call
_PTS, _GTS, and _SI._SST. So I'm amazed that in previous version, _PTS
worked and that it does not anymore !

Regards,
Willy


  reply	other threads:[~2004-02-08  9:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07  9:10 Len Brown
2004-02-08  8:20 ` Willy Tarreau
2004-02-08  9:08   ` Willy Tarreau [this message]
     [not found]     ` <20040214081726.GH29363@alpha.home.local>
     [not found]       ` <1076824106.25344.78.camel@dhcppc4>
2004-02-25  7:00         ` [RFC] ACPI power-off on P4 HT Willy Tarreau
2004-02-25  7:55           ` Len Brown
2004-02-25 16:13             ` Zwane Mwaikambo
2004-02-26  7:56             ` Gregory Finch
2004-02-26 10:57               ` Willy Tarreau
2004-02-26 12:28                 ` Stian Jordet
2004-02-26 13:07                   ` Willy Tarreau
2004-02-26 13:29                     ` Stian Jordet
2004-02-26 13:16           ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2005-01-31  8:32 [BKPATCH] ACPI for 2.4 Len Brown
2004-11-23  6:34 Len Brown
2004-11-16 19:26 Len Brown
2004-11-09  8:17 Len Brown
2004-10-28  9:33 Len Brown
2004-06-18  7:32 Len Brown
2004-05-20  6:14 Len Brown
2004-05-06 22:28 Len Brown
2004-04-01 12:24 O.Sezer
2004-04-01 12:57 ` O.Sezer
2004-04-01 10:40 Len Brown
2004-03-27  0:53 Len Brown
2004-03-23 10:43 Len Brown
2004-03-14  6:01 Len Brown
2004-03-06  6:32 Len Brown
2004-02-25 10:01 Len Brown
2003-11-18 20:58 Len Brown
2003-11-20 11:16 ` Len Brown
2003-11-21 17:49   ` Willy Tarreau
2003-11-21 18:46     ` Willy Tarreau

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=20040208090854.GE29363@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com.br \
    /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

all inboxes | Powered by JetHome®