Before a LL_FEATURE_REQ is sent, verify that the Data Length Update procedure is still supported as it could have been unmasked as the result of a previously completed Feature Exchange procedure. Add unit test to verify the case of enqueuing both a Feature Exchange procedure and Data Length Update procedure, where the Feature Exchange procedure would result in the unmasking of the Data Length Update procedure. Signed-off-by: Thomas Ebert Hansen <thoh@oticon.com> |
||
|---|---|---|
| .. | ||
| common | ||
| ctrl_api | ||
| ctrl_chmu | ||
| ctrl_cis_create | ||
| ctrl_cis_terminate | ||
| ctrl_collision | ||
| ctrl_conn_update | ||
| ctrl_cte_req | ||
| ctrl_data_length_update | ||
| ctrl_encrypt | ||
| ctrl_feature_exchange | ||
| ctrl_hci | ||
| ctrl_invalid | ||
| ctrl_le_ping | ||
| ctrl_min_used_chans | ||
| ctrl_phy_update | ||
| ctrl_sca_update | ||
| ctrl_terminate | ||
| ctrl_tx_buffer_alloc | ||
| ctrl_tx_queue | ||
| ctrl_unsupported | ||
| ctrl_version | ||
| mock_ctrl | ||
| uut | ||