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] 869383: emulator: Generate PA Sync Lost
Date: Fri, 07 Nov 2025 10:57:06 -0800	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1021045/000000-25ede9@github.com> (raw)

  Branch: refs/heads/1021045
  Home:   https://github.com/bluez/bluez
  Commit: 869383e1f2e84bda2ba86ebbed3c031509a3ee20
      https://github.com/bluez/bluez/commit/869383e1f2e84bda2ba86ebbed3c031509a3ee20
  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: 4f7efd3da49706a7b4a51a6db9dc290ab78efb5c
      https://github.com/bluez/bluez/commit/4f7efd3da49706a7b4a51a6db9dc290ab78efb5c
  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: 06607bce043ac3c291c153eb351e6fd7bb8b6fcd
      https://github.com/bluez/bluez/commit/06607bce043ac3c291c153eb351e6fd7bb8b6fcd
  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: a0a0b839e0c0a522e1a6594b5cdd2733cf94c51b
      https://github.com/bluez/bluez/commit/a0a0b839e0c0a522e1a6594b5cdd2733cf94c51b
  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: 25ede9f3504721060506c81b6f1bcb43fd7c1848
      https://github.com/bluez/bluez/commit/25ede9f3504721060506c81b6f1bcb43fd7c1848
  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/869383e1f2e8%5E...25ede9f35047

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

                 reply	other threads:[~2025-11-07 18:57 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/1021045/000000-25ede9@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).