All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Subhash Jadavani" <subhashj@codeaurora.org>
To: "'Luca Porzio (lporzio)'" <lporzio@micron.com>,
	'Saugata Das' <saugata.das@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	girish.shivananjappa@linaro.org,
	"'Danilo Caraccio (dcaracci)'" <dcaracci@micron.com>
Subject: RE: [PATCH v1 1/1] mmc: core: fix power class selection
Date: Mon, 9 Apr 2012 18:16:16 +0530	[thread overview]
Message-ID: <000301cd164e$c3c12e50$4b438af0$@codeaurora.org> (raw)
In-Reply-To: <26E7A31274623843B0E8CF86148BFE326FB57152@NTXAVZMBX04.azit.micron.com>

Hi Porzio,

> -----Original Message-----
> From: Luca Porzio (lporzio) [mailto:lporzio@micron.com]
> Sent: Tuesday, April 03, 2012 10:36 PM
> To: Subhash Jadavani; 'Saugata Das'
> Cc: linux-mmc@vger.kernel.org; linux-arm-msm@vger.kernel.org;
> girish.shivananjappa@linaro.org; Danilo Caraccio (dcaracci)
> Subject: RE: [PATCH v1 1/1] mmc: core: fix power class selection
> 
> Hi,
> 
> >
> > Yes, this makes sense. With current implementation,
> > mmc_select_powerclass() should never really fail which means failure
> > should be treated as fatal and we should really skip the card
initialization.
> > This patch is already pushed to mmc-next. So I will post another patch
> > (by next week as I will be on vacation in this week) to skip the card
> > initialization if mmc_select_powerclass fails.
> >
> > Is this ok?
> >
> > Regards,
> > Subhash
> >
> 
> There was an error in the public JEDEC eMMC 4.5 version: PWR_CL_200_360 =
> EXT_CSD[237] is wrongly defined because HS200 can be supported only @1.2V
> or 1.8V. New Jedec spec revision might fix this.
> 
> I and Danilo did a quick check in the power class selection routines and
it looks
> like the power class is set according to the OCR parsing.
> The OCR parsing to check the supported voltage range does not totally
cover
> the device capabilities because Vccq = 1.2V support is not encoded in the
> register.

According to my understanding, "vvv" in "PWR_CL_ff_vvv" (or
"PWR_CL_DDR_ff_vvv") indicates is VDD voltage not the VCCQ voltage. So we
shouldn't bother about what is the vccq level to decide which particular
field to read for power class. Please correct me if this understanding is
wrong.

Regards,
Subhash

> 
> If the above is true, this implies that indexes EXT_CSD_PWR_CL_200_360
will
> lead to an error.
> 
> DEVICE_TYPE = EXT_CSD[196] is more useful because it provides information
> on the Speed Rate and Voltage Range supported by the device.
> 
> Cheers,
>     Luca

  reply	other threads:[~2012-04-09 12:46 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
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 [this message]
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='000301cd164e$c3c12e50$4b438af0$@codeaurora.org' \
    --to=subhashj@codeaurora.org \
    --cc=dcaracci@micron.com \
    --cc=girish.shivananjappa@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lporzio@micron.com \
    --cc=saugata.das@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 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.