esp_hf_client_deinit() function

De-initialize for HFP client module. This function should be called only after esp_bluedroid_enable() completes successfully. ESP_HF_CLIENT_PROF_STATE_EVT with ESP_HF_DEINIT_SUCCESS will reported to the APP layer.

Syntax

Show:

Summary

Declaration

from esp_hf_client_api.h:356

esp_err_t esp_hf_client_deinit(void);

Return value

- ESP_OK: success - ESP_ERR_INVALID_STATE: if bluetooth stack is not yet enabled - ESP_FAIL: others

References

Code

Location

esp_err_t esp_hf_client_deinit(void)

esp_hf_client_api.c:49

esp_err_t esp_hf_client_deinit(void);

esp_hf_client_api.h:356

Call Tree

esp_hf_client_deinit() calls 2 functions:

esp_hf_client_deinit()

btc_transfer_context()

esp_bluedroid_get_status()

Data Use

esp_hf_client_deinit() reads 5 variables and writes 3 variables:

btc_sig_t::BTC_SIG_API_CALL

btc_pid_t::BTC_PID_HF_CLIENT

esp_bluedroid_status_t::ESP_BLUEDROID_STATUS_ENABLED

bt_status_t::BT_STATUS_SUCCESS

btc_hf_client_act_t::BTC_HF_CLIENT_DEINIT_EVT

esp_hf_client_deinit()

btc_msg::sig

btc_msg::pid

btc_msg::act

Class Tree

All items filtered out

Override Tree

All items filtered out

Implementations

All items filtered out

Instances

Lifecycle

All items filtered out