public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
To: "Moore, Robert" <robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	"Grover,
	Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Fix wake GPE enabling
Date: Thu, 8 Apr 2004 08:45:21 +0200	[thread overview]
Message-ID: <20040408064521.GA7674@dominikbrodowski.de> (raw)
In-Reply-To: <37F890616C995246BE76B3E6B2DBE055442912-sBd4vmA9Se7vCEQmvpVV9VDQ4js95KgL@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]

On Wed, Apr 07, 2004 at 02:34:43PM -0700, Moore, Robert wrote:
> 
> No, this does not fit the model correctly.
> 
> It is the responsibility of the upper software to selectively enable the
> devices which are to be used for wakeup.  This is one of the functions
> of the AcpiGpeEnable interface.  The ACPI CA core cannot just blindly
> enable all "wake" GPEs.

However, the ACPI subsystem, and I do not care whether it is the CA core or
any other part, currently does not enable any(!) wake GPEs.

-> wake_enable is not touched directly,
-> events/evgpeblk.c does not care, and according to your opinion, should
   not care.
-> acpi_enable_gpe is _only_ called by drivers/acpi/ec.c, which means it is
   _not_ called for buttons, which are very clearly needed in most cases to
   wake up a system.

At least for buttons, the ACPI subsystem should enable their wake
functionality, e.g. the wake GPEs, unconditionally. Having to manually enter
"echo powerbutton > /proc/acpi/wakeup_devices", as the patch in bug #1415
suggests, seems to be overly complicated. However, having this file as
override might be a valid option, I agree.

> The ACPI CA core simply identifies the "wake" GPEs in order to leave
> them disabled during runtime.
> 
> Therefore, in (1) and (2) below, this is the correct behavior.  No
> "wake" GPEs are enabled.

IMHO, (2) is not correct behavior. It is a different thing to
- disable wake GPEs during runtime,
and
- mark wake GPEs as runtime GPEs, which is what the current code does.

Also, as it has been experienced by Linus, for example[*], some "wake" GPEs are also useful to
have during runtime, so the code in acpi_enable_gpe() which disables a GPE
marked as "wake" is flawed. IMO it should be able to set it to both RUNTIME and
WAKE, if it's runtime, enable it during runtime, if it's wake, enable it for
wakeup.

[*] And that's the reason the acpi_disable_wake_gpes_during_runtime flag is
_not_ set to true in Linux 2.6.5, in contrast to the original ACPI patch
sent out. And I'm glad it is this way: with this flag set, my notebook's
keyboard stops functioning...

	Dominik

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-04-08  6:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 21:34 Fix wake GPE enabling Moore, Robert
     [not found] ` <37F890616C995246BE76B3E6B2DBE055442912-sBd4vmA9Se7vCEQmvpVV9VDQ4js95KgL@public.gmane.org>
2004-04-08  6:45   ` Dominik Brodowski [this message]
2004-04-08 13:50   ` Takayoshi Kochi
  -- strict thread matches above, loose matches on Subject: below --
2004-04-09 22:12 Moore, Robert
2004-04-09 16:57 Moore, Robert
     [not found] ` <37F890616C995246BE76B3E6B2DBE0554F207E-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-04-09 23:27   ` Masanori Kanaoka
2004-04-08 20:38 Moore, Robert
     [not found] ` <37F890616C995246BE76B3E6B2DBE0554F1C5F-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-04-08 22:20   ` Nate Lawson
2004-04-08 16:43 Moore, Robert
     [not found] ` <37F890616C995246BE76B3E6B2DBE0554F1A53-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-04-08 17:47   ` Nate Lawson
     [not found]     ` <20040408104615.K42238-Y6VGUYTwhu0@public.gmane.org>
2004-04-08 21:05       ` Dominik Brodowski
2004-04-08 21:13   ` Dominik Brodowski
     [not found]     ` <20040408211323.GB7340-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-04-21 21:57       ` Pavel Machek
2004-04-08 16:32 Moore, Robert
     [not found] ` <37F890616C995246BE76B3E6B2DBE0554F1A3B-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-04-09 10:10   ` Masanori Kanaoka
2004-04-08 16:00 Moore, Robert
2004-04-07 22:20 Manpreet Singh
2004-04-07 20:53 Dominik Brodowski

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=20040408064521.GA7674@dominikbrodowski.de \
    --to=linux-x3ehhduj6siigcdfoqap7bvvk+yq3zxh@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@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