forked from zephyrproject-rtos/zephyr
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update zephyr 3 6 #13
Merged
Merged
Conversation
This file contains 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
The driver masked the return value of a pin read operation before checking the error. Thus not detecting a potential error and leading to logically dead code, which was detected by coverity in CID 340853. Anther instance XORs 1 before returning, resulting in an unexpected return value; Signed-off-by: Thomas Stranger <[email protected]>
Documentation does not describe how to run QEMU on Windows. Add description of steps needed to run QEMU and use QEMU with Twister on Windows in Beyond the Getting Started Guide. Add a reference to it in Aplication Development section. Tested using Windows 11 and QEMU installer from https://qemu.weilnetz.de/w64/ Signed-off-by: Michal Smola <[email protected]>
If the channel suspend with draining fails on stop because of reasons outside of the scope of the DMA driver (the peripheral is powered off before trying to drain for example) we must continue and disable the channel. The channel can be released by the client despite of it remained enabled. A new DMA channel request can pick the channel (as it is released) but re-configuration is going to be skipped and the use of the channel is going to fail. Then we will see the same drain timeout on channel stop again since the channel retained the configuration which resulted the first timeout. The drain timeout was made fatal by an earlier commit which fixed the WAIT_FOR return value handling. Fixes: 6226f9e ("dma: dw: fix the return value check") Signed-off-by: Peter Ujfalusi <[email protected]>
I am applying for Collaborator on the recommendation of @simonguinot. Signed-off-by: TOKITA Hiroshi <[email protected]>
Change reset pin polarity for MIPI DBI SPI controller, so that the board devicetree is responsible for setting the GPIO to active low, and the driver always sets the pin to a logic 1 to reset the display. Fixes zephyrproject-rtos#68562 Signed-off-by: Daniel DeGrasse <[email protected]>
Update MIPI DBI display migration note to match the correct display configuration settings for reset and MIPI DBI command pins after ILI9xxx display was transitioned to this API. Signed-off-by: Daniel DeGrasse <[email protected]>
LTO cannot be really used with the native simulator based targets neither today. When doing a partial link as we do for these targets the linker will complain if we are mixing LTO and non LTO built code, and fall back to only produce non-LTO output. (The link warning will cause twister to fail the test) Today not all inputs to this partial link are built with LTO enabled (offsets.c and the app library are not). Even if they were, the native targets are mostly a test and debugging facility, so optimizations like these are not beneficial in general. Let's just prevent selecting LTO for these targets. Signed-off-by: Alberto Escolar Piedras <[email protected]>
Update outdated links. This includes a new repository address for the Golioth OTA sample and an updated path for the OTA documentation. Signed-off-by: Mike Szczys <[email protected]>
Updated the instance with the device id to have it in the summary report also when using pytest harness. Signed-off-by: Grzegorz Chwierut <[email protected]>
Resume the TX Data Q when a LL_UNKNOWN_RSP is recieved instead of a LL_PHY_RSP. Update PHY Update unit test with more coverage of the TX Data Q pause state. Signed-off-by: Thomas Ebert Hansen <[email protected]>
Before a LL_FEATURE_REQ is sent, verify that the Data Length Update procedure is still supported as it could have been unmasked as the result of a previously completed Feature Exchange procedure. Add unit test to verify the case of enqueuing both a Feature Exchange procedure and Data Length Update procedure, where the Feature Exchange procedure would result in the unmasking of the Data Length Update procedure. Signed-off-by: Thomas Ebert Hansen <[email protected]>
Once an ISO channel has connected, the sequence number always starts at 0. This reset was missing in the implementation, and the _prev_seq_num from a previous connection may have been kept. Signed-off-by: Emil Gydesen <[email protected]>
Currently, the number of channels supported by the controlled is computed based on the size of the channel array. This works well only if there's no gaps (i.e: "dma-channels" property is used or "valid-channels" property is used with contiguous channels) but will break if there are any gaps. For instance, if the user wants to use channels 16 and 17 and specifies them through the "valid-channels" property, they won't be allowed to do so because dma_request_channels() will stop at channel 1. As such, to fix this, simply use the number of channels from the HAL configuration which is the maximum number of channels. Signed-off-by: Laurentiu Mihalcea <[email protected]>
After zephyrproject-rtos#63289, multi-level interrupts are now encoded using macro magic. This means that using the generic DT_INST_IRQ_BY_IDX() to fetch the INTID is no longer an option as the queried INTID will be the one specified through the node's `interrupts` properties. To fix this, switch to using DT_INST_IRQN_BY_IDX() which will return the correctly encoded INTID. Signed-off-by: Laurentiu Mihalcea <[email protected]>
The point of this commit is to allow users to request specific channels. The following code snippet shows how this may now be achieved: int requested_channel = 5; int ret = dma_request_channel(dev, &requested_channel); Signed-off-by: Laurentiu Mihalcea <[email protected]>
Changed poll to perform incoming data check with connected DTLS connections. This allows the CONFIG_NET_SOCKETS_DTLS_TIMEOUT to timeout the connections to server socket if there is no incoming data. Previously, if the remote client closed the DTLS connection without close notify, the timeout of the ongoing connection only happened when next connection was taken to the server socket. Depending on the timeouts, this could prevent the next connection from succeeding. Signed-off-by: Markus Lassila <[email protected]>
Correct documentation of the internal class API. Signed-off-by: Johann Fischer <[email protected]>
The reference document says that the formula for negative temperatures has two minus signs missing. fixes zephyrproject-rtos#68710 Signed-off-by: Tobias Röhmel <[email protected]>
Multiple CDC ACM instances can block each other because there are only buffers for a single instance. Fix this by configuring the number of buffers in the pool based on the number of CDC ACM instances. Signed-off-by: Johann Fischer <[email protected]>
Add more assert() to DMAR parsing functions. Signed-off-by: Andrei Emeltchenko <[email protected]>
Add asserts catching sub-sctructure overflow. Signed-off-by: Andrei Emeltchenko <[email protected]>
Refactor DMAR structure to allow more tests. Use fake void function for invalid size tests. Signed-off-by: Andrei Emeltchenko <[email protected]>
Add unit testing for dmar_foreach_devscope() function. Signed-off-by: Andrei Emeltchenko <[email protected]>
Add testing for acpi_dmar_ioapic_get() function. Signed-off-by: Andrei Emeltchenko <[email protected]>
Catch assert() when invalid unit size is bigger then actual table or subtable size. Signed-off-by: Andrei Emeltchenko <[email protected]>
Cleanup headers and definitions to make code more readable. Signed-off-by: Andrei Emeltchenko <[email protected]>
Add test verifying we catch assert() when subsctrucure is too big. Signed-off-by: Andrei Emeltchenko <[email protected]>
When allowing dynamic thread stack allocation the stack may come from the heap in coherent memory, trying to use cached memory is over complicated because of heap meta data and cache line sizes. Also when userspace is enabled, stacks have to be page aligned and the address of the stack is used to track kernel objects. Signed-off-by: Flavio Ceolin <[email protected]>
When running it in a multicore and with incoherent cache environment it is possible that the thread allocating dynamic stacks is switched to a different cpu. In this situation further access to that memory (like when releasing resources) will be invalid. Signed-off-by: Flavio Ceolin <[email protected]>
This commit implements simple rate-limiting for Neighbor Reachability Hints in TCP module to prevent the potentially costly process of frequent neighbor searches in the table, enhancing system performance. Signed-off-by: Łukasz Duda <[email protected]>
Add release notes for USB support. Signed-off-by: Johann Fischer <[email protected]>
Fix double "the" in the mcumgr example. Signed-off-by: Andrej Butok <[email protected]>
Security release notes for 3.6 Signed-off-by: Flavio Ceolin <[email protected]>
Disclose information about cve-2023-6881. Signed-off-by: Flavio Ceolin <[email protected]>
Fixes commit 25173f7 ("pm: device_runtime: Extend with synchronous runtime PM") Fixes compilation with gcc 4.2-based toolchain used by SOF for TGL generation products. As seen in the error message below, that gcc version requires braces for initialization of anonymous unions: ``` zephyr/soc/xtensa/intel_adsp/common/mem_window.c:62: error: unknown field ‘pm_base’ specified in initializer warning: missing braces around initializer warning: (near initialization for ‘__device_dts_ord_66.<anonymous>’) ``` This is a well-known and recurring issue, see past example(s) in zephyrproject-rtos#68118 As the Zephyr build is deterministic, I could easily verify that this commit makes zero .obj difference (when using the Zephyr SDK). Signed-off-by: Marc Herbert <[email protected]>
Remove the Recommended Changes section from the migration guide so that it only contains required changes. This aligns with the decision made in the Architechture WG on 2023-10-24. Signed-off-by: Henrik Brix Andersen <[email protected]>
This adds a high-level summary of the most notable highlights of Zephyr 3.6. Signed-off-by: Benjamin Cabé <[email protected]>
ZBus release notes for Zephyr 3.6. Signed-off-by: Rodrigo Peixoto <[email protected]>
The zbus related migrations. Signed-off-by: Rodrigo Peixoto <[email protected]>
Group related entries under subheadings and add a local table of contents to improve readability. Signed-off-by: Henrik Brix Andersen <[email protected]>
Divide the "Device Drivers and Devicetree" section into subsections for the various driver classes. Signed-off-by: Henrik Brix Andersen <[email protected]>
Fix use of backticks. Signed-off-by: Henrik Brix Andersen <[email protected]>
Add ARC release notes for 3.6 Zephyr release Signed-off-by: Nikolay Agishev <[email protected]>
Fixes grammar, punctuation, and spelling errors in the v3.6.0 release notes. Signed-off-by: Maureen Helm <[email protected]> Signed-off-by: Benjamin Cabé <[email protected]>
The first item in a list or sublist must have a blank line before it. Signed-off-by: Maureen Helm <[email protected]>
Removes empty sections from the v3.6.0 release notes. Signed-off-by: Maureen Helm <[email protected]>
Update the list of 3rd party code licensed under the GPL. Signed-off-by: Henrik Brix Andersen <[email protected]>
Adds v3.6.0 to the list of supported releases. The EOL date corresponds to the expected release date for v4.0.0. Signed-off-by: Maureen Helm <[email protected]>
Only the two most recent mainline releases are supported. Signed-off-by: Maureen Helm <[email protected]>
Removes working draft status from the v3.6.0 release notes and migration guide. Signed-off-by: Maureen Helm <[email protected]>
Sets the version to v3.6.0. Signed-off-by: Maureen Helm <[email protected]>
Zephyr 3.6.0
gordon-mckillop-molex
approved these changes
Jul 24, 2024
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.