diff options
| author |   Zong-Zhe Yang <kevin_yang@realtek.com> | 2025-05-11 11:52:16 +0800 |
|---|---|---|
| committer |   Ping-Ke Shih <pkshih@realtek.com> | 2025-05-16 08:43:41 +0800 |
| commit | 122b74ac9b9d19cfbc5f319ca5c0da0efc8be9fb (patch) | |
| tree | 5d217bb71f6973373e11d8bc7c4492a3feffe795 /scripts/gdb/linux/utils.py | |
| parent | wifi: rtw89: mcc: introduce calculation of anchor pattern (diff) | |
| download | wireguard-linux-122b74ac9b9d19cfbc5f319ca5c0da0efc8be9fb.tar.xz wireguard-linux-122b74ac9b9d19cfbc5f319ca5c0da0efc8be9fb.zip | |
wifi: rtw89: mcc: deal with non-periodic NoA
Originally, MCC just took periodic NoA into account. When the connected GO
announces non-periodic NoA and GC side is during MCC, sometimes GC cannot
receive beacons well if the MCC scheduling conflicts with the non-periodic
NoA planning. After the loss exceeds the tolerable amount, beacon filter
will report connection loss. However, in this case, the loss is acceptable.
So now, MCC will calculate the range of non-periodic NoA. And then, don't
care beacon loss during the range.
Besides, rtw89_mcc_fill_role_limit() only makes sense for GC. Remove the
redundant check of GO.
Signed-off-by: Zong-Zhe Yang <kevin_yang@realtek.com>
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
Link: https://patch.msgid.link/20250511035217.10410-6-pkshih@realtek.com
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions