Skip to content
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

Bluetooth: Controller: Fix lost_payloads calculation for FT > 1 #87038

Merged

Conversation

Tronil
Copy link
Collaborator

@Tronil Tronil commented Mar 13, 2025

The lost_payloads calculation in ull_conn_iso_start() could easily end up negative for CIS with FT > 1; Add a check to avoid this

The lost_payloads calculation in ull_conn_iso_start() could easily
end up negative for CIS with FT > 1; Add a check to avoid this

Signed-off-by: Troels Nilsson <trnn@demant.com>
@cvinayak cvinayak requested a review from Thalley March 13, 2025 17:03
@Thalley
Copy link
Collaborator

Thalley commented Mar 13, 2025

Could this be related to #83584 ?

@cvinayak
Copy link
Contributor

Could this be related to #83584 ?

Can be related if the symptom of the failure is to have a MIC failure on the very first non-zero length SDU reception after CIS is established. If there are MIC failure in subsequent SDUs, then the issue can be something else.

@Thalley
Copy link
Collaborator

Thalley commented Mar 13, 2025

Can be related if the symptom of the failure is to have a MIC failure on the very first non-zero length SDU reception after CIS is established. If there are MIC failure in subsequent SDUs, then the issue can be something else.

The MIC error happens at the time of establishment. No SDUs are sent by the central yet when this occurs

Copy link
Collaborator

@erbr-ot erbr-ot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kartben kartben merged commit a87e8dc into zephyrproject-rtos:main Mar 25, 2025
28 checks passed
@Tronil Tronil deleted the fix-lost_payloads-calc-for-ft-over-1 branch March 26, 2025 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants