Feature/aia upstream rhx base #9
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update the 4.3 migration guide to include the change made on the STM32 ADC clocks. Signed-off-by: Guillaume Gautier <[email protected]>
Fix formatting errors reported by the dts linter. Signed-off-by: Guillaume Gautier <[email protected]>
Section 4.3.7.3.6 of the I3C v1.2 specification states that a value of 0 for the max ibi size indicates an unlimited payload size. Set it to the max it can be configured for. Signed-off-by: Ryan McClelland <[email protected]>
This updates the SHA for Xtensa HAL to latest. This brings in the SoC configuration for intel_adsp/ace40, and will be used with the next SDK release. Signed-off-by: Daniel Leung <[email protected]>
Replaces text to clarify a setting Signed-off-by: Jamie McCrae <[email protected]>
Fixes some errors and inconsistencies to show a fuller example of a Kconfig.soc file Signed-off-by: Jamie McCrae <[email protected]>
Addition of a helper function which takes care of dequeue from a source video device and queue into a sink video device. Signed-off-by: Alain Volmat <[email protected]>
Replace video_dequeue / video_enqueue buffer exchange code by video_transfer_buffer helper function. Signed-off-by: Alain Volmat <[email protected]>
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 <[email protected]>
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 <[email protected]>
Add rough estimate of a worth case H264 output size. The video_estimate_fmt_size would need more information such as quality, profile in order to give a better estimate for each formats so for the time being just stick to 16bpp based size, same as for JPEG. Signed-off-by: Alain Volmat <[email protected]>
This commit prepares introduction of the UVC Frame Based support by using the struct uvc_frame_descriptor as parameter of most of the UVC functions. struct uvc_frame_descriptor contains the common fields for all supported frame type and then depending on the DescriptorSubtype the pointer is casted in the correct struct definition. Signed-off-by: Alain Volmat <[email protected]>
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 <[email protected]>
Add proper check of the return value of video_enqueue / video_dequeue. Signed-off-by: Alain Volmat <[email protected]>
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 <[email protected]>
Add zephyr_h264enc and zephyr_jpegenc labels on node in order to be able to use VENC and JPEG codec from samples. Signed-off-by: Alain Volmat <[email protected]>
Add entries in sample.yaml for enabling h264enc / jpegenc uvc based test on the stm32n6570_dk/stm32n657xx/sb platform. Signed-off-by: Alain Volmat <[email protected]>
It's M33 rather than M7. Signed-off-by: Diego Herranz <[email protected]>
The Xilinx Zynq 7000 I2C controller has the following bugs: - completion indication is not given to the driver at the end of a read/receive transfer with HOLD bit set. - Invalid read transaction are generated on the bus when HW timeout condition occurs with HOLD bit set. - If the delay between address register write and control register write in cdns_i2c_mrecv function is more, the xfer size register rolls over and controller is stuck. As a result of the above, this patch disallows message transfers with a repeated start condition following a read operation. Also disables interrupts between the address register write and control register write during message reception, to prevent transfer size register rollover. Signed-off-by: Simon Maurer <[email protected]>
Relax the `Missing a blank line after declarations` checkpatch error by
loosening the requirements for a macro to be treated as one that
declared a variable.
Currently the regex matches the pattern `DECLARE` or `DEFINE`, as long
as there are between 1 and 6 trailing `_FOO` components to the macro
name (e.g. `DECLARE_MY_TYPE()`). Zephyr however contains many macros
that don't have the trailing components but still resolve to variables
(e.g. `ATOMIC_DEFINE`, `K_MUTEX_DEFINE, etc`).
By changing `{1,6}` to `{0,6}`, we remove the requirement for the
trailing `_FOO` component(s) while still allowing them. This stops
checkpatch from erroring on patterns like this:
```
struct driver_data {
uint16_t some_value;
ATOMIC_DEFINE(some_atomic, 16);
};
```
Signed-off-by: Jordan Yates <[email protected]>
The next patch will cause mps2/an385 board fail. The original code access 0x2000a10 but the interrupt statck start at 0x20002000 with size 2048 byte(end at 20001800) so the access causes stack overflow. Increase ISR stack size to resolve this issue. Signed-off-by: TaiJu Wu <[email protected]>
1. There are debug info within k_sched_unlock so we shoulld add same debug info to k_sched_lock. 2. The thread in run queue should be normal or metairq thread, we should check it is not dummy thread. Signed-off-by: TaiJu Wu <[email protected]>
Document the AD4170-4, AD4190-4, and AD4195-4 low noise, high precision 24-bit ADCs, each supporting 4 differential or 8 single-ended inputs, integrated PGA (0.5-128). All devices feature internal and external buffered references, operate from 4.75-5.25V analog and 1.7-5.25V digital supply. Signed-off-by: Kim Seer Paller <[email protected]>
Add initial support for the AD4170-4, AD4190-4, and AD4195-4 24-bit ADCs, including reference selection, programmable gain amplifier, ADC conversion modes, configurable analog inputs, filter settings, and both bipolar and unipolar operation. Supports internal and external buffered references, and operation from a 4.75-5.25V analog supply and a 1.7-5.25V digital supply. Signed-off-by: Kim Seer Paller <[email protected]>
Add build test for AD4170, AD4190, and AD4195 SPI-based ADC. Signed-off-by: Kim Seer Paller <[email protected]>
build.dir-fmt format string arguments are extended. New format args are 'west_topdir' (absolute path to the west workspace directory) and 'source_dir_workspace' (relative path of the source directory to west_topdir). Signed-off-by: Thorsten Klein <[email protected]>
Tests are added for different build.dir-fmt format string arguments. Signed-off-by: Thorsten Klein <[email protected]>
new format arguments for config option build.dir-fmt are documented accordingly. Signed-off-by: Thorsten Klein <[email protected]>
The stackprot test currently depends on compiler-generated stack frame layouts, which can vary between toolchains and optimization levels. This makes the overflow check fragile and may cause unintended faults. Add a small guard buffer in alternate_thread so the intentional overflow is always contained within the thread stack. This ensures the test behaves consistently across toolchains, architectures, and optimization settings. Signed-off-by: Mohamed Moawad <[email protected]>
Reorder TFM_BOARD entries by vendor name for improved clarity. Signed-off-by: BUDKE Gerson Fernando <[email protected]>
github-actions
bot
added
manifest
manifest-picolibc
manifest-trusted-firmware-m
manifest-edtt
manifest-mbedtls
manifest-hostap
manifest-hal_nxp
manifest-net-tools
manifest-mcuboot
manifest-hal_renesas
manifest-fatfs
manifest-hal_rpi_pico
manifest-hal_nuvoton
manifest-hal_xtensa
manifest-hal_stm32
manifest-trusted-firmware-a
manifest-hal_espressif
manifest-hal_microchip
manifest-hal_infineon
manifest-nrf_wifi
manifest-hal_bouffalolab
manifest-hal_silabs
manifest-nrf_hw_models
manifest-hal_ambiq
manifest-hal_wurthelektronik
manifest-mipi-sys-t
manifest-hal_gigadevice
manifest-percepio
DNM (manifest)
Binary Blobs Added
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.