All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Chris Ball <cjb@laptop.org>, linux-mmc@vger.kernel.org
Subject: Re: [PATCH 1/4] mmc: core: add high-capacity erase size capability flag
Date: Thu, 09 Feb 2012 09:02:39 +0200	[thread overview]
Message-ID: <4F336F8F.9080809@intel.com> (raw)
In-Reply-To: <CACRpkdZPQwO19y-JxY86QQtUri-1uxUHX5V1gkgfGDtNZSXaBQ@mail.gmail.com>

On 09/02/12 00:38, Linus Walleij wrote:
> On Tue, Feb 7, 2012 at 1:48 PM, Adrian Hunter <adrian.hunter@intel.com> wrote:
> 
>> Let drivers specify the use of high-capacity erase size.
>>
>> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
> (...)
>> @@ -949,7 +949,8 @@ static int mmc_init_card(struct mmc_host *host, u32 ocr,
>>         * If enhanced_area_en is TRUE, host needs to enable ERASE_GRP_DEF
>>         * bit.  This bit will be lost every time after a reset or power off.
>>         */
>> -       if (card->ext_csd.enhanced_area_en) {
>> +       if (card->ext_csd.enhanced_area_en ||
>> +           (card->ext_csd.rev >= 3 && (host->caps2 & MMC_CAP2_HC_ERASE_SZ))) {
> 
> It looks like there is a bug fix hidden inside this patch, is it not?
> The comparison for card->ext_csd.rev >= 3 was not there before,
> and looks like it's fixing something and should go into stable even,
> is that correct?

No because because enhanced areas were added in v4.4 so
"card->ext_csd.enhanced_area_en" implies "card->ext_csd.rev >= 4"

High-capacity erase size was added in v4.3 so "card->ext_csd.rev >= 3"
is parenthesised with "(host->caps2 & MMC_CAP2_HC_ERASE_SZ)"

  reply	other threads:[~2012-02-09  7:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 12:48 [PATCH 0/4] mmc: add a cap and a quirk Adrian Hunter
2012-02-07 12:48 ` [PATCH 1/4] mmc: core: add high-capacity erase size capability flag Adrian Hunter
2012-02-08 16:32   ` Ulf Hansson
2012-02-09  7:12     ` Adrian Hunter
2012-02-08 22:38   ` Linus Walleij
2012-02-09  7:02     ` Adrian Hunter [this message]
2012-02-07 12:48 ` [PATCH 2/4] mmc: sdhci-pci: select HC erase size for Medfield eMMC Adrian Hunter
2012-02-07 12:48 ` [PATCH 3/4] mmc: sdhci: add quirk for keeping card power during suspend Adrian Hunter
2012-02-07 12:48 ` [PATCH 4/4] mmc: sdhci-pci: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for Medfield SDIO Adrian Hunter
2012-03-13  6:41 ` [PATCH 0/4] mmc: add a cap and a quirk Adrian Hunter
2012-03-13  9:35   ` Chris Ball

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=4F336F8F.9080809@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=cjb@laptop.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mmc@vger.kernel.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.