From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 17e787: doc/btmon: Add Channel Sounding protocol flow docu...
Date: Wed, 01 Apr 2026 12:58:02 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1076017/000000-17e787@github.com> (raw)
Branch: refs/heads/1076017
Home: https://github.com/bluez/bluez
Commit: 17e787538712cddfa378a4fe6a3eb6fa40c3cfd2
https://github.com/bluez/bluez/commit/17e787538712cddfa378a4fe6a3eb6fa40c3cfd2
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-01 (Wed, 01 Apr 2026)
Changed paths:
A doc/btmon-cs.rst
Log Message:
-----------
doc/btmon: Add Channel Sounding protocol flow documentation
Add btmon-cs.rst documenting the complete CS protocol flow as seen
in btmon traces. Covers capability exchange, security enable,
configuration, procedure parameters, enable/disable, subevent
results with all four step modes (Mode 0-3), result status fields,
FAE table exchange, channel classification, CS test mode, the
typical setup sequence, and common issues.
This provides LLM context so automated trace analysis can correctly
interpret CS distance measurement sessions.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-01 19:58 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/1076017/000000-17e787@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