Technical detail ยท Low-Power Design: Duty-Cycle Energy Accounting
Clock and voltage scaling
Dynamic voltage and frequency scaling (DVFS) can reduce instantaneous power, but it is not automatically an energy win. If lower frequency stretches the active window enough, the total energy may stay the same or increase.
Use clock or voltage scaling when:
- The workload has slack before the next deadline.
- The lower-power mode still finishes and returns to sleep early.
- Peripheral timing, radio deadlines, ADC accuracy, and bus clocks remain valid.
- The before/after trace shows lower charge per cycle, not just lower peak current.
Do not use it as a substitute for sleep, power gating, or radio batching.
Clock selection is also a firmware evidence item, not just a datasheet feature. A SAM4L-style Cortex-M design may expose run, sleep, wait, and retention modes, plus clock sources such as a 32 kHz oscillator, a 116 kHz system clock, a 1 MHz RC clock, and a 12 MHz fast RC clock. Use the slowest source or divider that still meets UART, SPI, ADC, radio, and interrupt timing requirements, then record the current and wake latency for that exact mode. Vendor-specific low-power states and clock trees are not portable across MCU families, so the review record should name the silicon, enabled clocks, retained peripherals, and measured charge per useful cycle. The same record should justify cost: a larger MCU or SoC may save active energy for one workload, but it still needs evidence that the added memory, buses, accelerators, or radio features are worth their price and sleep-floor consequences.
A faster clock only helps if it finishes sooner and returns to sleep earlier.