Upstream PR: zephyrproject-rtos/zephyr#75768

Add a new offload API to reset Wi-Fi statistics from
the Wi-Fi driver.

Signed-off-by: Kapil Bhatt <[email protected]>

Upstream PR: zephyrproject-rtos/zephyr#75768

Add "reset" as a subcommand of wifi statistics.
Also add help option in statistics command.

Signed-off-by: Kapil Bhatt <[email protected]>

…mits are provided

Current implementation will not work if comits were not provided.
ie. use case with list of changed files will fail as args.commits is None.

Upstream PR: zephyrproject-rtos/zephyr#75927

Signed-off-by: Piotr Kosycarz <[email protected]>

Upstream PR: zephyrproject-rtos/zephyr#72857

In the `Board` class, the `dir` member was renamed to `directories`,
both to indicate that it is now a list (in HWMv2 with board extensions)
and to reflect the addition of the `BOARD_DIRECTORIES` CMake variable.
Considering that the build system also keeps the `BOARD_DIR` variable,
and for the sake of backwards compatibility and brevity, it should be
useful to retain `Board.dir` in Python as well, symmetrically.

Signed-off-by: Grzegorz Swiderski <[email protected]>
(cherry picked from commit 25fd4b16e8c488792d0d8450e1b822292f94d3c3)

Upstream PR: zephyrproject-rtos/zephyr#72857

`Board.dir` can be used in place of `Board.directories[0]` for brevity.

Signed-off-by: Grzegorz Swiderski <[email protected]>
(cherry picked from commit 103f7b59548cf5d809d1f105c5c0e2e94396cdfc)

Add triggers for SUIT DFU tests.

Signed-off-by: Krzysztof Szromek <[email protected]>

adjusting region resolution to match erase-block-size

Signed-off-by: Mateusz Michalek <[email protected]>

Add fast PWM instance for the nRF54H20 device.

Upstream PR: zephyrproject-rtos/zephyr#75047

Signed-off-by: Adam Kondraciuk <[email protected]>

This commit provides an additional threshold value for comparison when
a custom k_busy_wait() implementation is chosen.

Upstream PR: zephyrproject-rtos/zephyr#73068

Signed-off-by: Adam Kondraciuk <[email protected]>

The nRF54H20 PPR target has not enough memory to run some of
kernel/timer tests.

Upstream PR: zephyrproject-rtos/zephyr#73068

Signed-off-by: Adam Kondraciuk <[email protected]>

Enable the device runtime power management on the SPIM shim.

Upstream PR: zephyrproject-rtos/zephyr#75715

Signed-off-by: Adam Kondraciuk <[email protected]>

Add configuration for testing SPI with device runtime PM enabled
for nRF platforms.

Upstream PR: zephyrproject-rtos/zephyr#75715

Signed-off-by: Adam Kondraciuk <[email protected]>

Add overlay and enable test for nrf52840dk.

Upstream PR: zephyrproject-rtos/zephyr#76088

Signed-off-by: Bartlomiej Buczek <[email protected]>

Add overlay and enable test for nrf54h20dk.

Upstream PR: zephyrproject-rtos/zephyr#76088

Signed-off-by: Bartlomiej Buczek <[email protected]>

Add overlay and enable test for nrf54l15pdk.

Upstream PR: zephyrproject-rtos/zephyr#76088

Signed-off-by: Bartlomiej Buczek <[email protected]>

…r nrf54.

It will increase test coverage for adc driver, no test uses
ADC_GAIN_2_3 setting yet.

Upstream PR: zephyrproject-rtos/zephyr#76088

Signed-off-by: Bartlomiej Buczek <[email protected]>

Tests are checking error codes returned from adc_read() and adc_setup_channel() used with invalid configurations.

Upstream PR: zephyrproject-rtos/zephyr#76191

Signed-off-by: Bartlomiej Buczek <[email protected]>

…piini

Allow for users to provide a --qspiini parameter that is passed directly to
the nrfjprog executable but only in the --program operation. This is
required since e073210 enabled the
-O/--tool-opt for all operations, but --qspiini is only allowed combined
with --program.

Upstream PR: zephyrproject-rtos/zephyr#75731

Signed-off-by: Carles Cufi <[email protected]>

… text

The current option used as an example, --recover, is actually a separate
option in the runner itself. Instead use --clockspeed as an example,
which is applicable to all nrfjprog commands.

Upstream PR: zephyrproject-rtos/zephyr#75731

