From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Ball Subject: Re: SDHCI: Ricoh [1180:e823] unable to mount MMC cards. Date: Thu, 31 Mar 2011 14:33:19 -0400 Message-ID: References: <4D93AD5C.1070308@canonical.com> <4D93BDA9.1020107@canonical.com> <4D948BC4.6020904@canonical.com> <4D949298.4000701@canonical.com> <4D94A510.4040509@canonical.com> <4D94B552.8020108@canonical.com> <4D94C0E5.6070801@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from void.printf.net ([89.145.121.20]:55152 "EHLO void.printf.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753378Ab1CaS1i (ORCPT ); Thu, 31 Mar 2011 14:27:38 -0400 In-Reply-To: <4D94C0E5.6070801@canonical.com> (Manoj's message of "Thu, 31 Mar 2011 12:59:01 -0500") Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Manoj Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, Maxim Levitsky , Philip Langdale 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 One Laptop Per Child