CONFIG_NUM_IRQS is a promptless symbol so setting it is not trivial. Add a
pointer to the documentation page which explains how to do it in the STM32
section of the 4.4 migration guide related to CONFIG_NUM_IRQS changes.
Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
(cherry picked from commit 0ac4d66410)
Without the trailing underscore, the link gets rendered raw, and is not
clickable.
Signed-off-by: Reto Schneider <reto.schneider@husqvarnagroup.com>
(cherry picked from commit 110ba3ec16)
Provide qualification scope summary and link to design listing.
Signed-off-by: Szymon Janc <szymon.janc@codecoup.pl>
(cherry picked from commit 9834ca4ef2)
Adds 4.4 to the list of supported releases and updates references to the
next planned release as 4.5. The EOL date is set to one year after
release.
Signed-off-by: Maureen Helm <maureen.helm@analog.com>
Use tone consistent with other bullet points and link to the driver's
binding so that readers have a clear starting point to learn more.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Moves release notes documenting the removal of some Xtensa architecture
Kconfigs and some Bluetooth controller Kconfigs into the "Removed APIs
and options" section.
Signed-off-by: Maureen Helm <maureen.helm@analog.com>
Add a note about the new dependency of kernel.h to generated headers.
This has been a major source of breakages for us downstream, it'll
likely be useful to other users too.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Add zbus async listeners, improve multi-domain proxy agent notes, and add
new API entries to the v4.4.0 release notes.
Signed-off-by: Rodrigo Peixoto <rodrigopex@gmail.com>
Fixes spelling of "Alternatively", adds proper link to kconfig option,
and fixes Sphinx code block markup.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
As of 0.13.0, mcumgr-toolkit now supports all SMP groups.
Also, its CLI tool is now mentioned specifically.
Signed-off-by: Martin Stumpf <finomnis@gmail.com>
Fix up the existing migration guide entries.
Add missing bits.
Remove information about the PSA Crypto API changes; they belong to
upstream Mbed TLS.
Move `Mbed TLS` under `Modules` instead of `Other subsystems`.
Populate the release notes with the same information but in addition
add the new and deprecated Kconfig options.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
On SMP systems with tickless kernels, a race condition exists between
timer driver ISRs and the kernel's tick accounting. The driver updates
its hardware cycle baseline under a private lock, then calls
sys_clock_announce() which updates curr_tick under the separate
timeout_lock. In the gap between these two lock releases, any kernel
code calling sys_clock_elapsed() sees the new driver baseline but the
old curr_tick, producing inconsistent time values that can go backwards.
This affects every code path using the internal elapsed() helper:
uptime queries, timeout scheduling, timeout cancellation, remaining
time queries, and next-expiry calculations.
The root cause is two separate locks protecting state that must be
mutually consistent. Fix this by exposing the kernel's timeout_lock
to timer drivers via sys_clock_lock()/sys_clock_unlock(), and
providing sys_clock_announce_locked() which assumes the lock is
already held.
Timer drivers can now acquire the single lock, update their hardware
state, and announce ticks all under the same lock — eliminating the
race window entirely. The key is passed to sys_clock_announce_locked()
which consumes it (releasing the lock when it returns).
The existing sys_clock_announce() becomes a backward-compatible wrapper,
allowing incremental driver migration with no flag day.
Document that sys_clock_set_timeout(), sys_clock_elapsed(), and
sys_clock_idle_exit() are called by the kernel with the timer lock
held. Update the timer driver guide in clocks.rst accordingly.
Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
Add migration guide entry for the FlexSPI NOR DTS
restructuring to the soc-nv-flash child node
convention introduced in b1afb494b0.
Signed-off-by: Ofir Shemesh <ofirshemesh777@gmail.com>
This commit adds additional information for contributors
who whish to contribute safety requirements to the project.
Most importantly, the guide explains how to setup
strictdoc to work with the project's safety requirements
repo.
Signed-off-by: Nicole Pappler <nicole@alektometis.com>
Signed-off-by: nicpappler <github@pappler.eu>
This commit adds the project's Safety Requirements Checklist as
agreed on with the project's safety assessor.
The content is augmented with
* examples
* more explanation to help potential contributers and reviewers
Signed-off-by: Nicole Pappler <nicole@alektometis.com>
Code example for `pm_device_runtime_enable` referenced a return value
that does not exist anymore.
Signed-off-by: Eden Frosst <eden.frosst@rbr-global.com>
Fix alphabetically sorting for binding types as it was previously
putting abbreviation (for which "raw" text started with ':abbr:...') as
first in the list.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Drop a few mentions to new drivers appearing in an inappropriate section.
There is a dedicated "New Drivers" section for new drivers :)
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This commit updates the list of boards, shields, samples, and bindings
added in Zephyr 4.4, aiming for completeness now that project has entered
the feature freeze phase.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
At the moment, the documentation is not explicitly clear
on the thread safety of the net packets. So we need to make
it clear that the packet handling will always be done by
a single thread.
Signed-off-by: Nikhil Namjoshi <nikhilnamjoshi@google.com>
Pygments latest release ships with multiple fixes in the Devicetree lexer
that we want to be able to use.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This commit adds EXTRAVERSION to code through version.h.
This aligns the symbols available in code with those available
in the VERSION file.
Signed-off-by: Adrian Bieri <adrian.bieri@loepfe.com>
