Am 29.04.24 um 16:54 schrieb Heikki Krogerus:
Hi, There's a bug that is caused by an EmbeddedControl OpRegion which is declared inside the scope of a specific USB Type-C device (PNP0CA0): https://bugzilla.kernel.org/show_bug.cgi?id=218789 It looks like that's not the only case where that OpRegion ID is used outside of the EC device scope. There is at least one driver in Linux Kernel (drivers/platform/x86/wmi.c) that already has a custom handler for the EmbeddedControl OpRegion, and based on a quick search, the problem "Region EmbeddedControl (ID=3) has no handler" has happened with some other devices too. Br,
Hi, i support your proposal, but i think we first have to figure out how Windows handles such cases. Those devices are build for and tested with Windows only, so Windows seems to specify some behavior which allows for this. I will try to contact Microsoft and ask them how the Windows Kernel handles this OpRegions. Thanks, Armin Wolf
