mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Mario 'BitKoenig' Holbe'" <Mario.Holbe@RZ.TU-Ilmenau.DE>,
	Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: RE: [patch] ACPI: kbd-pw-on/WOL don't work anymore since 2.4.14
Date: Tue, 12 Mar 2002 11:57:48 -0800	[thread overview]
Message-ID: <59885C5E3098D511AD690002A5072D3C02AB7CDB@orsmsx111.jf.intel.com> (raw)

> From: Mario 'BitKoenig' Holbe [mailto:Mario.Holbe@RZ.TU-Ilmenau.DE]
> However, if someone of the ACPI developers or someone of the
> patch-acceptors (:)) tells me 'do it, we'll patch it in', I'll do
> it.
> If it has no chance to get in, I wont do it - for me myself, my
> patch is quite enough :)

Basically we have to disable non-wake GPEs prior to sleeping - I agree with
Pavel that this should not be a config option. The real problem is that the
keyboard GPE should be flagged as a wake GPE, but it isn't yet.

What needs to happen is, when we are entering a sleep state, we need to
evaluate _PRW and _PSW objects for devices, and take the appropriate action
- I would bet that a result of doing this would be that keyboard (WOL too?
maybe) would be properly flagged as a wake device, so the call to that
function would but turn off its GPE bit.

Regards -- Andy

             reply	other threads:[~2002-03-12 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12 19:57 Grover, Andrew [this message]
2002-03-12 20:40 ` Patrick Mochel
2002-03-12 22:38 ` Mario 'BitKoenig' Holbe
  -- strict thread matches above, loose matches on Subject: below --
2002-03-12 23:05 Grover, Andrew
2002-03-12 23:13 ` Mario 'BitKoenig' Holbe
2002-03-12 21:51 Grover, Andrew
2002-03-10 18:05 Mario 'BitKoenig' Holbe
2002-03-11 20:34 ` Pavel Machek
2002-03-12 15:08   ` Mario 'BitKoenig' Holbe

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=59885C5E3098D511AD690002A5072D3C02AB7CDB@orsmsx111.jf.intel.com \
    --to=andrew.grover@intel.com \
    --cc=Mario.Holbe@RZ.TU-Ilmenau.DE \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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®