From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v1] Bluetooth: hci_sync: Fix invalid Supervision_Timeout in LE Set Default Rate
Date: Thu, 15 Oct 2026 11:39:09 -0400 [thread overview]
Message-ID: <20261015153909.1870855-1-luiz.dentz@gmail.com> (raw)
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
The LE Set Default Rate Parameters command is rejected with Invalid HCI
Command Parameters (0x12) because the Supervision_Timeout of 120 ms is
exactly the minimum recommended by HOGP v1.2:
Greater than or equal to (1 + Peripheral Latency) x Subrate max x
Connection Interval max x 2
But the Core spec treats the equality as invalid:
BLUETOOTH CORE SPECIFICATION Version 6.3 | Vol 4, Part E
7.8.158. LE Set Default Rate Parameters command
If Connection_Interval_Max x Subrate_Max x (Max_Latency + 1) is
greater than or equal to Supervision_Timeout x 40, the Controller
shall return the error code Invalid HCI Command Parameters (0x12).
With the current values 0x78 x 4 x 1 = 480 >= 0x0c x 40 = 480.
Fix this by using 2 s as the default Supervision_Timeout, which is 10x
lower than the 20 s used for non-SCI connections while still well above
the minimum required, and make sure it remains above the minimum in
case interval_max is raised to match the controller's minimum supported
connection interval.
Fixes: 2f8784cfe8a9 ("Bluetooth: Add support for Shorter Connection Interval (SCI) feature")
Assisted-by: OpenCode:claude-opus-5.5
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
---
net/bluetooth/hci_sync.c | 30 +++++++++++++++++++++++++++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/net/bluetooth/hci_sync.c b/net/bluetooth/hci_sync.c
index 03f706c1f815..7ac26daba966 100644
--- a/net/bluetooth/hci_sync.c
+++ b/net/bluetooth/hci_sync.c
@@ -4828,6 +4828,9 @@ static int hci_le_set_def_rate_sync(struct hci_dev *hdev)
struct hci_cp_le_set_def_rate cp;
u16 interval_min = 0x000a; /* 1.25 ms */
u16 interval_max = 0x0078; /* 15 ms */
+ u16 subrate_max = 0x0004;
+ u16 max_latency = 0x0000;
+ u32 supv_timeout;
if (!le_sci_capable(hdev))
return 0;
@@ -4852,10 +4855,31 @@ static int hci_le_set_def_rate_sync(struct hci_dev *hdev)
cp.interval_min = cpu_to_le16(interval_min);
cp.interval_max = cpu_to_le16(interval_max);
cp.subrate_min = cpu_to_le16(0x0001);
- cp.subrate_max = cpu_to_le16(0x0004);
- cp.max_latency = cpu_to_le16(0x0000);
+ cp.subrate_max = cpu_to_le16(subrate_max);
+ cp.max_latency = cpu_to_le16(max_latency);
cp.cont_num = cpu_to_le16(0x0001);
- cp.supv_timeout = cpu_to_le16(0x000c); /* 120 ms */
+
+ /* HOGP v1.2 recommends a Supervision_Timeout greater than or equal to
+ * (1 + Max_Latency) x Subrate_Max x Connection_Interval_Max x 2, but
+ * the Core spec treats the equality as invalid:
+ *
+ * BLUETOOTH CORE SPECIFICATION Version 6.3 | Vol 4, Part E
+ * 7.8.158. LE Set Default Rate Parameters command
+ *
+ * If Connection_Interval_Max x Subrate_Max x (Max_Latency + 1) is
+ * greater than or equal to Supervision_Timeout x 40, the Controller
+ * shall return the error code Invalid HCI Command Parameters (0x12).
+ *
+ * So default to 2 s, 10x lower than the 20 s used for non-SCI
+ * connections while still well above the minimum required, but make
+ * sure it stays strictly above the minimum in case interval_max has
+ * been raised.
+ */
+ supv_timeout = (u32)interval_max * subrate_max * (max_latency + 1);
+ supv_timeout = supv_timeout / 40 + 1;
+ supv_timeout = clamp_t(u32, max_t(u32, supv_timeout, 0x00c8),
+ 0x000a, 0x0c80);
+ cp.supv_timeout = cpu_to_le16(supv_timeout);
/* The connection event length recommended in requests by a Peripheral
* uses units of 125 us with a valid range of 0x0001 to 0x7CFF
--
2.56.0
reply other threads:[~2026-10-15 15:39 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=20261015153909.1870855-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