All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chan-yeol Park <chanyeol.park@samsung.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC BlueZ 1/3] audio/a2dp: connect A2DP vendor codec if possible
Date: Tue, 26 May 2015 15:28:48 +0900	[thread overview]
Message-ID: <556412A0.4030004@samsung.com> (raw)
In-Reply-To: <CABBYNZ+tM==j0Af=X93jCCQAqenspFbtbLRs6KqFrMuA8-niOg@mail.gmail.com>

Hi Luiz,
On 05/07/2015 05:20 PM, Luiz Augusto von Dentz wrote:
> Hi Chan-yeol,
>
> On Wed, May 6, 2015 at 6:10 PM,  <chanyeol.park@samsung.com> wrote:
>> From: Chan-yeol Park <chanyeol.park@samsung.com>
>>
>> This patch gives the priority on vendor codec during A2DP codec
>> negotiation.
>
> There is already a prioritization based on the sender and in the order
> the endpoints are registered, so by doing this you would be breaking
> the prioritization instead register the codecs in order of preference
> that should have the same results.
>

Yes you're right. but most of phone(Android/iOS) register their SBC in 
the first SEP to support compatibility because some of headset try to 
connect first SEP without codec comparison. As a result I could not 
register vendor codec in the first SEP. So without this patch vendor 
codec establishment would not be made.

I am not clear how to give the priority on vendor codec in this case.

Thanks
Chanyeol

  reply	other threads:[~2015-05-26  6:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 15:10 [RFC BlueZ 1/3] audio/a2dp: connect A2DP vendor codec if possible chanyeol.park
2015-05-06 15:10 ` [RFC BlueZ 2/3] audio/a2dp: Fix SEP selection chanyeol.park
2015-05-06 15:10 ` [RFC BlueZ 3/3] audio/a2dp: Remove useless check_vendor_codec() chanyeol.park
2015-05-07  8:20 ` [RFC BlueZ 1/3] audio/a2dp: connect A2DP vendor codec if possible Luiz Augusto von Dentz
2015-05-26  6:28   ` Chan-yeol Park [this message]
2015-05-26 14:30     ` Luiz Augusto von Dentz

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=556412A0.4030004@samsung.com \
    --to=chanyeol.park@samsung.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.