Linux bluetooth development
 help / color / mirror / Atom feed
From: Silviu Florian Barbulescu <silviu.barbulescu@nxp.com>
To: linux-bluetooth@vger.kernel.org
Cc: Silviu Florian Barbulescu <silviu.barbulescu@nxp.com>
Subject: [PATCH v2 0/6] Add initial support for BAP broadcast source
Date: Thu, 25 May 2023 18:34:46 +0300	[thread overview]
Message-ID: <20230525153452.125789-1-silviu.barbulescu@nxp.com> (raw)

This patch adds initial support for BAP broadcast source.

The current implementation allows BAP source endpoint registration,
media transport creation, transport acquiring and sending broadcast ISO data.

Currently, one BIG containing one BIS is supported.

To test the current implementation use bluetoothctl with the following commands:
# endpoint.register 00001852-0000-1000-8000-00805f9b34fb 0x06
# transport.acquire /org/bluez/hci0/dev_00_00_00_00_00_00/pac_broadcast0/fd0
# transport.send /org/bluez/hci0/dev_00_00_00_00_00_00/pac_broadcast0/fd0 <file.wav>

The curent implementation checks that ISO_BROADCASTER is suported on the board so
"Check for ISO support in controller" patch is required
(https://patchwork.kernel.org/project/bluetooth/patch/20230510134557.11486-2-claudia.rosu@nxp.com/)

Silviu Florian Barbulescu (6):
  Update Docs for BAP broadcast source
  Add macro definitions for BAP broadcast source support
  Check for ISO broadcast support in controller
  Add support for setsockopt (BT_IO_OPT_BASE)
  Update bluetoothctl with support for broadcast source
  Add initial support for BAP broadcast source

 btio/btio.c                |  26 ++-
 btio/btio.h                |   2 +
 client/player.c            | 209 +++++++++++++++--
 doc/media-api.txt          |  11 +
 doc/mgmt-api.txt           |   2 +
 lib/bluetooth.h            |   9 +
 lib/mgmt.h                 |   2 +
 lib/uuid.h                 |   3 +
 monitor/packet.c           |   4 +-
 profiles/audio/bap.c       | 455 ++++++++++++++++++++++++++++++++-----
 profiles/audio/media.c     | 129 +++++++++--
 profiles/audio/transport.c |  51 +++--
 src/shared/bap.c           | 324 +++++++++++++++++++-------
 src/shared/bap.h           |  81 +++++--
 unit/test-bap.c            |  83 +++----
 15 files changed, 1121 insertions(+), 270 deletions(-)


base-commit: 718f27d09fc129d0b94ef61192482ac7e18cbaed
-- 
2.34.1


             reply	other threads:[~2023-05-25 15:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 15:34 Silviu Florian Barbulescu [this message]
2023-05-25 15:34 ` [PATCH v2 1/6] Update Docs for BAP broadcast source Silviu Florian Barbulescu
2023-05-25 18:41   ` Add initial support " bluez.test.bot
2023-05-25 15:34 ` [PATCH v2 2/6] Add macro definitions for BAP broadcast source support Silviu Florian Barbulescu
2023-05-25 15:34 ` [PATCH v2 3/6] Check for ISO broadcast support in controller Silviu Florian Barbulescu
2023-05-25 15:34 ` [PATCH v2 4/6] Add support for setsockopt (BT_IO_OPT_BASE) Silviu Florian Barbulescu
2023-05-25 15:34 ` [PATCH v2 5/6] Update bluetoothctl with support for broadcast source Silviu Florian Barbulescu
2023-05-25 17:47   ` Luiz Augusto von Dentz
2023-05-25 15:34 ` [PATCH v2 6/6] Add initial support for BAP " Silviu Florian Barbulescu
2023-05-26 22:10 ` [PATCH v2 0/6] " patchwork-bot+bluetooth
2023-05-26 22:37   ` Luiz Augusto von Dentz
2023-05-26 22:40 ` patchwork-bot+bluetooth

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=20230525153452.125789-1-silviu.barbulescu@nxp.com \
    --to=silviu.barbulescu@nxp.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