From a2da12a67e7921c97f495f26398b04b6c7a7afe0 Mon Sep 17 00:00:00 2001 From: Petteri Aimonen Date: Tue, 26 Sep 2023 14:03:17 +0300 Subject: [PATCH] Fix dependencies of CONFIG_SCHED_CPULOAD_ settings CONFIG_SCHED_CPULOAD_EXTCLK doesn't actually require tickless mode. As long as the platform provides external call to nxsched_process_cpuload(), it will work in either tickless or ticking mode. Removed Kconfig dependency. Instead, CONFIG_SCHED_CPULOAD_SYSCLK does require ticking mode to work, as documented in CONFIG_SCHED_CPULOAD help text. Added the dependency to Kconfig also. --- sched/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sched/Kconfig b/sched/Kconfig index 6dd1882e3d..40f6a06f4b 100644 --- a/sched/Kconfig +++ b/sched/Kconfig @@ -911,6 +911,7 @@ choice config SCHED_CPULOAD_SYSCLK bool "Use system clock" + depends on !SCHED_TICKLESS ---help--- If this option is enabled, the system clock is used for cpu load measurement by default. @@ -929,7 +930,6 @@ config SCHED_CPULOAD_SYSCLK config SCHED_CPULOAD_EXTCLK bool "Use external clock" - depends on SCHED_TICKLESS ---help--- There is a serious issue for the accuracy of measurements if the system clock is used, however. NuttX threads are often started at