From: Chris Ball <chris@printf.net>
To: Chao Xu <caesarxuchao@gmail.com>
Cc: Luciano Coelho <luciano.coelho@intel.com>,
ohad@wizery.com, linux-mmc@vger.kernel.org
Subject: Re: wl1271: sdio: is fine-grained runtime_pm possible?
Date: Tue, 14 Jan 2014 03:27:00 +0000 [thread overview]
Message-ID: <867ga39raz.fsf@void.printf.net> (raw)
In-Reply-To: <CAKZq+rdaCivZTFSTGt9_Q+3KFE9Ft0XfmWZ=1Vr7QcDDs9=Muw@mail.gmail.com> (Chao Xu's message of "Mon, 13 Jan 2014 20:58:02 -0600")
Hi,
On Tue, Jan 14 2014, Chao Xu wrote:
> The patch "SDIO Runtime PM Support" implements the pm for wl12xx
> driver this way: the power for sdio is on whenever the WLAN interface
> is on, and the power is down only when the interface is down.
> Is it possible to do pm in a more fine-grained way, such as only
> turning on the power when reading/writing through sdio? An example is
> the mmc_blk_issue_rq() in drivers/mmc/card/block.c, where the host is
> released when there are no more requests. And in turn the host driver,
> such as omap_hsmmc.c, calls pm_runtime_put_autosuspend().
> Is there any fundamental argument against doing fine-grained runtime
> pm for sdio? Or is it just too much trouble for too little power
> saved?
> Thank you!
I feel like I must be missing something, but:
Network devices generate interrupts when you have new network activity
to process, and to generate an interrupt they need to be turned on.
How would you avoid having the WLAN device be unpowered while someone
is trying to talk to you?
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
next prev parent reply other threads:[~2014-01-14 3:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 2:58 wl1271: sdio: is fine-grained runtime_pm possible? Chao Xu
2014-01-14 3:27 ` Chris Ball [this message]
2014-01-14 4:46 ` Chao Xu
2014-01-14 8:36 ` Ulf Hansson
2014-01-14 22:12 ` Chao Xu
2014-01-15 10:46 ` Ulf Hansson
2014-01-18 22:44 ` Chao Xu
2014-01-24 8:15 ` 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=867ga39raz.fsf@void.printf.net \
--to=chris@printf.net \
--cc=caesarxuchao@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--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.