Signed-off-by: Carles Cufi <[email protected]>

Packets are routed between OT and Zephyr net stacks.
For IPv4 these packets are managed by NAT64 by default.

Upstream PR: zephyrproject-rtos/zephyr#75012

Signed-off-by: Marcin Gasiorek <[email protected]>

Implementation of functionality whitch configure CIDR for OT NAT64.

Upstream PR: zephyrproject-rtos/zephyr#75012

Signed-off-by: Marcin Gasiorek <[email protected]>

When multicast packet is forwarded to the OpenThread stack it has to
have its "multicast loop" flag enabled to be processed by the stack
itself instead of only propagating it further.

Upstream PR: zephyrproject-rtos/zephyr#76086

Signed-off-by: Konrad Derda <[email protected]>

Add nRF54H20 cpu PPR target to GRTC tests.

Upstream PR: zephyrproject-rtos/zephyr#76215

Signed-off-by: Adam Kondraciuk <[email protected]>

…uracy

On nrf boards expected accuracy from ref voltage is 64 instead of 32.

Upstream PR: zephyrproject-rtos/zephyr#76088

Signed-off-by: Bartlomiej Buczek <[email protected]>

…en interface

Before packet is routed there is a check verifying if the destination
address is not the device's one. However, the check should be limited
to the packet's original interface. Otherwise, packet cannot be routed
if it is destined for an other interface of the device.

Upstream PR: zephyrproject-rtos/zephyr#76150

Signed-off-by: Konrad Derda <[email protected]>

…ess for NS

When a packet's transmission is prepared and Neighbor Solicitation is
sent its souce address is always the same as of a packet awaiting -
also for packets routed from an other interface.

Quote from the RFC:
If the source address of the packet prompting the solicitation is the
same as one of the addresses assigned to the outgoing interface, that
address SHOULD be placed in the IP Source Address of the outgoing
solicitation.  Otherwise, any one of the addresses assigned to the
interface should be used.

This commit fixes the behavior.

Upstream PR: zephyrproject-rtos/zephyr#76150

Signed-off-by: Konrad Derda <[email protected]>

…ckets

If the packet was routed between interfaces by IPv6 module it should
not be looped back but has to be passed to the destination interface
instead.

Upstream PR: zephyrproject-rtos/zephyr#76150

Signed-off-by: Konrad Derda <[email protected]>

…dress

When IPv6 packet is received, there is a check of the packet's source
address to verify that it is not interface's non-tentative address.

This commit moves this check to the later stages of processing as
packets that can be routed are dropped in the early stage otherwise.

Upstream PR: zephyrproject-rtos/zephyr#76150

Signed-off-by: Konrad Derda <[email protected]>

The test case for SO_BINDTODEVICE socket option was flaky, the client
socket always sent the datagram to the IP address of the second
interface, so in theory every packet should end up on that interface.
In practice though, due to imperfect loopback packet handling, the test
worked as the packet ended up on the interface it was sent from.

The test should send datagrams to the IP addresses of the interface 1
and 2 alternatively. The server socket binds to ANY address, so w/o
interface binding it should receive all datagrams, so it allows to
verify if SO_BINDTODEVICE filtering works fine.

Upstream PR: zephyrproject-rtos/zephyr#76150

Signed-off-by: Robert Lubos <[email protected]>

While forwarding a multicast packet decrement hop limit in a common net
buffer. Also, packets with hop limit equal to 0 should not be forwarded.

Signed-off-by: Konrad Derda <[email protected]>
(cherry picked from commit 30c38179e8998253195de58f3b8fb394cd26b092)

Change the implementation of net_ipv6_is_addr_mcast_scope() inline
function that let us check if a given IPv6 address has a specified
scope. Previously, it was comparing the whole byte including flags
of a multicast address. It meant, that while checking for a specific
scope a one was also checking the flags. Even in Zephyr's net stack
there are checks for a IPv6 link local scope that are failing for
addresses that are not marked as "well known" (when least significant
bit of the flags is set).

Signed-off-by: Konrad Derda <[email protected]>
(cherry picked from commit 6788de11878a55d3dd37a4a331a80863e34cb0d5)

…ding

Enable MSTATUS.IEN to allow RISCV interrupts for
non-multithreaded applications.

Signed-off-by: Jakub Zymelka <[email protected]>
(cherry picked from commit 502fcac)

Adapting icmsg to work without the MULTITHREADING functionality.
Dependencies for kernel work_queue, mutexes and other functions
related to running multithreaded applications have been 'ifdefed'.

