From: Chris Ball <cjb@laptop.org>
To: Manoj <manoj.iyer@canonical.com>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxim Levitsky <maximlevitsky@gmail.com>,
Philip Langdale <philipl@overt.org>
Subject: Re: SDHCI: Ricoh [1180:e823] unable to mount MMC cards.
Date: Thu, 31 Mar 2011 14:33:19 -0400 [thread overview]
Message-ID: <m3vcyzuols.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <4D94C0E5.6070801@canonical.com> (Manoj's message of "Thu, 31 Mar 2011 12:59:01 -0500")
Hi Manoj,
On Thu, Mar 31 2011, Manoj wrote:
> Card did not mount. New dmesg is attached.
Okay. There's nothing in the log about Ricoh, which probably means that
it bailed out early in the function. You could add a printk to the top
of ricoh_mmc_fixup_rl5c476() if you want to be really sure that the code
there is getting a chance to run.
I think the likely conclusion is that:
(a) The Ricoh controller has a proprietary MMC function that is stealing
MMC cards away from the SDHCI controller even though the SDHCI could
read them if it had a chance to.
(b) We don't know how to turn the MMC controller off, because our old
method for doing so isn't working on this new 0xe823 model.
I'm adding a few people who've touched this code to CC: in case they
have any ideas on working out how to disable the MMC function. If you
have contact with Ricoh directly or through a vendor, please ask them
for the PCI configuration writes needed to disable the MMC function on
this model so that you can read MMC cards with the SD interface instead.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-03-31 18:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 22:23 SDHCI: Ricoh [1180:e823] unable to mount MMC cards Manoj
2011-03-30 23:04 ` Chris Ball
2011-03-30 23:32 ` Manoj
2011-03-30 23:53 ` Chris Ball
2011-03-31 14:12 ` Manoj
2011-03-31 14:43 ` Chris Ball
2011-03-31 14:41 ` Manoj
2011-03-31 15:13 ` Chris Ball
2011-03-31 16:00 ` Manoj
2011-03-31 16:31 ` Chris Ball
2011-03-31 17:09 ` Manoj
2011-03-31 17:26 ` Chris Ball
2011-03-31 17:59 ` Manoj
2011-03-31 18:33 ` Chris Ball [this message]
2011-03-31 18:47 ` Philip Langdale
2011-03-31 18:47 ` Philip Langdale
2011-03-31 14:47 ` Manoj
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=m3vcyzuols.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=manoj.iyer@canonical.com \
--cc=maximlevitsky@gmail.com \
--cc=philipl@overt.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.