Re: Default to HW mSBC on capable controllers ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wednesday 23 December 2020 15:41:01 Joakim Tjernlund wrote:
> On Mon, 2020-12-21 at 22:07 +0100, Pali Rohár wrote:
> > 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.
> > 
> 
> I forgot, if BTUSB_WIDEBAND_SPEECH does not mean capable of HW mSBC, what does it mean?

BTUSB_WIDEBAND_SPEECH flag is just for usb bluetooth adapters. Not for
UART or SDIO bluetooth adapters.

It is a hint set for some bluetooth adapters which are on kernel
whitelist that wideband speech support is possible for them.

mSBC is not the only one codec which has wideband support.

Based on current "whitelist" implementation it does not mean adapters
without this hint are not mSBC capable (e.g. new adapters could not be
on this list) and also there is a theoretical chance that some with this
flag are not capable of mSBC. But this is only theoretical and I think
you can say that BTUSB_WIDEBAND_SPEECH is sufficient for mSBC. But it is
not necessary condition for mSBC (e.g. because of UART or SDIO adapters
or adapters which are not whitelist yet).

I hope to see AuriStream support which is also wideband speech codec but
should work also with some adapters which are not able to provide enough
bandwidth for mSBC.



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux