From: Kyle Pepper <cochcoder@proton.me>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com
Subject: [PATCH BlueZ v2] shared/asha: Send STOP without a response
Date: Sat, 07 Nov 2026 01:24:00 +0000 [thread overview]
Message-ID: <20261107012310.1224254-1-cochcoder@proton.me> (raw)
In-Reply-To: <20261028133034.261833-1-cochcoder@proton.me>
Avoid leaving a STOP Write Request pending after local state has been
reset. Send a Write Command using the existing helper instead.
ASHA specifies Write with response for STOP; this changes that procedure
and needs renderer STOP/restart validation.
Fixes: 9948168cca15 ("shared/asha: Don't wait for status notification on stop")
Assisted-by: OpenCode:gpt-6.1-sol
Assisted-by: Codex:gpt-6
---
v2: Drop the standalone mock test and redundant state-reset comment.
Keep the unchanged regression harness as local evidence.
Previous submission: https://lore.kernel.org/linux-bluetooth/20261028133034.261833-1-cochcoder@proton.me/
The ASHA AudioControlPoint table specifies Write with response for STOP.
Maintainer agreement on this deviation and renderer STOP/restart evidence
remain open. The local mock cannot establish protocol interoperability.
https://source.android.com/docs/core/connect/bluetooth/asha#AudioControlPoint
Pristine source fails the expected local mock assertion. Sent and reduced
source pass; reduced source also passes ASan/UBSan and LTO. Full make check
was not rerun: the preceding baseline review reproduced an SDP linker
failure. No new hardware, remote CI or acceptance result is claimed.
src/shared/asha.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/shared/asha.c b/src/shared/asha.c
index 79bb29bf9a..f1edc06444 100644
--- a/src/shared/asha.c
+++ b/src/shared/asha.c
@@ -284,8 +284,8 @@ unsigned int bt_asha_stop(struct bt_asha *asha)
asha->state = ASHA_STOPPED;
- ret = asha_send_acp(asha, acp_stop_cmd, sizeof(acp_stop_cmd), NULL,
- NULL);
+ ret = asha_send_acp_without_response(asha, acp_stop_cmd,
+ sizeof(acp_stop_cmd));
asha_set_send_status(asha, false);
/* We reset our state without waiting for a response */
base-commit: a8067198717b38391ca183ed7f41a69ec4b81b6e
--
2.56.0
next prev parent reply other threads:[~2026-11-07 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 13:30 [PATCH RESEND] shared/asha: send STOP without waiting for a response Kyle Pepper
2026-10-28 16:02 ` [RESEND] " bluez.test.bot
2026-11-07 1:24 ` Kyle Pepper [this message]
2026-11-07 2:52 ` [BlueZ,v2] shared/asha: Send STOP without " bluez.test.bot
2026-11-10 22:00 ` [PATCH BlueZ v2] " patchwork-bot+bluetooth
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=20261107012310.1224254-1-cochcoder@proton.me \
--to=cochcoder@proton.me \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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