-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Bluetooth: Controller: Fix stuck forced continuation under throughput #92819
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
Open
cvinayak
wants to merge
4
commits into
zephyrproject-rtos:main
Choose a base branch
from
cvinayak:github_stuck_forced_continue_fix
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
Bluetooth: Controller: Fix stuck forced continuation under throughput #92819
cvinayak
wants to merge
4
commits into
zephyrproject-rtos:main
from
cvinayak:github_stuck_forced_continue_fix
+75
−22
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
Thalley
previously approved these changes
Jul 8, 2025
Fix stuck forced continuation of connection event under high throughput scenario. At near supervision timeout the force flag is set, but in the next connection event if full connection interval is used for data transmission and a subsequent request to abort happens it was not honoured causing the tx-rx chain to keep continuing until supervision timeout. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
75d73f0
to
773222e
Compare
Thalley
previously approved these changes
Jul 10, 2025
Fix missing radio status reset on early abort of central and peripheral prepare. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
Disable connection event continuation on overlap with same connection's next event. This implementation has bugs and needs to be fixed in subsequent commits. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
Introduce prepare being deferred due to previous events desire to continue. In such case the deferred prepare param will have the defer flag set. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
|
Thalley
approved these changes
Jul 17, 2025
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.
Fix stuck forced continuation of connection event under high throughput scenario. At near supervision timeout the force flag is set, but in the next connection event if full connection interval is used for data transmission and a subsequent request to abort happens it was not honoured causing the tx-rx chain to keep continuing until supervision timeout.