From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ v4 0/7] mcp: support multiple MCP and implement local GMCS
Date: Thu, 11 Dec 2025 21:08:40 +0200 [thread overview]
Message-ID: <cover.1765480081.git.pav@iki.fi> (raw)
v4:
- move uinput-util.h to src/shared + adapt accordingly
- improve debug logs in profile
v3:
- add missing #include to fix build in the test environment
v2:
- fix compilation issues
- remove unnecessary code in get_media_cp_op_supported
***
For Media Control Client, add support for multiple GMCS / MCS services
on the server. Revise the API accordingly.
For Media Control Server, make it a non-stub implementation (OTS still
missing), and add an API the profile can use.
Add tests.
This changes the design of the previous MCP code, so it's mostly a
rewrite.
The shared/mcp: commit doesn't fix the API in profiles/audio, that's
done in the later mcp: commit, as it's a rewrite of the API.
TODO (for later): OTP/OTS parts -- requires design for OTP/OTS
implementation first
TODO (for later): MPRIS integration to GMCS server -- this needs some
redesign in media.c as it's hardcoded to AVRCP there.
Tested devices (MCS):
- Creative Zen Hybrid Pro (doesn't even connect without GMCS)
- Samsung Galaxy Buds Pro2
- Creative Aurvana Ace 2
Tested devices (MCP):
- Samsung Galaxy A56
Pauli Virtanen (7):
shared/mcp: support multiple MCP, and add non-stub MCS server
test-mcp: add tests for MCP / MCS
mcp: adapt to new MCP API to support multiple remote MCS services
shared/uinput-util: extract uinput utility function from AVCTP
avctp: use uinput utilities from src/shared
mcp: add local GMCS service that emits uinput media keys
shared/gatt-client: fix notify_data leak in notify_data_write_ccc
.gitignore | 1 +
Makefile.am | 10 +-
lib/bluetooth/uuid.h | 27 +-
profiles/audio/avctp.c | 159 +-
profiles/audio/mcp.c | 812 +++++++---
src/shared/gatt-client.c | 3 +
src/shared/mcp.c | 3216 ++++++++++++++++++++++----------------
src/shared/mcp.h | 186 ++-
src/shared/mcs.h | 51 +-
src/shared/uinput-util.c | 195 +++
src/shared/uinput-util.h | 31 +
unit/test-mcp.c | 1807 +++++++++++++++++++++
12 files changed, 4742 insertions(+), 1756 deletions(-)
create mode 100644 src/shared/uinput-util.c
create mode 100644 src/shared/uinput-util.h
create mode 100644 unit/test-mcp.c
--
2.51.1
next reply other threads:[~2025-12-11 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 19:08 Pauli Virtanen [this message]
2025-12-11 19:08 ` [PATCH BlueZ v4 1/7] shared/mcp: support multiple MCP, and add non-stub MCS server Pauli Virtanen
2025-12-11 19:44 ` mcp: support multiple MCP and implement local GMCS bluez.test.bot
2025-12-11 19:08 ` [PATCH BlueZ v4 2/7] test-mcp: add tests for MCP / MCS Pauli Virtanen
2025-12-11 19:08 ` [PATCH BlueZ v4 3/7] mcp: adapt to new MCP API to support multiple remote MCS services Pauli Virtanen
2025-12-11 19:08 ` [PATCH BlueZ v4 4/7] shared/uinput-util: extract uinput utility function from AVCTP Pauli Virtanen
2025-12-11 19:08 ` [PATCH BlueZ v4 5/7] avctp: use uinput utilities from src/shared Pauli Virtanen
2025-12-11 19:08 ` [PATCH BlueZ v4 6/7] mcp: add local GMCS service that emits uinput media keys Pauli Virtanen
2025-12-11 19:08 ` [PATCH BlueZ v4 7/7] shared/gatt-client: fix notify_data leak in notify_data_write_ccc 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.1765480081.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).