sl_rail_util_built_in_phys.c provides strong definitions of the
RAIL_*_Phy* pointers for every protocol the device supports, overriding
the weak fallback definitions in the RAIL library. Core RAIL objects
reference these pointers regardless of which protocol is enabled, e.g.
rail_rf_hal.o references RAIL_BLE_Phy1MbpsViterbi and rail_zwave_rf_hal.o
references RAIL_ZWAVE_Phy9p6kbpsConcurrent, both of which are pulled in
via rail_singleprotocol.o.
Only compiling the Bluetooth and IEEE 802.15.4 PHY configurations
therefore breaks the link on devices supporting other protocols, such as
Z-Wave on EFR32xG23 and EFR32xG28:
undefined reference to `zwave_9p6kb_conc_channelConfig'
Compile the PHY configuration of every protocol supported by the device
instead. Unused configurations are discarded by the linker, so this has
no impact on the resulting image.
Assisted-by: GitHub Copilot:claude-opus-5
Signed-off-by: Johan Hedberg <johan.hedberg@silabs.com>
Getting the PMK out of the supplicant for offline decryption currently
requires WIFI_NM_WPA_SUPPLICANT_LOG_LEVEL_DBG plus DEBUG_SHOW_KEYS,
which floods the console with full debug output and may affect
application execution.
Add a dedicated Kconfig, decoupled from the supplicant debug level,
that gates a single PMK print per successful handshake. Also add a
CMake configure-time warning so it can't be left enabled unnoticed.
The print itself keys off "CTRL-EVENT-CONNECTED" in
zephyr_wpa_supplicant_msg(), hostap's registered wpa_msg() sink: that
message is hostap's own single-shot signal for a newly completed
connection (wpa_supplicant.c, gated on wpa_s->new_connection), and
wpa_s->wpa->pmk is already populated by the time it fires.
Add net.wifi.build.print_pmk to tests/net/wifi/configs/tests.yaml,
matching that file's existing per-option build_only coverage pattern,
so this Kconfig gets its own CI build check.
Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
Assisted-by: Claude:claude-sonnet-5
Remove NRFS_LOCAL_DOMAIN_DVFS_SCALE_DOWN_AFTER_INIT, deprecated in
Zephyr 4.1 when the equivalent option was added to the nRF HSFLL local
clock control driver. Use CLOCK_CONTROL_NRF_HSFLL_LOCAL_REQ_LOW_FREQ
instead, which requests the lowest operating point after DVFS
initialization in exactly the same way.
The option defaulted to n and no in-tree configuration enabled it, so
this does not change any in-tree build.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Assisted-by: Claude:opus-5
Remove the hidden Kconfig option GPIO_AS_PINRESET, deprecated in Zephyr
3.5 in favour of the "gpio-as-nreset" property on the UICR devicetree
node. Nothing in-tree selected it, and the MDK glue in mdk_config.h has
derived NRF_CONFIG_GPIO_AS_PINRESET purely from the devicetree property
since then; only the stale comment naming the Kconfig symbol is updated.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Assisted-by: Claude:opus-5
CONFIG_WIFI_NAN_MAX_SSI_LEN sizes the inline SSI arrays, but the
ssi_len fields describing them in the NAN parameter structures are
uint16_t. A value above 65535 therefore builds happily and then
truncates the length while the array stays full size, and a value of 0
leaves a zero sized array behind. Neither is a configuration anyone
wants, so reject both instead of letting them through.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
nan_parse_ssi() derived the SSI length from the input hex string and
then discarded what hex2bin() reported, so the length never described
what had actually landed in the buffer.
hex2bin() converts nothing and returns 0 when the destination is too
small, which is precisely the case the code meant to handle: an SSI
longer than WIFI_NAN_MAX_SSI_LEN clamped the length to the maximum but
left the buffer untouched, so the event carried a full length SSI of
zeros. The callers memset() the event first, so this never disclosed
stack contents, but every byte of the reported payload was wrong. A
malformed hex string failed the same way, as hex2bin() stops at the
first bad character and returns 0 while the reported length still
claimed the whole string had converted.
Take the length from the return value instead, and truncate the input
rather than the output when the peer sends more than fits, so the
prefix that is reported is really the prefix that was converted. Warn
in both cases: an SSI that does not fit is worth knowing about, as the
only remedy is a larger buffer.
Assisted-by: Claude:claude-opus-5
Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
Use controller/peripheral and SDO/SDI terminology in sensor drivers,
following coding guideline rule A.2: switch the SPI configuration
constants to SPI_OP_MODE_CONTROLLER and update SPI wiring comments.
For the Broadcom AFBR-S50 sensor, the spi-sdi-gpios/spi-sdo-gpios
devicetree properties (named from the sensor's own perspective per
the OSHWA resolution) replace spi-mosi-gpios/spi-miso-gpios. The old
property names are still accepted, marked as deprecated in the
binding, and used as fallbacks; the Zephyr platform glue in
modules/hal_afbr is updated to the renamed fields. The Broadcom
Argus API names (s2pi_slave_t, S2PI_*) come from the vendor library
and keep their names.
Occurrences that concern I2C rather than SPI (I2C controller ACK
behavior comments in NXP drivers, the lsm6dso sensor-hub I2C master
code using ST HAL APIs and application note quotes) and vendor
register names (TDK MPUREG_MASTER_LOCK) are out of scope and keep
their wording.
Assisted-by: Claude:fable-5
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Two-line copyright notices were wrapped in the SPDX "<text>...</text>"
construct, which is only valid in an SPDX document, not a file header.
The REUSE tool then folds the literal "<text>" into the holder name
and drops the second line from the SBOM.
Remove the markers and tag the continuation line. Holder, year and
e-mail are left unchanged; only the syntax is fixed.
Signed-off-by: Parthiban Nallathambi <parthiban@linumiz.com>
LVGL's system monitor computes CPU usage as
100 - lv_os_get_idle_percent(). The Zephyr implementation of that hook
in lvgl_zephyr_osal.c can only return a real idle percentage when
CONFIG_CPU_LOAD is enabled; otherwise it returns 0 and the monitor
reports a constant 100% CPU usage.
Imply CPU_LOAD when LV_USE_SYSMON is set so the monitor works out of the
box. imply (rather than select) is used deliberately: CPU_LOAD depends
on a Cortex-M/RISC-V/Cortex-A architecture and !SMP, so a hard select
would produce unmet-dependency warnings and broken configurations on
unsupported targets (e.g. the POSIX architecture). With imply the option
is enabled only where its dependencies are met and remains overridable.
Signed-off-by: Vandra-Meyer Akos <akos@lvgl.io>
The AArch32 A-profile support was shared between ARMv7-A and ARMv8-A
AArch32 by threading "defined(CONFIG_ARMV7_A) ||
defined(CONFIG_AARCH32_ARMV8_A)" through every affected site. Each new
A-profile AArch32 variant would have to be added to all of those guards.
Introduce a hidden capability flag, ARM_A_PROFILE_AARCH32, selected by
both ARMV7_A and AARCH32_ARMV8_A, and migrate the shared guards to the
single CONFIG_ARM_A_PROFILE_AARCH32 symbol. Since the flag is selected
by exactly those two symbols, the guards are logically unchanged; a
future A-profile AArch32 variant now only needs to select the flag to
pick up the shared code paths.
Assisted-by: Claude:claude-opus-4-8
Signed-off-by: Pei Cheng Sung <pc_sung@realtek.com>
The CMSIS-DSP module has been updated to maintain Kconfig and
CMakeLists.txt in the module tree rather than external to
zephyr. Remove references to the obsolete feature-level Kconfig
options from all test and sample configurations.
The following options are no longer available:
- CONFIG_CMSIS_DSP_BASICMATH
- CONFIG_CMSIS_DSP_BAYES
- CONFIG_CMSIS_DSP_COMPLEXMATH
- CONFIG_CMSIS_DSP_DISTANCE
- CONFIG_CMSIS_DSP_FASTMATH
- CONFIG_CMSIS_DSP_FILTERING
- CONFIG_CMSIS_DSP_INTERPOLATION
- CONFIG_CMSIS_DSP_MATRIX
- CONFIG_CMSIS_DSP_QUATERNIONMATH
- CONFIG_CMSIS_DSP_STATISTICS
- CONFIG_CMSIS_DSP_SUPPORT
- CONFIG_CMSIS_DSP_SVM
- CONFIG_CMSIS_DSP_TRANSFORM
Signed-off-by: Ryan McClelland <ryanmcclelland@meta.com>
The SiWG917 has a data cache in front of PSRAM (family reference manual
rev 1.2 section 5.4.5). The bootloader leaves it enabled and nothing in a
Zephyr build maintains it: the SoC does not select CPU_HAS_DCACHE and
sys_cache_data_*() return -ENOTSUP. The network processor writes the same
memory, so contents read back stale or torn under load.
Disable it with the vendor call at the top of the memory controller init,
before PSRAM is set up.
Signed-off-by: Mikey Sklar <mikeysklar@gmail.com>
Argus_Malloc handed out 64-byte mem slab blocks while ignoring the
requested size, and Argus_CreateHandle asks for about 4.1 KiB, so the
handle overran into the following 64 blocks and destroyed the slab free
list. Size the blocks to cover the largest request the library makes
and fail a larger request honestly instead of returning undersized
memory.
Signed-off-by: Benjamin Perseghetti <bperseghetti@rudislabs.com>
Enable the smartdma_mcxa HAL driver component when CONFIG_DMA_MCUX_SMARTDMA
is selected on an MCXA SoC, mirroring the existing MCXN handling.
Signed-off-by: Neil Chen <cheng.chen_1@nxp.com>
The MFD init hook calls Cy_Crypto_Core_Enable(), but the driver never
selected the MXCRYPTO PDL sources that provide it: those are only
built when the TRNG or the crypto child driver selects one of the
USE_INFINEON_MXCRYPTO_* symbols. Any build that enables MFD for
another Infineon function driver (the autanalog or HPPASS drivers,
for instance) but leaves crypto and entropy off therefore failed to
link:
undefined reference to `Cy_Crypto_Core_Enable'
This broke the kit_pse84_eval comparator, adc_stream and autanalog
tests once the board defconfigs stopped enabling crypto and entropy.
Add USE_INFINEON_MXCRYPTO_CORE for the PDL sources shared by the three
accelerators and select it from the MFD driver, so the driver builds
on its own. Enable it by default only when a child function driver is
enabled so it is no longer pulled into builds with no use for the
block.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Assisted-by: Claude:opus-5
This commit updates the usage of ring_buf to utilize the new
put_ptr/commit/get_ptr/consume pattern instead of the traditional
claim/finish approach. This change is part of a larger refactor aimed at
streamlining the ring_buf API and improving its efficiency.
Signed-off-by: Måns Ansgariusson <mansgariusson@gmail.com>
The MCUX common header (fsl_common_arm.h) includes "fsl_clock.h"
unconditionally, and on i.MX952 that header lives in the device
drivers/ folder. The SDK only adds that folder to the include path when
one of its components is selected. On the Cortex-A55 the clocks are
managed over SCMI, so driver.clock is skipped and nothing else pulls
the folder in, which broke every A55 build:
error: fsl_clock.h: No such file or directory
(the imx952_evk A55 and A55 SMP builds of sample.kernel.synchronization
in CI).
Enable the header-only memory component for the device, the same
workaround already used for the i.MX943 fsl_elec_spec.h header.
driver.clock is not an option here: its fsl_clock.c drives the system
manager directly and is not meant for SCMI configurations.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Assisted-by: Claude:opus-5
1. update hal nxp to the SDK 26.09.00 pvw1
2. MCXA SystemInit initializes SRAM ECC by clearing
the first 8 KiB of SRAM. Zephyr calls SystemInit after
moving MSP to the main stack in that range, so the
clear corrupts the active return stack and locks up
during boot.
Move the ECC initialization to the no-stack early
reset hook and prevent SystemInit from repeating it.
This preserves cold-boot ECC initialization
without clearing an active Zephyr stack.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
When using WIFI_SECURITY_TYPE_EAP_PEAP_* security types,
the certificates are optional.
This skips their loading unless explicitely requested via the
verify_peer_cert parameter.
Signed-off-by: Bastien Jauny <bastien.jauny@smile.fr>
Add a CONFIG_BUILD_ONLY_NO_BLOBS path so the BLE applications can be
built in CI without fetching mcxw23 ll blobs.
When CONFIG_BUILD_ONLY_NO_BLOBS is set, the real link-layer components
(CONFIG_MCUX_COMPONENT_middleware.wireless.snps_ll and
CONFIG_MCUX_COMPONENT_middleware.wireless.snps_ll_os) are not enabled,
so neither the controller .c nor its blob dependency is pulled into the
build.
Signed-off-by: Yassine El Aissaoui <yassine.elaissaoui@nxp.com>
Remove the eight Mbed TLS Kconfig options that were renamed in Zephyr 4.3
to improve the 1:1 matching between Zephyr Kconfig symbols and Mbed TLS
build symbols, and that have been deprecated since then. They are removed
now as part of the 4.5 deprecation removal cycle.
The removed options and their replacements are:
CONFIG_MBEDTLS_MD -> CONFIG_MBEDTLS_MD_C
CONFIG_MBEDTLS_LMS -> CONFIG_MBEDTLS_LMS_C
CONFIG_MBEDTLS_TLS_VERSION_1_2 -> CONFIG_MBEDTLS_SSL_PROTO_TLS1_2
CONFIG_MBEDTLS_DTLS -> CONFIG_MBEDTLS_SSL_PROTO_DTLS
CONFIG_MBEDTLS_TLS_VERSION_1_3 -> CONFIG_MBEDTLS_SSL_PROTO_TLS1_3
CONFIG_MBEDTLS_TLS_SESSION_TICKETS -> CONFIG_MBEDTLS_SSL_SESSION_TICKETS
CONFIG_MBEDTLS_CTR_DRBG_ENABLED -> CONFIG_MBEDTLS_CTR_DRBG_C
CONFIG_MBEDTLS_HMAC_DRBG_ENABLED -> CONFIG_MBEDTLS_HMAC_DRBG_C
The two remaining in-tree users, the Mbed TLS module CMakeLists.txt
certificate validation warning and the smp_svr UDP/DTLS sample overlay,
are switched over to the new option names.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Assisted-by: Claude:opus-5
Expose mbedTLS's MBEDTLS_SSL_VARIABLE_BUFFER_LENGTH option in Kconfig.
When enabled, TLS in/out buffers are automatically resized after the
handshake to the size negotiated as max fragment length plus overhead.
This way the memory footprint after handshake is reduced to exactly
what is needed for the connection.
Add MBEDTLS_SSL_MAX_FRAGMENT_LENGTH as a proper Kconfig symbol,
so VARIABLE_BUFFER_LENGTH's dependency on it can be expressed directly
instead of duplicating the TLS 1.3 check.
Signed-off-by: Kacper Szkoda <kacperszkodaib@gmail.com>
This commit changes assignment of monochrome conversion
buffer from using a shared buffer between displays into using
and unique per display buffer. This is required when using multiple
monochrome displays and the display driver takes ownership of the
framebuffer
Signed-off-by: Erik Andersson <erian747@gmail.com>
Add support for direct rendering mode with monochrome
displays. This allows buffer swapping instead of copying with
display drivers that supports it
Signed-off-by: Erik Andersson <erian747@gmail.com>
When using direct rendering mode with LVGL there is
always a full size render buffer available compared to
partial rendering where only a smaller buffer is used
The idea here is to reuse lvgl:s rendering buffers as
framebuffers for display controllers that support direct
transfers from memory by using buffer swaps.
Lvgl calls flush for every redrawn area during a screen
refresh but the display driver requires a full size framebuffer
in order to allow buffer swaps. So in this case we only
write to the display when the final area is flushed and
use the full display area in display_write call
This commit provides glue logic to adapt lvgl flush calls
to display driver writes
Signed-off-by: Erik Andersson <erian747@gmail.com>
Render mode for display is set by lvgl from provided
render_mode argument when calling lv_display_set_buffers.
So there is no need to set it again afterwards with
lv_display_set_render_mode function.
To avoid confusion about which mode is used by lvgl
the lv_display_set_render_mode call is removed by
this commit.
Signed-off-by: Erik Andersson <erian747@gmail.com>
Adds new Kconfig symbols for the rendering modes supported by LVGL.
Previously only partial and full rendering mode did exist. Now that there
is also direct rendering mode convert the former into a choice symbol.
Signed-off-by: Fabian Blatz <fabianblatz@gmail.com>
Update driver to use new HAL library that supports both
Series 2 and Series 3 SoCs that share the same IP.
Split the check for transfer doneness in the block append
function into semantically equivalent parts: Check CHSTATUS
to see if the channel is active when appending a block, and
check CHDONE in the ISR.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Remove CONFIG_MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SCRATCH, deprecated in
Zephyr 4.1 in favour of CONFIG_MCUBOOT_BOOTLOADER_MODE_SWAP_USING_MOVE,
which selects the same MCUBOOT_BOOTLOADER_MODE_HAS_NO_DOWNGRADE and maps
to the same MCUBOOT_MODE_SWAP_USING_MOVE bootloader info value.
The MCUmgr img_mgmt and os_mgmt users only ever OR'd the deprecated
symbol with its replacement, so dropping the disjunct is behaviour
preserving. The sysbuild counterpart was already removed.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Assisted-by: Claude:opus-5
The path to the openthread blob changed in the latest HAL.
Update CMakeLists.txt to match the new location.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
The peap implementation in hostap allows to enforce a version, see
https://github.com/zephyrproject-rtos/hostap/blob/main/src/
eap_peer/eap_peap.c#L79.
However, the library can work fine without an enforced version.
This change allows that, when a value of -1 is filled in for eap_ver.
The wifi_shell CLI is also updated.
Signed-off-by: Sebastiaan Merckx <sebastiaan.merckx@verhaert.com>
The definition of "min" and "max" scheduler priority was
inverted in the latest HAL. Swap the definitions to pass
parameter validation in multiprotocol builds.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Set USB_HOST_CONFIG_BUFFER_PROPERTY_CACHEABLE when CONFIG_NOCACHE_MEMORY
is enabled and CONFIG_UHC_BUF_FORCE_NOCACHE is not set. This allows the
MCUX USB host stack to use cacheable buffers when nocache memory regions
are available for DMA operations.
Signed-off-by: Mark Wang <yichang.wang@nxp.com>
In order to have the Crypto partition enabled.
At the same time stop setting options that should not be set explicitly.
Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
The DMADRV HAL is deprecated, switch to DMA manager HAL for
channel allocation bookkeeping.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Adapt Series 2 HCI driver to changes in SiSDK v2026.6.0. The
functions to send and receive events have been renamed, and
the buffer memory is configured in a different way.
The radio also requires PHY configuration files to be separately
compiled, they are no longer built in to the library.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Introduce a Zephyr-specific Nema HAL implementation under
modules/lvgl/nemagfx to integrate NemaGFX with the Zephyr driver model.
The HAL provides abstraction for interrupt handling, register
access, and synchronization using Zephyr kernel APIs, replacing
platform-specific dependencies.
This enables LVGL to utilize GPU2D hardware acceleration through
NemaGFX in a Zephyr environment.
Signed-off-by: Radhika Changela <radhika.changela@siliconsignals.io>
Add baseline support for the nRF7120e SoC.
Add nRF7120 support for nrfutil recover, missing previously.
Signed-off-by: Robert Robinson <robert.robinson@nordicsemi.no>
Since nrfx-based MDK now offers option to provide header
with configuration symbols used within MDK, move all
global definitions from CMake script to header.
Signed-off-by: Michał Stasiak <michal.stasiak@nordicsemi.no>
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
