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: Add margin to ISOALs time offset #80126

Merged

Conversation

Tronil
Copy link
Contributor

@Tronil Tronil commented Oct 21, 2024

To ensure payloads are delivered in time for the first subevent in framed BIS, ISOAL now enforces a (configurable) margin of the calculated time offset

Without this margin, it has been observed that a broadcaster can end up consistently missing the first subevent in every third event in a 7.5 ms ISO with a 10 ms SDU interval

The margin is a conservative 2 ms by default, but can likely be set a lot lower for most implementations and HWs

To ensure payloads are delivered in time for the first subevent
in framed BIS, ISOAL now enforces a (configurable) margin of
the calculated time offset

Without this margin, it has been observed that a broadcaster
can end up consistently missing the first subevent in every third
event in a 7.5 ms ISO with a 10 ms SDU interval

The margin is a conservative 2 ms by default, but can likely be
set a lot lower for most implementations and HWs

Signed-off-by: Troels Nilsson <[email protected]>
Copy link
Contributor

@cvinayak cvinayak left a comment

Choose a reason for hiding this comment

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

Not an expert at ISOAL, but no objection to the use of margin.

@cvinayak cvinayak added this to the v4.0.0 milestone Oct 22, 2024
@mmahadevan108
Copy link
Collaborator

@Tronil , we are only merging PR that fix bugs. If this is needed for the 4.0 release then kindly add a Zephyr Issue describing the problem and link it to this PR.

@Tronil
Copy link
Contributor Author

Tronil commented Nov 7, 2024

@Tronil , we are only merging PR that fix bugs. If this is needed for the 4.0 release then kindly add a Zephyr Issue describing the problem and link it to this PR.

I'm not in a rush to get this in - after 4.0 is fine

@dkalowsk dkalowsk modified the milestones: v4.0.0, v4.1.0 Nov 7, 2024
@nashif nashif merged commit fa3bfa5 into zephyrproject-rtos:main Nov 16, 2024
31 checks passed
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.

7 participants