7c02367483
/proc/pm/state0 reported a flat 0 s in its SLEEP column on a board that was demonstrably light-sleeping, because this port never told the PM core it had slept. pm_stats() (drivers/power/pm/pm_changestate.c) splits the time since the last transition into dom->wake[state] or dom->sleep[state] depending on whether the state it is handed is PM_RESTORE. up_idlepm() called esp_pmstandby() and carried straight on, so every second -- including the ones spent in light sleep -- was billed to wake[]. The statistics CONFIG_PM_PROCFS advertises were simply never true here. Read from an esp32s3-xiao that had just spent 89 s in PM_STANDBY: DOMAIN0 WAKE SLEEP TOTAL standby 89s 83% 0s 0% 89s 83% Only PM_STANDBY needs this. PM_SLEEP is deep sleep and does not return at all -- the chip resets -- so there is nothing to attribute on its way back. pm_changestate(domain, PM_RESTORE) is the documented way to say this: it skips the driver prepare/veto phase, records the statistic, notifies drivers of the restore, and deliberately does not overwrite the domain's state, so the domain stays in PM_STANDBY as it should. Signed-off-by: Felipe Moura <moura.fmo@gmail.com> Assisted-by: Claude:claude-opus-5 |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .codespell-ignore-lines | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmessage | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.