public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ 00/11] Add local TMAS & GMAS servers
Date: Sat,  6 Dec 2025 13:01:16 +0200	[thread overview]
Message-ID: <cover.1765018766.git.pav@iki.fi> (raw)

Parse TMAS and GMAS features to expose from
MediaEndpoint::SupportedFeatures

Improve handling of changing TMAP & GMAP features: set the service
inactive when there is no Role set.  For GMAP, we must also remove the
feature chrc if a role is unset.

Also do some minor cleanup.

Pipewire side:
https://gitlab.freedesktop.org/pvir/pipewire/-/commits/tmap-features

Pauli Virtanen (11):
  lib: move VCS, TMAS, GMAS uuid strings to uuid.h
  shared/tester: check size before trying debug print
  shared/tmap, gmap: add macros for feature names and listing
  bap: use tmap/gmap macros for listing features
  shared/tmap: deactivate service if setting Role to 0
  shared/gmap: deactivate service or remove feature chrc if role removed
  test-tmap: test removing and adding role
  test-gmap: test removing, adding, and changing role
  media: parse SupportedFeatures from registered MediaEndpoints
  tmap: remove service on device remove
  gmap: remove service on device remove

 lib/bluetooth/uuid.h   |   3 +
 profiles/audio/bap.c   |  36 +++-------
 profiles/audio/gmap.c  |   2 +
 profiles/audio/media.c | 160 +++++++++++++++++++++++++++++++++++++++--
 profiles/audio/tmap.c  |   2 +
 profiles/audio/vcp.c   |   1 -
 src/shared/gmap.c      |  57 +++++++++++----
 src/shared/gmap.h      |  45 +++++++++++-
 src/shared/tester.c    |   2 +-
 src/shared/tmap.c      |  14 ++--
 src/shared/tmap.h      |  15 ++++
 unit/test-gmap.c       |  89 ++++++++++++++++-------
 unit/test-tmap.c       |  15 ++++
 13 files changed, 363 insertions(+), 78 deletions(-)

-- 
2.51.1


             reply	other threads:[~2025-12-06 11:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-06 11:01 Pauli Virtanen [this message]
2025-12-06 11:01 ` [PATCH BlueZ 01/11] lib: move VCS, TMAS, GMAS uuid strings to uuid.h Pauli Virtanen
2025-12-06 12:02   ` Add local TMAS & GMAS servers bluez.test.bot
2025-12-06 11:01 ` [PATCH BlueZ 02/11] shared/tester: check size before trying debug print Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 03/11] shared/tmap, gmap: add macros for feature names and listing Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 04/11] bap: use tmap/gmap macros for listing features Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 05/11] shared/tmap: deactivate service if setting Role to 0 Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 06/11] shared/gmap: deactivate service or remove feature chrc if role removed Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 07/11] test-tmap: test removing and adding role Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 08/11] test-gmap: test removing, adding, and changing role Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 09/11] media: parse SupportedFeatures from registered MediaEndpoints Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 10/11] tmap: remove service on device remove Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 11/11] gmap: " Pauli Virtanen
2025-12-08 19:20 ` [PATCH BlueZ 00/11] Add local TMAS & GMAS servers 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.1765018766.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