| commit | 968eafb3a3151bd77c0511ceaacb915fdde0d77c | [log] [tgz] |
|---|---|---|
| author | Liangwei Dong <quic_liangwei@quicinc.com> | Fri Sep 09 11:28:49 2022 +0800 |
| committer | Madan Koyyalamudi <quic_mkoyyala@quicinc.com> | Wed Nov 16 21:06:45 2022 -0800 |
| tree | e89a736682f9ce5d65f46d4f09099a94c5633e17 | |
| parent | 7ddb90fae2855402ff8b5c042d5f05167f8d0bda [diff] |
qcacld-3.0: Fix obss_width_trigger_interval zero in WMI command DUT roams to 2 GHz channel 6 bw 20 MHz, OBSS parameters are not initialized by lim_fill_ft_session. Later when DUT gets CSA event to 2 GHz channel 1 bw 40 MHz, the OBSS scan command will send invalid obss_width_trigger_interval with zero value to target. Fix by initialize the OBSS parameters without check current AP's BW. Change-Id: I6f895371898fde292cde5a108a3b4fcd95836186 CRs-Fixed: 3287522