From: Prathibha Madugonde <prathibha.madugonde@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
Subject: [PATCH BlueZ v1 0/2] Channel Sounding: Aggregate procedure data and expose via D-Bus
Date: Fri, 17 Jul 2026 12:56:45 +0530 [thread overview]
Message-ID: <20260717072647.255002-1-prathm@qti.qualcomm.com> (raw)
From: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
This series adds infrastructure to aggregate Channel Sounding (CS)
procedure results from both the local initiator and remote reflector
into a single bcs_procedure_data structure, and exposes the completed
data over D-Bus for use by distance-calculation applications.
Patch overview:
1/2 shared/rap: Add bcs_procedure_data aggregation and procedure data API
2/2 profiles/ranging: Add D-Bus ProcedureData signal for Channel Sounding
Prathibha Madugonde (2):
shared/rap: Add bcs_procedure_data aggregation and procedure data API
profiles/ranging: Add D-Bus ProcedureData signal for Channel Sounding
profiles/ranging/rap.c | 497 ++++++++++++++++++++++++++-
profiles/ranging/rap_hci.c | 59 ++++
src/shared/rap.c | 673 +++++++++++++++++++++++++++++++++++--
src/shared/rap.h | 50 +++
4 files changed, 1242 insertions(+), 37 deletions(-)
--
2.34.1
next reply other threads:[~2026-07-17 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 7:26 Prathibha Madugonde [this message]
2026-07-17 7:26 ` [PATCH BlueZ v1 1/2] shared/rap: Add bcs_procedure_data aggregation and procedure data API Prathibha Madugonde
2026-07-17 9:10 ` Channel Sounding: Aggregate procedure data and expose via D-Bus bluez.test.bot
2026-07-17 7:26 ` [PATCH BlueZ v1 2/2] profiles/ranging: Add D-Bus ProcedureData signal for Channel Sounding Prathibha Madugonde
2026-07-17 15:07 ` Luiz Augusto von Dentz
2026-07-17 15:17 ` Luiz Augusto von Dentz
2026-07-17 15:44 ` Luiz Augusto von Dentz
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=20260717072647.255002-1-prathm@qti.qualcomm.com \
--to=prathibha.madugonde@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