Linux bluetooth development
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v1 1/2] monitor: Add Minimum Supported Connection Interval
Date: Tue, 13 Oct 2026 10:02:54 -0400	[thread overview]
Message-ID: <20261013140255.521668-1-luiz.dentz@gmail.com> (raw)

From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

The LE Read Connection Interval response carries a
Minimum_Supported_Connection_Interval octet between the status and
Num_Groups, in units of 125 us with a range of 0x03 to 0x3C. Add it to
the structure and decode it.

Assisted-by: OpenCode:claude-opus-5.5
---
 monitor/bt.h     | 1 +
 monitor/packet.c | 2 ++
 2 files changed, 3 insertions(+)

diff --git a/monitor/bt.h b/monitor/bt.h
index 6efccb27e758..2ddf37ccc22f 100644
--- a/monitor/bt.h
+++ b/monitor/bt.h
@@ -3242,6 +3242,7 @@ struct bt_hci_le_conn_interval_group {
 
 struct bt_hci_rsp_le_read_conn_interval {
 	uint8_t  status;
+	uint8_t  min;
 	uint8_t  num_grps;
 	struct bt_hci_le_conn_interval_group grps[0];
 } __attribute__ ((packed));
diff --git a/monitor/packet.c b/monitor/packet.c
index 8450347fc56b..fe7b054dd7cb 100644
--- a/monitor/packet.c
+++ b/monitor/packet.c
@@ -10276,6 +10276,8 @@ static void le_read_conn_interval_rsp(uint16_t index, const void *data,
 	uint8_t i;
 
 	print_status(rsp->status);
+	print_field("Minimum Supported Interval: %.3f msec (0x%2.2x)",
+						rsp->min * 0.125, rsp->min);
 	print_field("Number of Groups: %u", rsp->num_grps);
 
 	if (!rsp->num_grps)
-- 
2.56.0


             reply	other threads:[~2026-10-13 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 14:02 Luiz Augusto von Dentz [this message]
2026-10-13 14:02 ` [PATCH BlueZ v1 2/2] emulator: Add Minimum Supported Connection Interval Luiz Augusto von Dentz
2026-10-13 19:59 ` [BlueZ,v1,1/2] monitor: " bluez.test.bot

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=20261013140255.521668-1-luiz.dentz@gmail.com \
    --to=luiz.dentz@gmail.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