[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <78EC62F6-40D5-4E18-B2FA-DA2EB9D67986@holtmann.org>
Date: Thu, 2 Jun 2022 18:10:49 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Bastian Germann <bage@...ian.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Maxime Ripard <mripard@...nel.org>,
Chen-Yu Tsai <wens@...e.org>,
Johan Hedberg <johan.hedberg@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kubakici@...pl>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-bluetooth@...r.kernel.org, netdev@...r.kernel.org,
Vasily Khoruzhick <anarsoul@...il.com>
Subject: Re: [PATCH v2 1/3] Bluetooth: Add new quirk for broken local ext
features max_page
Hi Bastian,
> Some adapters (e.g. RTL8723CS) advertise that they have more than
> 2 pages for local ext features, but they don't support any features
> declared in these pages. RTL8723CS reports max_page = 2 and declares
> support for sync train and secure connection, but it responds with
> either garbage or with error in status on corresponding commands.
please include btmon output for the garbage and/or error.
>
> Signed-off-by: Vasily Khoruzhick <anarsoul@...il.com>
> [rebase on current tree]
> Signed-off-by: Bastian Germann <bage@...ian.org>
> ---
> include/net/bluetooth/hci.h | 7 +++++++
> net/bluetooth/hci_event.c | 4 +++-
> 2 files changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.h
> index 69ef31cea582..af26e8051905 100644
> --- a/include/net/bluetooth/hci.h
> +++ b/include/net/bluetooth/hci.h
> @@ -265,6 +265,13 @@ enum {
> * runtime suspend, because event filtering takes place there.
> */
> HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL,
> +
> + /* When this quirk is set, max_page for local extended features
> + * is set to 1, even if controller reports higher number. Some
> + * controllers (e.g. RTL8723CS) report more pages, but they
> + * don't actually support features declared there.
> + */
> + HCI_QUIRK_BROKEN_LOCAL_EXT_FTR_MAX_PAGE,
> };
Can we just call it _BROKEN_LOCAL_EXT_FEATURES_PAGE_2.
Now with that said, is Secure Connections really broken? We need that bit to indicate support for this.
Regards
Marcel
Powered by blists - more mailing lists