Linux bluetooth development
 help / color / mirror / Atom feed
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 <naga.akella@oss.qualcomm.com>
Subject: [PATCH BlueZ v2 0/3] Add CS procedure data aggregation and D-Bus export
Date: Wed, 29 Jul 2026 16:00:16 +0530	[thread overview]
Message-ID: <20260729103019.4178720-1-naga.akella@oss.qualcomm.com> (raw)

This series adds support for collecting, aggregating, and exporting
Channel Sounding procedure data to userspace.

The first patch introduces a new procedure-data aggregation layer in
shared/rap. It tracks local initiator and remote reflector results for
each procedure, combines them once both sides are complete, and provides
a callback-based API for consumers.

The second patch builds on this infrastructure by serializing completed
CS procedure data into a binary blob and exposing it through a new
ProcedureData signal on the CS D-Bus interface. This allows external
ranging estimation daemons to consume raw controller measurement data
without requiring BlueZ to expose or maintain a fixed D-Bus structure
for evolving CS result formats.

The final patch updates the D-Bus API documentation to reflect the new
signal format


Naga Bhavani Akella (2):
  profiles/ranging: Emit CS ProcedureData signal over D-Bus
  doc: Update ProcedureData signal doc for byte-blob format

Prathibha Madugonde (1):
  shared/rap: Add bcs_procedure_data aggregation and procedure data API

 doc/org.bluez.ChannelSounding1.rst | 365 ++++++----------
 profiles/ranging/rap.c             | 285 +++++++++++-
 profiles/ranging/rap_hci.c         |  59 +++
 src/shared/rap.c                   | 673 +++++++++++++++++++++++++++--
 src/shared/rap.h                   |  50 +++
 5 files changed, 1153 insertions(+), 279 deletions(-)

-- 


             reply	other threads:[~2026-07-29 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 10:30 Naga Bhavani Akella [this message]
2026-07-29 10:30 ` [PATCH BlueZ v2 1/3] shared/rap: Add bcs_procedure_data aggregation and procedure data API Naga Bhavani Akella
2026-07-29 12:29   ` Add CS procedure data aggregation and D-Bus export bluez.test.bot
2026-07-29 10:30 ` [PATCH BlueZ v2 2/3] profiles/ranging: Emit CS ProcedureData signal over D-Bus Naga Bhavani Akella
2026-07-29 10:30 ` [PATCH BlueZ v2 3/3] doc: Update ProcedureData signal doc for byte-blob format Naga Bhavani Akella

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=20260729103019.4178720-1-naga.akella@oss.qualcomm.com \
    --to=naga.akella@oss.qualcomm.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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