From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ v2 0/9] Add TMAP & GMAP information services
Date: Fri, 28 Nov 2025 22:02:19 +0200 [thread overview]
Message-ID: <cover.1764360140.git.pav@iki.fi> (raw)
Add support for TMAP and GMAP services. They contain only device
audio capability bitmasks.
v2:
- Rework the service wait to be general mechanism that also determines
the service autoconnect order.
This is now slightly more involved, but this sort of "soft" ordering
dependency must know which services the autoconnect mechanism is going
to start.
Sorting autoconnect services is one of the ways to do it, probably
makes sense also otherwise, and we could insert service conflict
handling at the same place.
- Make org.bluez.MediaEndpoint::SupportedFeatures per-uuid dict
---
Expose the values from remote devices in
org.bluez.MediaEndpoint->SupportedFeatures
This maybe could also be org.bluez.Device->SupportedFeatures instead,
but MediaEndpoint looks OK too.
Sound server can use theses to determine which mandatory capabilities
devices have.
TODO (maybe later): add way to configure advertised local service
values, e.g. via config file.
Pauli Virtanen (9):
shared/gmap: add GMAP Service
test-gmap: add test for GMAP Service
gmap: Add GMAP profile
doc: org.bluez.MediaEndpoint: add SupportedFeatures
bap: add SupportedFeatures for MediaEndpoints
profile: add after_uuids for ordering profile startup
device: use after_uuids in service autoconnect and sort also GATT
service: add btd_profile::ready callback when after_uuids ready
bap: have unicast client wait for VCS & TMAS & GMAP
.gitignore | 1 +
Makefile.am | 7 +
Makefile.plugins | 5 +
configure.ac | 7 +
doc/org.bluez.MediaEndpoint.rst | 108 +++++++
lib/bluetooth/uuid.h | 8 +
profiles/audio/bap.c | 163 ++++++++++-
profiles/audio/gmap.c | 200 +++++++++++++
src/device.c | 74 ++++-
src/profile.c | 89 ++++++
src/profile.h | 16 ++
src/service.c | 100 +++++++
src/shared/gmap.c | 401 ++++++++++++++++++++++++++
src/shared/gmap.h | 70 +++++
unit/test-gmap.c | 496 ++++++++++++++++++++++++++++++++
15 files changed, 1730 insertions(+), 15 deletions(-)
create mode 100644 profiles/audio/gmap.c
create mode 100644 src/shared/gmap.c
create mode 100644 src/shared/gmap.h
create mode 100644 unit/test-gmap.c
--
2.51.1
next reply other threads:[~2025-11-28 20:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 20:02 Pauli Virtanen [this message]
2025-11-28 20:02 ` [PATCH BlueZ v2 1/9] shared/gmap: add GMAP Service Pauli Virtanen
2025-11-28 20:58 ` Add TMAP & GMAP information services bluez.test.bot
2025-11-28 20:02 ` [PATCH BlueZ v2 2/9] test-gmap: add test for GMAP Service Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 3/9] gmap: Add GMAP profile Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 4/9] doc: org.bluez.MediaEndpoint: add SupportedFeatures Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 5/9] bap: add SupportedFeatures for MediaEndpoints Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 6/9] profile: add after_uuids for ordering profile startup Pauli Virtanen
2025-12-01 17:00 ` Luiz Augusto von Dentz
2025-12-01 17:32 ` Pauli Virtanen
2025-12-01 17:57 ` Luiz Augusto von Dentz
2025-11-28 20:02 ` [PATCH BlueZ v2 7/9] device: use after_uuids in service autoconnect and sort also GATT Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 8/9] service: add btd_profile::ready callback when after_uuids ready Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 9/9] bap: have unicast client wait for VCS & TMAS & GMAP Pauli Virtanen
2025-12-01 14:43 ` [PATCH BlueZ v2 0/9] Add TMAP & GMAP information services Luiz Augusto von Dentz
2025-12-01 16:50 ` 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.1764360140.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