Switch libfuse installation instructionts to guide people to install v3
of the library by default, and be explicit about this v3 being the one
that will try to be used by default.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
Support for using v3 of the FUSE library instead of v2 was added in
b86e52bd6f
As time has been passing more distros are removing v2 support, and at
this point probably all include the v3 in their package repos.
So, let's switch the default to v3.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
Using only the fence instruction to gate the management of data in cache
is insufficient to prevent unordered access after flushing in some cases.
Gate dcache instructions like icache instructions.
Signed-off-by: Camille BAUD <mail@massdriver.space>
Adds support for the Modulino Latch Relay I2C/QWIIC board.
Adds an example which turns a connected relay on/off periodically.
Signed-off-by: Tamas Jozsi <tamas.jozsi@silabs.com>
Introduces a new regulator shell sample which can be used to control
regulator devices from the shell interactively.
Signed-off-by: Tamas Jozsi <tamas.jozsi@silabs.com>
This commit adds the "mxicy,mx25u" compatible to STM32 MSPI flash sample
board overlays.
Signed-off-by: Sara Touqan <zephyr@exalt.ps>
Signed-off-by: Sarah Younis <zephyr@exalt.ps>
this commit removes mspi_stm32_xspi_config_mem() and
mspi_stm32_ospi_config_mem() from their respective
*_dev_config() implementations.
we could remove these configurations by enabling mxicy,mx25u
compatible in STM32 board overlays. This compatible activates
the flash_quirks_mxicy_mx25u entry defined in
flash_mspi_nor_quirks.h
This quirks structure implements the required flash-specific
configuration, so XSPI/OSPI driver configuration flow could be
simplified.
Signed-off-by: Sara Touqan <zephyr@exalt.ps>
Signed-off-by: Sarah Younis <zephyr@exalt.ps>
When calling bt_avrcp_ct_register_notification,
it sets ct->ct_notify[event_id].cb = cb.
In process_register_notification_rsp, it clears the callback
by setting ct->ct_notify[event_id].cb = NULL. However, when
the connection is disconnected, the callback
ct->ct_notify[event_id].cb is not set to NULL , causing
subsequent notification registrations to fail immediately with
an error because the callback pointer is still active.
Similarly, this issue also exists in the AVRCP TG.
Signed-off-by: Lu Jia <jialu@xiaomi.com>
Add a new external module page for requests. The page introduces
requests and documents how to add it via west.
Signed-off-by: Muhammad Waleed Badar <walid.badar@gmail.com>
Refactored the Stream End Point (SEP) callback mechanism to use a
unified bt_avdtp_sep_ops structure instead of individual function
pointers. This change consolidates the connected, disconnected, and
media_data_cb callbacks into a single operations structure. The stream
established callback should be called when the stream l2cap is
connected not the open cmd is finished.
Signed-off-by: Mark Wang <yichang.wang@nxp.com>
Use sl_rail_util_pa_conversions on Series 2 SoCs.
Modules still use legacy pa_conversions.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Add `pa-max-power-dbm` property to Devicetree radio node.
Set the property to the appropriate value on all Series 2 SoCs.
Add additional options for 2.4 and sub-GHz PAs.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
I2C_STM32_V2_TIMING config has dependencies hence use
configdefault when setting in within Kconfig.defconfig
files.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
In several ST boards, MEMC is currently enabled depending on DISPLAY.
While this is correct based on the default dts file, the real
dependency is LTDC which defines within the dts file its framebuffer
into a memory accessible via the MEMC hence make this dependency
explicit by indicating STM32_LTDC instead of DISPLAY.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
Add CONFIG_LORA_SX126X_NATIVE_SLEEP (default y) to allow disabling
sleep mode power management. When disabled, the radio stays in
standby for faster response times at the cost of higher idle current.
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
Two fixes for the async RX path:
1. Only invoke the user callback for valid packets.
2. Re-check rx_cb != NULL before restarting RX. The user's callback may
call lora_recv_async(dev, NULL) to stop reception.
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
Fix three issues in the spi_transfer() helper:
1. pass NULL instead of the data pointer so the SPI driver sends dummy
bytes during reads rather than the caller's buffer contents (usually
rubbish)
2. unify TX and RX buf_set count. The old logic used different counts for
TX and RX, which caused a length mismatch when data_len > 0 on reads.
3. pass NULL for the rx buf_set on write operations. The chip's MISO output
during command writes is undefined, so a full-duplex transceive is only
needed for reads.
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
Add documentation for ADC shell commands in the shell services index.
This includes the general ADC shell commands (CONFIG_ADC_SHELL) and
the ADC emulator shell commands (CONFIG_ADC_EMUL_SHELL).
The ADC emulator shell requires both CONFIG_ADC_EMUL and
CONFIG_ADC_EMUL_SHELL to be enabled.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
Add shell commands for the ADC emulator driver (zephyr,adc-emul) to
allow runtime configuration of emulated ADC values during testing and
development.
The new shell commands support:
- Setting constant raw ADC codes for a channel
- Setting constant input voltage in millivolts for a channel
Commands are dynamically populated with available ADC emulator devices
from the devicetree. This enables interactive testing of ADC-dependent
code without requiring physical hardware or signal generators.
Example usage:
adc_emul <device> raw <channel> <value>
adc_emul <device> mv <channel> <millivolts>
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
Change the ADC emulator driver to accept differential mode configuration
instead of rejecting it with -ENOTSUP. When differential mode is requested,
the driver now logs a warning that samples are provided as raw codes and
continues operation.
This allows testing of ADC configurations that use differential mode
without requiring the emulator to implement full differential conversion
logic. The raw code values can still be set via shell commands or API
calls for testing purposes.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
The `k_thread_abort` syscall may be inlined, in which case setting a
breakpoint on `k_thread_abort` can result in breakpoints at multiple
locations being set (i.e. Breakpoint 3.1, 3.2, ...).
This commit updates the test regex to handle this case.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
Adding myself as a maintainer in preparation for a
few new boards/peripherals that have been requested.
Signed-off-by: James Bennion-Pedley <james@bojit.org>
Adding:
- ceolin
- valeriosetti
- tomi-font
as maintainers for the newly created tf-psa-crypto and mbedtls-framework
repos.
Signed-off-by: Valerio Setti <vsetti@baylibre.com>
in some multi-core platform, `west flash` can not support all cores.
`west debug` is supported to test secondary core, add this to twister
such as with
`--west-flash-cmd=debug` in twister command
or with
`--west-flash-cmd: debug` in hwmap.yaml
and same with pytest
command line setting will overrid the one in hwmap
Signed-off-by: Hake Huang <hake.huang@nxp.com>
Co-authored-by: Grzegorz Chwierut <grzegorz.chwierut@nordicsemi.no>
Drivers supporting device deinitialization should not select
CONFIG_DEVICE_DEINIT_SUPPORT. Enabling deinit should be left up to the
application configuration.
Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
Make sure that we don't allow bindings which manually
specify any defaults for the #address-cells or #size-cells
properties. See DTSpec 2.3.5.
Signed-off-by: Martí Bolívar <marti.bolivar@oss.qualcomm.com>
The devicetree specification section 2.3.5 says:
The #address-cells and #size-cells properties are not inherited
from ancestors in the devicetree. They shall be explicitly
defined.
A DTSpec-compliant boot program shall supply #address-cells and
#size-cells on all nodes that have children.
If missing, a client program should assume a default value of 2
for #address-cells, and a value of 1 for #size- cells.
We are currently allowing defaults -- and notably, different defaults
from those recommended in the spec -- in the zephyr bindings for these
properties to pass without complaint.
Further, allowing the user to specify a default other than the
recommendations by the spec would be a bad design decision in my
opinion.
Handle this by erroring out explicitly when we try to set these
defaults in a binding. It's fine for people to do things like define
descriptions for these properties in a binding for some specific
compatible, but it's a footgun to allow bindings that would seem to
allow overruling the specification's explicit recommendation.
Signed-off-by: Martí Bolívar <marti.bolivar@oss.qualcomm.com>
Adding PSE84 overlay for the dmic sample. Adding a kconfig option to
select a hardware channel index other than 0.
Signed-off-by: Brett Peterson <brett.peterson@infineon.com>
Adding PSE84 overlay to the dmic_api test and adding a kconfig option to
select a hardware channel index other than 0.
Signed-off-by: Brett Peterson <brett.peterson@infineon.com>
Updating PSE84 and PSC3 conf files to set the per-channel descriptor
count. This is needed after a change to the infineon DMA driver that
removed a shared descriptor pool.
Signed-off-by: Brett Peterson <brett.peterson@infineon.com>
Adding a way to configure x-loop increments greater than 1.
Fixing an issue where DMA descriptors that were allocated from a shared
pool were never freed.
Signed-off-by: Brett Peterson <brett.peterson@infineon.com>
Add tests for the fwcfg driver for qemu_x86, qemu_cortex_a53 and
qemu_riscv64. This includes driver instancing, feature discovery,
read path as well as error handling.
Signed-off-by: Maximilian Zimmermann <gitmz@posteo.de>
This PR adds a new driver for the QEMU Firmware Configuration Device.
It implements the device for both X86 and MMIO architectures (e.g. ARM).
It also supports the DMA interface for write support.
Signed-off-by: Maximilian Zimmermann <gitmz@posteo.de>
