https://bugzilla.kernel.org/show_bug.cgi?id=213579 Hans de Goede (jwrdegoede@xxxxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwrdegoede@xxxxxxxxxxxxxxxx | |g --- Comment #50 from Hans de Goede (jwrdegoede@xxxxxxxxxxxxxxxxx) --- (In reply to Andy Shevchenko from comment #49) > (In reply to wse from comment #48) > > More testing with same result: Hardcoding the adress to 0x2C works on > > widnows, but breaks on other values including 0x8C > > This is interesting, it may mean that Windows driver has a quirk against the > firmware bug. Or maybe it is adding 0x60 to all GpioInt numbers for some reason, it seems we are having a lot of issues with GpioInt lookups on Tiger Lake, so I suspect that there is actually something which Linux is doing differently then Windows, rather then there being model specific quirks in Windows. Also see bug 213857 which appears to be yet another instance of this problem, that is with a high-end Asus laptop, granted Asus ACPI table quality is all over the place but their higher end models tend to be pretty decent. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
