From: Chris Ball <cjb@laptop.org>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-mmc@vger.kernel.org, Daniel Drake <dsd@laptop.org>,
Arnd Hannemann <arnd@arndnet.de>
Subject: Re: [PATCH] sdio: fix runtime PM anomalies by introducing MMC_CAP_POWER_OFF_CARD
Date: Fri, 19 Nov 2010 22:08:46 +0000 [thread overview]
Message-ID: <20101119220846.GD19272@void.printf.net> (raw)
In-Reply-To: <1290151749-21308-1-git-send-email-ohad@wizery.com>
Hi Ohad,
On Fri, Nov 19, 2010 at 09:29:09AM +0200, Ohad Ben-Cohen wrote:
> Some board/card/host configurations are not capable of powering off the
> card after boot.
>
> To support such configurations, and to allow smoother transition to
> runtime PM behavior, MMC_CAP_POWER_OFF_CARD is added, so hosts need to
> explicitly indicate whether it's OK to power off their cards after boot.
>
> SDIO core will enable runtime PM for a card only if that cap is set.
> As a result, the card will be powered down after boot, and will only
> be powered up again when a driver is loaded (and then it's up to the
> driver to decide whether power will be kept or not).
>
> This will prevent sdio_bus_probe() failures with setups that do not
> support powering off the card.
>
> Reported-and-tested-by: Daniel Drake <dsd@laptop.org>
> Reported-and-tested-by: Arnd Hannemann <arnd@arndnet.de>
> Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
Thanks for doing this. Pushed to for-linus/mmc-next for 2.6.37; I'll
send a pull request once we have the fix for the 8-bit MMC regression
lined up too.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2010-11-19 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 7:29 [PATCH] sdio: fix runtime PM anomalies by introducing MMC_CAP_POWER_OFF_CARD Ohad Ben-Cohen
2010-11-19 22:08 ` Chris Ball [this message]
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=20101119220846.GD19272@void.printf.net \
--to=cjb@laptop.org \
--cc=arnd@arndnet.de \
--cc=dsd@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ohad@wizery.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.