From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: "Midhun Agnihotram" <agnimidhun@gmail.com>
Cc: "Hans-Jürgen Koch" <hjk@linutronix.de>,
jdi@l4x.org, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Mounting MMC card
Date: Tue, 3 Jul 2007 20:48:53 +0200 [thread overview]
Message-ID: <20070703204853.57ecea17@poseidon.drzeus.cx> (raw)
In-Reply-To: <4dde4acb0707030209n7b3b9236q2619a67f5c4dad5e@mail.gmail.com>
On Tue, 3 Jul 2007 14:39:40 +0530
"Midhun Agnihotram" <agnimidhun@gmail.com> wrote:
> Hi All,
>
> This is referring to my problem - not able to mount MMC card. I
> have some output from dmesg when I remove and put the card back (I
> have changes the kernel config to include i.MX SPI and disabled the
> generic SPI). DOes this give any clue as to why the MMC card is not
> appaering in /proc/partions and /sysfs/block ?? Any help will of
> great use. The output of dmesg is as follows. I have removed and
> inserted the card twice.
>
>
> <7>MMC: starting cmd 00 arg 00000000 flags 00000040
> <7>MMC: req done (00): 1: 00000000 00000000 00000000 00000000
These two and the ones like them were the ones I expected to see in
your dumps. So since you've discovered a way to get them functioning,
we can proceed with the debugging.
> <7>MMC: starting cmd 01 arg 00000000 flags 00000061
> <7>imx-mmc imx-mmc.0: CMD01 (0x01) mask set to 0x003b
> <7>imx-mmc imx-mmc.0: RESP 0x00000000, 0x00000000, 0x00000000,
> 0x00000000, error 0
> <7>MMC: req done (01): 0: 00000000 00000000 00000000 00000000
Here's your problem. CMD01 is a command that queries the cards for
their voltages. And the response is "no voltages". So either your host
driver is buggy, or your card is.
Have you tested with some other cards?
Also, the i.MX host driver is known to be a bit buggy. I would suggest
sending some questions out on the arm linux kernel mailing list as that
is where it's usually discussed.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-07-03 18:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4dde4acb0706261146s5906d8f3vb787d5aecb429116@mail.gmail.com>
2007-06-28 17:00 ` Midhun Agnihotram
2007-06-28 17:08 ` Midhun Agnihotram
2007-06-28 17:53 ` Jan Dittmer
2007-06-28 18:10 ` Hans-Jürgen Koch
2007-06-28 19:22 ` Pierre Ossman
2007-06-28 20:10 ` Hans-Jürgen Koch
2007-06-29 7:40 ` Fwd: " Midhun Agnihotram
2007-06-29 8:38 ` Hans-Jürgen Koch
2007-06-29 9:09 ` Midhun Agnihotram
2007-06-29 9:15 ` Pierre Ossman
2007-06-29 9:30 ` Midhun Agnihotram
2007-06-29 9:39 ` Pierre Ossman
2007-06-29 9:45 ` Midhun Agnihotram
2007-06-29 10:01 ` Hans-Jürgen Koch
2007-06-29 10:29 ` Pierre Ossman
2007-06-29 10:57 ` Midhun Agnihotram
2007-06-29 11:00 ` Pierre Ossman
2007-06-29 11:06 ` Midhun Agnihotram
2007-06-29 11:10 ` Pierre Ossman
2007-06-29 11:22 ` Midhun Agnihotram
2007-07-03 9:09 ` Midhun Agnihotram
2007-07-03 18:48 ` Pierre Ossman [this message]
2007-06-29 9:42 ` Uli Luckas
2007-06-29 10:29 ` Pierre Ossman
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=20070703204853.57ecea17@poseidon.drzeus.cx \
--to=drzeus-mmc@drzeus.cx \
--cc=agnimidhun@gmail.com \
--cc=hjk@linutronix.de \
--cc=jdi@l4x.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®