Hi team,
I received inquiry about this subject. When standby command was executed, it took around 1.4 seconds till it entered standby mode completely. When GPIO's wakeup signal was issued during entering standby-mode (1.4sec), it seems, this wakeup was ignored. Customer does not want to ignore this GPIO's wakeup signal. In other words, AM335x entered Standby-mode and never wakeup because AM335x was not able to catch this GPIO's wakeup.
According customer's detail analysis, when GPIO's wakeup issued between "systemctl suspend" message and " Suspending console(s)" message, wakeup was ignored. There is not any problem to enter standby-mode, however, customer would like to do wakeup after that. Can we have any solution (like queuing task or checking wakeup-event on final stage) for this ?
-----------------------------------------------------
[2021-02-02 10:37:53.533] system("systemctl suspend")
[2021-02-02 10:37:54.763] [ 4582.190570] PM: suspend entry (shallow)
[2021-02-02 10:37:54.844] [ 4582.201232] PM: Syncing filesystems ... done.
[2021-02-02 10:37:54.890] [ 4582.275336] Freezing user space processes ... (elapsed 0.003 seconds) done.
[2021-02-02 10:37:54.890] [ 4582.286218] OOM killer disabled.
[2021-02-02 10:37:54.890] [ 4582.289720] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[2021-02-02 10:37:54.890] [ 4582.299443] Suspending console(s) (use no_console_suspend to debug)
-----------------------------------------------------
This requirement is mandatory for customer. Customer needs Expert's comments within today (in your time).I'm sorry to rush you but it is really appreciated your quick reply
Best regards,
Miyazaki
