Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this page for instructions on how to get full permissions. Sorry for the inconvenience.
Do we have the hardware in place? our Wifi module supports wowlan and we have the wakeup source wired up? any reference / link to a source?
If so, do a first test using iw when connected to an AP, with a laptop waking up the devkit (magic frame / ping)
Test using iw to configure wakeup on "link changes", as suggested above.
(new issue): find WoWLAN "Patterns" we want to have in order for the essential services to wake up the system on incoming messages (calls via xmpp/matrix, messaging via xmpp/matrix, IMAPS email). best-case would be to stay independent of the TCP-port, but for testing, it could be a start.
suspending redpine feels more like unloading / shutting down. I get a new "iw dev" phy number after resume, it takes seconds to connect again, wowlan is disabled after resume and so on.
in short: we don't have plans (due to missing hardware support) for user-defined wakeups based on tcp/ip patterns - be it for the baseband or wifi modem. Instead we'll most likely work on resuming periodically (until an internet connection is established) and suspend again.
I still don't see the goal of this issue really. In my mind, we can only wake the system ourselves using an rtc. wifi seems to be reconnecting reliably in that case. but that's not at all what this issue is about. @angus.ainslie ?