From: Kevin Dewald <kevin@simpleble.org>
To: linux-bluetooth@vger.kernel.org
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Kevin Dewald <kevin@simpleble.org>
Subject: [PATCH BlueZ v3 0/5] Add Role property to org.bluez.Bearer.LE1
Date: Fri, 9 Oct 2026 11:04:43 -0700 [thread overview]
Message-ID: <20261009180448.29117-1-kevin@simpleble.org> (raw)
Applications acting as a peripheral, or in both roles, cannot tell
whether a connected device is a central that connected to the adapter
or a peripheral the adapter connected to. When several applications
share the adapter, a device object can appear because of any of them,
so the order of events does not answer it either.
bluetoothd already tracks this per bearer from the Device Connected
event. This series exposes it as a Role property on
org.bluez.Bearer.LE1, "central" or "peripheral", present only while
the device is connected over LE, and prints it as LE.Role in
bluetoothctl info. The documentation states that it is the link layer
role and says nothing about GATT client and server roles.
As a step towards marking the bearer interfaces stable, the series also
adds functional tests for them, test/functional/test_bearer.py,
described in doc/functional-bearer.rst. Two hosts connect or pair over
LE or BR/EDR, and each checks the bearer interfaces of the device
object it has for the other: Connect and Disconnect, Connected and the
Disconnected signal with its reason, Paired and Bonded, Connectable for
a connectable advertiser and for a broadcaster, and Role on both sides
of an LE connection.
The five tests take about 45 seconds and passed in five consecutive
runs, and the rest of test-functional still passes.
If these tests cover what you had in mind, I can follow up with a patch
marking the bearer interfaces stable.
Changes in v3:
- Add functional tests for the bearer interfaces, with their
documentation (Luiz)
Changes in v2:
- Move the property from org.bluez.Device1 to org.bluez.Bearer.LE1, so
it is clearly per connection (Luiz)
- State in the documentation that it says nothing about GATT roles
(Luiz)
Kevin Dewald (5):
org.bluez.Bearer: Add Role property
bearer: Add Role property
client: Print LE.Role in info
doc: Add functional-bearer documentation
test: functional: add bearer tests
Makefile.am | 1 +
client/main.c | 1 +
doc/functional-bearer.rst | 141 +++++++++++++++
doc/functional-testing.rst | 1 +
doc/org.bluez.Bearer.LE.rst | 24 +++
src/bearer.c | 42 +++++
src/device.c | 5 +
src/device.h | 1 +
test/functional/test_bearer.py | 302 +++++++++++++++++++++++++++++++++
9 files changed, 518 insertions(+)
create mode 100644 doc/functional-bearer.rst
create mode 100644 test/functional/test_bearer.py
--
2.54.0 (Apple Git-157)
next reply other threads:[~2026-10-09 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 18:04 Kevin Dewald [this message]
2026-10-09 18:04 ` [PATCH BlueZ v3 1/5] org.bluez.Bearer: Add Role property Kevin Dewald
2026-10-09 21:01 ` Add Role property to org.bluez.Bearer.LE1 bluez.test.bot
2026-10-09 18:04 ` [PATCH BlueZ v3 2/5] bearer: Add Role property Kevin Dewald
2026-10-09 18:04 ` [PATCH BlueZ v3 3/5] client: Print LE.Role in info Kevin Dewald
2026-10-09 18:04 ` [PATCH BlueZ v3 4/5] doc: Add functional-bearer documentation Kevin Dewald
2026-10-09 18:04 ` [PATCH BlueZ v3 5/5] test: functional: add bearer tests Kevin Dewald
2026-10-09 20:50 ` [PATCH BlueZ v3 0/5] Add Role property to org.bluez.Bearer.LE1 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=20261009180448.29117-1-kevin@simpleble.org \
--to=kevin@simpleble.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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