From: prathibhamadugonde <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] bc5713: shared/rap: Add client ranging registration and no...
Date: Thu, 04 Jun 2026 14:13:09 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/c6bc42-42b2c5@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: bc5713d69e1e4ef87bc097ecbe941a2162bf0eac
https://github.com/bluez/bluez/commit/bc5713d69e1e4ef87bc097ecbe941a2162bf0eac
Author: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
Date: 2026-06-04 (Thu, 04 Jun 2026)
Changed paths:
M src/shared/rap.c
M src/shared/rap.h
Log Message:
-----------
shared/rap: Add client ranging registration and notification parsing
Read the RAS Features characteristic to determine whether the remote
device supports real-time ranging. If supported, register for real-time
characteristic notifications using the reqtracker for the CS initiator
role.
Parse incoming segmented RAS ranging data notifications by accumulating
segments via iovec and parsing complete subevent headers and CS mode 0-3
step data, including IQ/tone PCT samples, once the last segment arrives.
Commit: 42b2c543a70c882ed12efa06334588b0c45ae0f3
https://github.com/bluez/bluez/commit/42b2c543a70c882ed12efa06334588b0c45ae0f3
Author: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
Date: 2026-06-04 (Thu, 04 Jun 2026)
Changed paths:
M profiles/ranging/rap_hci.c
Log Message:
-----------
profiles/ranging: Fix measured_freq_offset
As per Core spect it is 2 octects not 4.
Compare: https://github.com/bluez/bluez/compare/c6bc42d69661...42b2c543a70c
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-04 21:13 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/master/c6bc42-42b2c5@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