From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stefano Radaelli <stefano.radaelli21@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-bluetooth@vger.kernel.org
Cc: 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:03:27 +0100 [thread overview]
Message-ID: <a5d4ebf0-9d99-494c-b46b-a6140610c9e2@kernel.org> (raw)
In-Reply-To: <db4c7eab9d0c2f71eb61baff240957596f099401.1771847350.git.stefano.r@variscite.com>
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?
> HCI Enhanced Setup Synchronous Connection command but do not handle it
> correctly for SCO setup in certain configurations (e.g.
> BT_VOICE_TRANSPARENT/mSBC). This results in SCO audio not working unless
> the enhanced setup path is avoided.
>
> Add an optional boolean property, ti,no-enhanced-setup-sync-conn, to
> describe this controller limitation.
>
> Signed-off-by: Stefano Radaelli <stefano.r@variscite.com>
> ---
> .../devicetree/bindings/net/bluetooth/ti,bluetooth.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/bluetooth/ti,bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/ti,bluetooth.yaml
> index 290abc22e18a..92ed443cb427 100644
> --- a/Documentation/devicetree/bindings/net/bluetooth/ti,bluetooth.yaml
> +++ b/Documentation/devicetree/bindings/net/bluetooth/ti,bluetooth.yaml
> @@ -71,6 +71,13 @@ properties:
> items:
> - const: bd-address
>
> + ti,no-enhanced-setup-sync-conn:
> + type: boolean
> + description:
> + Indicates that the Bluetooth controller/firmware does not correctly
> + handle the HCI Enhanced Setup Synchronous Connection command for SCO
> + setup, despite advertising support for it.
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
next prev parent reply other threads:[~2026-02-23 12:03 UTC|newest]
Thread overview: 7+ 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 [this message]
2026-02-23 12:15 ` Stefano Radaelli
2026-02-24 7:35 ` Krzysztof Kozlowski
2026-02-24 10:42 ` Stefano Radaelli
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=a5d4ebf0-9d99-494c-b46b-a6140610c9e2@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@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 \
--cc=stefano.radaelli21@gmail.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