summaryrefslogtreecommitdiffstats
path: root/.gitignore
diff options
context:
space:
mode:
authorUlf Hansson2019-01-16 12:37:23 +0100
committerKalle Valo2019-01-22 17:23:49 +0100
commit13e62626c578d9889ebbda7c521be5adff9bef8e (patch)
treef99b8e9f87d609cad7e0a0fa3fd66affbdc1ffb7 /.gitignore
parentiwlwifi: make IWLWIFI depend on CFG80211 (diff)
downloadkernel-qcow2-linux-13e62626c578d9889ebbda7c521be5adff9bef8e.tar.gz
kernel-qcow2-linux-13e62626c578d9889ebbda7c521be5adff9bef8e.tar.xz
kernel-qcow2-linux-13e62626c578d9889ebbda7c521be5adff9bef8e.zip
wlcore: sdio: Fixup power on/off sequence
During "wlan-up", we are programming the FW into the WiFi-chip. However, re-programming the FW doesn't work, unless a power cycle of the WiFi-chip is made in-between the programmings. To conform to this requirement and to fix the regression in a simple way, let's start by allowing that the SDIO card (WiFi-chip) may stay powered on (runtime resumed) when wl12xx_sdio_power_off() returns. The intent with the current code is to treat this scenario as an error, but unfortunate this doesn't work as expected, so let's fix this. The other part is to guarantee that a power cycle of the SDIO card has been completed when wl12xx_sdio_power_on() returns, as to allow the FW programming to succeed. However, relying solely on runtime PM to deal with this isn't sufficient. For example, userspace may prevent runtime suspend via sysfs for the device that represents the SDIO card, leading to that the mmc core also keeps it powered on. For this reason, let's instead do a brute force power cycle in wl12xx_sdio_power_on(). Fixes: 728a9dc61f13 ("wlcore: sdio: Fix flakey SDIO runtime PM handling") Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Tested-by: Tony Lindgren <tony@atomide.com> Tested-by: Anders Roxell <anders.roxell@linaro.org> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions