qcacmn: Fix core_ctl_set_boost not released issue
hdd_napi_serialize(0) will call hif_napi_event() with NAPI_EVT_USR_NORMAL mode. But in this mode, blacklist_pending is not set as BLACKLIST_OFF_PENDING, so the function hif_napi_core_ctl_set_boost(false) is not called. Then core_ctl can not resume to normal status, which will result in performance and power issues. Change-Id: Ia2084d9febab0ff4aadb0951bd3347f608a1d101 CRs-Fixed: 2381895
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
/*
|
||||
* Copyright (c) 2015-2018 The Linux Foundation. All rights reserved.
|
||||
* Copyright (c) 2015-2019 The Linux Foundation. All rights reserved.
|
||||
*
|
||||
* Permission to use, copy, modify, and/or distribute this software for
|
||||
* any purpose with or without fee is hereby granted, provided that the
|
||||
@@ -192,6 +192,8 @@ int hif_exec_event(struct hif_opaque_softc *hif_ctx, enum qca_napi_event event,
|
||||
}
|
||||
case NAPI_EVT_USR_NORMAL: {
|
||||
NAPI_DEBUG("%s: User forced DE-SERIALIZATION", __func__);
|
||||
if (!napid->user_cpu_affin_mask)
|
||||
blacklist_pending = BLACKLIST_OFF_PENDING;
|
||||
/*
|
||||
* Deserialization timeout is handled at hdd layer;
|
||||
* just mark current mode to uninitialized to ensure
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/*
|
||||
* Copyright (c) 2015-2018 The Linux Foundation. All rights reserved.
|
||||
* Copyright (c) 2015-2019 The Linux Foundation. All rights reserved.
|
||||
*
|
||||
* Permission to use, copy, modify, and/or distribute this software for
|
||||
* any purpose with or without fee is hereby granted, provided that the
|
||||
@@ -632,6 +632,8 @@ int hif_napi_event(struct hif_opaque_softc *hif_ctx, enum qca_napi_event event,
|
||||
}
|
||||
case NAPI_EVT_USR_NORMAL: {
|
||||
NAPI_DEBUG("%s: User forced DE-SERIALIZATION", __func__);
|
||||
if (!napid->user_cpu_affin_mask)
|
||||
blacklist_pending = BLACKLIST_OFF_PENDING;
|
||||
/*
|
||||
* Deserialization timeout is handled at hdd layer;
|
||||
* just mark current mode to uninitialized to ensure
|
||||
|
Reference in New Issue
Block a user