<wadim_>
I was trying to understand the wakeup source IDs reported by ti_sci_resume. But in my case I can see 0xFF as the source regardless of the source used.
<wadim_>
Besides that I do not understand why my system is able to wakeup using the main GPIO controller. Why is the GPIO controller not powered off at all?
<dhruvag2000>
Should've caught sooner - This should not be s2idle: ``PM: suspend entry (s2idle)``
<dhruvag2000>
Do you have a custom TF-A as well @wadim_ ?
wadim_ has quit [Ping timeout: 256 seconds]
wadim_ has joined #linux-ti
<wadim_>
No, no changes to TFA. it is a vanilla build
<wadim_>
Any idea why it is entering the s2idle mode and not the deep sleep?
<dhruvag2000>
Not entirely sure at the moment, what happens if you `echo deep > /sys/power/mem_sleep` ? Does cat of that sysfs even give you that option?
<dhruvag2000>
Could you also help with full boot logs from SPL to Linux so we can be sure of all the firmware versions and SHAs being used on both our ends?
<wadim_>
No, I do not see the deep option in mem_sleep. Only s2idle option
minas has quit [Remote host closed the connection]
minas has joined #linux-ti
wadim_ has quit [Ping timeout: 256 seconds]
Peng_Fan has joined #linux-ti
wadim_ has joined #linux-ti
<wadim_>
Thank you!
<wadim_>
My device wakes up immediately after entering the deep sleep mode, caused by a USB1 wakeup. The usb interrupt count goes up, but it does only when entering the sleep mode.
<wadim_>
Disabling usb1 via device tree makes the suspend process hang after "printk: Suspending console(s) (use no_console_suspend to debug)"