summaryrefslogtreecommitdiffstats
path: root/drivers/net/bonding/bond_3ad.c
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2018-06-19 02:43:39 -0700
committerKalle Valo <kvalo@codeaurora.org>2018-06-27 18:45:12 +0300
commitdb68052bdf581eb5e7f74da4a5bb5933113dbaaf (patch)
tree4e1748c31993fbd249478987d56fdccaad83f785 /drivers/net/bonding/bond_3ad.c
parent3ebbabea4219816ff148209473e074adaaa5f610 (diff)
downloadlinux-stable-db68052bdf581eb5e7f74da4a5bb5933113dbaaf.tar.gz
linux-stable-db68052bdf581eb5e7f74da4a5bb5933113dbaaf.tar.bz2
linux-stable-db68052bdf581eb5e7f74da4a5bb5933113dbaaf.zip
wlcore: Fix timout errors after recovery
After enabling runtime PM, if we force hardware reset multiple times with: # echo 1 > /sys/kernel/debug/ieee80211/phy0/wlcore/start_recovery We will after few tries get the following error: wlcore: ERROR timeout waiting for the hardware to complete initialization And then wlcore is unable to reconnect until after the wlcore related modules are reloaded. Let's fix this by moving pm_runtime_put() earlier before we restart the hardware. And let's use the sync version to make sure we're done before we restart. Note that we still will get -EBUSY warning from wl12xx_sdio_set_power() but let's fix that separately once we know exactly why we get the warning. Reported-by: Eyal Reizer <eyalr@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'drivers/net/bonding/bond_3ad.c')
0 files changed, 0 insertions, 0 deletions