zephyr/subsys/pm
Bjarki Arge Andreasen 14117b453d pm: policy: separate default policy and events
The default policy currently directly references the private
variable next_event from policy_events.c to then convert the cycle
of said event (if exists) to a kernel tick in the future, something
policy_events.c already implements and exposes through
pm_policy_next_event_ticks().

Additionally, the implementation of pm_policy_next_state() in
policy_default.c already gets the nearest kernel tick, wherein
the next event has already been accounted for in, see
implementation of pm_system_suspend().

This commit removes the redundant and layer violating computation
if the tick of the next event from policy_default.c and updates
the test test_pm_policy_events to not use default policy to
determine if pm_policy_next_event_ticks() is correct.

Signed-off-by: Bjarki Arge Andreasen <bjarki.andreasen@nordicsemi.no>
2024-11-16 15:56:02 -05:00
..
policy pm: policy: separate default policy and events 2024-11-16 15:56:02 -05:00
CMakeLists.txt pm: policy: split policy APIs implementations 2024-10-24 17:50:44 +02:00
device_runtime.c everywhere: replace double words 2024-06-22 05:40:22 -04:00
device_system_managed.c pm: device: De-couple device pm from system pm 2024-06-04 19:13:53 -04:00
device_system_managed.h pm: device_system_managed: Fix functions return 2024-06-18 19:56:39 -04:00
device.c pm: device: allow optional support of TURN_ON action 2024-09-30 17:11:20 +01:00
Kconfig pm: policy: split policy APIs implementations 2024-10-24 17:50:44 +02:00
pm_shell.c pm: shell: filter out non PM enabled devices 2024-04-30 19:30:15 -05:00
pm_stats.c
pm_stats.h
pm.c pm: policy: change the policy event handling 2024-09-09 13:56:04 -04:00
state.c