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 v1 3/3] profiles: honor OndemandRanging config for RAS Initiator
Date: Mon, 7 Sep 2026 19:26:06 +0530 [thread overview]
Message-ID: <20260907135606.824752-4-naga.akella@oss.qualcomm.com> (raw)
In-Reply-To: <20260907135606.824752-1-naga.akella@oss.qualcomm.com>
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.
---
profiles/ranging/rap.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/profiles/ranging/rap.c b/profiles/ranging/rap.c
index cabf8a5de..b494d188c 100644
--- a/profiles/ranging/rap.c
+++ b/profiles/ranging/rap.c
@@ -1105,6 +1105,9 @@ static int rap_accept(struct btd_service *service)
return -EINVAL;
}
+ if (btd_opts.defaults.bcs.ondemand_ranging)
+ bt_rap_set_ondemand_ranging(data->rap, true);
+
if (!bt_rap_attach(data->rap, client)) {
error("RAP unable to attach");
return -EINVAL;
--
next prev parent reply other threads:[~2026-09-07 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 13:56 [PATCH BlueZ v1 0/3] RAS: Add support for on-demand ranging data Naga Bhavani Akella
2026-09-07 13:56 ` [PATCH BlueZ v1 1/3] rap: Add OndemandRanging configuration option Naga Bhavani Akella
2026-09-07 15:49 ` RAS: Add support for on-demand ranging data bluez.test.bot
2026-09-07 13:56 ` [PATCH BlueZ v1 2/3] shared: add on demand notification handling Naga Bhavani Akella
2026-09-07 13:56 ` Naga Bhavani Akella [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-08 4:27 [PATCH BlueZ v1 0/3] RAS: Add support for on-demand ranging data Naga Bhavani Akella
2026-09-08 4:27 ` [PATCH BlueZ v1 3/3] profiles: honor OndemandRanging config for RAS Initiator 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=20260907135606.824752-4-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