All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nitin Jadhav <nitin.jadhav@nxp.com>
To: linux-bluetooth@vger.kernel.org
Cc: devyani.godbole@nxp.com, mahesh.talewad@nxp.com,
	luiz.dentz@gmail.com, nitin.jadhav@nxp.com
Subject: [PATCH BlueZ v2 1/4] lib/uuid.h: Add UUID(s)
Date: Tue,  5 Sep 2023 10:09:09 +0300	[thread overview]
Message-ID: <20230905070912.82340-2-nitin.jadhav@nxp.com> (raw)
In-Reply-To: <20230905070912.82340-1-nitin.jadhav@nxp.com>

Add MICS characteristic uuid(s)

Co-developed-by: Mahesh Talewad <mahesh.talewad@nxp.com>
Signed-off-by: Mahesh Talewad <mahesh.talewad@nxp.com>
Signed-off-by: Nitin Jadhav <nitin.jadhav@nxp.com>
---
 lib/uuid.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/lib/uuid.h b/lib/uuid.h
index cd3b3655f..a79eeee18 100644
--- a/lib/uuid.h
+++ b/lib/uuid.h
@@ -206,6 +206,11 @@ extern "C" {
 #define CS_LOCK						0x2B86
 #define CS_RANK						0x2B87
 
+
+/* Microphone Control Service(MICS) */
+#define MICS_UUID					0x184D
+#define MUTE_CHRC_UUID 				0x2BC3
+
 typedef struct {
 	enum {
 		BT_UUID_UNSPEC = 0,
-- 
2.34.1


  reply	other threads:[~2023-09-05 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  7:09 [PATCH BlueZ v2 0/4] Implementation of MICS and MICP Nitin Jadhav
2023-09-05  7:09 ` Nitin Jadhav [this message]
2023-09-05  7:09 ` [PATCH BlueZ v2 2/4] src/shared/micp.c: To implement MICP profile MICS service Nitin Jadhav
2023-09-05  7:09 ` [PATCH BlueZ v2 3/4] profiles/audio/micp.c: To implement MICP plugin Nitin Jadhav
2023-09-05  7:09 ` [PATCH BlueZ v2 4/4] unit/test-micp-test-mics: To implement unit tester code Nitin Jadhav
2023-09-05 18:25   ` Luiz Augusto von Dentz
2023-09-06  6:39     ` Nitin Jadhav
2023-09-05 18:54 ` [PATCH BlueZ v2 0/4] Implementation of MICS and MICP patchwork-bot+bluetooth

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=20230905070912.82340-2-nitin.jadhav@nxp.com \
    --to=nitin.jadhav@nxp.com \
    --cc=devyani.godbole@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=mahesh.talewad@nxp.com \
    /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.