linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: mmci: Improve runtime PM support
Date: Mon, 24 Oct 2011 10:04:32 +0100	[thread overview]
Message-ID: <20111024090432.GA9893@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4EA51C4A.7040802@stericsson.com>

On Mon, Oct 24, 2011 at 10:05:30AM +0200, Ulf Hansson wrote:
> Sebastian Rasmussen wrote:
>> Hi!
>>
>>> Err, no.  You're not allowed to power down the card between commands
>>> unless the card has been removed or been has finished with.
>>>
>>> If you power down the card (which you _are_ doing by writing zero to
>>> the MMCIPOWER register), then you have to do a full setup of the card
>>> when you resume.
>>
>> MCIPower is according to ARM PL180 TRM signalling to an external power
>> supply to turn on/off (MCIPWR), whether to use open-drain (MCIROD),
>> what voltage to use (MCIVDD) and whether the card is clocked (MCICLK).
>>
>> According ST-Ericsson's public PL180 derivative spec[1] it seems to work
>> roughly in same way (but renaming the register SDI_PWR and the signals
>> SDIPWR & SDICLK). However, there is no SDIVDD as the derivative can not
>> signal desired voltage level externally (there are no bits in SDI_PWR for this).
>> This makes it plausible that SDIPWR may not be routed externally either.
>> Can you verify this as there are no signal routing diagrams in the spec..?
>>
>
> The hole idea with this PM patch is to make sure the vcore regulator and  
> the clock are disabled in runtime_suspend to be able to save a huge  
> amount of current in "idle" mode.
>
> Disabling the vcore regulator will sooner or later (depending on your  
> regulator tree) mean that that power to the controller is actually cut,  
> which then means that all registers will be "cleared" including the  
> MCIPWR. So the actual reason for clearing the registers in the  
> runtime_suspend function is because of two reasons.
>
> 1. Set the controller in a known state so no "magic" things happens when  
> we are runtime suspended, for example getting an IRQ.
>
> 2. Save power by disabling the clock etc. The actual power to the  
> controller does not have to be cut just because we have disabled the  
> vore regulator.
>
> If the ARM PL180 TRM prevent us from from doing this kind of operations  
> in runtime_suspend, we must think of an alternative solution which just  
> apply for ST-Ericssons derivative of PL180. THIS IS VERY IMPORTANT to be  
> able to implement a proper power management solution.
>
> Please check this Russell, this is VERY IMPORTANT!

I repeat: if you cut power to the card, you have to re-initialize it.
Re-initialization takes quite a bit of time to re-detect and setup
the card.  You'd also need to re-configure things like the transfer
mode and so forth.

The other problem is if you're doing runtime-pm between commands,
the re-initialization takes multiple commands - we don't want to be
in the middle of a reinitialization while we're also doing something
with runtime-pm - nested initialization would not be a nice problem
to solve.

  reply	other threads:[~2011-10-24  9:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 15:25 [PATCH] mmc: mmci: Improve runtime PM support Ulf Hansson
2011-10-21 17:36 ` Russell King - ARM Linux
     [not found]   ` <CAKnu2MrOriMzJH9NcwUivWa0cinASa6wrRf4a69si4WUs-aTrQ@mail.gmail.com>
2011-10-23  0:31     ` Sebastian Rasmussen
2011-10-24  8:05       ` Ulf Hansson
2011-10-24  9:04         ` Russell King - ARM Linux [this message]
2011-10-24  9:36           ` Ulf Hansson
2011-10-24  9:42             ` Russell King - ARM Linux
2011-10-24 10:06               ` Ulf Hansson
2011-10-24 10:14                 ` Russell King - ARM Linux
2011-10-24 11:48                   ` Ulf Hansson
2011-10-24 12:18                     ` Linus Walleij
2011-10-24 15:25                       ` Ulf Hansson
2011-10-24 15:34                         ` Ulf Hansson
2011-10-25  7:12                         ` Linus Walleij
2011-10-25  7:39                           ` Ulf Hansson
2011-10-24  9:11         ` Sebastian Rasmussen
2011-10-24  9:14         ` Linus Walleij
2011-10-24  9:36       ` Russell King - ARM Linux
2011-10-24  9:54         ` Linus Walleij
2011-10-24  9:56           ` Russell King - ARM Linux
2011-10-24 10:17             ` Ulf Hansson
2011-10-24 11:49               ` Linus Walleij
2011-10-25  8:05             ` Adrian Hunter
2011-10-25  8:53               ` Linus Walleij

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=20111024090432.GA9893@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).