All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Ulf Hansson <ulf.hansson@stericsson.com>,
	linux-mmc@vger.kernel.org, Per Forlin <per.forlin@stericsson.com>,
	Johan Rudholm <johan.rudholm@stericsson.com>,
	Lee Jones <lee.jones@linaro.org>,
	Jasi Brar <jassisinghbrar@gmail.com>,
	Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] mmc: core: Prevent eMMC VCC supply to be cut from late init
Date: Wed, 09 May 2012 12:56:05 -0400	[thread overview]
Message-ID: <87zk9hmgyi.fsf@laptop.org> (raw)
In-Reply-To: <20120509155622.GE3955@opensource.wolfsonmicro.com> (Mark Brown's message of "Wed, 9 May 2012 16:56:23 +0100")

Hi,

On Wed, May 09 2012, Mark Brown wrote:
> On Wed, May 09, 2012 at 04:15:26PM +0200, Ulf Hansson wrote:
>> From: Ulf Hansson <ulf.hansson@linaro.org>
>> 
>> For eMMC cards that has been initialized from a bootloader,
>> the VCC voltage supply must not be cut in an uncontrolled
>> manner, without first sending SLEEP or POWEROFF_NOTIFY.
>> 
>> The regulator_init_complete late initcall, may cut the VCC
>> regulator if it's reference counter is zero. To be able to
>> prevent the regulator from being cut, mmc_start_host, which
>> should execute at device init and thus before late init,
>> calls mmc_power_up. Then the host driver is able to increase
>> the reference to the regulator.
>
> This looks like a good, simple solution - working out how we avoid extra
> power ups will probably be more invasive and might not be worth the
> effort for something that's boot time only.
>
> Reviwed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

Thanks, pushed to mmc-next for 3.5.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2012-05-09 16:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 14:15 [PATCH] mmc: core: Prevent eMMC VCC supply to be cut from late init Ulf Hansson
2012-05-09 15:56 ` Mark Brown
2012-05-09 16:56   ` Chris Ball [this message]
2012-07-10 15:19 ` Girish K S
2012-07-10 17:32   ` Chris Ball
2012-07-11 12:40     ` Girish K S

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=87zk9hmgyi.fsf@laptop.org \
    --to=cjb@laptop.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=johan.rudholm@stericsson.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=per.forlin@stericsson.com \
    --cc=ulf.hansson@linaro.org \
    --cc=ulf.hansson@stericsson.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.