From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ 0/3] transport: distinguish BAP mic and playback volumes
Date: Sun, 4 Jan 2026 22:51:09 +0200 [thread overview]
Message-ID: <cover.1767559459.git.pav@iki.fi> (raw)
Currently we are confusing VCP and MICP volumes.
We are also mixing up AVRCP and VCP volumes.
As microphone volumes are commonly 100% and sound server may set them,
we end up with spurious 100% playback volumes.
Fix this, and also do some cleanup of #ifdefs in the volume code.
Pauli Virtanen (3):
shared/bap: add bt_bap_stream_is_server
transport: clean up volume set/get for A2DP and VCP
transport: distinguish BAP mic and playback volumes
profiles/audio/avrcp.c | 10 +--
profiles/audio/media.c | 2 +-
profiles/audio/media.h | 10 +++
profiles/audio/transport.c | 137 +++++++++++++++++++++----------------
profiles/audio/transport.h | 10 +--
profiles/audio/vcp.c | 12 ++--
profiles/audio/vcp.h | 21 +++++-
src/shared/bap.c | 6 ++
src/shared/bap.h | 2 +
9 files changed, 133 insertions(+), 77 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-04 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 20:51 Pauli Virtanen [this message]
2026-01-04 20:51 ` [PATCH BlueZ 1/3] shared/bap: add bt_bap_stream_is_server Pauli Virtanen
2026-01-04 21:49 ` transport: distinguish BAP mic and playback volumes bluez.test.bot
2026-01-05 18:45 ` [PATCH BlueZ 1/3] shared/bap: add bt_bap_stream_is_server Luiz Augusto von Dentz
2026-01-05 19:09 ` Pauli Virtanen
2026-01-05 19:29 ` Luiz Augusto von Dentz
2026-01-05 20:20 ` Pauli Virtanen
2026-01-04 20:51 ` [PATCH BlueZ 2/3] transport: clean up volume set/get for A2DP and VCP Pauli Virtanen
2026-01-04 20:51 ` [PATCH BlueZ 3/3] transport: distinguish BAP mic and playback volumes 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.1767559459.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.