https://bugzilla.kernel.org/show_bug.cgi?id=213579 --- Comment #18 from Andy Shevchenko (andy.shevchenko@xxxxxxxxx) --- Citing the hardware level documentation: "Each GPIO pad ownership assignment is pre-determined via OEM system configuration through BIOS, soft strap and/or embedded subsystems’ firmware settings with corresponding pin list documentation. ... In summary the pad ownership bit is used to determine: GPIO input event notification/status update to the subsystem owning the pad o setting of Host’s various interrupt status bits ... ... PAD Ownership (PAD_OWN) This register can be written by [Firmware] only. ... 00 = Host software (ACPI Mode or GPIO Driver Mode) has ownership of the pad. In Host GPIO Driver Mode (refer to HOSTSW_OWN), GPIO input event update is limited to GPI_STS update only. While in Host ACPI Mode, updates are limited to GPI_GPE_STS, GPI_NMI_STS and/or GPI_SMI_STS." Sorry, but OEM has to fix this. I love to know how Windows works around this. If anybody has that information, please share. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
