Bluetooth: controller: split: Fix LENGTH_REQ PDU prepare
There is an obscure bug in the case that CFG_BT_CTLR_PHY is not defined; when a feature-exchange already has happened the lr->max_tx_time and lr->max_rx_time are not calculated. This bug is fixed by this commit. Signed-off-by: Andries Kruithof <Andries.Kruithof@nordicsemi.no>
This commit is contained in:
parent
86116fe7de
commit
26a97aed4f
1 changed files with 1 additions and 1 deletions
|
@ -3170,7 +3170,7 @@ static inline void event_len_prep(struct ll_conn *conn)
|
||||||
#endif /* CONFIG_BT_CTLR_PHY_2M */
|
#endif /* CONFIG_BT_CTLR_PHY_2M */
|
||||||
1)
|
1)
|
||||||
#else /* !CONFIG_BT_CTLR_PHY */
|
#else /* !CONFIG_BT_CTLR_PHY */
|
||||||
0
|
1
|
||||||
#endif /* !CONFIG_BT_CTLR_PHY */
|
#endif /* !CONFIG_BT_CTLR_PHY */
|
||||||
) {
|
) {
|
||||||
u16_t rx_time = PKT_US(LL_LENGTH_OCTETS_RX_MAX, 0);
|
u16_t rx_time = PKT_US(LL_LENGTH_OCTETS_RX_MAX, 0);
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue