Bluetooth: controller: using REJECT_IND when EXT_IND was not negotiated

Unless a feature exchange determines support for REJECT_EXT_IND use
REJECT_IND for collision rejection

Signed-off-by: Erik Brockhoff <erbr@oticon.com>
This commit is contained in:
Erik Brockhoff 2022-04-06 12:42:21 +02:00 committed by Carles Cufí
commit 26f6941048
4 changed files with 18 additions and 5 deletions

View file

@ -918,6 +918,9 @@ void test_conn_update_central_loc_collision(void)
/* Role */
test_set_role(&conn, BT_HCI_ROLE_CENTRAL);
/* Emulate valid feature exchange */
conn.llcp.fex.valid = 1;
/* Connect */
ull_cp_state_set(&conn, ULL_CP_CONNECTED);
@ -941,8 +944,6 @@ void test_conn_update_central_loc_collision(void)
/* Release Tx */
ull_cp_release_tx(&conn, tx);
/**/
/* Prepare */
event_prepare(&conn);

View file

@ -699,6 +699,9 @@ void test_phy_update_central_loc_collision(void)
/* Role */
test_set_role(&conn, BT_HCI_ROLE_CENTRAL);
/* Emulate valid feature exchange */
conn.llcp.fex.valid = 1;
/* Connect */
ull_cp_state_set(&conn, ULL_CP_CONNECTED);

View file

@ -75,6 +75,10 @@
#define CONFIG_BT_CTLR_CONN_PARAM_REQ y
#endif
#ifndef CONFIG_BT_CTLR_EXT_REJ_IND
#define CONFIG_BT_CTLR_EXT_REJ_IND y
#endif
#ifndef CONFIG_BT_CTLR_XTAL_ADVANCED
#define CONFIG_BT_CTLR_XTAL_ADVANCED y
#endif