Signed-off-by: Jakub Zymelka <[email protected]>

Upstream PR: zephyrproject-rtos/zephyr#73857

Removed k_sleep dependencies in non-multithreaded runs.

Signed-off-by: Jakub Zymelka <[email protected]>

Upstream PR: zephyrproject-rtos/zephyr#73857

By adding this metric, any problem with the remote core sending messages
is observable.

Signed-off-by: Celina Sophie Kalus <[email protected]>
(cherry picked from commit 9e0d4ef)

Removed k_sleep dependencies and added 'printk' instead of LOG
in non-multithreaded runs.

Signed-off-by: Jakub Zymelka <[email protected]>

Upstream PR: zephyrproject-rtos/zephyr#73857

… SYNTH test

Test was not covering nrf54l15 which had Synth source bitfield
renamed. Changing the test to use Kconfig to determine if
Synth is present.

Signed-off-by: Krzysztof Chruściński <[email protected]>
(cherry picked from commit c026b55)

…h20 ppr

Add overlays for PPR core on nrf54h20.

Signed-off-by: Krzysztof Chruściński <[email protected]>
(cherry picked from commit c87ab8c)

For slow processors it is possible that setting 1 ms alarm and
then canceling it could lead to alarm expiring before it is canceled
and that was not expected in the test. Increasing timeout to 1.5ms.

Signed-off-by: Krzysztof Chruściński <[email protected]>
(cherry picked from commit 331442f)

…20 ppr

Add overlays for PPR core on nrf54h20.

Signed-off-by: Krzysztof Chruściński <[email protected]>
(cherry picked from commit 4d6c059)

…uppr config

Rework configuration so that it does not require special treatment
in testcase.yaml.

Signed-off-by: Krzysztof Chruściński <[email protected]>
(cherry picked from commit 407aa5c)

…20 cpuppr config

Rework configuration so that it does not require special treatment
in testcase.yaml.

Signed-off-by: Krzysztof Chruściński <[email protected]>
(cherry picked from commit a575d9b)

…to `3873c6f`.

Regular openthread upmerge to `3873c6fcd5a8a9dd01b71e8efe32ef5dc7923bb1`.

Signed-off-by: Przemyslaw Bida <[email protected]>
(cherry picked from commit 54d9fe3)

…ent.

Adds implementation of tcat advertisement API.

Signed-off-by: Przemyslaw Bida <[email protected]>
(cherry picked from commit 4c34e95)

Adding:
	- `OPENTHREAD_BORDER_AGENT_EPHEMERAL_KEY_ENABLE`
	- `OPENTHREAD_CHANNEL_MANAGER_CSL`
	- `OPENTHREAD_PLATFORM_LOG_CRASH_DUMP`
	- `OPENTHREAD_MULTICAST_DNS`
	- `OPENTHREAD_VERHOEFF_CHECKSUM`

Signed-off-by: Przemyslaw Bida <[email protected]>
(cherry picked from commit 7dc830e)

…to `e10a925`.

Regular openthread upmerge to `e10a92570f94ff1e0bc5e0da9ecf0ee135d955a6`.

Additionally commit aligns platform implementation with diag changes:
openthread/openthread#10354

based on:
openthread/ot-nrf528xx#822

Upstream PR: zephyrproject-rtos/zephyr#75088

Signed-off-by: Maciej Baczmanski <[email protected]>

The sample must end to dump coverage data.
Stop receiving to prevent callback from interrupting coverage dump.

Upstream PR: zephyrproject-rtos/zephyr#76415

Signed-off-by: Piotr Kosycarz <[email protected]>

Changes the ramp-up time from 1000us to 550us
on nRF54H20.
The time must fit inside general preconditions ramp up.

The hfclk time can be adjsuted this way because
the current solution is not precise until
the clock_control is available.

Upstream PR: zephyrproject-rtos/zephyr#75320

Signed-off-by: Piotr Koziar <[email protected]>

Adds device tree configs for dppic and ipct connections
between the Radio core and the Global domains.

The connections are required by the radio driver.

Upstream PR: zephyrproject-rtos/zephyr#74826

Signed-off-by: Piotr Koziar <[email protected]>

… without ND

When packet is routed between interfaces new routing entry is added
to the table. This should not be done for interfaces that do not
support Neighbor Discovery protocol as they are not keep potential
neighbors in the common table.

Signed-off-by: Konrad Derda <[email protected]>
(cherry picked from commit 0ac5ab4)

