From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] dbbf1c: client/btpclient: Add BTP_EV_BAP_ASE_FOUND support
Date: Fri, 04 Sep 2026 10:07:50 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1158120/000000-ac2d23@github.com> (raw)
Branch: refs/heads/1158120
Home: https://github.com/bluez/bluez
Commit: dbbf1ca81be7478d316b3288226cde021f56c90d
https://github.com/bluez/bluez/commit/dbbf1ca81be7478d316b3288226cde021f56c90d
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M client/btpclient/bap.c
M client/btpclient/bap.h
M client/btpclient/btpclient.c
M client/btpclient/btpclient.h
M src/shared/btp.h
Log Message:
-----------
client/btpclient: Add BTP_EV_BAP_ASE_FOUND support
This is used at least for BAP/UCL/SCC/BV-004-C and BAP/UCL/SCC/BV-019-C
tests.
Commit: b75191710a0865b4851966263ddd0c76a8ec10df
https://github.com/bluez/bluez/commit/b75191710a0865b4851966263ddd0c76a8ec10df
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M Makefile.tools
M client/btpclient/bap.c
M src/shared/btp.h
Log Message:
-----------
client/btpclient: Get Codec capabilities on ASE reply
Commit: 086a6b090ca0f5fa594565cefbb96e24db60cdc4
https://github.com/bluez/bluez/commit/086a6b090ca0f5fa594565cefbb96e24db60cdc4
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M Makefile.tools
A client/btpclient/ascs.c
A client/btpclient/ascs.h
M client/btpclient/btpclient.c
M client/btpclient/btpclient.h
M client/btpclient/core.c
M client/btpclient/gap.c
A client/btpclient/vendor.c
A client/btpclient/vendor.h
M src/shared/btp.h
Log Message:
-----------
client/btpclient: Add ASCS BTP support
The audio endpoints are registered by ASCS setup command of VENDOR
service at start of the test.
For SelectProperties() D-Bus method, the reply is postponed after
auto-pts has requested the ASE and PACS characteritic values.
This allows to pass the BAP/UCL/SCC/* tests.
Commit: 3dce831e290de35e5ce41543d1d7306e6038cee7
https://github.com/bluez/bluez/commit/3dce831e290de35e5ce41543d1d7306e6038cee7
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M Makefile.tools
M client/btpclient/btpclient.h
M client/btpclient/core.c
A client/btpclient/pacs.c
A client/btpclient/pacs.h
M src/shared/btp.h
Log Message:
-----------
client/btpclient: Add BTP_OP_PACS_SET_LOCATION support
This allows to store the expected location for a local endpoint.
Commit: 83d89e73933ff41a10baea2b5e1fa893fa54ed5c
https://github.com/bluez/bluez/commit/83d89e73933ff41a10baea2b5e1fa893fa54ed5c
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M client/btpclient/bap.c
M src/shared/btp.h
Log Message:
-----------
client/btpclient: Add BTP_OP_BAP_SEND support
Commit: 3b999e3d83b6c126985dee05441e6b22b44d87c3
https://github.com/bluez/bluez/commit/3b999e3d83b6c126985dee05441e6b22b44d87c3
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M client/btpclient/ascs.c
M client/btpclient/ascs.h
M client/btpclient/bap.c
M client/btpclient/btpclient.c
M client/btpclient/btpclient.h
M client/btpclient/vendor.c
M src/shared/btp.h
Log Message:
-----------
client/btpclient: Add ASCS support for BAP/UCL/STR/* tests
Commit: 6f0dbdc97d627bf97c9160dfbc5bd69ca6f79496
https://github.com/bluez/bluez/commit/6f0dbdc97d627bf97c9160dfbc5bd69ca6f79496
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M client/btpclient/ascs.c
M client/btpclient/bap.c
Log Message:
-----------
client/btpclient: Defer CIG/CIS assignment based on Client/Server role
Previously, CIG/CIS ids were eagerly assigned to each ASE as soon as
it was discovered (CIG 0, next available CIS), regardless of whether
the btpclient was acting as the Unicast Client or Server for that ASE.
This did not match how CIG/CIS ids are actually negotiated, nor what
auto-pts expects: unicast client tests expect CIG/CIS to start at 0/0,
while unicast server tests expect them to start at 1/1.
- As Unicast Client, the CIG/CIS ids are chosen locally when building
the QoS properties returned from SelectProperties(), starting at 0.
- As Unicast Server, the CIG/CIS ids are only known once the transport
reports them; if not yet available, all of the device's ASEs should
share a common CIG (1) with CIS ids starting at 1 as well.
Move get_next_cis() from bap.c to ascs.c and extend it to take a base
CIS value, so it can be reused both for the Client and Server code
paths (base 0 and base 1 respectively) and skips ASEs whose CIS id is
still unset. Leave ase->cig_id and ase->cis_id unset
(BT_ISO_QOS_CIG_UNSET/BT_ISO_QOS_CIS_UNSET) at ASE discovery time, and
resolve them lazily:
- In get_properties_reply(), assign CIG 0 and the next CIS starting at
0 when building the QoS reply for SelectProperties() (Client role).
- In ascs_proxy_added(), when the transport does not yet report a
CIG/CIS, assign CIG 1 to all of the device's ASEs and derive CIS ids
starting at 1 via the new set_cig_cis()/set_cig_cis_data helpers
(Server role).
Commit: ac2d23e22b8f4ff7f6e5caacf0aef3b9a6c7cafe
https://github.com/bluez/bluez/commit/ac2d23e22b8f4ff7f6e5caacf0aef3b9a6c7cafe
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M client/btpclient/ascs.c
M client/btpclient/bap.c
M client/btpclient/bap.h
M client/btpclient/btpclient.c
M client/btpclient/btpclient.h
Log Message:
-----------
client/btpclient: Add stream auto acquire for BAP/USR/STR/* tests
The sink stream should be auto acquired and data sent on it.
Compare: https://github.com/bluez/bluez/compare/dbbf1ca81be7%5E...ac2d23e22b8f
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-04 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/1158120/000000-ac2d23@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.