570f0aff4f
Scenario:- 1. Turn on SAP and STA on 2.4ghz and 5ghz 2. Turn off SAP 3. Turn off STA 4. Turn on SAP on 2.4ghz Issue:- In the start ap function, the driver calls the stop opportunistic timer and calls the handler to goto SMM mode. After this, the SAP checks whether it requires the DBS or not and then requests for DBS also, but since the driver is already in DBS mode this command gets rejected, so there would be 2 commands in the serialization queue which would be SMM and start AP, which would lead to a crash as SMM is sent before a connection on 2.4ghz as Hastings is not capable to start a vdev in 2.4ghz without DBS mode. Fix:- 1.Not allow SMM if the current connection requires DBS 2. Check the HW capabilty in the active command only and not before that to protect the reliability of hw mode. Change-Id: I1c0c05ea05ba14d1556af2612daa3de2ffcba367 CRs-Fixed: 2587508 |
||
|---|---|---|
| .. | ||
| action_oui | ||
| blacklist_mgr | ||
| cfg | ||
| cmn_services/policy_mgr | ||
| cp_stats/dispatcher/inc | ||
| disa | ||
| dsc | ||
| fw_offload | ||
| interop_issues_ap | ||
| ipa | ||
| mlme | ||
| nan | ||
| ocb | ||
| p2p | ||
| pmo | ||
| target_if | ||
| tdls | ||