I am experimenting with suspend to RAM power saving feature on my debian platform while using uavcan::Timer. As I understand, uavcan::Timer uses software timer (clock_gettime with CLOCK_ MONOTONIC) and therefore does not “tick” while suspended.
My platform automatically sync systemtime with RTC when waking up from low power mode, but it looks like it does not affect the timers, hence they resume ticking from the point in time low power mode was entered. As a result, the expected duration of the timers are not correct.
Are there any side affect if changing to CLOCK_REALTIME?
I may expect that changing RTC/System time may have an impact…