From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ 00/10] Add TMAP & GMAP information services
Date: Sun, 23 Nov 2025 18:17:05 +0200 [thread overview]
Message-ID: <cover.1763914558.git.pav@iki.fi> (raw)
Add support for TMAP and GMAP services. They contain only device
audio capability bitmasks.
Expose the values from remote devices in
org.bluez.MediaEndpoint->SupportedFeatures
Not sure if this should be org.bluez.Device->SupportedFeatures instead.
Sound server can use theses to determine which mandatory capabilities
devices have.
Some boilerplate maybe could be avoided by putting these into the BAP
service, but did them separately here.
TODO (maybe later): advertise local service values, these could be
configured either via config file or endpoint SupportedFeatures. Maybe
config file is better?
Pauli Virtanen (10):
shared/tmap: add TMAP Service
test-tmap: add test for TMAP Service
tmap: add TMAP profile
bap: have unicast client wait for VCS & TMAS
shared/gmap: add GMAP Service
test-gmap: add test for GMAP Service
gmap: Add GMAP profile
bap: unicast client wait for GMAP service
doc: org.bluez.MediaEndpoint: add SupportedFeatures
bap: add SupportedFeatures for MediaEndpoints
.gitignore | 2 +
Makefile.am | 14 +
Makefile.plugins | 10 +
configure.ac | 14 +
doc/org.bluez.MediaEndpoint.rst | 99 +++++++
lib/bluetooth/uuid.h | 12 +
profiles/audio/bap.c | 146 +++++++++-
profiles/audio/gmap.c | 203 +++++++++++++
profiles/audio/tmap.c | 203 +++++++++++++
src/shared/gmap.c | 402 ++++++++++++++++++++++++++
src/shared/gmap.h | 70 +++++
src/shared/tmap.c | 302 +++++++++++++++++++
src/shared/tmap.h | 39 +++
unit/test-gmap.c | 496 ++++++++++++++++++++++++++++++++
unit/test-tmap.c | 378 ++++++++++++++++++++++++
15 files changed, 2387 insertions(+), 3 deletions(-)
create mode 100644 profiles/audio/gmap.c
create mode 100644 profiles/audio/tmap.c
create mode 100644 src/shared/gmap.c
create mode 100644 src/shared/gmap.h
create mode 100644 src/shared/tmap.c
create mode 100644 src/shared/tmap.h
create mode 100644 unit/test-gmap.c
create mode 100644 unit/test-tmap.c
--
2.51.1
next reply other threads:[~2025-11-23 16:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 16:17 Pauli Virtanen [this message]
2025-11-23 16:17 ` [PATCH BlueZ 01/10] shared/tmap: add TMAP Service Pauli Virtanen
2025-11-23 17:24 ` Add TMAP & GMAP information services bluez.test.bot
2025-11-23 16:17 ` [PATCH BlueZ 02/10] test-tmap: add test for TMAP Service Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 03/10] tmap: add TMAP profile Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 04/10] bap: have unicast client wait for VCS & TMAS Pauli Virtanen
2025-11-24 16:25 ` Luiz Augusto von Dentz
2025-11-24 16:58 ` Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 05/10] shared/gmap: add GMAP Service Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 06/10] test-gmap: add test for " Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 07/10] gmap: Add GMAP profile Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 08/10] bap: unicast client wait for GMAP service Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 09/10] doc: org.bluez.MediaEndpoint: add SupportedFeatures Pauli Virtanen
2025-11-24 16:20 ` Luiz Augusto von Dentz
2025-11-24 16:55 ` Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 10/10] bap: add SupportedFeatures for MediaEndpoints Pauli Virtanen
2025-11-26 16:20 ` [PATCH BlueZ 00/10] Add TMAP & GMAP information services patchwork-bot+bluetooth
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=cover.1763914558.git.pav@iki.fi \
--to=pav@iki.fi \
--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