From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yegor Yefremov Subject: Re: am3517: geting MMC working Date: Fri, 20 Jul 2012 10:01:09 +0200 Message-ID: <50091045.7060102@visionsystems.de> References: <5007A838.3040309@visionsystems.de> <5007AF7C.1010902@visionsystems.de> <5007B721.9070305@visionsystems.de> <5007C215.7020904@visionsystems.de> <50090B30.3070206@visionsystems.de> Reply-To: yegor_sub1@visionsystems.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from ns.vscom.de ([62.145.30.242]:57626 "EHLO mail.visionsystems.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753146Ab2GTIBZ (ORCPT ); Fri, 20 Jul 2012 04:01:25 -0400 In-Reply-To: <50090B30.3070206@visionsystems.de> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "T Krishnamoorthy, Balaji" Cc: Paul Walmsley , "S, Venkatraman" , "Shilimkar, Santosh" , "linux-omap@vger.kernel.org" , "Mark A. Greer" , "Porter, Matt" Am 20.07.2012 09:39, schrieb Yegor Yefremov: > Am 20.07.2012 09:28, schrieb T Krishnamoorthy, Balaji: >> On Fri, Jul 20, 2012 at 3:08 AM, Paul Walmsley wrote: >>> On Thu, 19 Jul 2012, S, Venkatraman wrote: >>> >>>> >From this, one can only infer that the card is not responding at all, >>>> and all attempts >>>> are returning with a timeout (CTO=Command Time Out). >>> Looks to me like the card is responding to CMD8, CMD55, ACMD41, and CMD0. >>> It's only CMD52 and CMD5 that are timing out. Aren't those timeouts >>> expected with a SD memory card? >> yes, those timeouts are expected for SD card. >> The failure is due to irq not received/missing for last CMD0. >> Hi Yegor, Can you provide details for the SD card being used. > > This is Apacer 2GB. In 3.3-rc7 I have no problems with it. Should I enable debugging in 3.3-rc7 and post the output? I found the solution: diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c index e4fc88c..0ab26ab 100644 --- a/arch/arm/mach-omap2/pm34xx.c +++ b/arch/arm/mach-omap2/pm34xx.c @@ -359,7 +359,7 @@ static void omap3_pm_idle(void) { local_fiq_disable(); - if (omap_irq_pending()) + if (omap_irq_pending() || !omap3_has_io_wakeup()) goto out; trace_power_start(POWER_CSTATE, 1, smp_processor_id()); I've seen this hack for some on the mailing list. I think Mark A. Greer introduced it, but I don't remember for sure. Can this patch be applied as it is or there are some infrastructure changes required? Best regards, Yegor