From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 7c04cb: rap: Add OndemandRanging configuration option
Date: Tue, 08 Sep 2026 10:18:08 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1160130/000000-394aa8@github.com> (raw)
Branch: refs/heads/1160130
Home: https://github.com/bluez/bluez
Commit: 7c04cbcb418d32a30cfb467f1cfe0bec17b3df20
https://github.com/bluez/bluez/commit/7c04cbcb418d32a30cfb467f1cfe0bec17b3df20
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-09-08 (Tue, 08 Sep 2026)
Changed paths:
M src/btd.h
M src/main.c
M src/main.conf
Log Message:
-----------
rap: Add OndemandRanging configuration option
Add a per-adapter config knob under [ChannelSounding] to let the RAS
Initiator use on-demand Ranging Data delivery (Get_Ranging_Data/
ACK_Ranging_Data) instead of real-time notifications. Defaults to
false.
- src/btd.h: add bool ondemand_ranging to struct btd_le_bcs.
- src/main.c: parse "OndemandRanging" into
btd_opts.defaults.bcs.ondemand_ranging.
- src/main.conf: document the new option.
Commit: 4a8187e114426d90a34f25badf8f1118a54071a2
https://github.com/bluez/bluez/commit/4a8187e114426d90a34f25badf8f1118a54071a2
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-09-08 (Tue, 08 Sep 2026)
Changed paths:
M src/shared/rap.c
M src/shared/rap.h
Log Message:
-----------
shared: add support for on-demand notification handling
When OndemandRanging is enabled in main.conf, allow the reflector role
to send on-demand ranging data. In the initiator role, handle
on-demand ranging data notifications and the associated control point
opcodes.
Commit: 394aa8756fd2de2e4816ab61d0c74d07b30f9019
https://github.com/bluez/bluez/commit/394aa8756fd2de2e4816ab61d0c74d07b30f9019
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-09-08 (Tue, 08 Sep 2026)
Changed paths:
M profiles/ranging/rap.c
Log Message:
-----------
profiles: honor OndemandRanging config for RAS Initiator
In rap_accept(), call bt_rap_set_ondemand_ranging(data->rap, true)
before bt_rap_attach() when btd_opts.defaults.bcs.ondemand_ranging is
set, so the initiator uses on-demand ranging data delivery instead of
the default real-time stream.
Compare: https://github.com/bluez/bluez/compare/7c04cbcb418d%5E...394aa8756fd2
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-08 17:18 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/1160130/000000-394aa8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.