michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: L2CAP: Reword K-frame comment

Browse source 
The terminology was not following the Spec wording.

Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
This commit is contained in:
Théo Battrel 2024-03-27 10:43:58 +01:00 • committed by Anas Nashif
commit c0700d9825
1 changed files with 10 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

21
subsys/bluetooth/host/l2cap.c
View file

@ -3072,25 +3072,24 @@ static int bt_l2cap_dyn_chan_send(struct bt_l2cap_le_chan *le_chan, struct net_b
return -EINVAL;
}
/* Prepend SDU "header".
/* Prepend SDU length.
*
* L2CAP LE CoC SDUs are segmented into PDUs and sent over so-called
* K-frames that each have their own L2CAP header (ie channel, PDU
* length).
* L2CAP LE CoC SDUs are segmented and put into K-frames PDUs which have
* their own L2CAP header (i.e. PDU length, channel id).
*
* The SDU header is right before the data that will be segmented and is
* only present in the first segment/PDU. Here's an example:
* The SDU length is right before the data that will be segmented and is
* only present in the first PDU. Here's an example:
*
* Sent data payload of 50 bytes over channel 0x4040 with MPS of 30 bytes:
* First PDU / segment / K-frame:
* First PDU (K-frame):
* | L2CAP K-frame header | K-frame payload |
* | PDU length | Channel ID | SDU header | SDU payload |
* | 30 | 0x4040 | 50 | 28 bytes of data |
* | PDU length | Channel ID | SDU length | SDU payload |
* | 0x001e | 0x4040 | 0x0032 | 28 bytes of data |
*
* Second and last PDU / segment / K-frame:
* Second and last PDU (K-frame):
* | L2CAP K-frame header | K-frame payload |
* | PDU length | Channel ID | rest of SDU payload |
* | 22 | 0x4040 | 22 bytes of data |
* | 0x0016 | 0x4040 | 22 bytes of data |
*/
net_buf_push_le16(buf, sdu_len);