From: Chris Ball <chris@printf.net>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Tomasz Figa <t.figa@samsung.com>, Olof Johansson <olof@lixom.net>,
linux-mmc <linux-mmc@vger.kernel.org>,
devicetree@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
robh+dt@kernel.org, mark.rutland@arm.com,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/3] mmc: add support for power-on sequencing through DT
Date: Tue, 28 Jan 2014 01:08:32 +0000 [thread overview]
Message-ID: <861tzs29rj.fsf@void.printf.net> (raw)
In-Reply-To: <52E700F0.7040708@gmail.com> (Tomasz Figa's message of "Tue, 28 Jan 2014 01:59:28 +0100")
Hi,
On Tue, Jan 28 2014, Tomasz Figa wrote:
>> I am not sure I understand why this is needed. I think it would be
>> more convenient to use MMC_CAP_NONREMOVABLE instead as stated earlier.
>> But please elaborate, I might have missed something.
>
> See above. I'm not quite convinced that state of MMC interface should
> determine power state of the chip. I can easily imagine a situation
> where the MMC link is powered down (link power management) but the
> WLAN chip keeps operation. Keep in mind that those are usually
> complete SoCs that can keep processing network traffic autonomously
> and wake-up the application processor whenever anything interesting
> happens using extra out of bounds signalling, which might trigger
> re-enabling the MMC link.
For what it's worth, we did this using upstream code (libertas-sd8686
WLAN with sdhci-pxav3) at OLPC. We set the SDIO device to 1-bit mode
on system suspend, using MMC_CAP_NONREMOVABLE, MMC_PM_KEEP_POWER and
MMC_PM_WAKE_SDIO_IRQ, and tell the PMU to wake on the 1-bit data line.
When it wakes the system, the system sees the SDIO interrupt and
processes the waiting network traffic.
So this use case is already supported using the current interfaces.
If this interface doesn't work for your use case, could you talk a
little more about what you're trying to achieve?
Thanks,
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
next prev parent reply other threads:[~2014-01-28 1:08 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 3:56 [PATCH 0/3] RFC/RFT: Powering on MMC Wifi/BT modules in MMC core Olof Johansson
2014-01-20 3:56 ` [PATCH 1/3] mmc: add support for power-on sequencing through DT Olof Johansson
2014-01-20 8:44 ` Ulf Hansson
2014-01-20 19:13 ` Olof Johansson
2014-01-21 8:55 ` Ulf Hansson
2014-01-21 18:14 ` Olof Johansson
2014-01-22 11:30 ` Mark Brown
2014-01-20 16:36 ` Mark Brown
2014-01-20 16:48 ` Russell King - ARM Linux
2014-01-20 17:03 ` Fabio Estevam
2014-01-20 17:16 ` Russell King - ARM Linux
2014-01-20 18:47 ` Fabio Estevam
2014-01-21 19:19 ` Russell King - ARM Linux
2014-01-24 17:35 ` Fabio Estevam
2014-01-27 8:43 ` Jyri Sarha
2014-01-27 8:54 ` Chen-Yu Tsai
2014-01-27 9:48 ` Jyri Sarha
2014-01-20 18:58 ` Arnd Bergmann
[not found] ` <201401201958.57997.arnd-r2nGTMty4D4@public.gmane.org>
2014-01-20 19:04 ` Olof Johansson
2014-01-20 19:12 ` Arnd Bergmann
2014-01-20 19:14 ` Fabio Estevam
2014-01-20 19:14 ` Olof Johansson
2014-01-21 7:24 ` Sascha Hauer
2014-01-21 7:25 ` Sascha Hauer
2014-01-21 18:34 ` Tomasz Figa
2014-01-21 21:30 ` Olof Johansson
2014-01-21 21:39 ` Tomasz Figa
2014-01-26 17:26 ` Tomasz Figa
2014-01-27 10:19 ` Ulf Hansson
2014-01-28 0:59 ` Tomasz Figa
2014-01-28 1:08 ` Chris Ball [this message]
2014-01-28 10:06 ` Ulf Hansson
2014-01-28 10:48 ` Arnd Bergmann
2014-02-12 18:33 ` Mark Brown
2014-02-13 8:56 ` Ulf Hansson
2014-02-13 9:01 ` Tomasz Figa
2014-02-13 10:42 ` Russell King - ARM Linux
2014-02-13 12:48 ` Arnd Bergmann
2014-02-13 14:41 ` Russell King - ARM Linux
2014-02-13 16:13 ` Arnd Bergmann
2014-02-13 17:31 ` Olof Johansson
2014-02-15 12:18 ` Arnd Bergmann
2014-02-15 12:27 ` Russell King - ARM Linux
2014-02-15 13:09 ` Arnd Bergmann
2014-02-15 13:22 ` Tomasz Figa
2014-02-15 16:21 ` Arnd Bergmann
2014-02-15 20:52 ` Russell King - ARM Linux
2014-02-15 21:35 ` Tomasz Figa
2014-02-15 22:03 ` Russell King - ARM Linux
2014-02-17 13:00 ` Arnd Bergmann
2014-02-17 23:25 ` Mark Brown
2014-01-20 3:56 ` [PATCH 2/3] mmc: dw_mmc: call mmc_of_parse to fill in common options Olof Johansson
2014-01-20 4:53 ` Jaehoon Chung
2014-01-20 3:56 ` [PATCH 3/3] ARM: dts: exynos5250-snow: Enable wifi power-on Olof Johansson
2014-01-30 21:49 ` [PATCH 0/3] RFC/RFT: Powering on MMC Wifi/BT modules in MMC core Russell King - ARM Linux
2014-02-01 16:14 ` Russell King - ARM Linux
2014-02-13 10:36 ` Russell King - ARM Linux
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=861tzs29rj.fsf@void.printf.net \
--to=chris@printf.net \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=t.figa@samsung.com \
--cc=tomasz.figa@gmail.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;
as well as URLs for NNTP newsgroup(s).