public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: mdzik-sue <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 382bc2: transport: allow setting Metadata property on broa...
Date: Fri, 17 Apr 2026 02:42:37 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1082418/000000-5bea6e@github.com> (raw)

  Branch: refs/heads/1082418
  Home:   https://github.com/bluez/bluez
  Commit: 382bc2eaa84325d86c86e1aff6fa023cbc34e2ca
      https://github.com/bluez/bluez/commit/382bc2eaa84325d86c86e1aff6fa023cbc34e2ca
  Author: Michal Dzik <michal.dzik@streamunlimited.com>
  Date:   2026-04-17 (Fri, 17 Apr 2026)

  Changed paths:
    M profiles/audio/transport.c

  Log Message:
  -----------
  transport: allow setting Metadata property on broadcast

Also fixes a problem where 64-bit iov_len was incorrectly initialized with
32-bit value in dbus_message_iter_get_fixed_array().


  Commit: 90435903ddcfdc9a5bd461bc766f8ed0cb9287e7
      https://github.com/bluez/bluez/commit/90435903ddcfdc9a5bd461bc766f8ed0cb9287e7
  Author: Michal Dzik <michal.dzik@streamunlimited.com>
  Date:   2026-04-17 (Fri, 17 Apr 2026)

  Changed paths:
    M src/shared/bap.c

  Log Message:
  -----------
  shared/bap: run callback after setting the broadcast metadata

Without this callback, dbus property setting will stall.


  Commit: 8407969f173f2d0434adfca2773f497045f0fcad
      https://github.com/bluez/bluez/commit/8407969f173f2d0434adfca2773f497045f0fcad
  Author: Michal Dzik <michal.dzik@streamunlimited.com>
  Date:   2026-04-17 (Fri, 17 Apr 2026)

  Changed paths:
    M profiles/audio/bap.c

  Log Message:
  -----------
  audio/bap: fill BIG and BIS for receiver

This is for some reason a missing feature.
We receive QoS structure from the kernel via BT_ISO_QOS, but BIG and BIS
are not set there. In fact it is even impossible to pass them that way,
as it is only one structure per remote device. That's why we have to parse
BASE data to extract BIS and set it to stream->qos. BIG is not present
explicitely in BASE, but we can use subgroup index with success.

As a result of this commit, MediaTransport1 object has now a valid BIG
and BIS set in QoS property.


  Commit: 5bea6ed98c93bf3b7e0499bc80082f487c03f93e
      https://github.com/bluez/bluez/commit/5bea6ed98c93bf3b7e0499bc80082f487c03f93e
  Author: Michal Dzik <michal.dzik@streamunlimited.com>
  Date:   2026-04-17 (Fri, 17 Apr 2026)

  Changed paths:
    M profiles/audio/transport.c

  Log Message:
  -----------
  audio: update QoS dbus property after it is set

Dbus set and get on QoS property use different data:
- get uses bap->qos
- set uses bap->stream->qos
This works, because bap->qos is a copy of bap->stream->qos. The only
issue is when we set this property and then try to get it. We see old, not
updated copy. Simply calling bap_update_bcast_qos() fixes the problem.


Compare: https://github.com/bluez/bluez/compare/382bc2eaa843%5E...5bea6ed98c93

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

                 reply	other threads:[~2026-04-17  9:42 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/1082418/000000-5bea6e@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