ArenM 3ab2b5480f Read wakeup_count instead of using sxmo_wakeafter ... The approach sxmo_wakeafter uses is flawed because the kernel isn't obligated to pass control to it after suspend. I'm pretty sure it normally gets called when the kernel updates the system clock. Since we're waiting for some time after every suspend we're not actually using opportunistic suspend. It's much simpler to read wakeup_count to ask the kernel to wait until there's no active locks. Signed-off-by: Willow Barraco <contact@willowbarraco.fr>		2023-02-24 09:42:44 +01:00
..
sxmo_aligned_sleep.c	avoid drift in clocks	2022-07-01 12:06:27 +02:00
sxmo_vibrate.c	sxmo_vibrate.c: use SXMO_VIBRATE_DEV envvariable	2022-10-16 20:40:02 -07:00