Bluetooth: controller: legacy: Fix tx_time calculation for length update
Fix tx_time calculation for the case that BT_CTRL_PHY is defined and there has not been a feature exchange. Signed-off-by: Wolfgang Puffitsch <wopu@demant.com> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
This commit is contained in:
parent
41e6016885
commit
f5bbb4d3fd
1 changed files with 5 additions and 0 deletions
|
@ -8405,8 +8405,13 @@ static inline int event_len_prep(struct connection *conn)
|
|||
) {
|
||||
lr->max_rx_time =
|
||||
RADIO_PKT_TIME(LL_LENGTH_OCTETS_RX_MAX, 0);
|
||||
#if defined(CONFIG_BT_CTLR_PHY)
|
||||
lr->max_tx_time = conn->default_tx_time;
|
||||
#else /* !CONFIG_BT_CTLR_PHY */
|
||||
lr->max_tx_time =
|
||||
RADIO_PKT_TIME(conn->default_tx_octets, 0);
|
||||
#endif /* !CONFIG_BT_CTLR_PHY */
|
||||
|
||||
#if defined(CONFIG_BT_CTLR_PHY)
|
||||
#if defined(CONFIG_BT_CTLR_PHY_CODED)
|
||||
} else if (conn->llcp_feature.features &
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue