summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPadma, Santhosh Kumar <skpadma@qti.qualcomm.com>2014-01-17 19:51:54 +0530
committerPrakash Dhavali <pdhavali@qca.qualcomm.com>2014-01-26 21:37:02 -0800
commit9b968fc930ecf1927237a70deb736870b3b571b7 (patch)
treed51c0f38252ad69365e3c1ae31ef11212a447166
parent631295212558656d3a6fc26bce33e44f8bdc0880 (diff)
wlan: Updating suspension_interval from Tspec
Variable suspension_interval is hardcoded to zero.Since cisco requires zero inactivity_interval and as per spec suspension_interval should always be less than inactivity_interval, suspension_interval is hardcoded to zero. But this is giving issue of sending the trigger frames at service interval periods rather than sending at Delay interval period when there is no activity from STA. This fix updates suspension_interval from Tspec rather than hardcoding. Change-Id: I57cfd4e2ef3995be6fb0d6e3bd74fd2259180200 CRs-Fixed: 600697
-rw-r--r--CORE/SME/src/QoS/sme_Qos.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/CORE/SME/src/QoS/sme_Qos.c b/CORE/SME/src/QoS/sme_Qos.c
index fd61b087d8f2..54ee3567f75a 100644
--- a/CORE/SME/src/QoS/sme_Qos.c
+++ b/CORE/SME/src/QoS/sme_Qos.c
@@ -5788,7 +5788,7 @@ eHalStatus sme_QosAggregateParams(
requires inactivity interval to be > suspension interval: this could
be tricky!
-------------------------------------------------------------------------*/
- TspecInfo.suspension_interval = 0;
+ TspecInfo.suspension_interval = pInput_Tspec_Info->suspension_interval;
/*-------------------------------------------------------------------------
Remaining parameters do not come from app as they are very WLAN
air interface specific