aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPark Ju Hyung <qkrwngud825@gmail.com>2019-03-06 13:52:17 +0900
committerjro1979oliver <jroliveira.oliveira301@gmail.com>2022-08-02 19:53:58 +0200
commit5e14e3d127aea8013057ed7a2e9fcdf5dc2f1fb2 (patch)
treebaaa0ce66721a91432821f3e24e4dd39080aeb03
parent6b6b676220473fa39d1bda6884f6da9ca4c30831 (diff)
qcacld: disable qcom_rx_wakelock
qcom_rx_wakelock is one of the major culprit to increased power consumption. Although its total wakelock time is quite low, it's catched very frequently and prevents the system from entering suspend repeatedly. Original intention of this wakelock is to prevent dropping unicast or local ARP packet, but I'm having a hard time understanding why are those packets critical to regular Android users. qcacld's packet filter will still allow notifications to flow in. Disable qcom_rx_wakelock by forcing rx_wakelock_timeout to 0. Signed-off-by: Park Ju Hyung <qkrwngud825@gmail.com> Change-Id: I8234f1e753c953684515aea37e7adc84afe33bfb
-rw-r--r--drivers/staging/qcacld-3.0/core/hdd/src/wlan_hdd_cfg.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/drivers/staging/qcacld-3.0/core/hdd/src/wlan_hdd_cfg.c b/drivers/staging/qcacld-3.0/core/hdd/src/wlan_hdd_cfg.c
index baa828a561e4..09067280125c 100644
--- a/drivers/staging/qcacld-3.0/core/hdd/src/wlan_hdd_cfg.c
+++ b/drivers/staging/qcacld-3.0/core/hdd/src/wlan_hdd_cfg.c
@@ -4547,9 +4547,7 @@ struct reg_table_entry g_registry_table[] = {
REG_VARIABLE(CFG_RX_WAKELOCK_TIMEOUT_NAME, WLAN_PARAM_Integer,
struct hdd_config, rx_wakelock_timeout,
VAR_FLAGS_OPTIONAL | VAR_FLAGS_RANGE_CHECK_ASSUME_DEFAULT,
- CFG_RX_WAKELOCK_TIMEOUT_DEFAULT,
- CFG_RX_WAKELOCK_TIMEOUT_MIN,
- CFG_RX_WAKELOCK_TIMEOUT_MAX),
+ 0, 0, 0),
REG_VARIABLE(CFG_SAP_CH_SWITCH_BEACON_CNT, WLAN_PARAM_Integer,
struct hdd_config, sap_chanswitch_beacon_cnt,