Bluetooth: Classic: HFP_HF: Fix AT+CLCC can not be sent issue

[lylezhu2012]

Due to the flag BT_HFP_HF_FLAG_CLCC_PENDING is set when receiving the +CIEV or +CIND notification, the command AT+CLCC will be pending due to the flag is not cleared.

Add a flag BT_HFP_HF_FLAG_INITIATING to indicate the HF initialization is ongoing.

Add a flag BT_HFP_HF_FLAG_QUERY_CALLS to indicate the current calls list needs to be queried.

Set the flag BT_HFP_HF_FLAG_INITIATING at the beginning of the HF initialization. Set the flag BT_HFP_HF_FLAG_QUERY_CALLS instead of setting the flag BT_HFP_HF_FLAG_CLCC_PENDING if the current calls list needs to be queried and the flag BT_HFP_HF_FLAG_INITIATING is set.

After the HF initialization is done, query list of the current calls by calling the function hf_query_current_calls() if the flag BT_HFP_HF_FLAG_QUERY_CALLS is set.

Set the flag BT_HFP_HF_FLAG_CLCC_PENDING if it is not set in the function hf_query_current_calls().

[gzh-terry]

We actually need a interface for the upper layer to query current calls.
Note that Android (i.e., upper layer) needs to send AT+CLCC from its headsetClientStateMachine and is waiting for responses (include the "OK").

It seems like most of the APIs keeps at stack level (similar as Android BTIF/BTA). But for call informations, they become high level APIs (similar as Android AIDL). Indeed it works, but would be a little be hard to migrate to (co-work with) other system.

[lylezhu2012]

We actually need a interface for the upper layer to query current calls. Note that Android (i.e., upper layer) needs to send AT+CLCC from its headsetClientStateMachine and is waiting for responses (include the "OK").

It seems like most of the APIs keeps at stack level (similar as Android BTIF/BTA). But for call informations, they become high level APIs (similar as Android AIDL). Indeed it works, but would be a little be hard to migrate to (co-work with) other system.

Yes. I think we can improve it later.

[lylezhu2012]

Yes. I think we can improve it later.

It is created here #96564

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud