From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] fee356: shared: remove default settings params from bt_rap...
Date: Tue, 30 Jun 2026 08:45:55 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1119059/000000-74a305@github.com> (raw)
Branch: refs/heads/1119059
Home: https://github.com/bluez/bluez
Commit: fee3563b14f36116bdc4b1dd3bb827ff5113ebc2
https://github.com/bluez/bluez/commit/fee3563b14f36116bdc4b1dd3bb827ff5113ebc2
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M src/shared/rap.h
Log Message:
-----------
shared: remove default settings params from bt_rap_attach_hci
role, cs_sync_ant_sel and max_tx_power were passed into bt_rap_attach_hci
but these are CS default settings that belong to the measurement session,
Callers need to set them via bt_rap_set_default_settings_params() in
start_measurement where they belong, alongside the other per-session
CS parameters
Commit: 810a55beb6a01886ae9b80304d2778637032e677
https://github.com/bluez/bluez/commit/810a55beb6a01886ae9b80304d2778637032e677
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M profiles/ranging/rap.c
M profiles/ranging/rap_hci.c
Log Message:
-----------
profiles: update bt_rap_attach_hci call to drop def settings
role, cs_sync_ant_sel and max_tx_power are no longer passed at attach
time. They are applied via bt_rap_set_default_settings_params() in
start_measurement where they belong, alongside the other per-session
CS parameters
Commit: 7e04dff983faf194a6bf3cde42a73eb538d98e73
https://github.com/bluez/bluez/commit/7e04dff983faf194a6bf3cde42a73eb538d98e73
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M src/btd.h
M src/main.c
M src/main.conf
Log Message:
-----------
rap: remove CS default settings from main.conf
role, cs_sync_ant_sel and max_tx_power were configurable in main.conf
and parsed in main.c, but these are per-measurement parameters that
callers supply via StartMeasurement
Commit: 6a8079c039cc12db471ef2d722f345b9842d6015
https://github.com/bluez/bluez/commit/6a8079c039cc12db471ef2d722f345b9842d6015
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M src/shared/rap.h
Log Message:
-----------
shared: replace the wrapper API
Replace API bt_rap_attach_hci_v2 with
bt_rap_attach_hci which has less parameters
to avoid compilation error for individual patches
Commit: 7441d315e80ffe498e61f618d7d5d5d280c2194a
https://github.com/bluez/bluez/commit/7441d315e80ffe498e61f618d7d5d5d280c2194a
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M profiles/ranging/rap.c
M profiles/ranging/rap_hci.c
Log Message:
-----------
profiles: replace wrapper API
replace bt_rap_attach_hci_v2 with bt_rap_attach_hci API
which has less parameters to avoid compilation error
in individual patchsets
Commit: 74a3059a93b9a31aaa08c2dc354638d54e89a8b6
https://github.com/bluez/bluez/commit/74a3059a93b9a31aaa08c2dc354638d54e89a8b6
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M src/shared/rap.h
Log Message:
-----------
shared: remove wrapper API
Remove bt_rap_attach_hci_v2 wrapper API
which was added to prevent compilation error
in individual patchsets
Compare: https://github.com/bluez/bluez/compare/fee3563b14f3%5E...74a3059a93b9
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-30 15:45 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/1119059/000000-74a305@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.