cherry-pick Bluetooth Mesh commits #2639
Merged
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
Contributor
|
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
This fixes an issue where a subsequent Config Model Subscription Add message with the same virtual address UUID would result in a Config Model Subscription Status message with the Address field incorrectly set to 0. Signed-off-by: Pavel Vasilyev <[email protected]> (cherry picked from commit d3997c6)
…fset The offset value in the PSA ITS non-volatile space is dedicated to OpenThread key reference IDs. This offset must not overwrite any other ranges already in use within the PSA ITS non-volatile space. Signed-off-by: Arkadiusz Balys <[email protected]> (cherry picked from commit ba9f627)
theob-pro
force-pushed
the
bring-bt-mesh-changes
branch
from
000d0f2 to
2b40161
Compare
theob-pro
force-pushed
the
bring-bt-mesh-changes
branch
from
2b40161 to
3b5b02f
Compare
This reverts commit f1f6bc0. Signed-off-by: Théo Battrel <[email protected]>
The BLE acronym is not an official description of Bluetooth LE, and the Bluetooth SIG only ever refers to it as Bluetooth Low Energy or Bluetooth LE, so Zephyr should as well. This commit does not change any board or vendor specific documentation, and the term BLE may still be used in those. It will be up to the vendors to update it if they want, since many of them are using the term BLE in their products. Signed-off-by: Emil Gydesen <[email protected]> (cherry picked from commit 571f26c)
Update Kconfig options for qualification: - Remove experimental on qualified feature. - Add experimental on unqualified feature. - BT_L2CAP_ECRED is not marked as experimental upstream and we qualify it downstream. Signed-off-by: Joakim Andersson <[email protected]> Signed-off-by: Trond Einar Snekvik <[email protected]> Signed-off-by: Martí Bolívar <[email protected]> Signed-off-by: Robert Lubos <[email protected]> Signed-off-by: Dominik Ermel <[email protected]> Signed-off-by: Ingar Kulbrandstad <[email protected]> Signed-off-by: Torsten Rasmussen <[email protected]> Signed-off-by: Herman Berget <[email protected]> Signed-off-by: Tomasz Moń <[email protected]> Signed-off-by: Théo Battrel <[email protected]> (cherry picked from commit e92e87d)
…PSA key IDs We need to make sure that within Zephyr different users of the PSA APIs don't interfere with each other because of using the same numerical IDs for persistent assets. This takes care of the PSA key IDs when using persistent keys through the PSA Crypto API. See the comments in `<zephyr/psa/key_ids.h>` for more information. This removes the recently-introduced Kconfig options that allowed changing the base IDs subsystems were using for their persistent keys. Signed-off-by: Tomi Fontanilles <[email protected]> (cherry picked from commit 0c368e8)
…tions Commit removes weak attribute and renames some functions in crypto_psa.c since there is no centralized distribution of the PSA key ID in bsim tests and no necessity to reimplement native mesh approach. Signed-off-by: Aleksandr Khromykh <[email protected]> (cherry picked from commit acc752f)
Commit removes api prefix for static functions in crypto psa. Signed-off-by: Aleksandr Khromykh <[email protected]> (cherry picked from commit e075e08)
Commit removes centralized PSA key ID distribution in mesh bsim tests since secure storage is instantiated on every simulated device. Signed-off-by: Aleksandr Khromykh <[email protected]> (cherry picked from commit 6a9802e)
theob-pro
force-pushed
the
bring-bt-mesh-changes
branch
from
3b5b02f to
e553315
Compare
nordicjm
approved these changes
Mar 19, 2025
PavelVPV
approved these changes
Mar 19, 2025
tomi-font
approved these changes
Mar 19, 2025
alxelax
approved these changes
Mar 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
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.
Cherry-pick Bluetooth Mesh commits.