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 0/2] Channel Sounding reflector GATT registration and
Date: Fri, 10 Jul 2026 12:38:18 +0530 [thread overview]
Message-ID: <20260710070820.3793624-1-naga.akella@oss.qualcomm.com> (raw)
This series adds the initial plumbing required for Channel Sounding
reflector support and RAP-side management of CS configuration parameters.
The first patch registers Channel Sounding GATT profiles on reflector
devices before GATT client discovery checks, ensuring
org.bluez.ChannelSounding1 interface is available
when discovery is skipped.
The second patch adds shared CS parameter structures and
getter/setter APIs for exchanging configuration, frequency,
default settings and measurement-related data
between RAP and the HCI state machine.
Naga Bhavani Akella (2):
rap: Add Channel Sounding parameter types and APIs
src: Register GATT profiles for Channel Sounding reflector
Makefile.am | 2 +-
src/device.c | 28 ++++++++++++++++++------
src/shared/cs-types.h | 50 +++++++++++++++++++++++++++++++++++++++++++
src/shared/rap.h | 27 ++++++++++++++++++++++-
4 files changed, 98 insertions(+), 9 deletions(-)
create mode 100644 src/shared/cs-types.h
--
next reply other threads:[~2026-07-10 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 7:08 Naga Bhavani Akella [this message]
2026-07-10 7:08 ` [PATCH BlueZ v1 1/2] rap: Add Channel Sounding parameter types and APIs Naga Bhavani Akella
2026-07-10 9:27 ` Channel Sounding reflector GATT registration and bluez.test.bot
2026-07-10 7:08 ` [PATCH BlueZ v1 2/2] src: Register GATT profiles for Channel Sounding reflector 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=20260710070820.3793624-1-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