summaryrefslogtreecommitdiff
path: root/drivers/net/wireless/ath/ath9k/xmit.c
diff options
context:
space:
mode:
authorPin-yen Lin <treapking@chromium.org>2024-11-27 18:55:43 +0800
committerKalle Valo <kvalo@kernel.org>2024-12-09 17:59:45 +0200
commitf143cece43dd05fa651fa14d97726b67b92e9d03 (patch)
tree073abda29aa962db4ca7c1cd7d9f492429ff1e86 /drivers/net/wireless/ath/ath9k/xmit.c
parentaba23b0a6a0df84b06ed0323ce127bf7257e4025 (diff)
wifi: mwifiex: decrease timeout waiting for host sleep from 10s to 5s
In commit 52250cbee7f6 ("mwifiex: use timeout variant for wait_event_interruptible") it was noted that sometimes we seemed to miss the signal that our host sleep settings took effect. A 10 second timeout was added to the code to make sure we didn't hang forever waiting. It appears that this problem still exists and we hit the timeout sometimes for Chromebooks in the field. Recently on ChromeOS we've started setting the DPM watchdog to trip if full system suspend takes over 10 seconds. Given the timeout in the original patch, obviously we're hitting the DPM watchdog before mwifiex gets a chance to timeout. While we could increase the DPM watchdog in ChromeOS to avoid this problem, it's probably better to simply decrease the timeout. Any time we're waiting several seconds for the firmware to respond it's likely that the firmware won't ever respond. With that in mind, decrease the timeout in mwifiex from 10 seconds to 5 seconds. Suggested-by: Doug Anderson <dianders@chromium.org> Signed-off-by: Pin-yen Lin <treapking@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> Acked-by: Brian Norris <briannorris@chromium.org> Signed-off-by: Kalle Valo <kvalo@kernel.org> Link: https://patch.msgid.link/20241127105709.4014302-1-treapking@chromium.org
Diffstat (limited to 'drivers/net/wireless/ath/ath9k/xmit.c')
0 files changed, 0 insertions, 0 deletions