From: Igor Stoppa <igor.stoppa@nokia.com>
To: ext Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Syed Mohammed, Khasim" <khasim@ti.com>,
Pierre Ossman <drzeus@drzeus.cx>,
"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: MMC/SD cards hotplug scenario
Date: Thu, 22 May 2008 20:39:39 +0000 [thread overview]
Message-ID: <1211488779.6430.12.camel@mort> (raw)
In-Reply-To: <20080522200123.GS15328@flint.arm.linux.org.uk>
Hi,
On Thu, 2008-05-22 at 21:01 +0100, ext Russell King - ARM Linux wrote:
> Basically, what I'm trying to say is that ejecting any medium randomly
> from the system is _always_ going to result in problems of some nature.
> Some of which you can reduce the impact from, others are fairly terminal.
> The only safe solution is the unmount, wait for data to be written, and
> then eject the card.
from this point of view it is a watered down version of "what happens
when the power is removed abruptly", which unfortunately cannot really
be avoided on battery powered devices with removable battery.
If the system is supposed to survive such cases, then ext2 is probably
not the best choice and a journaling fs (ext3 ?) should be considered.
With MMC even the way the power fails (vcore fading away before/after
vio) affects the possibility of the embedded uC b0rking. So it needs to
be addressed also at board HW level.
This of course cannot be really controlled when the MMC is removed from
the slot, unless there is a sensor on the MMC lid.
Sensor that could be used for an emergency, controlled powerdown, with
no sync.
But on the Tablets we instead show a warning and tell the user to be
nice and close back the lid: UI designers prefer such approach.
Just my 2 cents.
--
Cheers, Igor
---
Igor Stoppa
Nokia Devices R&D - Helsinki
prev parent reply other threads:[~2008-05-22 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 6:12 MMC/SD cards hotplug scenario Madhusudhan Chikkature Rajashekar
2008-05-21 7:30 ` Russell King - ARM Linux
2008-05-21 9:31 ` Madhusudhan Chikkature Rajashekar
2008-05-21 18:32 ` Pierre Ossman
2008-05-22 13:40 ` Madhusudhan Chikkature Rajashekar
2008-06-01 10:03 ` Pierre Ossman
2008-05-22 19:46 ` Syed Mohammed, Khasim
2008-05-22 20:01 ` Russell King - ARM Linux
2008-05-22 20:39 ` Igor Stoppa [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=1211488779.6430.12.camel@mort \
--to=igor.stoppa@nokia.com \
--cc=drzeus@drzeus.cx \
--cc=khasim@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=madhu.cr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox