Reworking the Zephyr Clock Control Subsystem
summary
Claim: unify Zephyr clocks to a single API modeled on Linux so fixed and dynamic clocks work interchangeably. Implementation proof of concept modifies code generation and device-tree handling, adds a compile-time struct clock_dt_spec (three cell slots) and helper macros, and tweaks gen_defines.py. Conversion of an esp32c2 board exercises the change on hardware but breaks other boards. Tradeoffs: a few bytes per clock versus driver coupling, migration paths and dependency/refcounting remain unresolved.
AI-written summary · about
chapters (4)
related talks
47mUpdates To Clock Management Within Zephyr RTOS- 47mUpdates To Clock Management Within Zephyr RTOS
40mClock Management in Zephyr RTOS
26mA Clock-Distribution Abstraction for Resource-Constrained Real-Time Systems in Zephyr
40mClock Management in Zephyr RTOS
33mImproving System Configuration for Zephyr and Beyond
41mZephyr & Linux Devicetree, Similarities and Differences – Practical Guide To Boards, Shields and Con
40mHow to extract a bare metal flavor of code out of Zephyr to use in RTOS?