From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v2 1/8] doc/media-api: Enable MediaEndpoint to expose remote SEP
Date: Tue, 15 Jan 2019 11:10:16 -0300 [thread overview]
Message-ID: <20190115141023.353-1-luiz.dentz@gmail.com> (raw)
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
This adds the possibility to expose remote SEP using MediaEndpoint
interface to allow setting a configuration.
---
doc/media-api.txt | 27 +++++++++++++++++++++++++--
1 file changed, 25 insertions(+), 2 deletions(-)
diff --git a/doc/media-api.txt b/doc/media-api.txt
index b5ad2db12..af9485342 100644
--- a/doc/media-api.txt
+++ b/doc/media-api.txt
@@ -500,14 +500,23 @@ Properties object Player [readonly]
MediaEndpoint1 hierarchy
========================
-Service unique name
+Service unique name (Server role)
+ org.bluez (Client role)
Interface org.bluez.MediaEndpoint1
-Object path freely definable
+Object path freely definable (Server role)
+ [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX/sepX
+ (Client role)
Methods void SetConfiguration(object transport, dict properties)
Set configuration for the transport.
+ For client role transport must be set with a server
+ endpoint oject which will be configured and the
+ properties must contain the following properties:
+
+ array{byte} Capabilities
+
array{byte} SelectConfiguration(array{byte} capabilities)
Select preferable configuration from the supported
@@ -532,6 +541,20 @@ Methods void SetConfiguration(object transport, dict properties)
endpoint, because when this method gets called it has
already been unregistered.
+Properties string UUID [readonly, optional]:
+
+ UUID of the profile which the endpoint is for.
+
+ byte Codec [readonly, optional]:
+
+ Assigned number of codec that the endpoint implements.
+ The values should match the profile specification which
+ is indicated by the UUID.
+
+ array{byte} Capabilities [readonly, optional]:
+
+ Capabilities blob, it is used as it is so the size and
+ byte order must match.
MediaTransport1 hierarchy
=========================
--
2.17.2
next reply other threads:[~2019-01-15 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 14:10 Luiz Augusto von Dentz [this message]
2019-01-15 14:10 ` [PATCH v2 2/8] a2dp: Expose remote SEP Luiz Augusto von Dentz
2019-01-15 14:10 ` [PATCH v2 3/8] doc/media-api: Add Endpoint property to MediaTransport Luiz Augusto von Dentz
2019-01-15 14:10 ` [PATCH v2 4/8] a2dp: Implement MediaTransport.Endpoint Luiz Augusto von Dentz
2019-01-15 14:10 ` [PATCH v2 5/8] doc/settings-storage: Add Endpoint group to cache Luiz Augusto von Dentz
2019-01-15 14:10 ` [PATCH v2 6/8] a2dp: Cache remote endpoints Luiz Augusto von Dentz
2019-01-15 14:10 ` [PATCH v2 7/8] doc/media-api: Add Device property to MediaEndpoint Luiz Augusto von Dentz
2019-01-15 14:10 ` [PATCH v2 8/8] a2dp: Add implementation of MediaEndpoint.Device Luiz Augusto von Dentz
2019-01-21 18:25 ` [PATCH v2 1/8] doc/media-api: Enable MediaEndpoint to expose remote SEP Luiz Augusto von Dentz
2019-01-21 18:30 ` Pali Rohár
2019-01-22 12:35 ` Luiz Augusto von Dentz
2019-01-22 12:38 ` Pali Rohár
2019-01-22 12:54 ` Luiz Augusto von Dentz
2019-01-22 12:59 ` Pali Rohár
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=20190115141023.353-1-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox