All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@nokia.com>
To: aparna m <m.aparna01@gmail.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: Question about GENHD_FL_REMOVABLE flag for eMMC cards...
Date: Mon, 07 Jun 2010 10:13:42 +0300	[thread overview]
Message-ID: <4C0C9C26.9090504@nokia.com> (raw)
In-Reply-To: <AANLkTil7TuTw_VlUNo0pBKywQZ1Ol1t_okB-nBue9Xgm@mail.gmail.com>

aparna m wrote:
>  Hello,
> 
> I see a comment in the MMC block layer  drivers/mmc/card/block.c that
> GENHD_FL_REMOVABLE  should not be set for MMC block devices.
> How about the case of eMMC cards that are embedded on the chip.
> In that case, the eMMC card cannot be removed nor inserted and so the
> block device also cannot be removed.
> I guess eMMC falls under the case that it is a permanent block device
> and a permanent media.
> 
> How should this be set for this case? Please correct me if I am wrong.

Mostly it is an issue with unsafe resume (see CONFIG_MMC_UNSAFE_RESUME)

There is mmc_assume_removable module parameter (see drivers/mmc/core/core.c)

And there is the mmc_host capability flag MMC_CAP_NONREMOVABLE (see
include/linux/mmc/host.h)

> Thanks,
> Aparna.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2010-06-07  7:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07  6:39 Question about GENHD_FL_REMOVABLE flag for eMMC cards aparna m
2010-06-07  7:13 ` Adrian Hunter [this message]

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=4C0C9C26.9090504@nokia.com \
    --to=adrian.hunter@nokia.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=m.aparna01@gmail.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.