https://bugzilla.kernel.org/show_bug.cgi?id=213579 --- Comment #51 from Andy Shevchenko (andy.shevchenko@xxxxxxxxx) --- (In reply to Hans de Goede from comment #50) > (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. Actually you may be quite right because number of bugs is growing. The numbering scheme of GPIOs is mystery and subject to last minute changes (because it's pure artificial layer on top of the hardware). It's quite possible that the driver was upstreamed with outdated mapping (see 4th parameter to the groups in the communities in the driver). I'm investigating this. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
