From: Chris Ball <chris@printf.net>
To: Daniel Mack <daniel@zonque.org>
Cc: ulf.hansson@linaro.org, linux-mmc@vger.kernel.org,
libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] libertas: fix suspend and resume for SDIO connected cards
Date: Thu, 28 Jun 2018 00:13:42 +0100 [thread overview]
Message-ID: <20180627231342.GA32539@void.printf.net> (raw)
In-Reply-To: <20180627185845.31799-1-daniel@zonque.org>
On Wed, Jun 27, 2018 at 08:58:45PM +0200, Daniel Mack wrote:
> Prior to commit 573185cc7e64 ("mmc: core: Invoke sdio func driver's PM
> callbacks from the sdio bus"), the MMC core used to call into the power
> management functions of SDIO clients itself and removed the card if the
> return code was non-zero. IOW, the mmc handled errors gracefully and didn't
> upchain them to the pm core.
>
> Since this change, the mmc core relies on generic power management
> functions which treat all errors as a reason to cancel the suspend
> immediately. This causes suspend attempts to fail when the libertas
> driver is loaded.
>
> To fix this, power down the card explicitly in if_sdio_suspend() when we
> know we're about to lose power and return success. Also set a flag in these
> cases, and power up the card again in if_sdio_resume().
>
> Signed-off-by: Daniel Mack <daniel@zonque.org>
> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> Cc: Chris Ball <chris@printf.net>
Thanks, looks good.
Reviewed-by: Chris Ball <chris@printf.net>
--
Chris Ball <http://printf.net/>
next prev parent reply other threads:[~2018-06-27 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 18:58 [PATCH v2] libertas: fix suspend and resume for SDIO connected cards Daniel Mack
2018-06-27 23:13 ` Chris Ball [this message]
2018-06-29 15:39 ` Ulf Hansson
2018-06-29 17:57 ` Daniel Mack
2018-07-02 14:57 ` Kalle Valo
2018-07-03 4:51 ` Ulf Hansson
2018-07-04 15:13 ` [v2] " Kalle Valo
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=20180627231342.GA32539@void.printf.net \
--to=chris@printf.net \
--cc=daniel@zonque.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).