4108e14740
Accurate timekeeping is something that is often taken for granted. However, reliability of timekeeping code is critical for most core and subsystem code. Furthermore, Many higher-level timekeeping utilities in Zephyr work off of ticks but there is no way to modify ticks directly which would require either unnecessary delays in test code or non-ideal compromises in test coverage. Since timekeeping is so critical, there should be as few barriers to testing timekeeping code as possible, while preserving integrity of the kernel's public interface. With this, we expose `sys_clock_tick_set()` as a system call only when `CONFIG_ZTEST` is set, declared within the ztest framework. Signed-off-by: Chris Friedt <cfriedt@meta.com> |
||
|---|---|---|
| .. | ||
| arch/unit_testing | ||
| boards/unit_testing/unit_testing | ||
| busy_sim | ||
| coverage | ||
| include/zephyr | ||
| soc/unit_testing/unit_testing | ||
| ztest | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Kconfig.defconfig | ||