Bluetooth: Classic: CLCC report NULL when finish.

bug: v/78002

Rootcause: The CLCC API does not report when it finishes, app cannot know whether the CLCC procedure has ended.

Signed-off-by: liyuheng <[email protected]>

Author: expliyh

include/zephyr/bluetooth/classic/hfp_hf.h

@@ -493,7 +493,7 @@ struct bt_hfp_hf_cb {
 	 *  If this callback is provided it will be called whenever the
 	 *  result code `+CLCC: <idx>,<dir>,<status>,<mode>,<mprty>[,<number>,<type>]`
 	 *  is received from AG.
-	 *  If the request is failed or no active calls, the callback will not be called.
+	 *  If the request is finished (success or fail), the callback will be called with a null *call.
 	 *  If the @ref bt_hfp_hf_current_call::number is NULL, the
 	 *  @ref bt_hfp_hf_current_call::type shall be ignored.
 	 *

subsys/bluetooth/host/classic/hfp_hf.c

@@ -504,6 +504,11 @@ static int clcc_finish(struct at_client *hf_at, enum at_result result,
 		clear_call_without_clcc(hf);
 	}
 
+	if (atomic_test_bit(hf->flags, BT_HFP_HF_FLAG_USR_CLCC_CMD) &&
+	    (bt_hf->query_call != NULL)) {
+		bt_hf->query_call(hf, NULL);
+	}
+
 	atomic_clear_bit(hf->flags, BT_HFP_HF_FLAG_USR_CLCC_CMD);
 	atomic_clear_bit(hf->flags, BT_HFP_HF_FLAG_CLCC_PENDING);