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
[pull] main from zephyrproject-rtos:main #583
Open
pull
wants to merge
471
commits into
madmachineio:main
Choose a base branch
from
zephyrproject-rtos:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Change the type of num_tx/num_rx to avoid overflow. Fixes #80599 Signed-off-by: Zheng Wu <[email protected]>
Led blinking period was made configurable and time unit changed from sec to msec recently in the source code of the sample. Console harness regex was not changed accordingly in sample.yaml. Device testing fails when run with twister. Change the regex to accept any period and change the units to msec. Signed-off-by: Michal Smola <[email protected]>
This reverts commit 2068976. We must keep the frame completion interrupt disabled until we send a new frame to the eLCDIF, as the frame completion interrupt fires at each vertical blank interval. If we keep it enabled, then the semaphore we use to indicate the frame has been loaded by the eLCDIF will be posted to when we do not have a frame queued, and calls to `display_write` will return before the eLCDIF has actually loaded the new framebuffer. Fixes #80590 Signed-off-by: Daniel DeGrasse <[email protected]>
The 'west build' command does not know about conditional flags (in the format 'type:value:CONFIG_FOO=bar') in the 'extra_configs' argument of Twister testcase.yaml files, and currently converts them to malformed arguments that are silently ignored by cmake. This change adds a check to 'west build' to clearly warn the user if the 'extra_configs' list contains conditional flags and provide a hint on how to add them to the CMake command line. Signed-off-by: Luca Burelli <[email protected]>
A recent commit changed all references to the global 'west.log' instance (now deprecated) to the new WestCommand logging API, but another PR merged in the same period added an extra instance that is now causing CI to fail. Convert this last reference to the new API. Signed-off-by: Luca Burelli <[email protected]>
Add missing return before a `false`;. Signed-off-by: Emil Gydesen <[email protected]>
Remove an old __GNUC__ ifdef Signed-off-by: Robin Kastberg <[email protected]>
Gdb is typically able to reconstruct the first two frames of the failing stack using the "pc" and "lr" registers. After that, (if the frame pointer is omitted) it appears to need the stack pointer (sp register) to point to the top of the stack before a fatal error occurred. The ARM Cortex-M processors push registers r0-r3, r12, LR, {possibly FPU registers}, PC, SPSR onto the stack before entering the exception handler. We adjust the stack pointer back to the point before these registers were pushed for preservation in the dump. During k_oops/k_panic, the sp wasn't stored in the core dump at all. Apply similar logic to store it when failures occur in that path. Signed-off-by: Mark Holden <[email protected]>
The FPU is already disabled by the z_arm_svc function when the first thread starts. Therefore, disabling the FPU at boot is unnecessary for lazy FPU; instead, it must be enabled to handle floating-point instructions before the lazy FPU works. Signed-off-by: Ha Duong Quang <[email protected]>
ramfunc region is copied into RAM from FLASH region during XIP init. We copy from the loadaddr of the region, and were previously loading to the symbol __ramfunc_start. This is incorrect when using an MPU with alignment requirements, as the __ramfunc_start symbol may have padding placed before it in the region. The __ramfunc_start symbol still needs to be aligned in order to be used by the MPU though, so define a new symbol __ramfunc_region_start, and use that symbol when copying the __ramfunc region from FLASH to RAM. Fixes #75296 Signed-off-by: Daniel DeGrasse <[email protected]>
Move the link to old release notes and migration guides to the bottom of the document Signed-off-by: Benjamin Cabé <[email protected]>
This introduces the release notes and migration guide for 4.1.0 earlier than we typically do, so that people have a placeholder to start adding content as they line up pull requests for 4.1. The two documents are currently orphan and not visible from the main documentation as this would confuse users of 4.0. Signed-off-by: Benjamin Cabé <[email protected]>
Update of release notes in areas related to Storage and Flash. Additionally two known Stream Flash issues have been added to Know Issue section. Signed-off-by: Dominik Ermel <[email protected]>
This is needed to ensure Wi-Fi can always be used. Signed-off-by: Chaitanya Tata <[email protected]>
Add CAN related release notes for Zephyr v4.0.0. Signed-off-by: Henrik Brix Andersen <[email protected]>
Add EEPROM related release notes for Zephyr v4.0.0. Signed-off-by: Henrik Brix Andersen <[email protected]>
The authoritative source of these values is BlueZ: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/lib/hci.h#n38 Update our values with the above. The IPM definiton doesn't exist in BlueZ, but should be added there to make sure we don't get out of sync again. Signed-off-by: Johan Hedberg <[email protected]>
This bus type was originally created for what's today the ipc.c HCI driver. Since this type hasn't yet been synced with BlueZ, rename it for consistency, however leave the old define to not break backwards compatibility with existing DT bindings (there are several more that use "ipm" than ipc.c). Signed-off-by: Johan Hedberg <[email protected]>
If a device disconnects while we are in a procedure then get_next_active_instance would return a service instance pointer with the `conn` set to NULL. The issue was caused by the set_info being potentially memset when the device that disconnected was the one that held the set_info pointer. The solution is to not use a pointer, but rather a copy of the set_info, so that the active.set_info value is still valid after a disconnect. Since the set_info is not longer a pointer to a specific set_info from one of the members, the logs have been updated as well, as the pointer of the active.set_info is useless for debugging. Signed-off-by: Emil Gydesen <[email protected]>
fixes: #80721 Updated mpu region address to secure address. Signed-off-by: Xiaoli Ji <[email protected]>
- Fix typos for alarm field identification - Fix a bug where an alarm interrupt starts update interrupts - Rework interrupt code to reduce code size and complexity Signed-off-by: Daniel Kampert <[email protected]>
This unit test was added specifically to cover a regression reported by the CI while working on [1]. Further work on related issues [2] showed that: - [1] and [2] are dead end: we need to first rethink how bindings (and especially child-bindings) are initialized - the inclusion mechanism supported by Zephyr deserves more systematic testing in edtlib if we want to work with confidence The approach we choose is to: - revert all changes made in [1] - from there, systematically add unit tests as we address the issues we identified (or the additional features we need) one after the other [1] edtlib: fix last modified semantic in included property specs [2] edtlib: Preserve paths of properties from included child bindings See also: #65221, #78095 This reverts commit 33bb3b6. Signed-off-by: Christophe Dufaza <[email protected]>
This unit test was added to cover the change introduced by [1]. Further work on related issues [2] showed that the chosen approach is dead end. We're reverting all changes made in [1]. [1] edtlib: fix last modified semantic in included property specs [2] edtlib: Preserve paths of properties from included child bindings See also: #65221, #78095 This reverts commit 70eaa61. Signed-off-by: Christophe Dufaza <[email protected]>
Use-case "B includes I includes X": - X is a base binding file, specifying common properties - I is an intermediary binding file, which includes X without modification nor filter - B includes I, filtering the properties it chooses to inherit with an allowlist or a blocklist Check that the properties inherited from X via I are actually filtered as B intends to, up to the grandchild-binding level. Signed-off-by: Christophe Dufaza <[email protected]>
[1] was introduced to get more valuable answers from the PropertySpec.path API, which is supposed to tell in which file the property's specification was "last modfied". Further work on related issues [2] showed that the approach chosen in [1] is dead end: we need to first rethink how bindings (and especially child-bindings) are initialized. [1] edtlib: fix last modified semantic in included property specs [2] edtlib: Preserve paths of properties from included child bindings See also: #65221, #78095 This reverts commit b3b5ad8. Signed-off-by: Christophe Dufaza <[email protected]>
add missing switched_out trace point. Partially fixes #76057 Signed-off-by: Anas Nashif <[email protected]>
GAP PAST (and BAP) tests were also enabled since controller support is under review. This also adds bqw file which is exported draft project from Qualification Workspace. Signed-off-by: Szymon Janc <[email protected]>
This completes the existing "Documentation" section of the release notes for 4.0 by documenting the various changes/improvements implemented during the last development cycle. Signed-off-by: Benjamin Cabé <[email protected]>
On nRF54H and nRF92, booting certain cores requires programming a UICR, which is normally generated using nrf-regtool. This should be considered an optional dependency, because we do not wish to force non-Nordic users to install it just to work with Zephyr, or just for build-only tests. When nrf-regtool is not installed, a CMake warning will be displayed, but people ignore warnings all the time. As the last line of defense, check for missing UICR in the nrfutil flash runner, to prevent our users from unintentionally programming unbootable firmware. Show a fatal error specifically if CONFIG_NRF_REGTOOL_GENERATE_UICR=y, yet no UICR exists. Signed-off-by: Grzegorz Swiderski <[email protected]>
mdio_enet_nxp driver accesses the registers of its parent node Ethernet MAC This commit enables this node in mimxrt1062_fmurt6 board's device tree. This also fixes Issue #80881 Signed-off-by: Sumit Batra <[email protected]>
Add bjarki-andreasen as second maintainer for power management. Signed-off-by: Flavio Ceolin <[email protected]>
-Update formatting and contents of index.rst for cy8ckit_062s4 -Update formatting and contents of index.rst for cy8ckit_064s0s2_4343w -Update formatting and contents of index.rst for cy8cproto_062_4343w -Update formatting and contents of index.rst for cy8cproto_063_ble -Update formatting and contents of index.rst for xmc45_relax_kit -Update formatting and contents of index.rst for xmc47_relax_kit -Change all instances of "PSoC" to "PSOC" for infineon platforms Signed-off-by: McAtee Maxwell <[email protected]>
fix the path where the user has to be in order to execute make html-fast Signed-off-by: Jilay Pandya <[email protected]>
Currently, Twister Statuses are only useful for the initiated, save for the very basics. This is in opposition to the fact that they are the main thing end users take into account when checking their Twister run reports. In order to make Statuses more useful for the end user, a new documentation page has been created, elucidating the full meaning of all Statuses. Signed-off-by: Lukasz Mrugala <[email protected]>
Add entry in "Major enhancements with this release include:" for stepper device driver subsystem. Signed-off-by: Jilay Pandya <[email protected]>
Remove unwanted reference link to the section (Usage) in ARM Coresight Trace Deformatter that shows up in the main Debugging documentation page, by lowering the level of (Usage) heading from ##### to ***** The commit also has a typo fix. Signed-off-by: Ahmed Adel <[email protected]>
Let's fix the sample used in the example. The peripheral_hr and central_hr are meant to be run with each other. Let's also use the :zephyr:code-sample: directive to refer to the samples so we get a link. Signed-off-by: Alberto Escolar Piedras <[email protected]>
The #64939 introduced a few convenience function like rtc_utils_validate_rtc_time. However the PR did not replace all occurrences which result on a build error. This add the missing header include to remove a building warning and replace the old function by the new one. Fixes #81454 Signed-off-by: Gerson Fernando Budke <[email protected]>
Adding NXP's contributions to v4.0 Signed-off-by: Yves Vandervennet <[email protected]>
Previously, the anchor for `_POSIX_THREAD_SAFE_FUNCTIONS` was `posix_thread_safe_functions` but it should have been `posix_option_thread_safe_functions`. Signed-off-by: Chris Friedt <[email protected]>
Add POSIX API release notes for new features and enhancements since v3.7.0 . Signed-off-by: Chris Friedt <[email protected]>
This adds a few more entries to hopefully complete the list of 4.0 highlights. Signed-off-by: Benjamin Cabé <[email protected]>
Spell Devicetree with a capital D Signed-off-by: Benjamin Cabé <[email protected]>
Drop sections with no updates Signed-off-by: Benjamin Cabé <[email protected]>
Drop sections with no updates Signed-off-by: Benjamin Cabé <[email protected]>
Fix minor typos Signed-off-by: Benjamin Cabé <[email protected]>
Drop sections with no updates Signed-off-by: Benjamin Cabé <[email protected]>
fix typo in compatible name Signed-off-by: Benjamin Cabé <[email protected]>
The current name of the compatible is zephyr,gpio-steppers Signed-off-by: Benjamin Cabé <[email protected]>
some entries were not properly put under either Removed or Deprecated section. This commit fixes that. Signed-off-by: Benjamin Cabé <[email protected]>
Disclose information about published CVE Signed-off-by: Flavio Ceolin <[email protected]>
Add CVE-2024-11263 to release notes. Signed-off-by: Flavio Ceolin <[email protected]>
Add notes for Nordic HAL and other nRF related stuff plus one more ADC entry. Signed-off-by: Andrzej Głąbek <[email protected]>
1. Move deprecated items to the deprecated section. 2. Fixed a portion of a sentence that was deleted. 3. Miscellaneous cleanup. Signed-off-by: Mahesh Mahadevan <[email protected]>
add #80875 to known issues in release notes 4.0.0. Signed-off-by: Jilay Pandya <[email protected]>
This incorrectly had references to timers and watchdog related items. Signed-off-by: Mahesh Mahadevan <[email protected]>
Add v4.0.0 to the list of supported releases. Signed-off-by: Mahesh Mahadevan <[email protected]>
Remove working draft status from the 4.0.0 release notes and migration guide. Signed-off-by: Mahesh Mahadevan <[email protected]>
Set the version to v4.0.0 Signed-off-by: Mahesh Mahadevan <[email protected]>
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.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )