All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Sarmanow <as@discnull.de>
To: linux-bluetooth@vger.kernel.org
Cc: Alexander Sarmanow <as@discnull.de>
Subject: [PATCH BlueZ 0/2] org.bluez.LEAdvertisement: Add broadcast name support
Date: Thu, 24 Sep 2026 17:17:18 +0200	[thread overview]
Message-ID: <20260924151720.1769259-1-as@discnull.de> (raw)

From: Alexander Sarmanow (Televic) <as@discnull.de>

This series adds dedicated support for setting the broadcast name via DBus
to the org.bluez.LEAdvertisement object. Should make it easier for upper
layers to set this advertisement property.

The Public Broadcast Profile (PBP v1.0, see section 5.1.1) restricts the
string length to a minimum of 4 and a maximum of 32 characters. If the
provided name is shorter than the minimum, pasring returns an error.If it
exceeds the maximum, it is truncated, consistent with the behavior for the
local name.

The BroadcastName property will be parsed in any case, but only added to
the advertisement data in case it's of type broadcast.

Tested by setting a broadcast name via pipewire bluez spa plugin.

Alexander Sarmanow (2):
  doc/org.bluez.LEAdvertisement: Add broadcast name
  advertising: Add broadcast name property support

 doc/org.bluez.LEAdvertisement.rst |  7 +++++
 src/advertising.c                 | 44 +++++++++++++++++++++++++++++++
 src/shared/ad.h                   |  3 +++
 3 files changed, 54 insertions(+)

-- 
2.30.2


             reply	other threads:[~2026-09-24 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 15:17 Alexander Sarmanow [this message]
2026-09-24 15:17 ` [PATCH BlueZ 1/2] doc/org.bluez.LEAdvertisement: Add broadcast name Alexander Sarmanow
2026-09-24 19:06   ` org.bluez.LEAdvertisement: Add broadcast name support bluez.test.bot
2026-09-24 15:17 ` [PATCH BlueZ 2/2] advertising: Add broadcast name property support Alexander Sarmanow
2026-09-24 15:44 ` [PATCH BlueZ 0/2] org.bluez.LEAdvertisement: Add broadcast name support Luiz Augusto von Dentz
2026-09-24 18:57   ` Alexander Sarmanow

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=20260924151720.1769259-1-as@discnull.de \
    --to=as@discnull.de \
    --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.