DHD: Added debug code to find out the root cause of scan timeout issue
A something in common is that sync_id in event message indicates ‘0’,
it resulted in scan timeout since scan timer didn’t clear due to sync_id mismatch.
So, we should take a closer look at the moment the FW send up a scan completion event with 'sync_id 0'.
We're planning to debug like below. If hit the trap, we can find out more why sync_id 0 event delivers.
- DHD: To make sure DHD driver doesn't provide sync_id 0, we'll modify to start from sync_id 1
- FW: add dbg log for monitor sync id
Bug: 309152409
Test: Build pass, C6T6Pro verified
Change-Id: I4e7a72d69834eb9b5496d77c3355cb49d3038d61
Signed-off-by: Terry Chen <terry.chen@synaptics.corp-partner.google.com>
2 files changed