linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 9 Jan 2019 19:14:36 +0100	[thread overview]
Message-ID: <20190109181436.atlbhkqclpq3kcta@pali> (raw)
In-Reply-To: <20190109180340.5fh7adag6buij4px@pali>

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

On Wednesday 09 January 2019 19:03:40 Pali Rohár wrote:
> On Tuesday 08 January 2019 17:56:12 Pali Rohár wrote:
> > 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
> 
> Hi! I applied your 6 patches from https://marc.info/?l=linux-bluetooth&r=1&b=201901&w=2
> but whatever I did I was not able to locate in dbus hierarchy list of
> A2DP codecs supported by device.
> 
> I thought that somewhere in
> 
> qdbus --system org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX
> 
> I found A2DP codec capabilities...
> 
> So how to get list of all supported A2DP codecs for particular device?

Ah, I forgot to start bluetoothd with --experimental option. After that
I see sep*

/
/org
/org/bluez
/org/bluez/hci0
/org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX
/org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep1
/org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep3
/org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep5

and qdbus --system org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep1 org.freedesktop.DBus.Properties.GetAll org.bluez.MediaEndpoint1
list them correctly.

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

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

  reply	other threads:[~2019-01-09 18:14 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
2019-01-09 18:03                   ` Pali Rohár
2019-01-09 18:14                     ` Pali Rohár [this message]
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=20190109181436.atlbhkqclpq3kcta@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).