Bluetooth: TMAP: Fix issues with _SUPPORTED kconfigs

Some of the Kconfig options did not reflect the actual
requirements from the TMAP spec. Relying on the AUDIO_TX
and AUDIO_RX was misleading, as they could be set by
broadcast configurations when the features required
unicast features.

Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>

Author: Thalley

subsys/bluetooth/audio/Kconfig.tmap

@@ -5,18 +5,19 @@
 # SPDX-License-Identifier: Apache-2.0
 #
 config BT_TMAP_CG_SUPPORTED
-	def_bool (BT_CAP_INITIATOR && BT_CAP_COMMANDER && BT_BAP_UNICAST_CLIENT && BT_AUDIO_RX && \
-		  BT_AUDIO_TX && BT_VCP_VOL_CTLR && BT_TBS)
+	def_bool (BT_CAP_INITIATOR && BT_CAP_COMMANDER && BT_BAP_UNICAST_CLIENT && \
+		  BT_BAP_UNICAST_CLIENT_ASE_SRC > 0 && BT_BAP_UNICAST_CLIENT_ASE_SNK > 0 && \
+		  BT_VCP_VOL_CTLR && BT_TBS)
 
 config BT_TMAP_CT_SUPPORTED
-	def_bool BT_CAP_ACCEPTOR && BT_BAP_UNICAST_SERVER
+	def_bool BT_CAP_ACCEPTOR && (BT_ASCS_ASE_SNK > 0 || BT_ASCS_ASE_SRC > 0)
 
 config BT_TMAP_UMS_SUPPORTED
-	def_bool (BT_CAP_INITIATOR && BT_CAP_COMMANDER && BT_BAP_UNICAST_CLIENT && BT_AUDIO_TX && \
-		  BT_VCP_VOL_CTLR && BT_MCS)
+	def_bool (BT_CAP_INITIATOR && BT_CAP_COMMANDER && BT_BAP_UNICAST_CLIENT && \
+		  BT_BAP_UNICAST_CLIENT_ASE_SNK_COUNT > 0 && BT_VCP_VOL_CTLR && BT_MCS)
 
 config BT_TMAP_UMR_SUPPORTED
-	def_bool BT_CAP_ACCEPTOR && BT_BAP_UNICAST_SERVER && BT_VCP_VOL_REND
+	def_bool BT_CAP_ACCEPTOR && BT_ASCS_ASE_SNK > 0 && BT_VCP_VOL_REND
 
 config BT_TMAP_BMS_SUPPORTED
 	def_bool BT_CAP_INITIATOR && BT_BAP_BROADCAST_SOURCE