public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: linux-kernel@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>
Subject: Re: [PATCH v2 1/1] Bluetooth: hci_ll: Enable BROKEN_ENHANCED_SETUP_SYNC_CONN for WL183x
Date: Mon, 30 Mar 2026 15:04:58 +0200	[thread overview]
Message-ID: <acp0-qWerjms3n5U@Lord-Beerus.station> (raw)
In-Reply-To: <36a2c4c75e557527d101897b649f9de8d2180fb6.1771930508.git.stefano.r@variscite.com>

Hi,

On Tue, Feb 24, 2026 at 12:12:35PM +0100, Stefano Radaelli wrote:
> From: Stefano Radaelli <stefano.r@variscite.com>
> 
> TI WL183x controllers advertise support for the HCI Enhanced Setup
> Synchronous Connection command, but SCO setup fails when the enhanced
> path is used. The only working configuration is to fall back to the
> legacy HCI Setup Synchronous Connection (0x0028).
> 
> This matches the scenario described in commit 05abad857277
> ("Bluetooth: HCI: Add HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN quirk").
> 
> Enable HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN automatically for
> devices compatible with:
>   - ti,wl1831-st
>   - ti,wl1835-st
>   - ti,wl1837-st
> 
> Signed-off-by: Stefano Radaelli <stefano.r@variscite.com>
> ---
> v1->v2:
>  - 
> 
>  drivers/bluetooth/hci_ll.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/drivers/bluetooth/hci_ll.c b/drivers/bluetooth/hci_ll.c
> index 91acf24f1ef5..6f060eec3b81 100644
> --- a/drivers/bluetooth/hci_ll.c
> +++ b/drivers/bluetooth/hci_ll.c
> @@ -68,6 +68,7 @@ struct ll_device {
>  	struct gpio_desc *enable_gpio;
>  	struct clk *ext_clk;
>  	bdaddr_t bdaddr;
> +	bool broken_enhanced_setup;
>  };
>  
>  struct ll_struct {
> @@ -656,6 +657,10 @@ static int ll_setup(struct hci_uart *hu)
>  			hci_set_quirk(hu->hdev, HCI_QUIRK_INVALID_BDADDR);
>  	}
>  
> +	if (lldev->broken_enhanced_setup)
> +		hci_set_quirk(hu->hdev,
> +			      HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN);
> +
>  	/* Operational speed if any */
>  	if (hu->oper_speed)
>  		speed = hu->oper_speed;
> @@ -710,6 +715,11 @@ static int hci_ti_probe(struct serdev_device *serdev)
>  	of_property_read_u32(serdev->dev.of_node, "max-speed", &max_speed);
>  	hci_uart_set_speeds(hu, 115200, max_speed);
>  
> +	if (of_device_is_compatible(serdev->dev.of_node, "ti,wl1831-st") ||
> +	    of_device_is_compatible(serdev->dev.of_node, "ti,wl1835-st") ||
> +	    of_device_is_compatible(serdev->dev.of_node, "ti,wl1837-st"))
> +		lldev->broken_enhanced_setup = true;
> +
>  	/* optional BD address from nvram */
>  	bdaddr_cell = nvmem_cell_get(&serdev->dev, "bd-address");
>  	if (IS_ERR(bdaddr_cell)) {
> -- 
> 2.47.3
> 

I noticed that this patch has not received feedback and is now marked as
archived in patchwork.

I also saw that the CI reported some test failures (e.g. mgmt-tester and
others), and I was wondering if this might be the reason why it has not
been considered.

Could you please let me know if I should address those issues or if any
changes are needed for this patch?

Thanks,
Stefano

  parent reply	other threads:[~2026-03-30 13:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 11:12 [PATCH v2 0/1] Bluetooth: hci_ll: Enable BROKEN_ENHANCED_SETUP_SYNC_CONN for WL183x Stefano Radaelli
2026-02-24 11:12 ` [PATCH v2 1/1] " Stefano Radaelli
2026-02-24 11:59   ` bluez.test.bot
2026-03-30 13:04   ` Stefano Radaelli [this message]
2026-04-02 17:38     ` [PATCH v2 1/1] " Luiz Augusto von Dentz
2026-04-02 19:02       ` Stefano Radaelli
2026-04-02 17:14   ` bluez.test.bot
2026-04-02 18:47   ` [PATCH v2 1/1] " Stefano Radaelli
2026-04-02 20:51   ` Paul Menzel
2026-04-03 13:29     ` Stefano Radaelli
2026-04-02 18:47 ` [PATCH v2 0/1] " 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=acp0-qWerjms3n5U@Lord-Beerus.station \
    --to=stefano.radaelli21@gmail.com \
    --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=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