From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-acpi@vger.kernel.org
Cc: rjw@sisk.pl
Subject: [Regression] GPEs being enabled inappropriately
Date: Fri, 10 Dec 2010 17:55:05 +0000 [thread overview]
Message-ID: <20101210175505.GA12319@srcf.ucam.org> (raw)
I've just had a bug report from someone who's seeing high GPE-triggered
load in .37. It turns out that GPEs 1B and 1E are constantly firing.
Both have associated _L1B and _L1E methods, but they're also present in
_PRW methods s should be disabled by default. However, part of the GPE
rework means that we're now ignoring _PRW methods if the device they're
associated with reports itself missing in _STA. I think we need to pay
attention to _PRW regardless of whether or not the device is present, as
otherwise we may be enabling GPEs that are tied to GPIOs that aren't
connected to anything at the other end.
--
Matthew Garrett | mjg59@srcf.ucam.org
next reply other threads:[~2010-12-10 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 17:55 Matthew Garrett [this message]
2010-12-10 23:44 ` [Regression] GPEs being enabled inappropriately 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=20101210175505.GA12319@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
/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