All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhay Maheta <abhay.maheshbhai.maheta@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Abhay Maheta <abhay.maheshbhai.maheta@intel.com>
Subject: [PATCH BlueZ v2 4/6] media-api: Add CompanyID, VendorCodecID, Metadata
Date: Thu, 29 Dec 2022 17:58:21 +0530	[thread overview]
Message-ID: <20221229122821.340073-5-abhay.maheshbhai.maheta@intel.com> (raw)
In-Reply-To: <20221229122821.340073-1-abhay.maheshbhai.maheta@intel.com>

This adds CompanyID, VendorCodecID, Metadata for RegisterEndpoint method
---
 doc/media-api.txt | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/doc/media-api.txt b/doc/media-api.txt
index 847f8bee7..7bfa8a52b 100644
--- a/doc/media-api.txt
+++ b/doc/media-api.txt
@@ -34,11 +34,29 @@ Methods		void RegisterEndpoint(object endpoint, dict properties)
 					match the profile specification which
 					is indicated by the UUID.
 
+				uint16_t CompanyID [BAP only]:
+
+					Assigned number of Company ID that the
+					endpoint implements. It should be set to
+					appropriate value when Vendor Specific
+					Codec is used.
+
+				uint16_t VendorCodecID [BAP only]:
+
+					Vendor-specific codec ID that the endpoint
+					implements. It should be set to appropriate
+					value when Vendor Specific Codec is used.
+
 				array{byte} Capabilities:
 
 					Capabilities blob, it is used as it is
 					so the size and byte order must match.
 
+				array{byte} Metadata [BAP only]:
+
+					Metadata blob, it is used as it is
+					so the size and byte order must match.
+
 			Possible Errors: org.bluez.Error.InvalidArguments
 					 org.bluez.Error.NotSupported - emitted
 					 when interface for the end-point is
-- 
2.25.1


  parent reply	other threads:[~2022-12-29 12:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29 12:28 [PATCH BlueZ v2 0/6] To add support for Metadata, CID, VID Abhay Maheta
2022-12-29 12:22 ` Paul Menzel
2022-12-29 15:57   ` Maheta, Abhay
2022-12-29 12:28 ` [PATCH BlueZ v2 1/6] shared/bap: Fix handling for Company ID and Vendor Codec ID Abhay Maheta
2022-12-29 14:17   ` To add support for Metadata, CID, VID bluez.test.bot
2022-12-29 12:28 ` [PATCH BlueZ v2 2/6] shared/bap: Add support to set stream metadata Abhay Maheta
2022-12-29 12:28 ` [PATCH BlueZ v2 3/6] profiles: Add Support for Metadata, CID and VID Abhay Maheta
2022-12-29 12:28 ` Abhay Maheta [this message]
2022-12-29 12:28 ` [PATCH BlueZ v2 5/6] client/player: Add support for Company ID, Vendor ID in BAP Profile Abhay Maheta
2022-12-29 12:28 ` [PATCH BlueZ v2 6/6] client/player: Add support for Metadata " Abhay Maheta

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=20221229122821.340073-5-abhay.maheshbhai.maheta@intel.com \
    --to=abhay.maheshbhai.maheta@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.