diff options
author | 2024-05-02 12:01:23 +0300 | |
---|---|---|
committer | 2024-05-14 10:51:08 -0400 | |
commit | 21d74b6b4e82d27eead168d2b1ce3096937c0237 (patch) | |
tree | 3456b1fdf262b02e872ec3d1d0ef449e4e5e2144 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | dt-bindings: net: bluetooth: Add MediaTek MT7921S SDIO Bluetooth (diff) | |
download | wireguard-linux-21d74b6b4e82d27eead168d2b1ce3096937c0237.tar.xz wireguard-linux-21d74b6b4e82d27eead168d2b1ce3096937c0237.zip |
LE Create Connection command timeout increased to 20 secs
On our DUT, we can see that the host issues create connection cancel
command after 4-sec if there is no connection complete event for
LE create connection cmd.
As per core spec v5.3 section 7.8.5, advertisement interval range is-
Advertising_Interval_Min
Default : 0x0800(1.28s)
Time Range: 20ms to 10.24s
Advertising_Interval_Max
Default : 0x0800(1.28s)
Time Range: 20ms to 10.24s
If the remote device is using adv interval of > 4 sec, it is
difficult to make a connection with the current timeout value.
Also, with the default interval of 1.28 sec, we will get only
3 chances to capture the adv packets with the 4 sec window.
Hence we want to increase this timeout to 20sec.
Signed-off-by: Mahesh Talewad <mahesh.talewad@nxp.com>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions