After newly introduced changes the amount of RTC channels
used by the 802.15.4 driver is reduced to 2. This commit
updates this in samples configuration.

Signed-off-by: Artur Hadasz <[email protected]>
(cherry picked from commit 308e731)

Add hook needed to RTC pretick.

Signed-off-by: Krzysztof Chruściński <[email protected]>

This commit brings in Zephyr with workarounds for nRF5340 anomalies
165 and 168.

Signed-off-by: Andrzej Kuros <[email protected]>

For current ppi_trace_config it is impossible to trace events for
which PUBLISH register is overwritten in run-time after
ppi_trace_config is called. This function allows also to trace just
one event and does not allow to trace many-to-one topologies
which are possible with use of DPPIs.

To overcome above limitations ppi_trace_dppi_ch_trace is added.
In contrast to ppi_trace_config the function ppi_trace_dppi_ch_trace
focuses on tracing rather the DPPI channel leaving the preparation
of event network publishing to it to a user.

Signed-off-by: Andrzej Kuros <[email protected]>
(cherry picked from commit 503f8e4)

The function `z_nrf_rtc_timer_exact_set` is used in
`nrf_802154_platform_sl_lptimer_hw_task_prepare` to ensure
that moment of hardware timer task trigger is exactly as requested,
without possibility of CC channel adjustment due to late operation.

Signed-off-by: Andrzej Kuros <[email protected]>
(cherry picked from commit 0bb6241)

Instead of using an RTC1 channel for hardware tasks triggering
used by 802.15.4, an RTC0 channel is used. This frees an RTC1
CC channel, allowing it to be used by Zephyr for other purposes.

Signed-off-by: Artur Hadasz <[email protected]>
(cherry picked from commit 9b18cb3)

The cherry-picked workaround against nRF53 anomaly 165, the "pretick"
is based on nrfx 3.0.0. The added code introduces missing definitions
to the soc.c file which are missing in nrfx 2.11.0.

Signed-off-by: Andrzej Kuros <[email protected]>

This commit brings in the homekit with build size optimizations.

Signed-off-by: Andrzej Kuros <[email protected]>

The Network Core Monitor module provides network core status monitoring
by application core for the nRF5340 processor.
It allows detection of network processor suspensions and resets.
After a reset occurs, it is possible to read the cause of the reset.

Ref: NCSDK-22746

Signed-off-by: Marcin Jelinski <[email protected]>
(cherry picked from commit 30c05e3)

The `__weak ncm_net_core_event_handler` function is used to notify
the application about the network core staus.
This repleace the periodic call of the
`ncm_net_status_check` function.
This makes it easier to use and configure.

Ref: NCSDK-23996

Signed-off-by: Marcin Jelinski <[email protected]>
(cherry picked from commit 9939469)

* Make sure all C++ C includes have an end.
* Correct order of ifdefs and doxygen so that they are in the correct
  order. The order is not aligned from file to file, though it is
  corrected per file.
* Added space after license in some headers and source files.

Signed-off-by: Eivind Jølsgard <[email protected]>
(cherry picked from commit 6d8b9bb)

Let it have its own page in the menu.

Signed-off-by: Emanuele Di Santo <[email protected]>