Commit 06c3145d authored by Geert Uytterhoeven's avatar Geert Uytterhoeven Committed by Rob Herring

dt-bindings: arm: idle-states: Correct references to wake-up delay

The paragraph explains the use of wakup-delay, as defined above.
Signed-off-by: default avatarGeert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: default avatarAmit Kucheria <amit.kucheria@linaro.org>
Acked-by: default avatarDaniel Lezcano <daniel.lezcano@linaro.org>
Signed-off-by: default avatarRob Herring <robh@kernel.org>
parent fb2d2329
...@@ -99,8 +99,8 @@ of an idle state, e.g.: ...@@ -99,8 +99,8 @@ of an idle state, e.g.:
wakeup-delay = exit-latency + max(entry-latency - (now - entry-timestamp), 0) wakeup-delay = exit-latency + max(entry-latency - (now - entry-timestamp), 0)
In other words, the scheduler can make its scheduling decision by selecting In other words, the scheduler can make its scheduling decision by selecting
(e.g. waking-up) the CPU with the shortest wake-up latency. (e.g. waking-up) the CPU with the shortest wake-up delay.
The wake-up latency must take into account the entry latency if that period The wake-up delay must take into account the entry latency if that period
has not expired. The abortable nature of the PREP period can be ignored has not expired. The abortable nature of the PREP period can be ignored
if it cannot be relied upon (e.g. the PREP deadline may occur much sooner than if it cannot be relied upon (e.g. the PREP deadline may occur much sooner than
the worst case since it depends on the CPU operating conditions, i.e. caches the worst case since it depends on the CPU operating conditions, i.e. caches
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment