From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] dda6a6: rap: Add Channel Sounding parameter types and APIs
Date: Fri, 10 Jul 2026 01:35:57 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1125185/000000-c90ff7@github.com> (raw)
Branch: refs/heads/1125185
Home: https://github.com/bluez/bluez
Commit: dda6a66bf77cca529b8f11744370bf1b9f918515
https://github.com/bluez/bluez/commit/dda6a66bf77cca529b8f11744370bf1b9f918515
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-10 (Fri, 10 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: c90ff7c1ac6891fb9c027ea272875ae456d41453
https://github.com/bluez/bluez/commit/c90ff7c1ac6891fb9c027ea272875ae456d41453
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-10 (Fri, 10 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.
Compare: https://github.com/bluez/bluez/compare/dda6a66bf77c%5E...c90ff7c1ac68
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-10 8:35 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/1125185/000000-c90ff7@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