459c4b7f60
The rp23xx hardware headers define a register address macro for every register, then a block of register bit definitions. In three headers a bit definition reuses the name of a register address macro, so the register address is silently redefined as a bit mask: RP23XX_POWMAN_BADPASSWD address 0x40100000 -> (1 << 0) RP23XX_POWMAN_BOD_CTRL address 0x40100018 -> (1 << 12) RP23XX_POWMAN_DBG_PWRCFG address 0x401000a4 -> (1 << 0) RP23XX_BUSCTRL_BUS_PRIORITY_ACK address 0x40068004 -> (1 << 0) RP23XX_BUSCTRL_PERFCTR_EN address 0x40068008 -> (1 << 0) RP23XX_PADS_QSPI_VOLTAGE_SELECT address 0x40040000 -> (1 << 0) None of these headers has an in-tree user yet, which is why this has gone unnoticed; each clash appears as a "macro redefined" warning as soon as a driver includes the header. Code that included one of them and used the register by name would have dereferenced 1 or 0x1000 instead of the register. Two of the POWMAN clashes were plain duplicates. Per the RP2350 datasheet BOD_CTRL bit 12 is ISOLATE and DBG_PWRCFG bit 0 is IGNORE, and the correctly named RP23XX_POWMAN_BOD_CTRL_ISOLATE and RP23XX_POWMAN_DBG_PWRCFG_IGNORE were already defined with the same values on the following lines, so the bare names are simply removed. The blank line separating the VREG_LP_EXIT and BOD_CTRL groups is restored at the same time; its absence is what let the duplicate hide inside the preceding group. The other four are single field registers whose field carries no separate name (the datasheet and the SDK describe each as a one bit register), so their bit definitions are renamed to <REGISTER>_MASK, following the _MASK spelling these headers already use for a field extent, and written in hex like their peers. The rp23xx-rv copies of the three headers are identical to the arm ones and carry the same clashes, so they get the same change and stay in sync. No functional change: none of the six names has any user in the tree. Assisted-by: Claude Code:claude-opus-5 Signed-off-by: Marco Casaroli <marco.casaroli@gmail.com> |
||
|---|---|---|
| .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.