The send scheduler formatted LwM2M paths with `lwm2m_path_log_buf()` even
when debug logging was not enabled for the module, causing build issues
with CONFIG_LOG off.
Signed-off-by: Julien Vermillard <julien@clunkymachines.com>
Add test suite for verifying CAN controller power management behavior. The
test suite verifies the behavior currently implemented in the TCAN4x5x CAN
controller driver.
The test suite serves only as a baseline. It is subject to change as power
management support is implemented across a wider range of CAN
controller/transceiver drivers.
Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
Add devicetree overlay for UART1 async API support on the
nRF9151DK board, using GPIO pins P0.29 (TX) and P0.28 (RX)
with low-power sleep state configuration.
Signed-off-by: Waqar Ahmed <waqaryounasawan@outlook.com>
The TEST_SHELL config was removed in commit be0dff6844
("test: remove TEST_SHELL") a while ago.
Signed-off-by: Thomas Stranger <thomas.stranger@outlook.com>
The config options have been renamed in commit 8dc3f85622
("hwmv2: Introduce Hardware model version 2 and convert devices"),
therefore update them in the hardend file.
Signed-off-by: Thomas Stranger <thomas.stranger@outlook.com>
Adds board-specific configuration and devicetree overlay for the
ST NUCLEO-WBA65RI. This enablement allows the OpenThread coprocessor
sample to run using the UART_ASYNC_API by default on this target.
Included changes:
- boards/nucleo_wba65ri.conf: Sets UART ASYNC API.
- boards/nucleo_wba65ri.overlay: Configures DMA and UART nodes.
Signed-off-by: Michele Sardo <msmttchr@gmail.com>
Updates the OpenThread UART platform shim to support the Zephyr
Asynchronous UART API (DMA-based). This improves performance and
reduces CPU overhead when running the OpenThread stack.
Additionally, introduces new Kconfig symbols:
- CONFIG_OPENTHREAD_COPROCESSOR_UART_ASYNC
to enable UART async API mode.
- CONFIG_OPENTHREAD_COPROCESSOR_UART_RX_BUFFER_SIZE
to allow users to configure the DMA RX buffer size when
OPENTHREAD_COPROCESSOR_UART_ASYNC is enabled.
Signed-off-by: Michele Sardo <msmttchr@gmail.com>
On BL70x, pins 23-28 are output-only and must be routed through the
PSRAM IO pads. When PSRAM is not enabled, set GLB_GPIO_USE_PSRAM_IO
so these pins are usable as regular GPIOs.
Signed-off-by: William Markezana <william.markezana@gmail.com>
Use BIT(pin) instead of the raw pin number when setting or clearing
GPIO output values. Without BIT(), only the lowest pins were
affected and higher pins were never toggled.
Signed-off-by: William Markezana <william.markezana@gmail.com>
- Adds the i2c0 node in hpcore dts
- Adds the pinmux of the same
- Adds the i2c tag in board yaml for including the board for ci
tests
Signed-off-by: Muhammed Asif P <asifp3104@gmail.com>
Drop a note about prefixing device specific api naming with the full
normalized compatible for the device. Nothing in tree adopted this and
it would be unnecessarily verbose, the standard "keep the coding style
coherent" works just fine for this.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Allow the ADI MAX32 platform use `counter_reset` and `counter_set_value`
- `reset` clears the counter
- `set_value` sets it to a given value
Signed-off-by: James Roy <rruuaanng@outlook.com>
Limit iic1 to the device's max-bitrate-supported value to avoid
configuring an unsupported bus speed.
Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
This part of the regular expression may cause exponential backtracking
on strings containing many repetitions of '\n\r'.
Signed-off-by: Jan Gałda <jan.galda@nordicsemi.no>
Extracting text from a DOM node and interpreting it as HTML
can lead to a cross-site scripting vulnerability.
Signed-off-by: Jan Gałda <jan.galda@nordicsemi.no>
`last_nl` is 8 bits long, put it at the beginning of the packed struct, so
it can be read and written with one intruction, as it is now aligned.
Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>
Add support of NUCLEO_L4R5ZI in async API sample with DMA-enabled
LPUART1 devicetree overlay.
Configuration:
- DMA1 channel 5 for TX (DMAMUX slot 34)
- DMA1 channel 4 for RX (DMAMUX slot 35)
- LPUART1 on pins PG7 (TX) and PG8 (RX)
- Baud rate: 115200
Tested on hardware with loopback configuration.
Signed-off-by: Waqar Ahmed <waqaryounasawan@outlook.com>
Document zms_mount_force() in the mounting section and move this
capability from future features to existing features.
Signed-off-by: Andreas Anderberg <andreas.anderberg@u-blox.com>
Add a test that verifies zms_mount() fails on unsupported on-flash
version data while zms_mount_force() recovers by wiping and
reinitializing the partition.
Signed-off-by: Andreas Anderberg <andreas.anderberg@u-blox.com>
zms_mount_force() behaves like zms_mount() but automatically wipes and
reinitializes the partition if the initial mount attempt fails.
A corresponding Kconfig option SETTINGS_ZMS_FORCE_MOUNT is added to the
settings subsystem to enable this behavior when using ZMS as the
settings backend.
Signed-off-by: Andreas Anderberg <andreas.anderberg@u-blox.com>
Add an sample for usage of the timer/pwm mastermode configuration.
Timer is configured to generate 2 TRGO events per pwm period to the
interconnect matrix.
Signed-off-by: Matthias Plöger <matthias.ploeger@phoenixcontact.com>
Add dtc property node on RX26T dts, and ram section for
dtc_vector_table on RX26T SoC for dtc support
Signed-off-by: Quy Tran <quy.tran.pz@renesas.com>
LVGL BITS_PER_PIXEL and COLOR_DEPTH are closely linked to how the LTDC
is configured on the platform. Move all all STM32 common LVGL
configuration into the common stm32 Kconfig.defconfig.
CONFIG_LV_DPI_DEF and CONFIG_INPUT are application related.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
LVGL Kconfig already set the LV_Z_BITS_PER_PIXEL config based
on the LV_COLOR_DEPTH so avoid setting LV_Z_BITS_PER_PIXEL
for boards / shields when the LV_COLOR_DEPTH is also set.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
Fix the order of default in the Kconfig LV_Z_BITS_PER_PIXEL
in order to be able to have the value set automatically based
on the COLOR_DEPTH.
Without that since the default 32 was coming first, 32 would
always be selected.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
The LTDC pixel format and HEAP size is a matter of the application
rather than the configuration of the shield.
The LTDC has already a default RGB565 configuration hence such conf
is not more necessary, moreover sample display heap rework make the
CONFIG_HEAP_MEM_POOL_SIZE setting no more necessary.
cf "samples: display: define HEAP_MEM_POOL_ADD_SIZE_ for display buffer"
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
The RGB565 format should be suffisant as default format of LTDC
when using this shield and allows to keep the default framebuffer
memory usage low.
Application requiring RGB888 or ARGB8888 input format can later
on update the LTDC input format when really necessary.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
The RGB565 format should be suffisant as default format of LTDC
when using this shield and allows to keep the default framebuffer
memory usage low.
Application requiring RGB888 or ARGB8888 input format can later
on update the LTDC input format when really necessary.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
These samples do not seem to need the unistd.h header, but including it
limits us to C libraries which have it, which as it is a POSIX
extension is not all.
So let's not include it so we do not limit ourselves unnecessarily.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
This test does not seem to need the unistd.h header, but including it
limits us to C libraries which have it, which as it is a POSIX
extension is not all.
So let's not include it so we do not limit ourselves unnecessarily.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
Ubuntu 24.04 LTS is the current long-term support release of Ubuntu, and
what we test against in our CI, so update the documentation to reflect
that.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Update the few workflows that were testing against Ubuntu 22.04 since
current LTS is 24.04 and all other workflows (including anything using
our Docker image) are already using 24.04.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
