From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e60637: rap: Add Channel Sounding parameter types and APIs
Date: Sun, 12 Jul 2026 05:34:05 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1126078/000000-a317a3@github.com> (raw)
Branch: refs/heads/1126078
Home: https://github.com/bluez/bluez
Commit: e60637ba8cc4fa3eaf41de1f913138af64673571
https://github.com/bluez/bluez/commit/e60637ba8cc4fa3eaf41de1f913138af64673571
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-12 (Sun, 12 Jul 2026)
Changed paths:
M Makefile.am
A src/shared/cs-types.h
M src/shared/rap.h
Log Message:
-----------
rap: Add Channel Sounding parameter types and APIs
Add shared Channel Sounding parameter structures
(bt_rap_le_cs_config, bt_rap_le_cs_frequency and
bt_rap_le_cs_default_settings) for exchanging
CS configuration, frequency, and default settings
between the RAP DBus layer and HCI state machine.
Add getter/setter APIs for CS config, frequency
and default settings, add measurement.
Commit: dbbf2ac08f40b6537568fc2a418c3aeba75842ec
https://github.com/bluez/bluez/commit/dbbf2ac08f40b6537568fc2a418c3aeba75842ec
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-12 (Sun, 12 Jul 2026)
Changed paths:
M src/device.c
Log Message:
-----------
src: Register GATT profiles for Channel Sounding reflector
Probe and accept GATT_UUID profiles on non-initiator (reflector)
devices before gatt_client discovery checks,
ensuring RAP's org.bluez.ChannelSounding1 DBus interface is registered
even when GATT client discovery is skipped.
Commit: 481899b86437b09f50ee68c7ad0e9d1fabe9ce5a
https://github.com/bluez/bluez/commit/481899b86437b09f50ee68c7ad0e9d1fabe9ce5a
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-12 (Sun, 12 Jul 2026)
Changed paths:
M profiles/ranging/rap.c
M profiles/ranging/rap_hci.c
Log Message:
-----------
profiles: Add D-Bus Channel Sounding control APIs
Expose org.bluez.ChannelSounding1 on the device path,
adding SetDefaultSettings, StartMeasurement, and StopMeasurement methods
and an Active property to let external clients configure and
control CS ranging sessions.
Replace hardcoded CS configuration values with configurable HCI accessors
(bt_rap_{get,set}_cs_config_params, bt_rap_{get,set}_cs_freq_params,
bt_rap_{get,set}_default_settings_params).
Add measurement control APIs (bt_rap_start_measurement,
bt_rap_stop_measurement) with optional timeout-based auto-stop
and callbacks for timeout and procedure-state changes,
allowing DBus Active state to reflect actual controller procedure status.
Commit: a317a3fb368cde3546ce52c1371ce57f4947f56a
https://github.com/bluez/bluez/commit/a317a3fb368cde3546ce52c1371ce57f4947f56a
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-12 (Sun, 12 Jul 2026)
Changed paths:
M Makefile.tools
A client/cs.c
A client/cs.h
M client/main.c
Log Message:
-----------
client: Add Channel Sounding shell submenu
Add a cs bt_shell submenu for controlling
org.bluez.ChannelSounding1, supporting measurement start/stop,
default-setting configuration, and session status display.
Maintain reusable validated CS parameters and
track active sessions via D-Bus Active state,
replies, and disconnects.
Integrate with client/main.c to manage per-adapter
ChannelSounding proxies, device resolution,
property updates, and session cleanup.
Compare: https://github.com/bluez/bluez/compare/e60637ba8cc4%5E...a317a3fb368c
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-12 12:34 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/1126078/000000-a317a3@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