From: Kyle Pepper <cochcoder@proton.me>
To: linux-bluetooth@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, luiz.dentz@gmail.com, marcel@holtmann.org
Subject: [RFC PATCH v3 0/1] Bluetooth: btusb: UB500 reported maximum data length
Date: Thu, 29 Oct 2026 02:32:46 +0000 [thread overview]
Message-ID: <20261029023235.1280321-1-cochcoder@proton.me> (raw)
In-Reply-To: <20261013032742.497402-1-cochcoder@proton.me>
Hi Luiz,
LE Read Maximum Data Length reports TX/RX251, while LE Read Buffer
Size reports 27/eight. A separate raw HCI test verified sixteen
251-byte packets received byte-for-byte intact and completed, with
one packet outstanding at a time.
RFC v3 replaces 167 with the reported maximum TX length, retaining
eight LE credits. This establishes HCI251 acceptance, not physical
pool capacity or an absolute HCI limit. Audio with the revised
callback remains untested.
Prepared with LLM assistance.
Kyle
Kyle Pepper (1):
Bluetooth: btusb: test reported maximum LE length on TP-Link UB500
drivers/bluetooth/btusb_main.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
base-commit: 1081a6ef8f1e0661fd52eb3f878691b0b96cdff9
--
2.56.0
next prev parent reply other threads:[~2026-10-29 2:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 3:28 [RFC PATCH] Bluetooth: btusb: use shared ACL buffers for TP-Link UB500 Kyle Pepper
2026-10-13 4:24 ` [RFC] " bluez.test.bot
2026-10-28 14:01 ` [RFC PATCH] " cochcoder
2026-10-28 14:57 ` Luiz Augusto von Dentz
2026-10-29 0:13 ` [RFC PATCH v2 0/1] Bluetooth: btusb: UB500 MTU-only revision Kyle Pepper
2026-10-29 0:14 ` [RFC PATCH v2 1/1] Bluetooth: btusb: test larger LE packets on TP-Link UB500 Kyle Pepper
2026-10-29 1:21 ` Luiz Augusto von Dentz
2026-10-29 2:09 ` Bluetooth: btusb: UB500 MTU-only revision bluez.test.bot
2026-10-29 2:32 ` Kyle Pepper [this message]
2026-10-29 2:32 ` [RFC PATCH v3 1/1] Bluetooth: btusb: test reported maximum LE length on TP-Link UB500 Kyle Pepper
2026-10-29 2:36 ` cochcoder
2026-10-29 7:36 ` Bluetooth: btusb: UB500 reported maximum data length 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=20261029023235.1280321-1-cochcoder@proton.me \
--to=cochcoder@proton.me \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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.