Linux bluetooth development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"Pasi Kärkkäinen" <pasik@iki.fi>
Subject: Re: [PATCH v2 1/8] doc/media-api: Enable MediaEndpoint to expose remote SEP
Date: Tue, 22 Jan 2019 13:59:14 +0100	[thread overview]
Message-ID: <20190122125914.uotyzna5aasa4vw3@pali> (raw)
In-Reply-To: <CABBYNZK-qBX8cQmAmb4w1H21_W_PGKvvDPnQaTJ0RBK1TPJwJA@mail.gmail.com>

On Tuesday 22 January 2019 14:54:30 Luiz Augusto von Dentz wrote:
> Hi Pali,
> On Tue, Jan 22, 2019 at 2:38 PM Pali Rohár <pali.rohar@gmail.com> wrote:
> >
> > On Tuesday 22 January 2019 14:35:42 Luiz Augusto von Dentz wrote:
> > > I will send a v3 which does the reverse discovery, that should make it
> > > work with existing paired devices that reconnect and configure since
> > > otherwise there would not be any endpoints to associate with.
> >
> > Ok.
> >
> > > Note
> > > though that in case of PA the endpoint object should be considered
> > > optional no matter what since otherwise it won't be backward
> > > compatible.
> >
> > Yes, patches are already backward compatible. When endpoints do not
> > exist, pulseaudio just refuse to switch codec.
> 
> It refuses or there just no other profile/port to switch to?

It refuses just to switch from one A2DP profile to another A2DP profile
of same type (sink --> sink OR source --> source) with different codecs.
Switching between HFP and A2DP or between A2DP sink and A2DP source works.

> Btw, are
> there anything special I need to do in order to test your patches? I
> guess for apt-x I will need your lib right?

Yes, for aptX you need that libopenaptx library and remote device with
aptX codec support. See also profile switch limitation in patch
description (tl;dr you need to issue profile switch command two times).

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

      reply	other threads:[~2019-01-22 12:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 14:10 [PATCH v2 1/8] doc/media-api: Enable MediaEndpoint to expose remote SEP Luiz Augusto von Dentz
2019-01-15 14:10 ` [PATCH v2 2/8] a2dp: Expose " 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 [this message]

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=20190122125914.uotyzna5aasa4vw3@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