SAMPLES: BL : Bap_broadcast_source & sink: Added BIS_Number to log

[fjepse22]

SAMPLES: BL : Bap_broadcast_source & sink: Added BIS_Number to log

When people are new to Zephyr and run babblesim to learn how packets are received. Currently the different streams are identified by a pointer address to local memory for the device and not unique identification of the stream itself. I hope adding the BIS_Number to the log would help.

Practical changes

For the BAP_Broadcast_Sink
Changed log_stream_rx() so BIS_Number for the ISO stream is extracted and written to the out log.

For BAP_Broadcast_Source

send_data() now writes the BIS_Number for the stream

Note the function bt_iso_chan_get_info() is called every time when there is written to log for both samples, so there is function call overhead. A sollution whould be to save the information from bt_iso_chan_get_info() for each stream.

Signed-off-by: Frederik Bredtoft Boel Jepsen fjepse22@student.aau.dk

[github-actions]

Hello @fjepse22, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

[fjepse22]

I added changes to the code I made so it hopefully complies with the written code guidelines now.

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud