From: Daniel Drake <dsd@laptop.org>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-mmc@vger.kernel.org, Chris Ball <cjb@laptop.org>
Subject: Re: MMC runtime PM patches break libertas probe
Date: Sun, 7 Nov 2010 10:51:25 +0000 [thread overview]
Message-ID: <AANLkTimcoDvfVLxF6c3c78yeBOoNGsuTm1ZaSujM0A4b@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinXyW-iymJUeXGODLLBOevTwyUOcROg-B1wwJcA@mail.gmail.com>
On 7 November 2010 10:42, Ohad Ben-Cohen <ohad@wizery.com> wrote:
> Good. Did it also solve the 1st issue you had ?
Yes.
>> But, what you point out is quite interesting.
>> We currently have a (not-yet-upstream) rfkill driver for the XO-1.5,
>> which we also put in place for power saving reasons.
>
> Can you please elaborate ? What power saving ? How do you exactly plan
> to use it ? Do you plan to power off the card without taking the wlan
> interface down first ?
If you take the interface down, the card is still powered up in some
way. We were looking for a way to cut as much power as possible.
It can be used by the "rfkill block wifi" command, and theres a
checkbox available in the sugar UI which calls that.
> Chris and I briefly discussed this in LPC, and he mentioned that you
> might have an external power source to that card, that is not
> controlled by the mmc regulator, and which you disable/enable from
> user space just before suspending the host ?
Not sure what he's referring to there. Perhaps he can clarify.
When I asked the hardware guy he said it was entirely controlled by
the normal SD power pin, but a full card reset will be needed after
cycling the power.
Daniel
next prev parent reply other threads:[~2010-11-07 10:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 14:29 MMC runtime PM patches break libertas probe Daniel Drake
2010-10-31 14:42 ` Ohad Ben-Cohen
2010-10-31 14:55 ` Daniel Drake
2010-10-31 15:08 ` Ohad Ben-Cohen
2010-10-31 15:10 ` Daniel Drake
2010-10-31 15:16 ` Ohad Ben-Cohen
2010-10-31 15:21 ` Daniel Drake
2010-10-31 15:21 ` Daniel Drake
2010-10-31 15:27 ` Ohad Ben-Cohen
2010-10-31 15:57 ` Daniel Drake
2010-10-31 16:16 ` Ohad Ben-Cohen
2010-10-31 16:24 ` Daniel Drake
2010-10-31 19:06 ` Ohad Ben-Cohen
2010-11-01 8:27 ` Ohad Ben-Cohen
2010-11-06 21:19 ` Daniel Drake
2010-11-07 1:48 ` Nicolas Pitre
2010-11-07 10:19 ` Daniel Drake
2010-11-07 15:12 ` Nicolas Pitre
2010-11-07 10:42 ` Ohad Ben-Cohen
2010-11-07 10:51 ` Daniel Drake [this message]
2010-11-07 13:17 ` Ohad Ben-Cohen
2010-11-16 13:22 ` Ohad Ben-Cohen
2010-11-16 14:29 ` Daniel Drake
2010-11-16 14:49 ` Ohad Ben-Cohen
2010-11-17 6:46 ` Mike Rapoport
2010-11-17 7:29 ` Ohad Ben-Cohen
2010-11-17 14:54 ` Nicolas Pitre
2010-11-16 17:17 ` Arnd Hannemann
2010-11-16 20:58 ` Ohad Ben-Cohen
2010-11-16 21:16 ` Arnd Hannemann
2010-11-16 22:26 ` Ohad Ben-Cohen
2011-05-29 16:21 ` Daniel Drake
2011-05-30 6:52 ` Ohad Ben-Cohen
2011-05-30 7:01 ` Daniel Drake
2011-05-30 7:32 ` Ohad Ben-Cohen
2011-05-30 11:04 ` zhangfei gao
2011-05-30 11:16 ` Ohad Ben-Cohen
2011-06-02 8:39 ` Bing Zhao
2011-06-02 18:25 ` Ohad Ben-Cohen
2011-06-03 22:28 ` Bing Zhao
2011-06-03 22:52 ` Ohad Ben-Cohen
2011-06-07 14:34 ` Arnd Hannemann
2011-06-07 14:45 ` Ohad Ben-Cohen
2011-06-08 14:34 ` Ohad Ben-Cohen
2011-06-10 2:02 ` zhangfei gao
2011-06-10 4:28 ` Ohad Ben-Cohen
2011-06-11 2:33 ` zhangfei gao
2011-06-11 9:03 ` Ohad Ben-Cohen
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=AANLkTimcoDvfVLxF6c3c78yeBOoNGsuTm1ZaSujM0A4b@mail.gmail.com \
--to=dsd@laptop.org \
--cc=cjb@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.