The new ace30 files structure is organized as follows:
intel_adsp_ace30.dtsi - main file for all variants
intel_adsp_ace30_ptl.dtsi - additional file for PTL variant
intel_adsp_ace30_wcl.dtsi - additional file for WCL variant
The main ace30.dtsi file contains most of the fields,
with only the differences specified in the ace30_ptl.dtsi
and ace30_wcl.dtsi files.
Signed-off-by: Adrian Bonislawski <adrian.bonislawski@intel.com>
use public queue methods to clear queue on failure
-s Felix Behnke felixbeiderarbeit@gmail.com
Signed-off-by: Felix Behnke <felixbeiderarbeit@gmail.com>
Add Variscite DART-MX8M-PLUS board support. This SoM is based on NXP's
i.MX8M Plus SoC. It includes Cortex-A53 and Cortex-M7 support.
Signed-off-by: Andre Morishita <andre.m@variscite.com>
The image_def header shall not be added to apps that are booted by a
bootloader, e.g. mcuboot. Added proper handling for UF2 by hanan619.
Signed-off-by: Manuel Aebischer <manuel.aebischer@belden.com>
Some NXP boards are using legacy SDK driver, such as S32K, K64, MIMX8Q,
and so on. The legacy SDK driver will not be updated, migrate to use
SDK NG driver.
Signed-off-by: Jason Yu <zejiang.yu@nxp.com>
Avoid the following exception in the Identity test when the commit body
is empty:
Traceback (most recent call last):
File "zephyr/scripts/ci/check_compliance.py", line 2053, in main
n_fails = _main(args)
^^^^^^^^^^^
File "zephyr/scripts/ci/check_compliance.py", line 1988, in _main
test.run()
File "zephyr/scripts/ci/check_compliance.py", line 1459, in run
auth_name, auth_email, body = git(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 3, got 2)
This is triggered because ``%b`` represents the body of the commit
message, which can be empty if there's a single line in it, because the
first line is considered the title.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Rework renesas rcar_salvator_xs doc to meet what has
been done for the documentation of other rcar boards.
Also take advantage of these new boards documentation
features:
- zephyr:board
- zephyr:board-supported-hw
- zephyr:board-supported-runners
Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
Edit the rcar_salvator_xs board full_name
from specific A57 name to generic one
to meet names used by other rcar boards
and unify this boards range documentation.
Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
Rework renesas rcar_salvator_x doc to meet what has
been done for the documentation of other rcar boards.
Also take advantage of these new boards documentation
features:
- zephyr:board
- zephyr:board-supported-hw
- zephyr:board-supported-runners
Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
Edit the rcar_salvator_x board full_name
to meet names used by other rcar board
and unify this board range documentation.
Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
Merge both dedicated r52 and a55 spider_s4 boards doc
into an all-in-one documentation and take advantage
of these new boards documentation features:
- zephyr:board
- zephyr:board-supported-hw
- zephyr:board-supported-runners
Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
Edit the rcar_spider_s4 board full_name
from specific A55 name to generic one
as it is used as main name for the whole board.
Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
Merge both dedicated r7 and a57 h3ulcb boards doc
into an all-in-one documentation and take advantage
of these new boards documentation features:
- zephyr:board
- zephyr:board-supported-hw
- zephyr:board-supported-runners
Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
Edit the rcar_h3ulcb board full_name
from specific A57 name to generic one
as it is used as main name for the whole board.
Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
The first 1 KB is reserved for the NWP (Network Coprocessor). This
change also resolves the null pointer error issue, as a .data or a
_ramfunc might get the address 0x0.
Signed-off-by: Martin Hoff <martin.hoff@silabs.com>
The nRF52840 Preview development kit is no longer available and the
text in the README.rst is changed to be "nRF52840 Development kit" and
the link to the documentation is changed to point to the production
version.
Signed-off-by: Ole Sæther <ole.saether@nordicsemi.no>
if the provided name in argument is not null this could lead to un
undefined behavior.
Use strnlen to make this safe
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
Add a function to get the value's length of a Key. If it doesn't exist
returns 0.
Add ZMS implementation for csi_get_val_len() and a default implementation
for the other storage systems.
Add some functional tests to verify it.
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
When a power off happens after writing the settings name and before
writing the linked list node we cannot write the settings name again in
the future.
Fix this by writing the linked list node before writing the name.
When loading all settings, we already delete linked list node that do
not have any name or value written.
Adds as well a recover path if a power down happens in the middle of
unlinking an LL node after a delete.
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
Add a test for the new API settings_load_one that loads only one path
from the persistent storage.
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
Add a a function settings_load_one that allows to load only one settings
entry instead of a complete subtree.
Add as well its implementation for ZMS backend.
This will allow a faster return if the Settings entry doesn't exist in
the persistent storage.
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
Increase the load performance by adding an optional cache for the linked
list hashes.
This is used only when the settings_load is called with NULL parameter
and we need to load all Settings that exist in the persistent storage.
Cache is enabled using SETTINGS_ZMS_LL_CACHE and the size of the cache
is set using SETTINGS_ZMS_LL_CACHE_SIZE.
Each cache entry will add 8 bytes of RAM usage.
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
If the subtree argument is not NULL in the settings_load function, load
only the setting entry that corresponds to that subtree.
If the subtree argument is NULL or it is not found in the storage, load
all the existing entries in the storage.
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
Settings subsystem is storing the name ID and the linked list node ID
with only one bit difference at BIT(0).
Settings subsystem is also storing the name ID and the data ID in two
different ZMS entries at an exact offset of ZMS_DATA_ID_OFFSET.
Using the regular lookup function could result in many cache misses.
Therefore, to assure the least number of collisions in the lookup cache,
the BIT(0) of the hash indicates whether the given ZMS ID represents a
linked list entry or not, the BIT(1) indicates whether the ZMS ID is a
name or data and the remaining bits of the hash are set to a truncated
part of the original hash generated by Settings.
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
When the CONFIG_ZMS_NO_DOUBLE_WRITE is not enabled there is no need to
search in the cache for matching ID
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
When deleting a settings entry the linked list is updated by removing
the deleted node. This operation is time consuming and add some delays.
For applications that use almost the same set of Setting entries, add an
option to make this operation faster at a cost of having some empty
nodes in the linked list.
These empty nodes can be used later when the deleted entry is written
again.
Each empty node occupies 16B of storage.
Signed-off-by: Riadh Ghaddab <rghaddab@baylibre.com>
The NULL-pkt parameter for tcp_in() was designed for generating
a SYN packet to start the 1st TCP handshake. It is only used
in net_tcp_connect() and tp_input().
To simplify the tcp_in() code logic and make it better under-
standable, a tcp_start_handshake() is added for net_tcp_connect()
and tp_input() to use. Thus, the tcp_in() only handles the in-
coming TCP packets.
Signed-off-by: Shrek Wang <inet_eman@outlook.com>