Linux bluetooth development
 help / color / mirror / Atom feed
From: Kevin Dewald <kevin@simpleble.org>
To: linux-bluetooth@vger.kernel.org
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Kevin Dewald <kevin@simpleble.org>
Subject: [PATCH BlueZ 1/5] doc/mgmt: Document Connection Subrate for LE connections and updates
Date: Mon,  2 Nov 2026 23:27:45 -0800	[thread overview]
Message-ID: <20261103072749.50979-2-kevin@simpleble.org> (raw)
In-Reply-To: <20261103072749.50979-1-kevin@simpleble.org>

With "Bluetooth: MGMT: Send Connection Subrate on LE connection and
update", now in bluetooth-next, the kernel also sends the Connection
Subrate event when an LE connection is established and after each LE
Connection Update, so the connection parameters are known on
controllers without the Shorter Connection Interval feature, and a
failed connection rate change reports the current parameters. Document
this, and the Subrate and Continuation_Number values these events
carry.

Assisted-by: Claude:claude-opus-5.5
---
 doc/mgmt-protocol.rst | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/doc/mgmt-protocol.rst b/doc/mgmt-protocol.rst
index ed2bd3349..bf6a3b200 100644
--- a/doc/mgmt-protocol.rst
+++ b/doc/mgmt-protocol.rst
@@ -5520,6 +5520,11 @@ This event indicates that the connection rate has changed for a device. This
 can be a result of a successful LE Connection Rate Request or a change
 initiated by the remote device.
 
+It is also sent when an LE connection is established and after each LE
+Connection Update, which do not report subrating: the Subrate and
+Continuation_Number parameters then keep the values of the last connection
+rate change, or 1 and 0 if there was none.
+
 Possible values for the Address_Type parameter:
 
 .. csv-table::
@@ -5529,7 +5534,8 @@ Possible values for the Address_Type parameter:
 	0x01, LE Public
 	0x02, LE Random
 
-The Status indicates whether the connection rate change was successful.
+The Status indicates whether the connection rate change was successful. When it
+was not, the other parameters are the current ones of the connection.
 
 The Interval parameter specifies the new connection interval in units of
 0.125 ms.
-- 
2.54.0 (Apple Git-157)


  reply	other threads:[~2026-11-03  7:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03  7:27 [PATCH BlueZ 0/5] Add LE connection parameters to org.bluez.Bearer.LE1 Kevin Dewald
2026-11-03  7:27 ` Kevin Dewald [this message]
2026-11-03  8:56   ` bluez.test.bot
2026-11-03  7:27 ` [PATCH BlueZ 2/5] org.bluez.Bearer: Add connection parameter properties Kevin Dewald
2026-11-03  7:27 ` [PATCH BlueZ 3/5] bearer: " Kevin Dewald
2026-11-03  7:27 ` [PATCH BlueZ 4/5] client: Print LE connection parameters in info Kevin Dewald
2026-11-03  7:27 ` [PATCH BlueZ 5/5] test: functional: add bearer connection parameter tests Kevin Dewald
2026-11-03 16:30 ` [PATCH BlueZ 0/5] Add LE connection parameters to org.bluez.Bearer.LE1 patchwork-bot+bluetooth

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=20261103072749.50979-2-kevin@simpleble.org \
    --to=kevin@simpleble.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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