From f28b57ff8ddb425ea540bcd5a51406a680b4ed88 Mon Sep 17 00:00:00 2001 From: Gerard Marull-Paretas Date: Tue, 9 Nov 2021 23:16:04 +0100 Subject: [PATCH] doc: guides: pm: system: fix DT bindings references Use the :dtcompatible: role to refer to DT bindings. Signed-off-by: Gerard Marull-Paretas --- doc/guides/pm/system.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/guides/pm/system.rst b/doc/guides/pm/system.rst index 2cc6049f541..e9c31405ed6 100644 --- a/doc/guides/pm/system.rst +++ b/doc/guides/pm/system.rst @@ -63,16 +63,16 @@ The policy manager is responsible for informing the power subsystem which power state the system should transition to based on states defined by the platform and possible runtime :ref:`constraints` -Information about states can be found in the device tree, see -:zephyr_file:`dts/bindings/power/state.yaml`. +More details on the states definition can be found in the +:dtcompatible:`zephyr,power-state` binding documentation. Residency --------- The power management system enters the power state which offers the highest -power savings, and with a minimum residency value (in device tree, see -:zephyr_file:`dts/bindings/power/state.yaml`) less than or equal to -the scheduled system idle time duration. +power savings, and with a minimum residency value (see +:dtcompatible:`zephyr,power-state`) less than or equal to the scheduled system +idle time duration. This policy also accounts for the time necessary to become active again. The core logic used by this policy to select the best power