From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e8cdd5: doc: Add org.bluez.Ranging1 documentation
Date: Thu, 27 Aug 2026 08:27:42 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1152414/000000-2e92f8@github.com> (raw)
Branch: refs/heads/1152414
Home: https://github.com/bluez/bluez
Commit: e8cdd5d30e733c53f420691dbb88fcd7fcee120c
https://github.com/bluez/bluez/commit/e8cdd5d30e733c53f420691dbb88fcd7fcee120c
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M Makefile.am
A doc/org.bluez.Ranging1.rst
Log Message:
-----------
doc: Add org.bluez.Ranging1 documentation
Document org.bluez.Ranging1 interface, which
exposes the Distance estimate computed by an
external ranging provider registered via
RangingProviderManager.
Add org.bluez.ChannelSounding1.rst to EXTRA_DIST
Commit: ec7f3986933b40b89b9fcf6241649553143ea946
https://github.com/bluez/bluez/commit/ec7f3986933b40b89b9fcf6241649553143ea946
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M Makefile.am
A doc/org.bluez.RangingProvider1.rst
Log Message:
-----------
doc: Add org.bluez.RangingProvider1 documentation
Document org.bluez.RangingProvider1 interface,
implemented by external clients to expose per-device Channel Sounding
distance estimates that BlueZ reflects onto the corresponding device
object.
Commit: 63d6e092c6eb7c05413f223f474078c4e0f7db7e
https://github.com/bluez/bluez/commit/63d6e092c6eb7c05413f223f474078c4e0f7db7e
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M Makefile.am
A doc/org.bluez.RangingProviderManager1.rst
Log Message:
-----------
doc: Add org.bluez.RangingProviderManager1 documentation
Document org.bluez.RangingProviderManager1 interface,
used by external clients to register and unregister
themselves as Channel Sounding distance providers via
RegisterRangingProvider/UnregisterRangingProvider
Commit: a27cde3ba9155a0b09fab860a15677ad2e032d13
https://github.com/bluez/bluez/commit/a27cde3ba9155a0b09fab860a15677ad2e032d13
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M doc/bluetoothctl-cs.rst
Log Message:
-----------
doc: Modify bluetoothctl-cs documentation
Add documentation for register-provider and
unregister-provider cs menu options
Commit: 938bcfda7c8c3e6cca81de76148754fe1cd91794
https://github.com/bluez/bluez/commit/938bcfda7c8c3e6cca81de76148754fe1cd91794
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M Makefile.am
M src/adapter.c
A src/ranging.c
A src/ranging.h
Log Message:
-----------
src: Add Ranging provider D-Bus API
Introduce org.bluez.Ranging1 and
org.bluez.RangingProvider1/ RangingProviderManager1
D-Bus interfaces
External providers can register a root path
via RegisterDistanceProvider and expose per-device
RangingProvider objects; updates to their Distance
property are mirrored onto exported Ranging objects via
btd_ranging_update(), emitting a PropertiesChanged signal.
The Ranging provider manager is wired into the adapter lifecycle,
created on adapter setup and destroyed on adapter
removal.
Commit: e48adbe73547d39bf4eb565525ab1a1b6f4e0c01
https://github.com/bluez/bluez/commit/e48adbe73547d39bf4eb565525ab1a1b6f4e0c01
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M client/cs.c
M client/cs.h
M client/main.c
Log Message:
-----------
client: Add ranging distance display support to bluetoothctl
Track org.bluez.Ranging proxies and append/remove them
on InterfacesAdded/InterfacesRemoved.
Print the Distance property on PropertiesChanged,
and show it under info option alongside the existing
Battery Percentage and CS Active properties.
Add register-provider and unregister-provider options
as reference implementation.
Commit: 2e92f87fdfc981cec6f8234e908356675fbb724d
https://github.com/bluez/bluez/commit/2e92f87fdfc981cec6f8234e908356675fbb724d
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M Makefile.tools
A test/example-ranging-provider
Log Message:
-----------
test: Add Python Ranging Provider example
This patch introduces test/example-ranging-provider which implements
a simple D-Bus client application for ranging profile.
Compare: https://github.com/bluez/bluez/compare/e8cdd5d30e73%5E...2e92f87fdfc9
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-27 15:27 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/1152414/000000-2e92f8@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