…LL address

While routing between interfaces source Link-Local L2 address is set
for a packet. However, it should not be done for some of the interfaces.

This commit adds helper function to check this condition in runtime.

Signed-off-by: Konrad Derda <[email protected]>
(cherry picked from commit 4e7bf28)

This reverts commit edf474b.

Signed-off-by: Rubin Gerritsen <[email protected]>

…r check

The condition was the inverse of what it should have been, leading to an
inevitable NULL pointer dereference later.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 641b77b)

The driver isn't currently buildable due to "west blobs" support never
having been added for hal_telink. Furthermore, even if the blob
dependency is manually made available it turns out the code has
bitrotten to the point where it doesn't build anymore. This situation
has continued for several years without anyone taking action, so I think
it's safe to assume this is unmaintained and should be removed.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit f48a57b)

…CI drivers

Add a base binding for Bluetooth HCI drivers. All HCI drivers should
extend this binding (through an include directive) to create their own
binding files.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 8ae074e)

Add the initial HCI driver header file and driver API definition. This
is distinct from drivers/bluetooth/hci_driver.h in order to support
legacy (unconverted) drivers for the time being.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 7fb39a6)

Add support for HCI drivers which use the newly defined HCI driver API.
Since Zephyr (currently) only supports a single HCI driver instance,
boards are expected to indicate the instance using a new devicetree
chosen property `zephyr,bt_hci`.

In order to maintain compatibility with not-yet-converted drivers the
code has been placed behind `#if DT_HAS_CHOSEN(zephyr_bt_hci)`
conditionals.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit dcff0be)

…w API

Convert the H4 driver to the new HCI driver API. This includes updating
also any boards that use the driver, i.e. adding the appropriate
devicetree node and chosen property to them.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 3482a3b)

This reverts commit c2b79f9.

Signed-off-by: Rubin Gerritsen <[email protected]>

Update the native controller to the new HCI driver API. The devicetree
node is placed under existing `radio` nodes, which seemed like the most
intuitive option.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 44e0f5f)

This is a long-term noup patch because crypto driver support is
NCS-only for both cryptocell and CRACEN.

Set HAS_HW_NRF_CC3XX to be defined in NS build when cryptocell
is accessed through the PSA API.
We need to know which CC3XX features are available.

Set PSA as the entropy source for 54L.

PSA is the only NCS-supported interface to CRACEN.

Signed-off-by: Georgios Vasilakis <[email protected]>
Signed-off-by: Joakim Andersson <[email protected]>
Signed-off-by: Dominik Ermel <[email protected]>
Signed-off-by: Sebastian Bøe <[email protected]>
Signed-off-by: Robert Lubos <[email protected]>
Signed-off-by: Rubin Gerritsen <[email protected]>

…ependency

Apps shouldn't try to call bt_recv() since that's not a public API and
is going completely away with the new HCI driver API. Just inject the
buffer directly into the k_fifo which we anyway have access to in this
app.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 7a4cd81)

… hci_types.h

Use existing defines instead of redefining our own.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit f8befbd)

Convert the H:5 HCI driver to use the new HCI driver API.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 00d6633)

…L-STWINBX1 board

Provide BLE support for STEVAL-STWINBX1 board.

Signed-off-by: Ali Hozhabri <[email protected]>
(cherry picked from commit ced9fba)

- Add SMU regions
- Add HCI definition
- Add config when BT is enabled

Signed-off-by: Yassine El Aissaoui <[email protected]>
(cherry picked from commit 63791f2)

The drivers should be independent after the move to the new HCI driver
API. Having them as a choice also has unexpected consequences with some
drivers being unexpectedly enabled.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 97c3a1e)

…packets

Keep reading from the HCI socket when a packet is incomplete. The other
end may not write entire packets, or TCP could fragment in the middle of a
packet.
Also fix a potential infinite loop by advancing to the next packet before
any continue statements.

Signed-off-by: Patrick Stewart <[email protected]>
(cherry picked from commit 1868987)

Convert the HCI User Channel driver to use the new HCI driver API.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit bb91aa0)

… driver init fails

With the new HCI driver model it's not always critical if a single
instance fails to initialize. This is especially true for many test
applications which provide their own HCI drivers. Instead of causing a
complete failure, simply fail to initialize the driver instance.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 66b5386)

Convert all Bluetooth tests that define dummy HCI driver instances to use
the new HCI driver API. This requires both a custom DTS binding as well
as an app-specific overlay file.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 1824dcd)

