d31609d8dd
up_idlepm() put the domain back in PM_NORMAL with pm_changestate() but left its local oldstate holding whatever it was before sleeping, usually PM_STANDBY. The pm_checkstate() below then returned PM_STANDBY again, the "newstate != oldstate" test compared PM_STANDBY against a stale PM_STANDBY, and the whole block was skipped -- including the esp_pmstandby() call that is the only thing in here that ever sleeps. So after the very first wakeup the board reported PM_NORMAL essentially forever, and light-slept only when something else happened to perturb oldstate, such as an application taking and releasing a PM_IDLE wakelock around a transmission window. Measured on the esp32s3-xiao collar before this fix: 4.1 s of actual light sleep in 2 h of near-total idleness, a 1780:1 awake-to-asleep ratio. After it: ~13.5% of wall time asleep, thousands of sleeps, no storms. The dead "newstate = PM_NORMAL" assignment that used to sit here was presumably meant to be this; it is overwritten by pm_checkstate() a few lines below and never had any effect. Note that fixing this is what exposed two further bugs that had been dormant behind a board that never slept: the systimer double-count in esp_pmstandby(), and I2C transfers being cut in half by sleep. Both are fixed in their own commits. 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.