From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] d8ed4a: shared/bap: Skip local metadata Config callbacks
Date: Thu, 17 Sep 2026 09:58:33 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1167792/000000-c27e15@github.com> (raw)
Branch: refs/heads/1167792
Home: https://github.com/bluez/bluez
Commit: d8ed4a642abad923c56e90c038547d9cc7f7ba44
https://github.com/bluez/bluez/commit/d8ed4a642abad923c56e90c038547d9cc7f7ba44
Author: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
Date: 2026-09-17 (Thu, 17 Sep 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Skip local metadata Config callbacks
When reconfiguring a client stream that is already Codec Configured,
setup_config() queues Codec Configuration and then caches metadata.
stream_metadata() emits a same-state CONFIG notification for that local
update. The profile callback treats it as the peer's configuration
completion and clears config_pending before the peer has responded.
If the control point response precedes the ASE state notification, QoS
setup can run while need_reconfig is still set and fail locally.
Cache client metadata in CONFIG without emitting a state notification.
Keep genuine peer CONFIG notifications and server metadata handling
unchanged.
Commit: c27e1581c612b134d33ec19e56b92fcfbf20d6c6
https://github.com/bluez/bluez/commit/c27e1581c612b134d33ec19e56b92fcfbf20d6c6
Author: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
Date: 2026-09-17 (Thu, 17 Sep 2026)
Changed paths:
M doc/functional-bap.rst
M test/functional/test_bap.py
Log Message:
-----------
test-functional: Cover BAP metadata reconfiguration
Exercise the real daemon by clearing a configured unicast endpoint and
reconfiguring its retained ASE with empty or Media-context metadata.
Require successful configuration and check the resulting transport.
Use ATT MTU 48 to prevent the control-point response and fresh ASE
notification from being batched together. Without the shared/bap fix,
the Media case fails QoS setup; the empty-metadata control still passes.
Call SetConfiguration directly because endpoint.config does not pass
metadata for unicast presets. Remove the fixture's redundant config
command: SelectProperties already configures both ASEs after pairing.
Compare: https://github.com/bluez/bluez/compare/d8ed4a642aba%5E...c27e1581c612
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-17 16:58 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/1167792/000000-c27e15@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox