From: Jan Kiszka <jan.kiszka@web.de>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Kalle Valo <kvalo@codeaurora.org>,
Tony Lindgren <tony@atomide.com>, Eyal Reizer <eyalr@ti.com>,
linux-wireless@vger.kernel.org
Cc: Ricardo Salveti <rsalveti@rsalveti.net>,
Kishon Vijay Abraham I <kishon@ti.com>,
Anders Roxell <anders.roxell@linaro.org>,
John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH V2] wlcore: sdio: Fixup power on/off sequence
Date: Wed, 16 Jan 2019 21:26:02 +0100 [thread overview]
Message-ID: <258ecb6b-c2b2-c8b8-9804-4df69002d9f5@web.de> (raw)
In-Reply-To: <20190116113723.15668-1-ulf.hansson@linaro.org>
On 16.01.19 12:37, Ulf Hansson wrote:
> 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>
> ---
>
> Changes in v2:
> - Keep the SDIO host claimed when calling mmc_hw_reset().
> - Add a fixes tag.
> ---
> drivers/net/wireless/ti/wlcore/sdio.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/net/wireless/ti/wlcore/sdio.c b/drivers/net/wireless/ti/wlcore/sdio.c
> index bd10165d7eec..4d4b07701149 100644
> --- a/drivers/net/wireless/ti/wlcore/sdio.c
> +++ b/drivers/net/wireless/ti/wlcore/sdio.c
> @@ -164,6 +164,12 @@ static int wl12xx_sdio_power_on(struct wl12xx_sdio_glue *glue)
> }
>
> sdio_claim_host(func);
> + /*
> + * To guarantee that the SDIO card is power cycled, as required to make
> + * the FW programming to succeed, let's do a brute force HW reset.
> + */
> + mmc_hw_reset(card->host);
> +
> sdio_enable_func(func);
> sdio_release_host(func);
>
> @@ -174,20 +180,13 @@ static int wl12xx_sdio_power_off(struct wl12xx_sdio_glue *glue)
> {
> struct sdio_func *func = dev_to_sdio_func(glue->dev);
> struct mmc_card *card = func->card;
> - int error;
>
> sdio_claim_host(func);
> sdio_disable_func(func);
> sdio_release_host(func);
>
> /* Let runtime PM know the card is powered off */
> - error = pm_runtime_put(&card->dev);
> - if (error < 0 && error != -EBUSY) {
> - dev_err(&card->dev, "%s failed: %i\n", __func__, error);
> -
> - return error;
> - }
> -
> + pm_runtime_put(&card->dev);
> return 0;
> }
>
>
Just tested on both HiKey (620) and Ultra96 but it fails to fix the issue on
both. I'm getting
wl1271_sdio: probe of mmc2:0001:1 failed with error -16
during boot again, and the interface is not available.
Jan
next prev parent reply other threads:[~2019-01-16 20:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 11:37 Ulf Hansson
2019-01-16 15:43 ` Tony Lindgren
2019-01-16 15:48 ` Ulf Hansson
2019-01-16 16:18 ` Kalle Valo
2019-01-18 15:05 ` Anders Roxell
2019-01-18 15:36 ` Kalle Valo
2019-01-18 15:49 ` Tony Lindgren
2019-01-16 20:26 ` Jan Kiszka [this message]
2019-01-17 9:54 ` Ulf Hansson
2019-01-18 12:09 ` Jan Kiszka
2019-01-18 15:09 ` Ulf Hansson
2019-01-18 15:35 ` Tony Lindgren
2019-01-21 14:40 ` Ulf Hansson
2019-01-21 19:30 ` Tony Lindgren
2019-01-22 16:08 ` Jan Kiszka
2019-01-23 8:50 ` Ulf Hansson
2019-01-23 20:17 ` Jan Kiszka
2019-01-23 21:18 ` Ulf Hansson
2019-01-22 16:24 ` Kalle Valo
[not found] ` <20190122162421.7F047609B4@smtp.codeaurora.org>
2019-01-23 8:52 ` Ulf Hansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=258ecb6b-c2b2-c8b8-9804-4df69002d9f5@web.de \
--to=jan.kiszka@web.de \
--cc=anders.roxell@linaro.org \
--cc=eyalr@ti.com \
--cc=john.stultz@linaro.org \
--cc=kishon@ti.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rsalveti@rsalveti.net \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome