237c59585e
To make it easier to understand the code, the following was done: - Use INITIATING/ADV for state names that are exclusive to central or peripheral. Previously it was not necessarily clear that the state BT_CONN_CONNECTING was for central only by just looking at where it was used. The terms INITIATING/ADV were used in favor of central and peripheral as these terms also work for SCO connection establishment. - BT_CONN_CONNECTING_SCAN -> BT_CONN_SCAN_BEFORE_INITIATING to make it more clear that we are not scanning and connecting at the same time. The new name should make it more clear why we are scanning - only with the intention to start the initiator later. - BT_CONN_CONNECTING_AUTO -> BT_CONN_INITIATING_FILTER_LIST. This makes it clear that this state is something different than BT_CONN_AUTO_CONNECT. Signed-off-by: Rubin Gerritsen <rubin.gerritsen@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| bt_br_oob_get_local | ||
| bt_id_add | ||
| bt_id_adv_random_addr_check | ||
| bt_id_create | ||
| bt_id_del | ||
| bt_id_delete | ||
| bt_id_get | ||
| bt_id_init | ||
| bt_id_read_public_addr | ||
| bt_id_reset | ||
| bt_id_scan_random_addr_check | ||
| bt_id_set_adv_own_addr | ||
| bt_id_set_adv_private_addr | ||
| bt_id_set_adv_random_addr | ||
| bt_id_set_create_conn_own_addr | ||
| bt_id_set_private_addr | ||
| bt_id_set_scan_own_addr | ||
| bt_le_ext_adv_oob_get_local | ||
| bt_le_oob_get_local | ||
| bt_le_oob_get_sc_data | ||
| bt_le_oob_set_legacy_tk | ||
| bt_le_oob_set_sc_data | ||
| bt_lookup_id_addr | ||
| bt_setup_public_id_addr | ||
| bt_setup_random_id_addr | ||
| mocks | ||
| testing_common_defs.h | ||