Hi Luiz,
Yes, its auto connect scenario.
While running connect disconnect in a loop on one of the chip, we are getting issue with this default timeout . Hence we increased this timeout value to standard LE timeout i.e 20s.
Kindly let us know, is there any timeout explicitly defined for the autoconnect in the spec.
Thanks and regards,
Mahesh Vithal Talewad
-----Original Message-----
From: Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>
Sent: Wednesday, March 20, 2024 3:21 PM
To: Mahesh Talewad <mahesh.talewad@xxxxxxx>
Cc: linux-bluetooth@xxxxxxxxxxxxxxx; Devyani Godbole <devyani.godbole@xxxxxxx>; Sarveshwar Bajaj <sarveshwar.bajaj@xxxxxxx>
Subject: [EXT] Re: [PATCH BlueZ v1 1/1] LE Create Connection command timeout increased to 20 secs from 4 secs
Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
Hi Mahesh,
On Mon, Mar 18, 2024 at 12:37 PM Mahesh Talewad <mahesh.talewad@xxxxxxx> wrote:
>
> - As per specs LE Connection timeout is 20 secs but in implementation,
> it was 4 secs. Hence increased this timeout to 20 Secs.
>
> Signed-off-by: Mahesh Talewad <mahesh.talewad@xxxxxxx>
> ---
> net/bluetooth/hci_event.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> index 4ae224824012..06fe5f6b9546 100644
> --- a/net/bluetooth/hci_event.c
> +++ b/net/bluetooth/hci_event.c
> @@ -6067,7 +6067,7 @@ static struct hci_conn *check_pending_le_conn(struct hci_dev *hdev,
> }
>
> conn = hci_connect_le(hdev, addr, addr_type, addr_resolved,
> - BT_SECURITY_LOW, hdev->def_le_autoconnect_timeout,
> + BT_SECURITY_LOW, HCI_LE_CONN_TIMEOUT,
> HCI_ROLE_MASTER);
> if (!IS_ERR(conn)) {
> /* If HCI_AUTO_CONN_EXPLICIT is set, conn is already
> owned
> --
> 2.34.1
Afaik this is on purpose since it is the autoconnect procedure, rather than user initiate connection, so are you running into a problem if the timeout is different?
--
Luiz Augusto von Dentz
