From: "Šimon Mikuda" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 1fd31c: media: Add Mute property to MediaTransport1
Date: Tue, 09 Jun 2026 11:35:39 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1108770/000000-c01f9b@github.com> (raw)
Branch: refs/heads/1108770
Home: https://github.com/bluez/bluez
Commit: 1fd31cca12a6e9a34e93ec3d1fc1814ffce2a0e4
https://github.com/bluez/bluez/commit/1fd31cca12a6e9a34e93ec3d1fc1814ffce2a0e4
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-09 (Tue, 09 Jun 2026)
Changed paths:
M doc/org.bluez.MediaTransport.rst
M profiles/audio/transport.c
M profiles/audio/vcp.c
M profiles/audio/vcp.h
M src/shared/vcp.c
M src/shared/vcp.h
Log Message:
-----------
media: Add Mute property to MediaTransport1
Boolean, optional, readwrite. Only present for LE Audio (BAP) unicast
transports backed by VCS. A2DP has no mute concept in AVRCP.
bt_vcp_set_mute() writes VCS Control Point Mute/Unmute for a client
session, or updates Volume State for a server session.
bt_vcp_get_mute() returns the cached value updated by Volume State
notifications.
Commit: c01f9bd015cbe527b9f30a6338fb393da034e782
https://github.com/bluez/bluez/commit/c01f9bd015cbe527b9f30a6338fb393da034e782
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-09 (Tue, 09 Jun 2026)
Changed paths:
M client/player.c
Log Message:
-----------
client/player: Add transport.mute command
Mirrors transport.volume. Accepts on/off, yes/no, 1/0.
Compare: https://github.com/bluez/bluez/compare/1fd31cca12a6%5E...c01f9bd015cb
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-09 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1108770/000000-c01f9b@github.com \
--to=noreply@github.com \
--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