Am 01.01.25 um 11:48 schrieb Hridesh MG:
On Wed, Dec 18, 2024 at 1:42 AM Armin Wolf <W_Armin@xxxxxx> wrote:
Actually i think you need to look into the Windows application and check if they call a
WMI method during initialization to enable this event. On the Linux side this event should
be supported if received.
I looked into this and the only two WMI calls made by the predator
sense service during initialization are SetGamingMiscSetting and
GetGamingSysInfo. Neither of those seem to contain the logic for
enabling the turbo button though. Could you tell me where you found
the ACPI code for submitting the turbo mode WMI event?
The ACPI method handling the Acer gaming WMI interface is called "WMBH" and is found inside
the "SSDT6" ACPI table.
This ACPI method should trigger the turbo mode button (found inside the DSDT table):
Method (_Q58, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF
{
Debug = "=====PROJECT_QUERY_58====="
^^^WMID.FEBC [Zero] = 0x07
^^^WMID.FEBC [One] = 0x04
^^^WMID.FEBC [0x02] = One
Notify (WMID, 0xBC) // Device-Specific
}
This method should be called by the embedded controller driver when he receives a special query
notification from the embedded controller.
Did you make sure that the turbo functionality is whitelisted for your model?
Alternatively here seems to be several other settings available through "SetGamingMiscSetting",
on of which (0x0F) seems to write to a field called "FMKY".
Maybe this stand for "Function modifier key"? Is there a way for you to find out which misc settings
exactly are being changed during initialization of the OEM application?
Thanks,
Armin Wolf
