public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: Why don't we use _TTS method?
Date: Fri, 4 May 2007 01:22:56 +0200	[thread overview]
Message-ID: <200705040122.56563.rjw@sisk.pl> (raw)
In-Reply-To: <B28E9812BAF6E2498B7EC5C427F293A40267F659@orsmsx415.amr.corp.intel.com>

On Friday, 4 May 2007 00:57, Moore, Robert wrote:
> 
> > -----Original Message-----
> > From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-
> > owner@vger.kernel.org] On Behalf Of Rafael J. Wysocki
> > Sent: Thursday, May 03, 2007 1:02 PM
> > To: ACPI Devel Maling List
> > Cc: pm list; Pavel Machek
> > Subject: Why don't we use _TTS method?
> > 
> > Hi,
> > 
> > I've got two questions regarding the implementation of the ACPI
> > poweroff/sleep
> > code in drivers/acpi/sleep and drivers/acpi/hardware .
> > 
> > 1) We don't seem to use the _TTS system-control method, although the
> ACPI
> > specification (ACPI 3.0b) says that this method should be used for
> > intiating
> > and finishing power transitions.  Could you please tell me why we
> don't
> > use it?
> > 
> [Moore, Robert] 
> 
> Probably because it's fairly new and it takes a long time for these
> things to appear in real machines. Also, needs to be supported in
> Windows before we ever see it in real machines.

Hmm, it already was in the 3.0 spec from 2004, so it doesn't seem to be
that new.  Still, I'm not an expert ...

> > 2) In the functions acpi_enter_sleep_state_prep(),
> > acpi_enter_sleep_state(),
> > acpi_leave_sleep_state() we manipulate GPEs quite extensively (we
> disable
> > and enable them for a couple of times during a transition), although
> the
> > specification doesn't tell anything about that explicitly.  Could you
> > please
> > explain to me what the purpose of that is?
> > 
> [Moore, Robert] 
> 
> There a wake GPEs and runtime GPEs that need to be managed separately.
> We want to make sure that only the "Wake" GPEs are enabled as we goto
> sleep.

I understand that, but the runtime GPEs seem to be disabled before we call
device drivers' .suspend() routines (ie. before the devices are placed in the
appropriate Dx states) and that's the point I don't quite get.  Is there a
technical reason for doing it in this particular place?

Thanks a lot for your reply.

Greetings,
Rafael

  reply	other threads:[~2007-05-03 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 20:01 Why don't we use _TTS method? Rafael J. Wysocki
2007-05-03 22:27 ` Pavel Machek
2007-05-03 22:55   ` Rafael J. Wysocki
2007-05-03 22:57 ` Moore, Robert
2007-05-03 23:22   ` Rafael J. Wysocki [this message]
2007-05-04  4:34     ` Alexey Starikovskiy
2007-05-04  8:50       ` Rafael J. Wysocki
2007-05-04 18:10         ` Moore, Robert
2007-05-04 20:09           ` Rafael J. Wysocki

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=200705040122.56563.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=robert.moore@intel.com \
    /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