From: "Madhusudhan Chikkature Rajashekar" <madhu.cr@ti.com>
To: 'Pierre Ossman' <drzeus@drzeus.cx>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org
Subject: MMC/SD cards hotplug scenario
Date: Wed, 21 May 2008 11:42:04 +0530 [thread overview]
Message-ID: <004e01c8bb09$989fac00$538918ac@ent.ti.com> (raw)
Hi Pierre/All,
I have a query regarding one of the MMC/SD cards hotplug use case scenario and its expected behavior.
In the case where the MMC/SD card is removed physically from the slot during an active data transfer happening on the card, I notice
lot of
I/O errors being generated. The numbers of I/O errors seem to depend on the size of the file being copied(the errors semm to be a
mixture of FS + MMC core errors). After the end of the I/O errors I can umount the partition that was mounted and I reinsert the
card. It seem not to work very well consistently. I mean some times the card removal/insertion does seem to work that well. Whereas
card insertion/removal works perfectly fine if tested when no data transfer is happening.
Does MMC/SD core need to handle some things to support this scenario? Does MMC/SD core handle this scenario gracefully? Has anyone
tried something similar before?
As far as I understand this type of scenario can not be handled well in the controller drivers alone. Am I missing something here?
Regards,
Madhu
next reply other threads:[~2008-05-21 6:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 6:12 Madhusudhan Chikkature Rajashekar [this message]
2008-05-21 7:30 ` MMC/SD cards hotplug scenario 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
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='004e01c8bb09$989fac00$538918ac@ent.ti.com' \
--to=madhu.cr@ti.com \
--cc=drzeus@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@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.