This issue generally happens to platforms that default to use s2idle but S3 is in use.
BIOS doesn't turn off the touchpad power during S3, hence the IRQ gets pulled up.
So I suggest use s2idle, or ask the platform vendor to solve the issue from BIOS.
Do you have this issue after S3?
This issue generally happens to platforms that default to use s2idle but S3 is in use.
BIOS doesn't turn off the touchpad power during S3, hence the IRQ gets pulled up.
So I suggest use s2idle, or ask the platform vendor to solve the issue from BIOS.