From: Ajay KV <ajay.k.v@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: kiran.k@intel.com, Ajay KV <ajay.k.v@intel.com>
Subject: [PATCH BlueZ 2/3] lib/uuid: Add GTBS UUIDS for Call Control Profile.
Date: Tue, 13 Feb 2024 23:56:59 +0200 [thread overview]
Message-ID: <20240213215703.21507-2-ajay.k.v@intel.com> (raw)
In-Reply-To: <20240213215703.21507-1-ajay.k.v@intel.com>
---
lib/uuid.h | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/lib/uuid.h b/lib/uuid.h
index 124e74985a80..8404b287ed01 100644
--- a/lib/uuid.h
+++ b/lib/uuid.h
@@ -221,6 +221,27 @@ extern "C" {
#define MICS_UUID 0x184D
#define MUTE_CHRC_UUID 0x2BC3
+/* Call Control Service(TBS/CCS) */
+#define TBS_UUID 0x184B
+#define GTBS_UUID 0x184C
+
+#define BEARER_PROVIDER_NAME_CHRC_UUID 0x2bb3
+#define BEARER_UCI_CHRC_UUID 0x2bb4
+#define BEARER_TECH_CHRC_UUID 0x2bb5
+#define BEARER_URI_SCHEME_CHRC_UUID 0x2bb6
+#define BEARER_SIGNAL_STR_CHRC_UUID 0x2bb7
+#define BEARER_SIGNAL_INTRVL_CHRC_UUID 0x2bb8
+#define CURR_CALL_LIST_CHRC_UUID 0x2bb9
+#define BEARER_CCID_CHRC_UUID 0x2bba
+#define CALL_STATUS_FLAG_CHRC_UUID 0x2bbb
+#define INCOM_CALL_TARGET_URI_CHRC_UUID 0x2bbc
+#define CALL_STATE_CHRC_UUID 0x2bbd
+#define CALL_CTRL_POINT_CHRC_UUID 0x2bbe
+#define CALL_CTRL_POINT_OPT_OPCODE_CHRC_UUID 0x2bbf
+#define TERMINATION_REASON_CHRC_UUID 0x2bc0
+#define INCOMING_CALL_CHRC_UUID 0x2bc1
+#define CALL_FRIENDLY_NAME_CHRC_UUID 0x2bc2
+
typedef struct {
enum {
BT_UUID_UNSPEC = 0,
--
2.34.1
next prev parent reply other threads:[~2024-02-13 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 21:56 [PATCH BlueZ 1/3] lib/uuid: Add support to compare 16bit uuids Ajay KV
2024-02-13 18:01 ` [BlueZ,1/3] " bluez.test.bot
2024-02-13 20:50 ` [PATCH BlueZ 1/3] " patchwork-bot+bluetooth
2024-02-13 21:56 ` Ajay KV [this message]
2024-02-13 21:57 ` [PATCH BlueZ 3/3] shared/ccp: Add initial code for Call Control Profile for Client Role Ajay KV
2024-02-13 21:57 ` [PATCH v2 1/3] lib/uuid: Add support to compare 16bit uuids Ajay KV
2024-02-13 17:34 ` [v2,1/3] " bluez.test.bot
2024-02-13 20:50 ` [PATCH v2 1/3] " patchwork-bot+bluetooth
2024-02-13 21:57 ` [PATCH v2 2/3] lib/uuid: Add GTBS UUIDs for Call Control Profile Ajay KV
2024-02-13 20:50 ` patchwork-bot+bluetooth
2024-02-13 21:57 ` [PATCH v2 3/3] shared/ccp: Add initial code for Call Control Profile for Client Role Ajay KV
2024-02-13 20:50 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-02-12 16:17 [PATCH BlueZ 1/3] lib/uuid: Add support to compare 16bit uuids Ajay KV
2024-02-12 16:17 ` [PATCH BlueZ 2/3] lib/uuid: Add GTBS UUIDS for Call Control Profile Ajay KV
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240213215703.21507-2-ajay.k.v@intel.com \
--to=ajay.k.v@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.