972a4d9f6f
This test assumes that nothing will wake the CPU apart from the timer set by the test. But that is not necessarily the case. Some other platform thread started at boot may be waking the CPU every now and then. Let's allow for some spurious wakes while we are testing k_cpu_idle, while at the same time ensuring we are not just busy waiting all the way. Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
15 lines
509 B
Plaintext
15 lines
509 B
Plaintext
# Copyright (c) 2024 Nordic Semiconductor ASA
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
config MAX_IDLE_WAKES
|
|
int "Maximum number of spurious wakes during k_cpu_idle() test"
|
|
default 1 if NRF53_SYNC_RTC
|
|
default 0
|
|
help
|
|
The platform may have some component running in the background while the k_cpu_idle test is
|
|
running causing the CPU to awake. With this option we allow for a maximum number of wakes
|
|
for each 10ms idle test, which by default should be 0.
|
|
|
|
# Include Zephyr's Kconfig
|
|
source "Kconfig"
|