diff options
| author | hqu <hqu@codeaurora.org> | 2019-01-30 21:28:53 +0800 |
|---|---|---|
| committer | nshrivas <nshrivas@codeaurora.org> | 2019-03-01 15:23:25 -0800 |
| commit | 3b7d04b401ce24a0f687ab6fe841f866ba580111 (patch) | |
| tree | 4588c35554406f7d82a5cefa8782f4f26de4a104 /tools/perf/scripts/python/check-perf-trace.py | |
| parent | 37c2907a0a800d2fbdea2450db87d17d0a8538cb (diff) | |
qcacld-3.0: Save sap_operating_band from MAC global context
When user layer APP updates STA roaming policy, sap_operating_band
will be saved to MAC global context pMac through sme_update_config.
But other operation may cause sap_operating_band from pMac missing.
For example when updating parameter it will call
sme_get_config_param to copy many fields without sap_operating_band
from pMac firstly, then it do sme_update_config, sap_operating_band
value from pMac is lost. It will cause unsafe channel can't be
ignored in csr_scan_copy_request_valid_channels_only.
Fix is to save sap_operating_band from pMac in csr_get_config_param.
Change-Id: I3211f8264f9eb650471a0813d929d217911510fd
CRs-Fixed: 2407060
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions