-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Bluetooth: Controller: Fix device address in Periodic Adv Sync #84908
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
Merged
kartben
merged 1 commit into
zephyrproject-rtos:main
from
cvinayak:github_sync_accept_list_addr_match_fix
Feb 12, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless there are any specific plans to qualify the Zephyr controller again by anyone, I think we can just remove the old implementation right? The existing qualification is for a much older version of Zephyr, and cannot be used with this version anyhow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not have information about users of the Zephyr Controller doing/planning qualified end product listing of their downstream fork applications.
Qualified design listing applies to a design and as long as the design remains same for the said finite feature set (ICS), newer versions of the implementation tested using the same test plan are listed under the same listing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get your point, but I still feel like this TODO is out of place. We are modifying existing features in both the host and controller all the time, and using a design listing for Zephyr 2.3 with Zephyr 4.0 would, even without removing this specific old implementation, likely not go well. The design listing is specifically for 2.2 and 2.3, so I don't think we need to care about that for 4.1 and future releases.
Then that's up to them. We can deprecate the old implementation by following the deprecation process in Zephyr, and then it will be up to downstream forks to determine whether they want to follow this, fork, or revert the removal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From https://docs.nordicsemi.com/bundle/comp_matrix_nrf52833/page/COMP/nrf52833/nrf52833_ble_qdid_qual_matrix.html
"The Zephyr™ Controller subsystem was qualified with QDID 150092 for nRF52833 and nRF Connect SDK 1.3.2 for core specification 5.1. Other qualifications for the Zephyr Controller subsystem are not planned."
This is a revision in the Zephyr v3.x release (v3.2.99) leading to the v3.7.0 LTS. We do not deprecate a design and go back to experimental as default, but deprecate a design when there is equivalent qualified design as default replacing it.
Example, #49573
@Tronil Do we know a newer design listing with the chain implementation, and shall we switch the default design upstream?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know of one (but I really only know what we have qualified here downstream). I can say that we regularly run EBQ on our downstream version that uses the new design and haven't had any failures.
In my opinion we can switch the default - I don't know what the usual procedure is wrt. qualifications and deprecations though, so I'll refrain from having an opinion on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sufficient to create this #85209 and #85210.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jakkra FYI.