All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: Alex Hung <alex.hung@canonical.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Linux ACPI Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: Re: [PATCH] ACPI / blacklist: blacklist Win8 OSI for Dell Inspiron 7437
Date: Thu, 14 May 2015 14:02:02 -0500	[thread overview]
Message-ID: <5554F12A.3010003@dell.com> (raw)
In-Reply-To: <CAJ=jquZMMBNsKO2CZe649OcXTBxfzO43gkxwkJn2mvHhnp+zSQ@mail.gmail.com>



On 04/29/2015 05:09 AM, Alex Hung wrote:
> Matthew,
>
> Your conclusion is correct. Disabling OSI(Windows 2012/2013) in kernel
> 4.1rc will not work. I will take a closer look into this machine.
>
> Thanks.
>
> On Wed, Apr 29, 2015 at 1:11 AM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>> 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
Matthew,

Thank you for bringing this to my attention on that other thread. I've 
checked with the team more on this.  I'm also looking into any other 
platforms that are quirking behavior on _REV.  If you are aware of any 
other specifics I can inquire on those too.
The 7437 platform (and it's two sister platforms 7537 and 7737) include 
the following differences when acpi_osi=Windows 2009 and _REV is 5.  
These platforms were enabled in the era before Windows 2013 was default 
_OSI in the Linux kernel.
* Backlight control is set to 16 levels in Win7 and Linux.  It's set to 
10 levels in Win 8/Win8.1.
* Battery information was not displayed in the OS.  The BIOS team found 
that the Linux wasn't asking for battery information in the OS in the 
same way that Windows does.  The delta path creates a SMI event to get 
battery information.

Alex,

Does dell-rbtn/dell-airplane work properly with this platform when set 
to Windows 2013?  I'd expect that should fix the wireless hotkey issue.  
As you know airplane mode is only effective on systems with _OSI of 
Windows 2013.



  reply	other threads:[~2015-05-14 19:02 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
2015-04-29 10:09               ` Alex Hung
2015-05-14 19:02                 ` Mario Limonciello [this message]
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=5554F12A.3010003@dell.com \
    --to=mario_limonciello@dell.com \
    --cc=alex.hung@canonical.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.