Current issues with the driver

[qaz6750]

Problem

• In some cases, when installing and starting Windows for the first time, there may be a possibility of some users staying in the Windows spinning circle. The probability of this situation still exists based on the current user feedback, but after a forced restart, the Windows driver installation can be completed correctly and enter OOBE.

  • Guess: The FingerTipS521 driver encountered an exception while reading an interrupt or completing initialization, causing it to stay on a thread of the driver and unable to send an error return, resulting in continuous suspension during Windows loading.

• In some cases, if wireless charging is used for charging (the charging power is really low), the touch driver may stop working after a while and only recover after restarting.

  • Guess: When the driver reads an interrupt, it gets stuck abnormally, as in the previous text, and cannot return an error.

TODO.

• Investigate the causes of the above two issues and attempt to resolve them.
• Improve the resource configuration of Touch in ACPI, as in some cases the touch screen may stop working abnormally, and we suspect this is a power management issue.
• Fixed the issue where the touch driver failed to correctly restore to D0 state after entering D3 state, causing the touch driver to stop working. This is also the reason why we had previously disabled this function.
• Add firmware Auto Update and CRC error check to touch driver.