From: raghava447 <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 9db173: profiles/audio: Support MCS track position writes
Date: Fri, 04 Sep 2026 10:07:57 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1158246/000000-c7a20d@github.com> (raw)
Branch: refs/heads/1158246
Home: https://github.com/bluez/bluez
Commit: 9db1732402fc80263721882d90f66f1aeb9c98ae
https://github.com/bluez/bluez/commit/9db1732402fc80263721882d90f66f1aeb9c98ae
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M profiles/audio/mcp.c
M profiles/audio/media.c
M profiles/audio/media.h
Log Message:
-----------
profiles/audio: Support MCS track position writes
Use MPRIS Seek to handle MCS Track Position writes.
This is required by PTS GMCS/SR/SP/BV-02-C test.
Commit: b6e189629a6ce5ed2b4ffdc2314a9fdf79d9a529
https://github.com/bluez/bluez/commit/b6e189629a6ce5ed2b4ffdc2314a9fdf79d9a529
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M profiles/audio/mcp.c
Log Message:
-----------
profiles/audio: Support MCS fast seeking
Map Fast Rewind and Fast Forward to relative MPRIS Seek calls.
Report direction through Seeking Speed until Seeked restores player
state.
This is required by PTS tests GMCS/SR/MCP/BV-05-C to BV-08-C.
Commit: 4098dfadf887b6c622e38fec0c80ca2c2d2e3727
https://github.com/bluez/bluez/commit/4098dfadf887b6c622e38fec0c80ca2c2d2e3727
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M src/shared/mcp.c
Log Message:
-----------
shared/mcp: Notify unsupported RFU opcodes
Use the ATT result to suppress responses for malformed writes while
allowing opcode 0x00 to report Operation Not Supported.
This is required by GMCS/SR/SPE/BI-01-C.
Commit: c7a20dce06a2ac3737e89754dd81a16122767957
https://github.com/bluez/bluez/commit/c7a20dce06a2ac3737e89754dd81a16122767957
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M unit/test-mcp.c
Log Message:
-----------
unit/test-mcp: Test unsupported RFU opcode
Verify that GMCS/SR/SPE/BI-01-C opcode 0x00 produces an Operation Not
Supported notification.
Compare: https://github.com/bluez/bluez/compare/9db1732402fc%5E...c7a20dce06a2
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-04 17:07 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/1158246/000000-c7a20d@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