Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp9025304pxu; Mon, 28 Dec 2020 04:45:49 -0800 (PST) X-Google-Smtp-Source: ABdhPJxGguAaDbVak1Ap+hhfadx8ASylNUCD1/zc7Rjsws7Vp7w6ox+AjozZITc73UF8gAzu5gGs X-Received: by 2002:a50:9991:: with SMTP id m17mr41680720edb.48.1609159549756; Mon, 28 Dec 2020 04:45:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609159549; cv=none; d=google.com; s=arc-20160816; b=X8RiKWEnPPQDmC3cyMjPeljlLtDQ7F+xL18reelrmvy+LgnkX27+dtx9Z/8ldk1wnk giscBtpIUhx0W4rW72iQ9TxHeRfxoOV8UQogDXrvRy0fZI/85SfHmhhrsWBd3XNhDHVq K5WOCIv4nJ1ydd4KYlEg/51oRh5OggZ4cenxY6o0YE2BdlUK37w+4B1aRRO63fxdKHCV keneMWnG+7Dh1vCOqZ7XjZa8E+IU76Oc6/mlUKck4dMH7S7liNVcW7qkjYiC20GYApDc B79Bmx0oycpi9NYzVyLIzMN72Uoh2QCXf7HVSYR9/v8hJTFHrPOplebMpGWUzlx4GMAm lwmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=uJSH+afkodjYhRZEszYuAsoN9b7SbfoBb5Ryfn09PWA=; b=IhpaPALSSeEomnd7rofYvXVVou7i7GGaZDmzorCilVwLR8P4TGHWhVD4ZGrNwJcYw+ fcgYLN8BhrH7ha9Qm9lMO0n2rqFIsKUou/nTU6CItVgUq4iONhq3e/K/06YN5TLw6XeA uY2WQN5Q6lB071kjWoazvaBWs+Ye3sJNwiQmCOoDcN50Ne0qhvKBiawyw4MTcmOxunlJ 1u87cXG24NyirEm2jHWSzWnBujYKgkjreU6Png5gpGbCV1QKGUO9d2ZFR4J0m5elEnRt cE2dfpGgxFxjcvuPSjOQhR+C3RMqCkhqAKstbX/GHJNCcvWsDH8e9iyguQdfYgDxOezW PYZw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ga25si18463858ejb.636.2020.12.28.04.45.19; Mon, 28 Dec 2020 04:45:49 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727255AbgL1MnI convert rfc822-to-8bit (ORCPT + 99 others); Mon, 28 Dec 2020 07:43:08 -0500 Received: from coyote.holtmann.net ([212.227.132.17]:32866 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727217AbgL1MnI (ORCPT ); Mon, 28 Dec 2020 07:43:08 -0500 Received: from mac-pro.holtmann.net (p4ff9f924.dip0.t-ipconnect.de [79.249.249.36]) by mail.holtmann.org (Postfix) with ESMTPSA id C239ECECEC; Mon, 28 Dec 2020 13:49:45 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: Default to HW mSBC on capable controllers ? From: Marcel Holtmann In-Reply-To: Date: Mon, 28 Dec 2020 13:42:26 +0100 Cc: =?utf-8?Q?Pali_Roh=C3=A1r?= , Joakim Tjernlund , "linux-bluetooth@vger.kernel.org" Content-Transfer-Encoding: 8BIT Message-Id: References: <20201221210707.evrdeyiki45pivux@pali> <26db80417b43d919b6e33a4ee56c0e44a2f42a5c.camel@infinera.com> <20201223155624.uzbxfxtowenjrwm2@pali> To: Luiz Augusto von Dentz X-Mailer: Apple Mail (2.3654.40.0.2.32) Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Luiz, >>>>> 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. > > Actually it is meant indicate to application that BT_PKT_STATUS can be > used which enables the implementation of PLC (Packet Loss > Concealment), Ive been advocating to change it or just remove it > entirely and move it to be queried with BT_PKT_STATUS. after we fixed the bug with the SCO packet flags, we might not even need this anymore at all and just enable the error reporting unconditionally. On a side note, I insisted on calling this WIDEBAND_SPEECH option since we should be hiding details behind a single flag and not spread multiple flags for things that need to be combined into one logical feature anyway. Regards Marcel