From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alex Hung <alex.hung@canonical.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Linux ACPI Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI / blacklist: blacklist Win8 OSI for Dell Inspiron 7437
Date: Tue, 28 Apr 2015 18:11:00 +0100 [thread overview]
Message-ID: <20150428171100.GA24599@srcf.ucam.org> (raw)
In-Reply-To: <CAJ=jquYYDixG7-XtVJRvuHDWHgF3Ww3fiafDbmgD5KY8QJjeQQ@mail.gmail.com>
With Windows 8 enabled you're going down this path:
If (_OSI (WIN8))
{
Local0 = 0x81
}
With it blacklisted, you're going down this path:
If (_OSI (WIN7))
{
Local0 = 0x80
Local1 = _REV /* \_REV */
If ((Local1 == 0x05))
{
Local0 = 0x40
}
}
So your guess about _REV was actually correct - if the OS claims to be
Windows 7 and returns 5 to _REV, it'll let Local0 to 0x40. This results
in:
If ((Local0 == 0x40))
{
MIS0 = SMI (0x98, Zero)
MIS0 &= 0x13
}
MIS0 appears to be involved in various event delivery paths, so my
suspicion is that the firmware is deliberately working around a quirk of
Linux behaviour in order to deliver events appropriately. If so, your
patch won't help in 4.1 because _REV now returns 2, and so we need to
root cause the actual problem and fix that instead.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2015-04-28 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 3:24 [PATCH] ACPI / blacklist: blacklist Win8 OSI for Dell Inspiron 7437 Alex Hung
2015-04-24 8:21 ` Matthew Garrett
2015-04-27 8:30 ` Alex Hung
2015-04-27 17:46 ` Matthew Garrett
2015-04-28 4:53 ` Alex Hung
2015-04-28 5:24 ` Matthew Garrett
2015-04-28 9:51 ` Alex Hung
2015-04-28 17:11 ` Matthew Garrett [this message]
2015-04-29 10:09 ` Alex Hung
2015-05-14 19:02 ` Mario Limonciello
2015-05-14 19:13 ` Matthew Garrett
2015-05-14 19:17 ` Mario Limonciello
2015-05-20 17:42 ` Mario Limonciello
2015-05-20 18:42 ` Matthew Garrett
2015-05-20 20:16 ` Mario Limonciello
2015-06-02 3:20 ` Alex Hung
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=20150428171100.GA24599@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alex.hung@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).