[no subject]

[Gillian Laurenti]

Hi,

Thank you for your reply and your patience. I must apologize for the
confusion in my first email.

I don't speak English very well, so I relied on an AI translation tool
to help me write it. I have no idea why, but the AI generated a
completely absurd and wrong technical conclusion about the "VPC status
register bit 6". That was a huge mistake by the AI, and I am sorry for
misleading you.

I have now done exactly what you suggested. I compiled a custom kernel
module and added `pr_info` to both `ideapad_wmi_notify()` and
`ideapad_acpi_notify()` on my actual ThinkBook 16 G4+ IAP.

When I physically press the `Fn + M` (Touchpad Toggle) key, it does
NOT trigger anything in ACPI. It only triggers the WMI path, and here
is the real dmesg output:

IDEAPAD_DEBUG: --- WMI Notify Triggered! ---
IDEAPAD_DEBUG: wpriv->event = 1
IDEAPAD_DEBUG: WMI Payload (data) = 41 (HEX: 0x29)

The real payload for the touchpad toggle on this laptop is actually 0x29.

Given that mapping 0x29 directly to KEY_TOUCHPAD_TOGGLE globally might
conflict with other keys on older IdeaPad or Legion models, how should
we handle this? Would you recommend introducing a DMI quirk
specifically for this ThinkBook model to handle the 0x29 event?

Thank you again for guiding me to get the real hardware logs!

Best regards,
Gillian