Clock Management in Zephyr RTOS
summary
Proposal adds a two-layer clock model: a clock driver layer that exposes per-node APIs (get_rate, configure, optional set_rate/round_rate) and a management layer that maps hierarchical device tree clock nodes into named run and sleep states. Rate-change notify callbacks propagate parent changes to children. Prototype runs on an S5S69 and boots a hello world; notification path adds ~1 KB flash, and with callbacks disabled the implementation reports lower footprint compared to current clock_control.
AI-written summary · about
chapters (6)
- 0:00Introduction and agenda
- 1:06Current framework overview
- 6:32Requirements for a rework
- 10:32Proposed implementation
- 23:33Technical details and status
- 30:45Discussion and Q&A
related talks
40mClock Management in Zephyr RTOS
47mUpdates To Clock Management Within Zephyr RTOS- 47mUpdates To Clock Management Within Zephyr RTOS
40mReworking the Zephyr Clock Control Subsystem
26mA Clock-Distribution Abstraction for Resource-Constrained Real-Time Systems in Zephyr
42mCommon Clock Framework: How to use it
42mSTM32 on Zephyr, What You Need to Know
49mThe Zephyr™ Project – An Updated Overview