NishanthMenon changed the topic of #linux-ti to: Linux development for TI SoCs | Logs: https://libera.irclog.whitequark.org/linux-ti/| paste logs in https://pastebin.ubuntu.com/ | Let it rock! Vendor SDK/kernel: Also see e2e.ti.com
HcE has quit [Ping timeout: 255 seconds]
HcE has joined #linux-ti
florian_kc has joined #linux-ti
florian_kc is now known as florian
goliath has joined #linux-ti
Kubu_work has joined #linux-ti
ikarso has joined #linux-ti
<Kubu_work> Hello, it seems a new j721e Silicon Revision 2.0 has been released but the errata is not updated yet
wadim_ has joined #linux-ti
<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?
<vigneshr> wadim_: could you provide info about the TIFS and DM firmware being used?
<dhruvag2000> Also, kernel version, u-boot version helps..
<wadim_> Everything is based on TI Tag 10.00.07
<dhruvag2000> Something funny with the m4f firmware, ideally should get: `remoteproc remoteproc0: stopped remote processor 5000000.m4fss
<dhruvag2000> `
<dhruvag2000> Are these complete verbose logs? I don't even see your CPU's being suspended
<dhruvag2000> ```
<dhruvag2000> [ 30.981215] Disabling non-boot CPUs ...
<dhruvag2000> [ 30.983394] psci: CPU1 killed (polled 0 ms)
<dhruvag2000> [ 30.986714] psci: CPU2 killed (polled 0 ms)
<dhruvag2000> [ 30.990028] psci: CPU3 killed (polled 0 ms)
<dhruvag2000> ```
<dhruvag2000> These logs should've come ideally
<wadim_> I have no debug enabled. That is all I see on the debug console
<wadim_> Oh wait, my ti-linux-firmware was on 10.00.06
<dhruvag2000> Can you try once without the m4 rproc module if possible? It seems like system is aborting suspend
<dhruvag2000> Hence I can see a resume log immediately after the m4 rproc timeout occurs.
<wadim_> We have a custom m4 fw, but it has a graceful shutdown procedure afaik. Give me a minute
<wadim_> https://pastebin.ubuntu.com/p/NQQv6prMDr/ Based on 10.00.07 + no ti_k3_m4_remoteproc.ko
<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
<wadim_> Here is a full log: https://pastebin.ubuntu.com/p/6sDNWzQ22v/
ikarso has quit [Quit: Connection closed for inactivity]
<wadim_> Thanks for the s2idle hint :)
<dhruvag2000> You'll need to enable the config suspend in yocto for atf ... I can send the exact file in ti yocto if required
<NishanthMenon> i thought latest tfa tip dropped that req?
<NishanthMenon> if you are talking of K3_PM_SYSTEM_SUSPEND i think..
<wadim_> Thanks for the pointers, I will try it
wadim_ has quit [Ping timeout: 256 seconds]
wadim_ has joined #linux-ti
<wadim_> Seems to work with a more recent TFA version :)!
<wadim_> How do I find the mapping of the wakeup sources? wakeup source: 0x71
florian has quit [Ping timeout: 276 seconds]
wadim_ has quit [Ping timeout: 256 seconds]
<dhruvag2000> https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/pm/lpm.html @wadim_ see TISCI_MSG_LPM_WAKE_REASON
<dhruvag2000> USB1
florian has joined #linux-ti
wadim_ has joined #linux-ti
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)"
<dhruvag2000> @wadim_ maybe it's not stuck, can you try waking with rtc + usb disabled
wadim_ has quit [Ping timeout: 256 seconds]
wadim_ has joined #linux-ti
<wadim_> It is not waking up
<wadim_> [  117.005121] PM: suspend entry (deep)
<wadim_> [  117.008819] Filesystems sync: 0.000 seconds
<wadim_> [  117.014782] Freezing user space processes
<wadim_> [  117.020464] Freezing user space processes completed (elapsed 0.001 seconds)
<wadim_> [  117.027443] OOM killer disabled.
<wadim_> [  117.030671] Freezing remaining freezable tasks
<wadim_> [  117.036495] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
<wadim_> [  117.043891] printk: Suspending console(s) (use no_console_suspend to debug)
goliath has quit [Quit: SIGSEGV]
<wadim_> Will give an update tomorrow, have to double check my builds!
<dhruvag2000> Sure, really appreciate you testing out low power on new hardware.
_whitelogger has quit [Ping timeout: 246 seconds]
_whitelogger has joined #linux-ti
florian has quit [Quit: Ex-Chat]
wadim_ has quit [Ping timeout: 256 seconds]
florian has joined #linux-ti
ecdhe has quit [Ping timeout: 260 seconds]
ecdhe has joined #linux-ti
Kubu_work has quit [Quit: Leaving.]
florian has quit [Ping timeout: 252 seconds]