Changes from Balint for the review#4
Changes from Balint for the review#4Ziegler András (AndrasZiegler) wants to merge 1 commit intoSiliconLabsSoftware:doccurator/25q4p3from
Conversation
| # Bluetooth Link Layer Scheduling | ||
|
|
||
| It is possible to choose between three different scheduling algorithms depending from the different use cases. | ||
| Link Layer scheduling defines how Bluetooth radio tasks share airtime on |
There was a problem hiding this comment.
suggest removing \ at the end of lines in this file and allow paragraphs to more naturally flow so that DSC builds cleanly
| receptions | ||
| - **Multiple PAwR trains**, each considered a separate task | ||
|
|
||
| Tasks have intervals, required runtime, and anchor points. The scheduler |
There was a problem hiding this comment.
suggested revision:
Tasks are defined by an interval, required runtime, and anchor point. The scheduler allocates radio time among tasks while minimizing overlaps.
|
|
||
| - Anchor placement affects **throughput**, **latency**, and | ||
| coexistence between tasks. | ||
| - Efficient anchor distribution ensures radio time is used without |
There was a problem hiding this comment.
Suggested revision:
Efficient anchor distribution enables effective use of radio time while minimizing conflicts.
| It ensures tasks share the radio and resolves conflicts only when | ||
| overlaps occur. | ||
|
|
||
| Best for: - Advertising / **Peripheral low‑throughput** applications |
There was a problem hiding this comment.
Put the first bullet on its own line
| **Anchor selection is done in an even manner** is selected. | ||
|
|
||
| Even anchor selection algorithm is best for single central multi peripheral use case where all connections have the same intervals. It tries to give connections the most airtime without interfering with other link layer tasks. | ||
| Best for: - Local device acting as **Central** connected to **multiple |
There was a problem hiding this comment.
start first bullet on own line throughout section
|
|
||
| - `Bluetooth Low Energy Controller` component has some configuration parameters related to Link Layer Scheduling under `Bluetooth Controller Configuration`. | ||
| Choose **Even Anchor Selection** when: - Central device with multiple | ||
| Peripherals |
There was a problem hiding this comment.
lower case peripherals and append to previous line
| coexistence between tasks. | ||
| - Efficient anchor distribution ensures radio time is used without | ||
| unnecessary conflicts. | ||
| - Misaligned anchors may reduce available airtime or increase |
There was a problem hiding this comment.
Suggested revision:
Misaligned anchors may reduce available airtime or increase the likelihood of collisions.
|
|
||
| The Bluetooth Link Layer supports three selectable scheduling | ||
| algorithms.\ | ||
| Developers may choose the most suitable one based on device role, |
There was a problem hiding this comment.
suggested revision:
Developers can select the most suitable option based on device role, resource needs, and traffic requirements.
| Hints the scheduler to reserve a minimum runtime for each connection. | ||
|
|
||
| Example:\ | ||
| Transmitting + receiving 251‑byte packets on 1M PHY requires \~4.3 ms. |
There was a problem hiding this comment.
Suggested revision:
Transmitting and receiving 251‑byte packets on 1M PHY requires ~4.3 ms.
|
|
||
| ### Bluetooth Controller Connection Event Extension | ||
|
|
||
| Allows connection events to extend beyond their scheduled window if they |
There was a problem hiding this comment.
Suggested revision:
Allows connection events to extend beyond their scheduled window if data remains to be exchanged and the maximum connection event length has not been exceeded.
3 participants
Description
Related Issue
Closes #<issue_number>
Changes Made
Checklist
Screenshots (if applicable)
Additional Notes