Add sample support for sdhc driver on Renesas ek_ra8m1 and
ek_ra8p1 board:
- samples/subsys/fs/fs_sample
Signed-off-by: Khoa Tran <khoa.tran.yj@bp.renesas.com>
driver using SDMMC card on Renesas RA boards
Add Renesas RA board support for these samples:
- samples/subsys/fs/fs_sample
Signed-off-by: Khoa Tran <khoa.tran.yj@bp.renesas.com>
On platforms where `Z_LIBC_PARTITION_EXISTS` is true - such as Cortex-M
- it is necessary to add this partition to the memory domains of
userspace extensions, otherwise they get memory faults.
Signed-off-by: Ederson de Souza <ederson.desouza@intel.com>
Use zu% format for size_t type.
Use d% format for int type.
Use u% format for uint32_t type.
Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
Signed-off-by: Jony Zhang <jony.zhang@nxp.com>
DISK_DRIVER_SDMMC is already by default y,
if it is enabled in the dt, so we shouldn't overwrite
that.
Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>
Add documentation for the instrumentation subsystem as this was missing
from the initial contribution.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
When CROSS_DIM doesn’t evenly divide the panel WIDTH/HEIGHT, the last
tile on the right/bottom edge can extend past the display bounds.
Fix by clipping the edge tiles.
Signed-off-by: Charles Dias <charlesdias.cd@outlook.com>
We have two places defining cpu_load_get() and trying to the same thing,
one is a core kernel feature supported on all architecture, the other is
part of debug, requires tracing and supported only on a subset of
architectures. Both deliver different results and accuracy.
While we figure our how to merge those into one API and with the
advanatges of both, rename the API so there is no confusion about what
is being used.
Fixes#97845
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
The stm32f3_disco board requires an external AD4114 sensor for the
ADC test to pass. Since this sensor is not available by default in
CI environments, the test fails.
Removing stm32f3 from the allow list prevents false negatives during
automated testing.
Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com>
Rename dt_node_prop_enabled filtering expression to
dt_nodelabel_prop_enabled as it takes a node label as a 1st argument.
Enhance dt_node_has_prop inline doc and param name.
Signed-off-by: Abderrahmane JARMOUNI <git@jarmouni.me>
Commit d93561da68 ("samples: zbus: benchmark: Filter SMP from
benchmark_sync test") avoided the SMP race condition for the
SUBSCRIBERS variant (benchmark_sync) by filtering out SMP configurations,
but the MSG_SUBSCRIBERS variant (benchmark_async_msg_sub) has the
identical race condition and needs the same filter.
Both variants use the same threading model:
- Producer thread: priority 5 (lower priority, runs later)
- Consumer threads: priority 3 (higher priority, runs first)
- Both use asynchronous delivery via queues (msgq vs fifo)
The race condition on SMP (detailed in d93561da68):
CPU 0 (Producer): CPU 1-3 (Consumers):
----------------- ----------------------
Publish all messages Still processing...
atomic_get(&count) atomic_add() comes later
→ Reports incomplete count!
The LISTENERS variant (benchmark_async) does NOT need filtering because
listeners are synchronous callbacks. Looking at subsys/zbus/zbus.c:130,
the listener callback executes directly within zbus_chan_pub():
case ZBUS_OBSERVER_LISTENER_TYPE: {
obs->callback(chan); /* Synchronous! */
break;
}
All atomic_add() operations complete before the producer checks the
count, so there is no race condition with LISTENERS.
Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
Since the i index is already being incremented as part of the
for loop statement, the i++ done as part of the loop body should
not be done since this lead to skip of entries of the table and
moreover might lead to invalid access outside of the table.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
There is a function, `fork()`, inside of the philosophers example that
conflicts with the POSIX `fork()` function.
Since it is customary to avoid using reserved names, adjust the sample
so that the function in question is called `philosopher_fork()`.
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
There is a macro, `fork()`, inside of the philosophers example that
conflicts with the POSIX `fork()` function.
Since it is customary to avoid using reserved names, adjust the sample
so that the macro in question is called `philosopher_fork()`.
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
There is a macro, `fork()`, inside of the philosophers example that
conflicts with the POSIX `fork()` function.
Since it is customary to avoid using reserved names, adjust the sample
so that the macro in question is called `philosopher_fork()`.
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
The instrumentation.h header is not needed to compile the
instrumentation sample and it can be misleading for folks to think they
have to include it in their code to use the subsystem, so remove it.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
io-channels in zephyr,user is required for this sample to compile, so
add that to the filter and remove the redundant ifdef in the source code.
Signed-off-by: Amneesh Singh <amneesh@ti.com>
This commit disables monolithic wifi functionality for rw612 platform as
CI environement does not use binary blobs
Signed-off-by: Cristian Bulacu <cristian.bulacu@nxp.com>
Fix prj_minimal.conf as the project configuration and not as
the extra configuration for the sample.
Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
Utilize a code spell-checking tool to scan for and correct spelling errors
in `.rst` files within the `boards`, `doc`, and `tests` directories.
Signed-off-by: Pisit Sawangvonganan <pisit@ndrsolution.com>
Utilize a code spell-checking tool to scan for and correct spelling errors
in `.conf` files within the `samples` and `tests` directories.
Signed-off-by: Pisit Sawangvonganan <pisit@ndrsolution.com>
Recent addition of UVC Video encoder added sample targets to the sample
without the proper filter to ensure twister didn't try to automatically
build the sample target.
Not all boards have the zephyr_h264enc and zephyr_h264enc in their
device tree.
Fixes#98275
Signed-off-by: David Leach <david.leach@nxp.com>
Uses the correct way to partition memory as per the linux binding,
also fixes names which were not compliant with the zephyr
devicetree guidelines
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
- in order to support different bit widths introduce a Kconfig parameter
SAMPLE_BIT_WIDTH used in the main.c - default is 16 bits
- for platforms with NXP micfil peripheral, default is 32 bits
- BYTES_PER_SAMPLE needs to correspond to BIT_WIDTH
Signed-off-by: Tomas Barak <tomas.barak@nxp.com>
- add overlays for frdm_mcxn947 and mcxn_n9xx_evk boards in order to
enable micfil for the dmic sample
Signed-off-by: Tomas Barak <tomas.barak@nxp.com>
Add entries in sample.yaml for enabling h264enc / jpegenc
uvc based test on the stm32n6570_dk/stm32n657xx/sb platform.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
Add overlay files in order to enable usage of
the encoder in the UVC sample.
This work with platform defining node label
zephyr_jpegenc
zephyr_h264enc
Mode can be selected by using -DFILE_SUFFIX="jpegenc" or
-DFILE_SUFFIX="h264enc" when building the sample while
also adding -DCONFIG_VIDEO_ENCODER_JPEG or
-DCONFIG_VIDEO_ENCODER_H264 as well in the command line.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
The frame_based descriptors differ from the frame descriptors
in that there is no dwMaxVideoFrameBufferSize field.
In order to do that, add a new uvc_frame_based_discrete_descriptor
structure to be used to fill in proper information into the
frame descriptor. In addition to that, a new format descriptor
is also added for frame based transfer.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
Allow creating a pipeline as follow
camera receiver -> encoder -> uvc
If the chosen zephyr,videoenc is available, the sample will pipe
the camera receiver to the encoder and then the UVC device instead
of directly the camera receiver to the UVC.
Current implementation has several points hardcoded for the time
being:
1. intermediate pixel format between the camera receiver and encoder
is set to NV12. This shouldn't be hardcoded and should instead be
discovered as a commonly capable format from the encoder / video dev
2. it is considered that encoder device do NOT perform any resolution
change and that encoder output resolution is directly based on the
camera receiver resolution. Thanks to this, UVC exposed formats
are thus the encoder output pixel format & camera receiver
resolutions.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
In preparation for the introduction of video encoder support
add an indirection for handling of the buffers of the UVC
source device. Currently this is only video_dev however it
can also be an encoder device when encoder is introduced
between video capture device and the UVC device.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
Add a 1 second delay before printing environment variables to give the
shell time to initialize and print its prompt. This prevents a race
condition where the shell prompt could interleave with the environment
variable output on SMP systems, causing test failures.
Without this delay, the output could appear as:
BUILD_VERSIuart:~$ ON=v4.2.0...
With the delay, the shell completes initialization first:
uart:~$
BOARD=...
BUILD_VERSION=...
ALERT=
This fixes the sample.posix.env test timeout on FVP v9a/smp where the
test harness regex failed to match the corrupted output.
Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
Now that ext_flash_app variant is available, it should be used for
mcuboot related apps on this board.
Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
Allow the display to also use if() instead of #if by leveraging the
DEVICE_DT_GET_OR_NULL() that permit display_dev to always be defined.
The compiler will const-fold all the unused variables and functions.
Signed-off-by: Josuah Demangeon <me@josuah.net>
Centralize exit of all helper functions and display a common message
that indicates clearly that the sample is not blocking on any function
but instead stopped running.
Signed-off-by: Josuah Demangeon <me@josuah.net>