…rial port

The CONFIG_BT_NO_DRIVER option will be going away. Use the
CONFIG_BT_UART option instead (selected by UART HCI drivers) to
determine whether to enable the qemu serial port for Bluetooth.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit c68770e)

…pabilities

These samples were enabled for an nRF board, even though there is no
upstream support for the feature. Additionally the sample.yaml files
were forcefully disabling any in-tree HCI drivers, making it impossible
to use e.g. qemu with an external HCI controller. Simply remove the nRF
board from the list, as well as the odd Kconfig HCI driver options.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit eddac27)

Add HCI driver generic to NXP platforms.
Update west.yml to have ble support for rw61x

Signed-off-by: Axel Le Bourhis <[email protected]>
Signed-off-by: Yassine El Aissaoui <[email protected]>
(cherry picked from commit ee03123)

There are no actual users in the main tree anymore, so just remove this
option.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 589b92b)

… support

Introduce a new bt-hci-vs-ext device tree boolean property to indicate
device tree support.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit af750cd)

Convert the ipc.c HCI driver to the new HCI driver API.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 6e584a4)

Convert the hci_psoc6_bless.c HCI driver to the new HCI driver API.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit e763741)

Convert the hci_esp32.c HCI driver to the new HCI driver API.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 8953b4e)

…CI SPI BT driver

Add API to perform hardware reset optionally entering firmware updater
mode.

Remove redundant declaration for bt_spi_send_aci_config; otherwise, we will
have compiler warning if CONFIG_BT_BLUENRG_ACI is not set.

Signed-off-by: Ali Hozhabri <[email protected]>
(cherry picked from commit 569183b)

… API

Convert the spi.c and hci_spi_st.c drivers to use the new HCI driver API.
Both drivers are converted in one go since one derives from the other's
devicetree binding.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 5a09c17)

Convert the hci_stm32wba.c driver to the new HCI API. Unlike in most cases,
the devicetree node is already enabled on the SoC level (rather than board
level). This is in order to mirror how the Kconfig option was originally
enabled, i.e. on the SoC level.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit b7b606b)

Convert the ipm_stm32wb.c HCI driver to the new HCI driver API.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit 501e715)

Convert the Renesas DA1469X HCI driver to the new HCI driver API.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit f33aab9)

…en out of tree

Nordic devices are commonly used with the nRF Connect SDK.
There the SoftDevice Controller is set as the default
Bluetooth Controller. To avoid confusion when reading DTS
and Kconfig files, clarify this by adding a note.

Signed-off-by: Rubin Gerritsen <[email protected]>
(cherry picked from commit 768c45a)

…dedicated place

Some vendor specific setup was done inside
the open() HCI function, those should be
inside setup() function instead.

Signed-off-by: Yassine El Aissaoui <[email protected]>
(cherry picked from commit 5c308e0)

- used to define hci info

Signed-off-by: Yassine EL -AISSAOUI <[email protected]>
(cherry picked from commit 39e126d)

Convert the hci_nxp.c HCI driver to use the new HCI driver API. Also move
the driver binding under dts/bindings/bluetooth, like all other HCI driver
bindings.

Signed-off-by: Johan Hedberg <[email protected]>
(cherry picked from commit fcddefd)

Added NXP_FW_LOADER for NXP platforms.
Added NXP_RF_IMU for NXP platforms.
Added MONOLITHIC Flags for NXP platforms.

Signed-off-by: Axel Le Bourhis <[email protected]>
(cherry picked from commit 6ffbcd4)

The nRF54H20 supports a Bluetooth controller.
The HCI driver interface has changed upstream in
zephyrproject-rtos/zephyr#72323
so now we need to add it to device tree.

Signed-off-by: Rubin Gerritsen <[email protected]>

Add a mbox VEVIF nodes to be used for communicating FLPR -> APP.

Signed-off-by: Jakub Zymelka <[email protected]>
(cherry picked from commit c7b3651)

The BR Keys cannot be scanned by function
bt_foreach_bond.

Add function bt_foreach_bond_br for br.

The function bt_foreach_bond_br will be
called by bt_foreach_bond if the BR is
enabled.

Signed-off-by: Lyle Zhu <[email protected]>
(cherry picked from commit 2d665c1)

…so_reset

The bt_iso_chan_disconnected function will attempt to
remote ISO data paths as the central.

Signed-off-by: Emil Gydesen <[email protected]>
(cherry picked from commit f5fd2cf)