mbox series

[v3,0/1] Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync

Message ID 20230817064427.3647-1-iulia.tanasescu@nxp.com (mailing list archive)
Headers show
Series Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync | expand

Message

Iulia Tanasescu Aug. 17, 2023, 6:44 a.m. UTC 
Some scenarios require a Broadcast Sink to complete the PA sync and
BIG sync procedures separately.

For example, a Broadcast Sink might synchronize to the periodic
advertising transmitted by a Broadcast Source and it might detect
that the BIG is encrypted, by looking at the BIGInfo advertising
reports. If the Broadcast Sink doesn't know which Broadcast Code
to pass as parameter to the BIG Create Sync command, it might learn
it from a BASS Client through the Set Broadcast Code operation.
Only then will it be able to successfully sync to the BIG.

This patch implements defer setup support for the Broadcast Sink
scenario: By setting defer setup on a broadcast socket before calling
listen, the user is able to trigger the PA sync and BIG sync procedures
separately.

This patch contains a rebase against latest commits.

Iulia Tanasescu (1):
  Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync

 include/net/bluetooth/hci_core.h |  30 +++++-
 net/bluetooth/hci_conn.c         |  13 ++-
 net/bluetooth/hci_event.c        |  41 +++++++-
 net/bluetooth/hci_sync.c         |  15 +++
 net/bluetooth/iso.c              | 160 ++++++++++++++++++++++++-------
 5 files changed, 218 insertions(+), 41 deletions(-)


base-commit: ef6d9b23aa589073cff4371135d017724728ae9f

Comments

patchwork-bot+bluetooth@kernel.org Aug. 17, 2023, 7:50 p.m. UTC | #1 
Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu, 17 Aug 2023 09:44:26 +0300 you wrote:
> Some scenarios require a Broadcast Sink to complete the PA sync and
> BIG sync procedures separately.
> 
> For example, a Broadcast Sink might synchronize to the periodic
> advertising transmitted by a Broadcast Source and it might detect
> that the BIG is encrypted, by looking at the BIGInfo advertising
> reports. If the Broadcast Sink doesn't know which Broadcast Code
> to pass as parameter to the BIG Create Sync command, it might learn
> it from a BASS Client through the Set Broadcast Code operation.
> Only then will it be able to successfully sync to the BIG.
> 
> [...]

Here is the summary with links:
  - [v3,1/1] Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync
    https://git.kernel.org/bluetooth/bluetooth-next/c/f0835e7404b7

You are awesome, thank you!