diff options
| author | Himanshu Agarwal <himanaga@codeaurora.org> | 2018-02-13 14:40:56 +0530 |
|---|---|---|
| committer | Gerrit - the friendly Code Review server <code-review@localhost> | 2018-02-22 22:55:02 -0800 |
| commit | a5405cf94bfe3f94b460bb6248702eb392993663 (patch) | |
| tree | 670b24b2303619e2486a0d85285a4b0d6bd07015 /uapi/linux | |
| parent | 9b73c0fab08ba3c6b9d05578770ad82001227c55 (diff) | |
qcacld-3.0: Avoid 2.4Ghz channel in 40Mhz for SAP start
When the channel list provided from hostapd contains both
2.4Ghz and 5Ghz channels and channel width is 40Mhz, scan
happens on all the 2.4Ghz and 5Ghz channels and ACS algo
runs on all the channels to find the best channel for
starting SAP in 40Mhz. If a 2.4Ghz is selected, an OBSS
scan happens on all the 2.4Ghz channels to check if there
is any legacy BSS present on any overlapping channel. If
any BSS is found, channel width fallbacks to 20Mhz and
SAP gets started in 20Mhz bw instead of 40Mhz. This is
generally the case with 2.4Ghz whereas there is no such
issue in 5Ghz channels.
Avoid 2.4Ghz channels for starting SAP in 40Mhz bw by
assigning max weight to all the 2.4Ghz channels if 5Ghz
channels are also present in the channel list provided
from hostapd.
Change-Id: I079d20b912282c9db5c9b51b1ed4b85a4aa9c5df
CRs-Fixed: 2186658
Diffstat (limited to 'uapi/linux')
0 files changed, 0 insertions, 0 deletions