Maximilian Luz

Should be fixed by #540 (8e6c7b8).

@xeiraex Thanks for reporting this! Unfortunately this means that the GPE numbers can not be determined by MSHW0081, so I'll have to look for another solution. This might take me...

@tmarkov That's interesting. According to the DSDT of the SB1, `_L17` should be the GPE interrupt for the lid. There are some changes compared to the DSDT of the SB2,...

@kitakar5525 > This commit was made to fix wakeup from LID or Keyboard on 5.2, but it seems that it didn't work for us. > > * [ACPI: PM: Set...

You could try and set-up/enable other GPEs for wake (I think that should be possible from the command line if I'm not mistaken), maybe it needs a different one or...

I think if you enable ACPI/AML debug messages you should also see `_L17` in the output. From the SB1 DSDT that I have: ``` Method (_L17, 0, NotSerialized) // _Lxx:...

@kitakar5525 > > _PRW is not there > > Yeah, it may be the reason why we cannot see LID device on `/proc/acpi/wakeup` (I was wondering why.) Yes, that is...

@kitakar5525 > Any `surface_acpi` output should be appeared on dmesg if `surface_acpi` is working? I see no output from `dmesg -x | grep -i surface_acpi` You'd have to enable debug...

There seems to be something we're missing here, as it's working with 4.14. Either that was not the only change inbetween, or I've set-up the GPE wrong, or we need...

@kitakar5525 Thanks for figuring that out! I messed that up, sorry. On the SB1 `has_perf_mode` should also be false (at least until we've figured SAM-over-I2C out), since it doesn't use...