Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: Subhash Jadavani <subhashj@codeaurora.org>,
	linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Girish K S <girish.shivananjappa@linaro.org>
Subject: Re: [PATCH v1 1/1] mmc: core: fix power class selection
Date: Tue, 03 Apr 2012 07:32:14 -0400	[thread overview]
Message-ID: <87fwclhwzl.fsf@laptop.org> (raw)
In-Reply-To: <CAKYAXd_9AwrBpbVoZxPN6JNcg1SQP6pemJ4gAY4gZQKRQexqmg@mail.gmail.com> (Namjae Jeon's message of "Tue, 3 Apr 2012 17:06:35 +0900")

Hi,

On Tue, Apr 03 2012, Namjae Jeon wrote:
> 2012/4/3 Girish K S <girish.shivananjappa@linaro.org>:
>> On 3 April 2012 15:55, Subhash Jadavani <subhashj@codeaurora.org> wrote:
>>> mmc_select_powerclass() function returns error if eMMC
>>> VDD level supported by host is between 2.7v to 3.2v.
>>>
>>> According to eMMC specification, valid voltage for high
>>> voltage cards is 2.7v to 3.6v. This patch ensures that
>>> 2.7v to 3.6v VDD range is treated as valid range.
>>>
>>> Also, failure to set the power class shouldn't be treated
>>> as fatal error because even if setting the power class
>>> fails, card can still work in default power class.
>>> If mmc_select_powerclass() returns error, just print
>>> the warning message and go ahead with rest of the card
>>> initialization.
>>>
>>> Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
>> looks good to me
>> Acked By:  Girish K S <girish.shivananjappa@linaro.org>
>
> I double checked with specification. this patch make good sense.
> Reviewed-by: Namjae Jeon <linkinjeon@gmail.com>

Thanks, pushed to mmc-next for 3.4.

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

  reply	other threads:[~2012-04-03 11:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03  6:55 [PATCH v1 1/1] mmc: core: fix power class selection Subhash Jadavani
2012-04-03  7:19 ` Girish K S
2012-04-03  8:06   ` Namjae Jeon
2012-04-03 11:32     ` Chris Ball [this message]
2012-04-03 15:24 ` Saugata Das
2012-04-03 15:50   ` Subhash Jadavani
2012-04-03 16:17     ` Saugata Das
2012-04-03 16:44       ` Subhash Jadavani
2012-04-03 17:06         ` Luca Porzio (lporzio)
2012-04-09 12:46           ` Subhash Jadavani
2012-04-03 18:48         ` Saugata Das

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=87fwclhwzl.fsf@laptop.org \
    --to=cjb@laptop.org \
    --cc=girish.shivananjappa@linaro.org \
    --cc=linkinjeon@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=subhashj@codeaurora.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