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.
This commit is contained in:
parent
d68c8ec560
commit
a2da12a67e
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue