From: "Pali Rohár" <pali@kernel.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Default to HW mSBC on capable controllers ?
Date: Mon, 21 Dec 2020 22:07:07 +0100 [thread overview]
Message-ID: <20201221210707.evrdeyiki45pivux@pali> (raw)
In-Reply-To: <CY4PR1001MB2389075CC44E480B446535E5F4C30@CY4PR1001MB2389.namprd10.prod.outlook.com>
On Friday 18 December 2020 13:32:29 Joakim Tjernlund wrote:
> There seems to be quite a few USB controllers gaining the BTUSB_WIDEBAND_SPEECH which I guess means HW mSBC
No, it does not mean mSBC.
If you want to query if your bluetooth adapter supports hw mSBC then you
need to check OCF_READ_LOCAL_CODECS command. You can look into script
sco_features.pl for details.
Note that currently it is not possible to send OCF_READ_LOCAL_CODECS
command from non-root user as kernel currently does not allow it.
> but currently there is no way to select this mode.
Yes. "/bin/hciconfig voice" allows to set only voice settings for old
Add Synchronous Connection HCI command which does not support hw mSCB.
> Any idea if one could patch the kernel to default to HW mSBC and user apps like bluealsa/pulseaudio would just use it automatically?
For usage mSBC hw encoder you need to use Enhanced Setup Synchronous
Connection HCI command for establishing SCO connection.
For using HW encoder you need to stop feeding socket with mSBC encoded
data and instead put into this socket RAW pcm samples. Also you need
somehow inform kernel about this change.
For both things I designed new setsockopt() API which I described in:
https://lore.kernel.org/linux-bluetooth/20200419234937.4zozkqgpt557m3o6@pali/
next prev parent reply other threads:[~2020-12-21 21:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 13:32 Default to HW mSBC on capable controllers ? Joakim Tjernlund
2020-12-18 19:43 ` Luiz Augusto von Dentz
2020-12-20 17:09 ` Joakim Tjernlund
2020-12-21 21:14 ` Pali Rohár
2020-12-22 1:54 ` Luiz Augusto von Dentz
2020-12-22 9:21 ` Pali Rohár
2020-12-22 9:36 ` Jamie Mccrae
2020-12-22 9:48 ` Pali Rohár
2020-12-22 10:05 ` Marcel Holtmann
2020-12-22 10:19 ` Pali Rohár
2020-12-22 11:04 ` Marcel Holtmann
2020-12-22 11:46 ` Pali Rohár
2020-12-22 12:20 ` Marcel Holtmann
2020-12-22 13:17 ` Pali Rohár
2020-12-22 21:11 ` Marcel Holtmann
2020-12-22 21:13 ` Pali Rohár
2020-12-31 10:09 ` Pasi Kärkkäinen
2021-01-13 14:46 ` Pali Rohár
2020-12-21 21:07 ` Pali Rohár [this message]
2020-12-22 11:40 ` Pasi Kärkkäinen
2020-12-22 11:49 ` Pali Rohár
2020-12-22 13:20 ` Pali Rohár
2020-12-23 15:41 ` Joakim Tjernlund
2020-12-23 15:56 ` Pali Rohár
2020-12-23 21:58 ` Luiz Augusto von Dentz
2020-12-28 12:42 ` Marcel Holtmann
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=20201221210707.evrdeyiki45pivux@pali \
--to=pali@kernel.org \
--cc=Joakim.Tjernlund@infinera.com \
--cc=linux-bluetooth@vger.kernel.org \
/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.