[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee6259a2-05c3-4d6d-9dda-7a7b8f55fbfe@molgen.mpg.de>
Date: Thu, 28 Mar 2024 14:23:19 +0100
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Werner Sembach <wse@...edocomputers.com>,
Marcel Holtmann <marcel@...tmann.org>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc: Christoffer Sandberg <cs@...edo.de>, linux-bluetooth@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: btintel: Add devices to
HCI_QUIRK_BROKEN_LE_CODED
Dear Christoffer, dear Werner,
Thank you for the patch.
Am 28.03.24 um 14:18 schrieb Werner Sembach:
> From: Christoffer Sandberg <cs@...edo.de>
>
> For HW variants 0x17, 0x18 and 0x19 LE Coded PHY causes scan and
> connection issues when enabled. This patch disables it through
> the existing quirk.
It would fit in two lines with 75 characters per line.
On what hardware with what clients do you experience this exactly?
> Signed-off-by: Christoffer Sandberg <cs@...edo.de>
> Signed-off-by: Werner Sembach <wse@...edocomputers.com>
> Cc: <stable@...r.kernel.org>
> ---
> drivers/bluetooth/btintel.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
> index cdc5c08824a0a..6dbfb74d0adf9 100644
> --- a/drivers/bluetooth/btintel.c
> +++ b/drivers/bluetooth/btintel.c
> @@ -2881,6 +2881,8 @@ static int btintel_setup_combined(struct hci_dev *hdev)
> case 0x17:
> case 0x18:
> case 0x19:
> + /* 0x17, 0x18 and 0x19 have issues when LE Coded PHY is enabled */
> + set_bit(HCI_QUIRK_BROKEN_LE_CODED, &hdev->quirks);
> case 0x1b:
> case 0x1c:
> /* Display version information of TLV type */
Kind regards,
Paul
Powered by blists - more mailing lists