wl12xx/wl18xx: use a dynamic PS timeout of 1.5sec
It seems some parties have bad user experience when smaller values are used. This should have little implications for power consumption, since traffic is bursty in nature. Signed-off-by: Arik Nemtsov <arik@wizery.com>
This commit is contained in:
parent
091185d6bc
commit
0fc1d2e9fe
2 changed files with 2 additions and 2 deletions
|
@ -242,7 +242,7 @@ static struct wlcore_conf wl12xx_conf = {
|
|||
.psm_entry_retries = 8,
|
||||
.psm_exit_retries = 16,
|
||||
.psm_entry_nullfunc_retries = 3,
|
||||
.dynamic_ps_timeout = 200,
|
||||
.dynamic_ps_timeout = 1500,
|
||||
.forced_ps = false,
|
||||
.keep_alive_interval = 55000,
|
||||
.max_listen_interval = 20,
|
||||
|
|
|
@ -369,7 +369,7 @@ static struct wlcore_conf wl18xx_conf = {
|
|||
.psm_entry_retries = 8,
|
||||
.psm_exit_retries = 16,
|
||||
.psm_entry_nullfunc_retries = 3,
|
||||
.dynamic_ps_timeout = 200,
|
||||
.dynamic_ps_timeout = 1500,
|
||||
.forced_ps = false,
|
||||
.keep_alive_interval = 55000,
|
||||
.max_listen_interval = 20,
|
||||
|
|
Loading…
Reference in a new issue