media-api: Add Vendor and Metadata

This adds Vendor and Metadata properties to MediaEndpoint1.

1 files changed, 27 insertions, 0 deletions

diff --git a/doc/media-api.txt b/doc/media-api.txt
index 847f8bee7..26527622c 100644
--- a/doc/media-api.txt
+++ b/doc/media-api.txt
@@ -34,11 +34,25 @@ Methods		void RegisterEndpoint(object endpoint, dict properties)
 					match the profile specification which
 					is indicated by the UUID.
 
+				uint16_t, uint16_t Vendor [Optional]:
+
+					Vendor-specific Company ID, Codec ID
+					tuple that the endpoint implements.
+
+					It shall be set to appropriate value
+					when Vendor Specific Codec (0xff)
+					is used.
+
 				array{byte} Capabilities:
 
 					Capabilities blob, it is used as it is
 					so the size and byte order must match.
 
+				array{byte} Metadata [Optional]:
+
+					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
@@ -635,11 +649,24 @@ Properties	string UUID [readonly, optional]:
 			The values should match the profile specification which
 			is indicated by the UUID.
 
+		uint16_t, uint16_t Vendor [readonly, Optional]:
+
+			Vendor-specific Company ID, Codec ID tuple that the
+			endpoint implements.
+
+			It shall be set to appropriate value when Vendor
+			Specific Codec (0xff) is used.
+
 		array{byte} Capabilities [readonly, optional]:
 
 			Capabilities blob, it is used as it is so the size and
 			byte order must match.
 
+		array{byte} Metadata [readonly, Optional]:
+
+			Metadata blob, it is used as it is so the size and
+			byte order must match.
+
 		object Device [readonly, optional]:
 
 			Device object which the endpoint is belongs to.