From: Christoffer Sandberg <cs@tuxedo.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Werner Sembach <wse@tuxedocomputers.com>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Christoffer Sandberg <cs@tuxedo.de>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btintel: Add devices to HCI_QUIRK_BROKEN_LE_CODED
Date: Tue, 02 Apr 2024 11:17:45 +0200 [thread overview]
Message-ID: <bda6baa41b6b4511830603138d896add@tuxedocomputers.com> (raw)
In-Reply-To: <ee6259a2-05c3-4d6d-9dda-7a7b8f55fbfe@molgen.mpg.de>
Dear Paul,
On 28.3.2024 14:23, Paul Menzel wrote:
> On what hardware with what clients do you experience this exactly?
>
The wifi/bluetooth modules AX201, AX210 and AX211 (cases 0x18, 0x17 and
0x19 respectively) used in various notebook devices started having
issues as of the patch that enabled le coded phy in the driver. (We also
use AX200, however without issue.)
Noted behaviour as of the issues: Device scan took longer and when it
did find a device connection often failed or timed out.
I do not know if a special type of bluetooth client is affected. It was
partially tested by looking at the difference in enumeration of the
current mix of bluetooth clients in the area (where you could clearly
see the difference at a glance) and with one specific device. A
bluetooth connected watercooling system (TUXEDO Aquaris or
LCT21001/LCT22002) where a test case showed the mentioned issues.
Best regards,
Christoffer
next prev parent reply other threads:[~2024-04-02 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 13:18 Werner Sembach
2024-03-28 13:23 ` Paul Menzel
2024-04-02 9:17 ` Christoffer Sandberg [this message]
2024-03-28 14:17 ` Luiz Augusto von Dentz
2024-03-28 23:20 ` Werner Sembach
2024-03-31 4:52 ` K, Kiran
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=bda6baa41b6b4511830603138d896add@tuxedocomputers.com \
--to=cs@tuxedo.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=wse@tuxedocomputers.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®