mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-15 01:01:56 -04:00
qcacld-3.0: Start vendor ACS timer after the vendor event is sent
Driver starts a vendor ACS timer which times out if vendor app doesn't respond with commands within stipulated time. But in do_acs this timer is started before all the channel list parsing, regulatory checks and buffer allocation code. In some cases this takes up enough time to expire the timer before sending the vendor event. Similar situation will arise if a buffer allocation fails in between. To avoid this start timer after the vendor event is sent. Change-Id: If9bea4643e03f0541ac8d8af2183c1e8d3a6cc40 CRs-Fixed: 2096246
This commit is contained in:
parent
2882bb0e00
commit
a48556932a
1 changed files with 3 additions and 3 deletions
|
|
@ -7261,10 +7261,10 @@ int hdd_update_acs_timer_reason(hdd_adapter_t *adapter, uint8_t reason)
|
|||
timer_context = (struct hdd_external_acs_timer_context *)
|
||||
adapter->sessionCtx.ap.vendor_acs_timer.user_data;
|
||||
timer_context->reason = reason;
|
||||
qdf_mc_timer_start(&adapter->sessionCtx.ap.vendor_acs_timer,
|
||||
WLAN_VENDOR_ACS_WAIT_TIME);
|
||||
/* Update config to application */
|
||||
/* Update config to application and start the timer */
|
||||
hdd_cfg80211_update_acs_config(adapter, reason);
|
||||
qdf_mc_timer_start(&adapter->sessionCtx.ap.vendor_acs_timer,
|
||||
WLAN_VENDOR_ACS_WAIT_TIME);
|
||||
hdd_notice("Updated ACS config to nl with reason %d", reason);
|
||||
|
||||
return 0;
|
||||
|
|
|
|||
Loading…
Reference in a new issue