All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH BlueZ] shared/asha: Only update device set after start succeeds
@ 2025-04-25 14:04 Arun Raghavan
  2025-04-25 15:34 ` [BlueZ] " bluez.test.bot
  2025-04-25 19:01 ` [PATCH BlueZ] " patchwork-bot+bluetooth
  0 siblings, 2 replies; 3+ messages in thread
From: Arun Raghavan @ 2025-04-25 14:04 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: Arun Raghavan, sanchayan

This ensures that one side's connected status is only exposed to the
other after the connection is actually complete.
---
 src/shared/asha.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/shared/asha.c b/src/shared/asha.c
index e623e7156..33bec40da 100644
--- a/src/shared/asha.c
+++ b/src/shared/asha.c
@@ -421,8 +421,6 @@ static void read_rops(bool success,
 			asha->right_side, asha->binaural, asha->csis_supported,
 			asha->render_delay, asha->codec_ids);
 
-	update_asha_set(asha, true);
-
 	check_probe_done(asha);
 }
 
@@ -447,6 +445,7 @@ static void audio_status_notify(uint16_t value_handle, const uint8_t *value,
 		if (status == 0) {
 			asha->state = ASHA_STARTED;
 			DBG("ASHA start complete");
+			update_asha_set(asha, true);
 			asha_set_send_status(asha, true);
 		} else {
 			bt_asha_state_reset(asha);
-- 
2.49.0


^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-04-25 19:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-04-25 14:04 [PATCH BlueZ] shared/asha: Only update device set after start succeeds Arun Raghavan
2025-04-25 15:34 ` [BlueZ] " bluez.test.bot
2025-04-25 19:01 ` [PATCH BlueZ] " patchwork-bot+bluetooth

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.