diff options
author | Zong-Zhe Yang <kevin_yang@realtek.com> | 2024-08-19 17:17:24 +0800 |
---|---|---|
committer | Ping-Ke Shih <pkshih@realtek.com> | 2024-08-27 10:58:01 +0800 |
commit | fef63150940c2aaa50721dde33d48f00ab510591 (patch) | |
tree | fa5f065e75f98be88f44c3af1add609d76e58a2e /tools/perf/scripts/python/gecko.py | |
parent | d03b3d7493f5a3908c86bac443631e144e4ffb7d (diff) |
wifi: rtw89: introduce chip support link number and driver MLO capability
Configure supported link number by chip. And, introduce driver capability
flag for MLO. Driver should depend on runtime FW features and chip info to
determine whether to set the MLO capability flag or not. Once the MLO flag
is set, driver will consider/register/initialize things for MLO usages.
However, we just add the driver MLO capability flag ahead and don't really
set it. Then, we can start to tweak driver architecture for MLO. Some code
should depend on this flag. And after tweaking driver architecture is done,
we will set it based on runtime conditions as mentioned above.
Besides, MLD number supported by HW should be
chip supported mac_id number / chip supported link number
Without driver MLO capability flag, we allocate stations based on supported
mac_id number. With driver MLO capability flag, we allocate stations based
on supported MLD number.
Signed-off-by: Zong-Zhe Yang <kevin_yang@realtek.com>
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
Link: https://patch.msgid.link/20240819091724.33730-9-pkshih@realtek.com
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions