From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 7059a2: shared: Add create_context CS config parameter
Date: Fri, 17 Jul 2026 07:17:29 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1129618/000000-9efbc3@github.com> (raw)
Branch: refs/heads/1129618
Home: https://github.com/bluez/bluez
Commit: 7059a2547f09eb71e3fe0faf597918d9e658ed73
https://github.com/bluez/bluez/commit/7059a2547f09eb71e3fe0faf597918d9e658ed73
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M src/shared/cs-types.h
Log Message:
-----------
shared: Add create_context CS config parameter
Add create_context in bt_rap_le_cs_config structure
Commit: ee37dfde9ccfd98fd8ac9d19065d10b654c6db0b
https://github.com/bluez/bluez/commit/ee37dfde9ccfd98fd8ac9d19065d10b654c6db0b
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M profiles/ranging/rap.c
M profiles/ranging/rap_hci.c
Log Message:
-----------
profiles: Add create_context param as part of CS Create Config cmd
- Add the create_context field to the CS Create Config command.
- Route HCI command-send failures and non-zero-status completion
events to CS_STATE_HOLD instead of CS_STATE_STOPPED.
reserving CS_STATE_STOPPED for the clean/expected
stop (Procedure Enable Complete with state == 0x00)
Commit: 54de92d0bf259b924f89566ab777043fa467d900
https://github.com/bluez/bluez/commit/54de92d0bf259b924f89566ab777043fa467d900
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M client/cs.c
M client/cs.h
Log Message:
-----------
client: Add create_context CS config parameter
- Add the create_context field to the CS config parameter table so
bluetoothctl can control whether cs.start writes the CS configuration
to the local Controller only (0x00) or to both local and remote
Controllers via the CS Configuration procedure (0x01), matching the
Create_Context field of the LE CS Create Config HCI command
- Change the license in cs.c and cs.h.
- Drop RangingInterface support for now,
as it is still under discussion.
Commit: 9efbc3b2c56a230045209606316e6bcb3dee6f5e
https://github.com/bluez/bluez/commit/9efbc3b2c56a230045209606316e6bcb3dee6f5e
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M doc/bluetoothctl-cs.rst
Log Message:
-----------
doc: Document create_context in bluetoothctl-cs.rst
Document the new create_context parameter introduced in client/cs.c.
Compare: https://github.com/bluez/bluez/compare/7059a2547f09%5E...9efbc3b2c56a
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-17 14:17 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/1129618/000000-9efbc3@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.