[bluez/bluez] c31e90: org.bluez.Bearer: Add Role property

[bluez/bluez] c31e90: org.bluez.Bearer: Add Role property

[Luiz Augusto von Dentz]

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: c31e9091e646b61cfce3634baac03636f2760ac8
      https://github.com/bluez/bluez/commit/c31e9091e646b61cfce3634baac03636f2760ac8
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-09 (Fri, 09 Oct 2026)

  Changed paths:
    M doc/org.bluez.Bearer.LE.rst

  Log Message:
  -----------
  org.bluez.Bearer: Add Role property

This adds Role property to org.bluez.Bearer.LE1 which indicates whether
the remote device is the central or the peripheral of the current LE
connection, so applications can tell a central that connected to the
adapter from a peripheral the adapter connected to.

Assisted-by: Claude:claude-opus-5.5


  Commit: 76890c8fd3255bd1b0d64e3c35abb38ef3d87b22
      https://github.com/bluez/bluez/commit/76890c8fd3255bd1b0d64e3c35abb38ef3d87b22
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-09 (Fri, 09 Oct 2026)

  Changed paths:
    M src/bearer.c
    M src/device.c
    M src/device.h

  Log Message:
  -----------
  bearer: Add Role property

This implements Role property for the LE bearer using the initiator
flag of the Device Connected event, which the kernel sets when the
adapter created the connection as central, and emits PropertiesChanged
along with Connected.

Assisted-by: Claude:claude-opus-5.5


  Commit: 2515706490c2d569885cd553a553de12cb2fc867
      https://github.com/bluez/bluez/commit/2515706490c2d569885cd553a553de12cb2fc867
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-09 (Fri, 09 Oct 2026)

  Changed paths:
    M client/main.c

  Log Message:
  -----------
  client: Print LE.Role in info

This prints the Role property of the LE bearer with the likes of info
command:

bluetoothctl> info <addr>
...
        LE.Connected: yes
        LE.Connectable: yes
        LE.Role: central

Assisted-by: Claude:claude-opus-5.5


  Commit: 926bbc5dfe29a19d579d29fd81d7c5a5952a3ecd
      https://github.com/bluez/bluez/commit/926bbc5dfe29a19d579d29fd81d7c5a5952a3ecd
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-09 (Fri, 09 Oct 2026)

  Changed paths:
    M Makefile.am
    A doc/functional-bearer.rst
    M doc/functional-testing.rst

  Log Message:
  -----------
  doc: Add functional-bearer documentation

Document the bearer functional tests, where two hosts connect or pair
over LE or BR/EDR and each checks the org.bluez.Bearer.LE1 and
org.bluez.Bearer.BREDR1 properties of the device object it has for the
other:

- Connected and Role on both sides of an LE connection, and the
  Disconnected signal with its reason on both sides
- Connectable for a connectable advertiser and for a broadcaster
- Paired, Bonded and Connected after LE and BR/EDR pairing, Role being
  only reported for LE

Assisted-by: Claude:claude-opus-5.5


  Commit: ce448a8a7a3bf538c443235c9c7b38d4aea841cf
      https://github.com/bluez/bluez/commit/ce448a8a7a3bf538c443235c9c7b38d4aea841cf
  Author: Kevin Dewald <kevin@simpleble.org>
  Date:   2026-10-09 (Fri, 09 Oct 2026)

  Changed paths:
    A test/functional/test_bearer.py

  Log Message:
  -----------
  test: functional: add bearer tests

Add tests where host0 connects to or pairs with host1 over LE or
BR/EDR, and both hosts check the properties and the Disconnected
signal of the bearer interfaces of the device object they have for the
other, including the LE Role of each side of the connection.

See doc/functional-bearer.rst for details.

Assisted-by: Claude:claude-opus-5.5


  Commit: 7428ca2df9356363079db0f48412c20cbdb9471f
      https://github.com/bluez/bluez/commit/7428ca2df9356363079db0f48412c20cbdb9471f
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2026-10-09 (Fri, 09 Oct 2026)

  Changed paths:
    M src/device.c

  Log Message:
  -----------
  device: Fix LE bearer Connect not replying

If the ATT socket of an outgoing LE connection connects before the MGMT
Device Connected event is processed, att_connect_cb sets the LE state as
connected, so device_add_connection bails out as already connected and
btd_bearer_connected is never called. Bearer.LE1.Connect is then left
without a reply, the initiator flag is not set and Device1.Connected is
not emitted.

Fix it by calling device_add_connection from att_connect_cb when the LE
state is not yet connected.

Fixes: 4e21ebcaa5d0 ("bearer: Implement Connect/Disconnect methods")
Assisted-by: OpenCode:claude-opus-5.5


Compare: https://github.com/bluez/bluez/compare/b111351fd617...7428ca2df935

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