mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-15 17:24:14 -04:00
| Filename | Latest commit message | Latest commit date |
|---|---|---|
b8db936cfe
Scenario of the issue is :- 1. Keep sta+sap_scc_dfs_ch as 0 to disable the dfs concurrency 2. Start a SAP on any 5ghz channel(NON-DFS). 3. Start a STA on a DFS channel. Expectation: The SAP should not do MCC, SCC as the above mentioned ini is 0, also MCC is not prefereed in a HW solution where DFS is preferred, hence the SAP should go to 2.4ghz and DBS should be the expectation. Observation: The SAP does not do a DBS operation, and falls to MCC here. Reason: When the SAP gets a PCL in the path of SAP restart, the PCL feels that a new SAP is going to come up, and hence gives the best channel (first element of PCL ) as its own, which leads to restart being rejected, as the SAP cannot start on a channel which is the same as existing. The final channel then selected is the STA channel, leading to DFS SCC which is also not allowed. Hence the SAP is now stuck in MCC(STA+SAP , one on DFS, and the other on NON-DFS channel). Fix: The fix is to get an alternate channel for SAP restart, other than the channel on which the SAP is already up, to lead to DBS, if the STA channel is not suitable for SCC operaion. Change-Id: Iab3ad22b2f970ca26ce3e6bc7a9b5ee34bc7e7ba CRs-Fixed: 2443718 |
||
| .. | ||
| action_oui | ||
| cfg | ||
| cmn_services/policy_mgr | ||
| disa | ||
| dsc | ||
| fw_offload | ||
| ipa | ||
| mlme | ||
| nan | ||
| ocb | ||
| p2p | ||
| pmo | ||
| target_if | ||
| tdls | ||