blackbeard420/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf synced 2025-04-06 06:40:11 -04:00
Code Issues Projects Releases Wiki Activity

ble_mesh: Add comment explaining use of byte order [Zephyr]

Browse Source 
Add comment that explains why a different byte order is used for the
3-byte opcode on the CID part of the opcode.
This commit is contained in:
lly 2020-03-26 11:19:17 +08:00
parent ad14507e3f
commit bbfaaa2044
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
components/bt/esp_ble_mesh/mesh_core/access.c
View File

@ -797,6 +797,10 @@ static int get_opcode(struct net_buf_simple *buf, u32_t *opcode)
} }
*opcode = net_buf_simple_pull_u8(buf) << 16; *opcode = net_buf_simple_pull_u8(buf) << 16;
/* Using LE for the CID since the model layer is defined as
* little-endian in the mesh spec and using BT_MESH_MODEL_OP_3
* will declare the opcode in this way.
*/
*opcode |= net_buf_simple_pull_le16(buf); *opcode |= net_buf_simple_pull_le16(buf);
return 0; return 0;
} }
@ -921,6 +925,10 @@ void bt_mesh_model_msg_init(struct net_buf_simple *msg, u32_t opcode)
break; break;
case 3: case 3:
net_buf_simple_add_u8(msg, ((opcode >> 16) & 0xff)); net_buf_simple_add_u8(msg, ((opcode >> 16) & 0xff));
/* Using LE for the CID since the model layer is defined as
* little-endian in the mesh spec and using BT_MESH_MODEL_OP_3
* will declare the opcode in this way.
*/
net_buf_simple_add_le16(msg, opcode & 0xffff); net_buf_simple_add_le16(msg, opcode & 0xffff);
break; break;
default: default: