Linux bluetooth development
 help / color / mirror / Atom feed
From: cochcoder <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e04c6b: asha: Notify connection interval changes
Date: Mon, 12 Oct 2026 21:00:53 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1184363/000000-e04c6b@github.com> (raw)

  Branch: refs/heads/1184363
  Home:   https://github.com/bluez/bluez
  Commit: e04c6bffe4f203b054a5989c43bb682bbdc6c04f
      https://github.com/bluez/bluez/commit/e04c6bffe4f203b054a5989c43bb682bbdc6c04f
  Author: Kyle Pepper <cochcoder@proton.me>
  Date:   2026-10-13 (Tue, 13 Oct 2026)

  Changed paths:
    M .gitignore
    M Makefile.am
    M profiles/audio/asha.c
    M src/shared/asha.c
    M src/shared/asha.h
    A unit/test-asha-conn.c
    A unit/test-asha-interval.c

  Log Message:
  -----------
  asha: Notify connection interval changes

Omitting the connection-update STATUS notification causes repeated N8
supervision timeouts even with a negotiated 20 ms interval. Restoring
the notification alone prevents the reported link failures.

Observe successful LE connection and update events per adapter, associate
them with the ATT socket's handle, and announce the observed interval
before START and on subsequent successful updates. Clear the observation
on disconnect so a reused handle cannot inherit another link's interval.
Notify the attached HiSyncId peer as well, matching Android's
connection-update STATUS handling, without truncating the interval byte.

Reuse the verified socket handle when delivering a live update.

Add tests for event delivery, controller isolation, disconnect/reuse,
pre-START ordering, failed updates and peer notification.
Use source-level mocks so the tests remain valid with link-time
optimization enabled.

Fixes: c26389c466a0 ("profiles/audio: Add an ASHA plugin")
Assisted-by: OpenCode:gpt-6.1-sol



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-10-13  4:00 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/1184363/000000-e04c6b@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