Skip to content

Conversation

@kruithofa
Copy link

Define the API for the distribute broadcast code CAP procedure

Copy link
Contributor

@Thalley Thalley left a comment

Choose a reason for hiding this comment

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

A few minor things, otherwise LGTM

Define the API for the distribute broadcast code CAP procedure

Signed-off-by: Andries Kruithof <[email protected]>
@kruithofa kruithofa force-pushed the CAP_distribute_broadcastcode_API branch from 28fefde to 7ab1fe0 Compare November 5, 2024 10:43
Comment on lines +1003 to +1013
/**
* @brief 16-octet broadcast code.
*
* If the value is a string or a the value is less than 16 octets,
* the remaining octets shall be 0.
*
* Example:
* The string "Broadcast Code" shall be
* [42 72 6F 61 64 63 61 73 74 20 43 6F 64 65 00 00]
*/
uint8_t broadcast_code[BT_ISO_BROADCAST_CODE_SIZE];
Copy link
Contributor

Choose a reason for hiding this comment

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

Out of scope of this PR, but perhaps we should consider defining a type for the broadcast code (similar to the UUID type in #77884), so that we don't have to write the explanation of how a broadcast code should be formatted all the places it is used, and can just add that to the type instead

Copy link
Author

Choose a reason for hiding this comment

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

Good idea, since this piece of code is in 3 files: iso.h, bap.h, and cap.h and the description is (more or less) copied to all places

@Thalley Thalley added this to the v4.1.0 milestone Nov 5, 2024
@nashif nashif merged commit f1f7868 into zephyrproject-rtos:main Nov 16, 2024
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants