From: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.dentz@gmail.com, quic_mohamull@quicinc.com,
quic_hbandi@quicinc.com, quic_anubhavg@quicinc.com,
Naga Bhavani Akella <nakella@qti.qualcomm.com>
Subject: [PATCH BlueZ v3 0/7] Add ranging provider implementation
Date: Thu, 27 Aug 2026 10:50:27 +0530 [thread overview]
Message-ID: <20260827052034.1374180-1-naga.akella@oss.qualcomm.com> (raw)
From: Naga Bhavani Akella <nakella@qti.qualcomm.com>
This series documents and implements the D-Bus API that lets an
external ranging daemon compute Channel Sounding distance estimates
from the raw procedure data BlueZ reports, and feed them back for
reflection on the device's Channel Sounding interface
Patch 1 documents Ranging, the BlueZ-owned interface
that reflects the provider's Distance estimate for consumption
by desktop clients.
Patch 2 documents RangingProvider, the interface the
registered provider implements to expose per-device distance
estimates.
Patch 3 documents RangingProviderManager, which a
ranging daemon uses to register/unregister itself as a distance
provider.
Patch 4 documents addition of new options (register/unregister)
in bluetoothctl cs menu
Patch 5 and 6 implements Ranging Provider and Rangign Provider Manager
interfaces
Patch 7 implements test/example-ranging-provider,
a simple D-Bus client application for ranging profile
Changes in v3:
- Change interface naming fro CS to ranging
- Add Register/Unregister provider options as part of CS menu
- Add example-ranging-provider to show client application for
ranging profile
Changes in v2:
- Add implementation of ranging provider and ranging provider manager
Naga Bhavani Akella (7):
doc: Add org.bluez.Ranging1 documentation
doc: Add org.bluez.RangingProvider1 documentation
doc: Add org.bluez.RangingProviderManager1 documentation
doc: Modify bluetoothctl-cs documentation
src: Add Ranging provider D-Bus API
client: Add ranging distance display support to bluetoothctl
test: Add Python Ranging Provider example
Makefile.am | 16 +-
Makefile.tools | 1 +
client/cs.c | 514 ++++++++++++++++-
client/cs.h | 6 +
client/main.c | 58 ++
doc/bluetoothctl-cs.rst | 41 ++
doc/org.bluez.Ranging1.rst | 78 +++
doc/org.bluez.RangingProvider1.rst | 92 ++++
doc/org.bluez.RangingProviderManager1.rst | 91 +++
src/adapter.c | 11 +
src/ranging.c | 644 ++++++++++++++++++++++
src/ranging.h | 25 +
test/example-ranging-provider | 222 ++++++++
13 files changed, 1796 insertions(+), 3 deletions(-)
create mode 100644 doc/org.bluez.Ranging1.rst
create mode 100644 doc/org.bluez.RangingProvider1.rst
create mode 100644 doc/org.bluez.RangingProviderManager1.rst
create mode 100644 src/ranging.c
create mode 100644 src/ranging.h
create mode 100644 test/example-ranging-provider
--
next reply other threads:[~2026-08-27 5:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 5:20 Naga Bhavani Akella [this message]
2026-08-27 5:20 ` [PATCH BlueZ v3 1/7] doc: Add org.bluez.Ranging1 documentation Naga Bhavani Akella
2026-08-27 16:16 ` Add ranging provider implementation bluez.test.bot
2026-08-27 5:20 ` [PATCH BlueZ v3 2/7] doc: Add org.bluez.RangingProvider1 documentation Naga Bhavani Akella
2026-08-27 5:20 ` [PATCH BlueZ v3 3/7] doc: Add org.bluez.RangingProviderManager1 documentation Naga Bhavani Akella
2026-08-27 5:20 ` [PATCH BlueZ v3 4/7] doc: Modify bluetoothctl-cs documentation Naga Bhavani Akella
2026-08-27 5:20 ` [PATCH BlueZ v3 5/7] src: Add Ranging provider D-Bus API Naga Bhavani Akella
2026-08-27 5:20 ` [PATCH BlueZ v3 6/7] client: Add ranging distance display support to bluetoothctl Naga Bhavani Akella
2026-08-27 5:20 ` [PATCH BlueZ v3 7/7] test: Add Python Ranging Provider example Naga Bhavani Akella
2026-09-02 17:10 ` [PATCH BlueZ v3 0/7] Add ranging provider implementation 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=20260827052034.1374180-1-naga.akella@oss.qualcomm.com \
--to=naga.akella@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=nakella@qti.qualcomm.com \
--cc=quic_anubhavg@quicinc.com \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohamull@quicinc.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