Bluetooth: Mesh: Expose destination address in bt_mesh_msg_ctx
There are valid use cases where the model layer must know the true destination address. So far only the fact that it was one of the addresses that the model subscribes to (its element's unicast included) has been knowable. Solve the issue by moving the destination address from the internal net_rx context to the public bt_mesh_msg_ctx struct. Fixes #7453 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
3be0c56d50
commit
c1c5f3d9a3
6 changed files with 57 additions and 46 deletions
|
@ -130,6 +130,9 @@ struct bt_mesh_msg_ctx {
|
|||
/** Remote address. */
|
||||
u16_t addr;
|
||||
|
||||
/** Destination address of a received message. Not used for sending. */
|
||||
u16_t recv_dst;
|
||||
|
||||
/** Received TTL value. Not used for sending. */
|
||||
u8_t recv_ttl:7;
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue