Re: [ibm-acpi-devel] Lid sensor on Yoga 11e

[Steven P. <st...@pr...>]

WMI is Windows Management Instrumentation, right?  What does it mean for 
my attempts to get this working that the device to be behind that?

I was able to do a bit more digging on the Windows side.  I found a 
device driver named "GPIO Laptop or Slate Indicator Driver". This has a 
location path of "ACPI(_SB_)#ACPI(LSID)".  In the decompiled DSDT, there 
IS a LSID device, with the text reproduced below.  I've been poking at 
it most of the day and haven't managed to get _STA to change.  I suspect 
I'm going down the wrong path here, given that nothing Notify()s this 
device.

As before, any advice on where to look is deeply appreciated.

Steve


Device (LSID)
                     {
                         Method (_HID, 0, NotSerialized)  // _HID: 
Hardware ID
                         {
                             Return ("MSFT9001")
                         }

                         Name (_CID, "PNP0C60" /* Display Sensor Device 
*/)  // _CID: Compatible ID
                         Name (_CRS, ResourceTemplate ()  // _CRS: 
Current Resource Settings
                         {
                         })
                         Method (_STA, 0, NotSerialized)  // _STA: Status
                         {
                             If ((OSYS <= 0x07D9) || (TSMT == Zero))
                             {
                                 Return (Zero)
                             }

                             Return (0x0F)
                         }


On 09/29/2017 09:53 PM, Henrique de Moraes Holschuh wrote:
> On Wed, 27 Sep 2017, Steven Presser wrote:
>> I have some new elements to this puzzle that may be useful:
>>
>> - I've extracted the ACPI DST table.  This device, like the X1 Yoga
>> (https://patchwork.kernel.org/patch/9395641/) has the MHKG method.  But on
>> this device it's a no-op!  (just returns zero)
>>
>> - I've extracted the same table under Windows, just to make sure this wasn't
>> an OS difference.  It's a no-op there too, but the sensor works.
>>
>>
>> I'm trying to figure out how to watch ACPI events under Windows to see if
>> that gives any clues.  However, is this new info helpful to anyone's
>> understanding?  Is anyone able to help me with where to investigate next?
> It is likely behind WMI, then...
>