From: "Šimon Mikuda" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 237d4d: shared/bap: Transition ASE to QoS Configured on CI...
Date: Mon, 15 Jun 2026 11:09:02 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/40f2e3-9c36e4@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 237d4d5d20a556ea11f6cf5d0013884a0a70962e
https://github.com/bluez/bluez/commit/237d4d5d20a556ea11f6cf5d0013884a0a70962e
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Transition ASE to QoS Configured on CIS loss
stream_io_disconnected() only handled the Releasing state, leaving
Enabling, Streaming and Disabling ASEs stuck when the CIS was lost
unexpectedly.
The ASE shall autonomously move to QoS Configured on loss of the
CIS and notify the peer
Fixes PTS test BAP/USR/SCC/BV-167-C
Commit: 986e220b77ea7803af0279200db7b011667302d7
https://github.com/bluez/bluez/commit/986e220b77ea7803af0279200db7b011667302d7
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M unit/test-bap.c
Log Message:
-----------
unit/bap: Add CIS loss test
Verify a Source ASE in the Enabling state transitions to QoS Configured
rather than Disabling when its CIS is lost.
Assisted-by: ClaudeCode:claude-opus-4.8
Commit: bd9eac15a27ac2eb14f9b2f69d046088d687bfa3
https://github.com/bluez/bluez/commit/bd9eac15a27ac2eb14f9b2f69d046088d687bfa3
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M profiles/audio/media.c
Log Message:
-----------
media: use custom DBus timeouts only when remote side is waiting
Under high system load (VM instance on boot) it's observed the 3 sec
timeout BlueZ uses for BAP broadcast SetConfiguration may be missed by
Wireplumber, as these are set up immediately on startup together with
any other setup (eg ALSA) that may need time.
There's no actual need for using a short custom timeout in BlueZ for
this, as in this case there is no remote side that is waiting for a reply.
Fix by limiting custom timeouts to cases where there is a waiting
remote, and use separate defines for A2DP and BAP.
Commit: 9c36e4189e32f4b8ab1376749dda4b97e71af9af
https://github.com/bluez/bluez/commit/9c36e4189e32f4b8ab1376749dda4b97e71af9af
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M src/gatt-database.c
Log Message:
-----------
gatt-database: Prefer notifications over indications
When both notifications and indications are enabled (CCC value=0x0003)
we will send notifications by default.
Compare: https://github.com/bluez/bluez/compare/40f2e34b3739...9c36e4189e32
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-15 18:09 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/master/40f2e3-9c36e4@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