From: "Pali Rohár" <pali.rohar@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: bluez: dbus method call for switching endpoint
Date: Tue, 8 Jan 2019 17:56:12 +0100 [thread overview]
Message-ID: <20190108165612.5krhgtmce336xjx3@pali> (raw)
In-Reply-To: <CABBYNZK4+K5vRF0JCHFcUjbfzWanp_ju6XfQQJWBtiLqKi=e7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On Tuesday 08 January 2019 13:44:24 Luiz Augusto von Dentz wrote:
> > > Regarding the API I still didn't have time to start it, so it will
> > > take a little longer than I antecipated.
>
> Ive just sent the patches adding support to switch the endpoints, Ive
> only tested with a couple of sony headsets so I would appreciate if
> you guys could try it as well. Note that the SetConfiguration must
> come from the same D-Bus connection as the endpoint that would be
> used, also if there is already an stream in place it must also be from
> the same client since it would be terminated in the process, this is
> to prevent entities fighting to configure with its own priority though
> usually we only PA endpoints, if you want to bypass this just for now
Great! Once patches would be ready I would look at my last A2DP
pulseaudio patches [1] and would try to implement switching, including
support for bi-directional FastStream codec -- which can benefit from
it.
[1] - https://lists.freedesktop.org/archives/pulseaudio-discuss/2018-July/030344.html
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-01-08 16:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 8:23 bluez: dbus method call for switching endpoint Pali Rohár
2018-07-11 13:27 ` Luiz Augusto von Dentz
2018-07-11 14:45 ` Pali Rohár
2018-12-15 20:29 ` Pali Rohár
2018-12-18 16:02 ` Luiz Augusto von Dentz
2018-12-28 19:11 ` Pasi Kärkkäinen
2018-12-28 22:10 ` Luiz Augusto von Dentz
2018-12-29 13:08 ` Pali Rohár
2019-01-08 16:44 ` Luiz Augusto von Dentz
2019-01-08 16:51 ` Pali Rohár
2019-01-08 16:56 ` Pali Rohár [this message]
2019-01-09 18:03 ` Pali Rohár
2019-01-09 18:14 ` Pali Rohár
2019-01-10 11:29 ` Luiz Augusto von Dentz
2019-01-10 11:59 ` Pali Rohár
2019-01-26 10:15 ` Pali Rohár
2019-01-19 17:15 ` 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=20190108165612.5krhgtmce336xjx3@pali \
--to=pali.rohar@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pasik@iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).