From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 4f1054: BASS: support for encrypted broadcast source
Date: Wed, 11 Jun 2025 02:12:30 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/970719/000000-4f1054@github.com> (raw)
Branch: refs/heads/970719
Home: https://github.com/bluez/bluez
Commit: 4f105421ced5afad0fdb188cbe08ba902be70010
https://github.com/bluez/bluez/commit/4f105421ced5afad0fdb188cbe08ba902be70010
Author: Yang Li <yang.li@amlogic.com>
Date: 2025-06-11 (Wed, 11 Jun 2025)
Changed paths:
M profiles/audio/bass.c
M src/shared/bass.c
Log Message:
-----------
BASS: support for encrypted broadcast source
If the BIS is encrypted as indicated in the BIG Info Report, the
broadcast code needs to be requested from the Assistant.
step 1: Broadcast_Code required
> HCI Event: LE Meta Event (0x3e) plen 20 #631 [hci0] 27.176606
LE Broadcast Isochronous Group Info Advertising Report (0x22)
Sync Handle: 0x0000
Number BIS: 2
NSE: 8
ISO Interval: 20.00 msec (0x0010)
BN: 2
PTO: 2
IRC: 2
Maximum PDU: 60
SDU Interval: 10000 us (0x002710)
Maximum SDU: 60
PHY: LE 2M (0x02)
Framing: Unframed (0x00)
Encryption: 0x01
< ACL Data TX: Handle 16 flags 0x00 dlen 44 #633 [hci0] 27.184478
ATT: Handle Value Notification (0x1b) len 39
Handle: 0x005f Type: Broadcast Receive State (0x2bc8)
Data[37]: 01016698a411bb13019f103b02010100000000110d03506978656c20395f32303938020502
Source_ID: 1
Source_Address_Type: 1
Source_Address: 13:BB:11:A4:98:66
Source_Adv_SID: 1
Broadcast_ID: 0x3b109f
PA_Sync_State: Synchronized to PA
BIG_Encryption: Broadcast_Code required
Num_Subgroups: 1
Subgroup #0:
BIS_Sync State: 0x00000000
Metadata: #0: len 0x0d type 0x03
Metadata: 50 69 78 65 6c 20 39 5f 32 30 39 38 Pixel 9_2098
Metadata: #1: len 0x02 type 0x05
Metadata: 02
> ACL Data RX: Handle 16 flags 0x02 dlen 25 #636 [hci0] 27.455744
ATT: Write Command (0x52) len 20
Handle: 0x0065 Type: Broadcast Audio Scan Control Point (0x2bc7)
Data[18]: 04013a4931614b3a2b7c4b7431722b666724
Opcode: Set Broadcast_Code (0x04)
Source_ID: 1
Broadcast_Code[16]: 3a4931614b3a2b7c4b7431722b666724
step 2: Set Broadcast Code when BIG Create Sync
< HCI Command: LE Broadcast Isoc.. (0x08|0x006b) plen 26 #641 [hci0] 27.669211
BIG Handle: 0x00
BIG Sync Handle: 0x0000
Encryption: Encrypted (0x01)
Broadcast Code[16]: 3a4931614b3a2b7c4b7431722b666724
Maximum Number Subevents: 0x00
Timeout: 20000 ms (0x07d0)
Number of BIS: 2
BIS ID: 0x01
BIS ID: 0x02
Fixes: https://github.com/bluez/bluez/issues/1306
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-11 9:12 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/970719/000000-4f1054@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 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.