-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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: BAP: Unicast client Split start and connect #73032
Conversation
454ded8
to
214e0c1
Compare
6914177
to
4bb24a8
Compare
@@ -32,6 +32,7 @@ Commands | |||
config : <direction: sink, source> <index> [loc <loc_bits>] | |||
[preset <preset_name>] | |||
stream_qos : interval [framing] [latency] [pd] [sdu] [phy] [rtn] | |||
stream_connect : Connect the CIS of the stream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it would be good to show this call in a small example (with complete flow)
4bb24a8
to
1c26a48
Compare
1c26a48
to
c665f73
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks ok, but I would like to just try it out on a device
@@ -961,7 +1397,8 @@ static bool valid_unicast_audio_update_param(const struct bt_cap_unicast_audio_u | |||
} | |||
|
|||
if (!can_update_metadata(bap_stream)) { | |||
LOG_DBG("param->stream_params[%zu].stream is not in right state to be " | |||
LOG_DBG("param->stream_params[%zu].stream is not in right state to " | |||
"be " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
extra line needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope - Some weird clang-format stuff I guess :D
uart:~$ bap qos | ||
uart:~$ bap enable | ||
uart:~$ bap connect | ||
uart:~$ bap start |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your comment is for the Connect and establish a source stream
when you are doing it on a sink stream. See the above steps for sink streams
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes... I see that now (was following the steps in the previous push that had config sink... all good... and approved :D
c665f73
to
c604726
Compare
c604726
to
7f3dd4f
Compare
Rebased to solve merge conflicts |
7f3dd4f
to
8c570f5
Compare
uart:~$ bap qos | ||
uart:~$ bap enable | ||
uart:~$ bap connect | ||
uart:~$ bap start |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes... I see that now (was following the steps in the previous push that had config sink... all good... and approved :D
Removes the CIS connection establishment from bt_bap_stream_start and move the behavior to a new funciton bt_bap_stream_connect. This has 2 advantages: 1) The behavior of bt_bap_stream_start is much more clear and more aligned with the spec's behavior for the receiver start ready opcode. 2) It is possible to connect streams in both the enabling and the QoS configured state with bt_bap_stream_connect as per the spec. This allows us to pass additional PTS test cases. To implement this new behavior, samples and tests have been updated. The CAP Initiator implementation has also been updated to accomodate for the change in BAP, but the CAP initiator implementation should work the same for application, except that it's now possible to do unicast start on ASEs in any order (zephyrproject-rtos#72138). Signed-off-by: Emil Gydesen <[email protected]>
8c570f5
to
b37bcf8
Compare
Rebased to solve merge conflicts |
Removes the CIS connection establishment from bt_bap_stream_start and move the behavior to a new funciton bt_bap_stream_connect.
This has 2 advantages:
To implement this new behavior, samples and tests have been updated. The CAP Initiator implementation has also been updated, and slightly refactored, to accomodate for the change in BAP, but the CAP initiator implementation should work the same for application, except that it's now possible to do unicast start on ASEs in any order (#72138).
fixes #72138
fixes #70089