android_kernel_xiaomi_sm8350/core
gaurank kathpalia 37dcc70525 qcacld-3.0: Lower down the channel BW in 2.4ghz case
Currently the driver in case of force SCC picks up
2.4ghz SCC channel if any other STA/AP is already
up on that channel, so in the process of shifting
in the API sap_validate_channel it picks up 2.4ghz
and calls a reg API to set the freq related params
to it. Now since the frequency for 2.4ghz is 40 mhz
capable the max BW supported for 2.4ghz becomes 40 and
the driver starts the SAP on 40mhz.
Now since the OBSS scan is offloaded to the hostpad
and now since it was driver which started the SAP
on 40mhz there is no mechanism to start OBSS scan
from driver, which leads to channel blockage if
any legacy 11g, 11b lient is operating on the channel.

Fix is to lower down the BW to 20Mhz if the SAP does a
force SCC in 2.4ghz.

Change-Id: I0d85dfb5e9e8332957d853173063e77d18ea600c
CRs-Fixed: 2581495
2019-12-11 13:35:13 -08:00
..
bmi qcacld-3.0: Add synchronization between unloading & SSR recovering 2019-10-19 19:25:31 -07:00
cds qcacld-3.0: cdp: Converge stats API 2019-12-10 19:39:12 -08:00
dp qcacld-3.0: Print FW tx path counters in txrx_fw_stats 2019-12-11 00:19:01 -08:00
hdd qcacld-3.0: Set wdev for vendor event HANG_REASON_INDEX 2019-12-10 16:15:19 -08:00
mac Release 5.2.0.160X 2019-12-11 08:52:15 -08:00
pld qcacld-3.0: Add WHUNT bus types in pld_lock/unlock_reg_window APIs 2019-11-19 03:38:43 -08:00
sap qcacld-3.0: Lower down the channel BW in 2.4ghz case 2019-12-11 13:35:13 -08:00
sme qcacld-3.0: Cleanup unused legacy crypto api of csr 2019-12-11 03:21:03 -08:00
wma qcacld-3.0: Handle WMI_ROAM_STATS_EVENTID from firmware 2019-12-11 08:52:14 -08:00