A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-14 00:24:41 -04:00
Code Issues Projects Releases Packages Wiki Activity

qcacld-3.0: Enable network queue directly in case of roaming

Browse source 
Currently in the case of roaming between latency-critical connection
and non-latency critical connection we are scheduling work to
update features and after feature update we are enabling network queues
which is introducing a delay in enabling queues due to work schedule.

To Fix the issue enable network queue in the current context and schedule
work to update features.

Change-Id: Idba5b81a58aaf2bd47d80da1d17ad0acf9939071
CRs-Fixed: 3070688
This commit is contained in:
Amit Mehta 2021-11-08 14:38:00 +05:30 • committed by Madan Koyyalamudi
commit 05734c5c11
2 changed files with 8 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

7
core/hdd/src/wlan_hdd_assoc.c
View file

@ -2943,11 +2943,10 @@ static inline void hdd_netif_queue_enable(struct hdd_adapter *adapter)
adapter->vdev_id);
qdf_queue_work(0, hdd_ctx->adapter_ops_wq,
&adapter->netdev_features_update_work);
} else {
wlan_hdd_netif_queue_control(adapter,
WLAN_WAKE_ALL_NETIF_QUEUE,
WLAN_CONTROL_PATH);
}
wlan_hdd_netif_queue_control(adapter,
WLAN_WAKE_ALL_NETIF_QUEUE,
WLAN_CONTROL_PATH);
}
static void hdd_save_connect_status(struct hdd_adapter *adapter,

18
core/hdd/src/wlan_hdd_main.c
View file

@ -10725,24 +10725,16 @@ __hdd_adapter_param_update_work(struct hdd_adapter *adapter)
{
/**
* This check is needed in case the work got scheduled after the
* interface got disconnected. During disconnection, the network queues
* are paused and hence should not be, mistakenly, restarted here.
* There are two approaches to handle this case
* 1) Flush the work during disconnection
* 2) Check for connected state in work
*
* Since the flushing of work during disconnection will need to be
* done at multiple places or entry points, instead its preferred to
* check the connection state and skip the operation here.
* interface got disconnected.
* Netdev features update is to be done only after the connection,
* since the connection mode plays an important role in identifying
* the features that are to be updated.
* So in case of interface disconnect skip feature update.
*/
if (!hdd_adapter_is_connected_sta(adapter))
return;
hdd_netdev_update_features(adapter);
hdd_debug("Enabling queues");
wlan_hdd_netif_queue_control(adapter, WLAN_WAKE_ALL_NETIF_QUEUE,
WLAN_CONTROL_PATH);
}
/**