Re: [PATCH v2 1/8] doc/media-api: Enable MediaEndpoint to expose remote SEP

["Pali Rohár" <pali.rohar@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3107 bytes --]

On Monday 21 January 2019 20:25:41 Luiz Augusto von Dentz wrote:
> Hi,
> On Tue, Jan 15, 2019 at 4:12 PM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
> >
> > 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
> 
> Are there any comments for this set? Notice that I did include the
> device path in this set so there is no need to hack to guess what
> device the endpoint belongs to.

I did not know about V2 as I'm not subscribed to list. I tested and used
with PA only V1.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]