From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ v2 0/3] mcp: expose org.bluez.MediaPlayer information via GMCS
Date: Fri, 19 Dec 2025 19:10:36 +0200 [thread overview]
Message-ID: <cover.1766164144.git.pav@iki.fi> (raw)
v2:
- use --index/-i option for mpris-proxy, similar to btmon
***
Select one of the local org.bluez.MediaPlayer instances as the "active"
player, and expose its playback controls via GMCS.
To do this, decouple media.c player API from AVRCP by adding a similar
API for org.bluez.MediaPlayer --> remote as used for the remote -->
org.bluez.MediaPlayer direction. Use it for both AVRCP and MCS.
In theory we could also expose each org.bluez.MediaPlayer in separate
MCS instances. This is not implemented here; it would need to be done so
that we don't consume ATT handles when players come and go.
Pauli Virtanen (3):
media: decouple local org.bluez.MediaPlayer from AVRCP
mcp: expose org.bluez.MediaPlayer information via GMCS
tools/mpris-proxy: allow selecting which adapter to use
Makefile.plugins | 3 +-
profiles/audio/avrcp-player.c | 291 +++++++++++++++++++
profiles/audio/avrcp.c | 4 +
profiles/audio/avrcp.h | 3 +
profiles/audio/mcp.c | 506 +++++++++++++++++++++++++++++-----
profiles/audio/media.c | 501 ++++++++++++++++++---------------
profiles/audio/media.h | 45 +++
tools/mpris-proxy.c | 37 ++-
8 files changed, 1103 insertions(+), 287 deletions(-)
create mode 100644 profiles/audio/avrcp-player.c
--
2.51.1
next reply other threads:[~2025-12-19 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 17:10 Pauli Virtanen [this message]
2025-12-19 17:10 ` [PATCH BlueZ v2 1/3] media: decouple local org.bluez.MediaPlayer from AVRCP Pauli Virtanen
2025-12-19 17:10 ` [PATCH BlueZ v2 2/3] mcp: expose org.bluez.MediaPlayer information via GMCS Pauli Virtanen
2025-12-19 17:10 ` [PATCH BlueZ v2 3/3] tools/mpris-proxy: allow selecting which adapter to use Pauli Virtanen
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.1766164144.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;
as well as URLs for NNTP newsgroup(s).