linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 27eb90: emulator: Generate PA Sync Lost
Date: Fri, 07 Nov 2025 12:31:16 -0800	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1021075/000000-1b3bd7@github.com> (raw)

  Branch: refs/heads/1021075
  Home:   https://github.com/bluez/bluez
  Commit: 27eb90249173369fe000749a1d7e1a4ab81b7f2f
      https://github.com/bluez/bluez/commit/27eb90249173369fe000749a1d7e1a4ab81b7f2f
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2025-11-07 (Fri, 07 Nov 2025)

  Changed paths:
    M emulator/btdev.c

  Log Message:
  -----------
  emulator: Generate PA Sync Lost

This attempts to generate a PA Sync Lost whenever a PA is disabled and
there is a remote synced to it.


  Commit: 1874de0a078158798e78debc09ba373bd83a9d91
      https://github.com/bluez/bluez/commit/1874de0a078158798e78debc09ba373bd83a9d91
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2025-11-07 (Fri, 07 Nov 2025)

  Changed paths:
    M emulator/bthost.c
    M emulator/bthost.h

  Log Message:
  -----------
  bthost: Add support for terminating a BIG

This adds support for sending BT_HCI_CMD_LE_TERM_BIG via
bthost_terminate_big.


  Commit: a4c24d8af5c4c7b7307c8fb2ba3ffe74486f0aac
      https://github.com/bluez/bluez/commit/a4c24d8af5c4c7b7307c8fb2ba3ffe74486f0aac
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2025-11-07 (Fri, 07 Nov 2025)

  Changed paths:
    M tools/iso-tester.c

  Log Message:
  -----------
  iso-tester: Add tests for checking proper handling of Sync Lost

This introduces the following tests to check if BIG/PA Sync Lost are
handled properly:

ISO Broadcaster Receiver Sync Lost - Success
ISO Broadcaster PAST Receiver Sync Lost - Success


  Commit: 9f1669ae9412b4443ea138cd82d33ed88310d328
      https://github.com/bluez/bluez/commit/9f1669ae9412b4443ea138cd82d33ed88310d328
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2025-11-07 (Fri, 07 Nov 2025)

  Changed paths:
    M profiles/audio/bap.c
    M profiles/audio/bass.c

  Log Message:
  -----------
  bass: Fix not cleaning up delegator properly

When BIG sync is lost, or the assistant modify removing all streams,
delegator should be freed to so the assistant can start over and share
another stream.


  Commit: 1b3bd732173925a05528676873a8c5d1c6eb04f5
      https://github.com/bluez/bluez/commit/1b3bd732173925a05528676873a8c5d1c6eb04f5
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2025-11-07 (Fri, 07 Nov 2025)

  Changed paths:
    M btio/btio.c

  Log Message:
  -----------
  btio: Fix endless loop if accept return -EBADFD

In certain cases, e.g. ISO Broadcast Listen, the listening socket may
get into an invalid state (CONNECTED) if the PA Sync is terminated
causing an endless loop of accept syscall.


Compare: https://github.com/bluez/bluez/compare/27eb90249173%5E...1b3bd7321739

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

                 reply	other threads:[~2025-11-07 20:31 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/1021075/000000-1b3bd7@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;
as well as URLs for NNTP newsgroup(s).