From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 0bb304: audio: Add support for specific error codes for A2...
Date: Thu, 11 Sep 2025 08:29:17 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1001420/000000-bc59c8@github.com> (raw)
Branch: refs/heads/1001420
Home: https://github.com/bluez/bluez
Commit: 0bb3040a52bd312582eab35b267c24e8677c5e86
https://github.com/bluez/bluez/commit/0bb3040a52bd312582eab35b267c24e8677c5e86
Author: Per Waagø <pwaago@cisco.com>
Date: 2025-09-11 (Thu, 11 Sep 2025)
Changed paths:
M profiles/audio/a2dp.c
M profiles/audio/a2dp.h
M profiles/audio/avdtp.c
M profiles/audio/media.c
Log Message:
-----------
audio: Add support for specific error codes for A2DP configuration
The A2DP specification defines error codes that shall be used if
the codec capabilities contain improper settings. This change allows
clients to trigger the sending of these specific error codes by
returning the corresponding error messages from
MediaEndpoint1.SetConfiguration.
This update is fully backwards compatible: clients passing other error
messages will continue to receive the default error code as before. On
older BlueZ versions, these new errors will also result in the default
error code, enabling clients to implement support for the new errors
without breaking compatibility.
This change enables passing A2DP/SNK/AVP/* and A2DP/SRC/AVP/*
qualification tests.
Commit: bc59c8df6d48162a9cdd156332e897f339b488b1
https://github.com/bluez/bluez/commit/bc59c8df6d48162a9cdd156332e897f339b488b1
Author: Per Waagø <pwaago@cisco.com>
Date: 2025-09-11 (Thu, 11 Sep 2025)
Changed paths:
M doc/org.bluez.MediaEndpoint.rst
Log Message:
-----------
doc: Document error codes for A2DP MediaEndpoints
Compare: https://github.com/bluez/bluez/compare/0bb3040a52bd%5E...bc59c8df6d48
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-09-11 15:29 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/1001420/000000-bc59c8@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