From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-bluetooth@vger.kernel.org, pierluigi.p@variscite.com,
Stefano Radaelli <stefano.r@variscite.com>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
David Lechner <david@lechnology.com>
Subject: Re: [PATCH v1 1/2] dt-bindings: net: bluetooth: ti: Add property for enhanced SCO setup erratum
Date: Mon, 23 Feb 2026 13:15:59 +0100 [thread overview]
Message-ID: <aZxE__Ybg5p2DaFM@Lord-Beerus.station> (raw)
In-Reply-To: <a5d4ebf0-9d99-494c-b46b-a6140610c9e2@kernel.org>
On Mon, Feb 23, 2026 at 01:03:27PM +0100, Krzysztof Kozlowski wrote:
> On 23/02/2026 12:52, Stefano Radaelli wrote:
> > From: Stefano Radaelli <stefano.r@variscite.com>
> >
> > Some Bluetooth controller/firmware combinations advertise support for the
>
> Which ones?
>
>
> This looks a lot like controller issue, thus deducible from the
> compatible. And even if particular firmware has problem, how do you see
> changing static DTS on linux-firmware update?
>
> Best regards,
> Krzysztof
Hi Krzysztof,
thank you for your review!
We have observed this behaviour specifically on TI WL1831 modules.
When using the HCI Enhanced Setup Synchronous Connection command,
SCO setup fails even though the controller reports the command as
supported. The only working path for this controller is to fall back
to the legacy HCI Setup Synchronous Connection (0x0028).
The behaviour matches the scenario described in commit 05abad857277,
which introduced HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN for that
reason.
We are using the latest firmware available from TI for the wl18xx
family (from the official TI repository), so this is not related to
an outdated firmware version.
The reason for proposing a DT property was to keep the workaround
flexible and avoid forcing the quirk on all TI controllers handled
by hci_ll without confirmation.
However, since this may be considered deducible from the compatible,
would you prefer enabling
HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN automatically for
"ti,wl1831-st" instead of using a DT property?
Thanks for the feedback.
Best regards,
Stefano
next prev parent reply other threads:[~2026-02-23 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 11:52 [PATCH v1 0/2] Bluetooth: hci_ll: Add DT control for enhanced SCO setup erratum Stefano Radaelli
2026-02-23 11:52 ` [PATCH v1 1/2] dt-bindings: net: bluetooth: ti: Add property " Stefano Radaelli
2026-02-23 12:03 ` Krzysztof Kozlowski
2026-02-23 12:15 ` Stefano Radaelli [this message]
2026-02-24 7:35 ` Krzysztof Kozlowski
2026-02-24 10:42 ` Stefano Radaelli
2026-02-23 13:11 ` Bluetooth: hci_ll: Add DT control " bluez.test.bot
2026-02-23 11:52 ` [PATCH v1 2/2] Bluetooth: hci_ll: Add DT property to disable enhanced SCO setup Stefano Radaelli
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=aZxE__Ybg5p2DaFM@Lord-Beerus.station \
--to=stefano.radaelli21@gmail.com \
--cc=conor+dt@kernel.org \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pierluigi.p@variscite.com \
--cc=robh@kernel.org \
--cc=stefano.r@variscite.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