From: Christian Eggers <ceggers@arri.de>
To: <linux-bluetooth@vger.kernel.org>
Subject: Support for Data Length Extension (DLE)?
Date: Mon, 17 Oct 2022 16:54:04 +0200 [thread overview]
Message-ID: <2264504.ElGaqSPkdT@n95hx1g2> (raw)
When monitoring a Bluetooth connection between two Linux systems
(kernel 5.14 / 5.15 + bluez-5.65), I noticed the following:
> HCI Event: LE Meta Event (0x3e) plen 12 #21108 [hci0] 1650.255887
LE Read Remote Used Features (0x04)
Status: Success (0x00)
Handle: 25 Address: 00:1A:7D:F0:21:40 (OUI 00-1A-7D)
Features: 0xbd 0x5f 0x66 0x00 0x00 0x00 0x00 0x00
...
LE Data Packet Length Extension
...
> ACL Data RX: Handle 25 flags 0x02 dlen 18 #21109 [hci0] 1650.300224
LE L2CAP: LE Connection Request (0x14) ident 1 len 10
PSM: 128 (0x0080)
Source CID: 64
MTU: 672
MPS: 23
Credits: 30
< ACL Data TX: Handle 25 flags 0x00 dlen 18 #21110 [hci0] 1650.300431
LE L2CAP: LE Connection Response (0x15) ident 1 len 10
Destination CID: 64
MTU: 672
MPS: 23
Credits: 30
Result: Connection successful (0x0000)
...
> HCI Event: LE Meta Event (0x3e) plen 11 #21113 [hci0] 1650.345822
LE Data Length Change (0x07)
Handle: 25 Address: 00:1A:7D:F0:21:40 (OUI 00-1A-7D)
Max TX octets: 251
Max TX time: 2120
Max RX octets: 251
Max RX time: 2120
I can't find that HCI_EV_LE_DATA_LEN_CHANGE is implemented anywhere in the kernel nor in bluez userspace.
So why do I get this event? Is it generated by controller firmware itself?
I think that both adapters support DLE. Is there there already support for using it with Linux?
regards
Christian
next reply other threads:[~2022-10-17 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 14:54 Christian Eggers [this message]
2022-10-17 20:11 ` Support for Data Length Extension (DLE)? Luiz Augusto von Dentz
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=2264504.ElGaqSPkdT@n95hx1g2 \
--to=ceggers@arri.de \
--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