Can we have a more clear test setup here?
For example, now we have 2 devkits.
- Do both devices see bluetooth host wake interrupt on rel-32.5.1 without patch?
- Do both devices see bluetooth host wake interrupt on rel-32.5.1 with the patch?
It sounds like this patch does not work for rel-32.4.4 or older release. Which is under my expectation since we always use the latest branch to debug. There may be other patches on rel-32.5.1 which enhance the bluetooth interrupt issue. For older release bluetooth host interrupt issue, I would suggest you can directly rmmod the bluedroid driver as a workaround.
As for cpu cores, may I know what do you mean “remain 100%” usage? Do you already stop the pipeline but the cpu cores still have 100% usage?