public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: "T Krishnamoorthy, Balaji" <balajitk@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	"S, Venkatraman" <svenkatr@ti.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Mark A. Greer" <mgreer@animalcreek.com>,
	"Porter, Matt" <mporter@ti.com>
Subject: Re: am3517: geting MMC working
Date: Fri, 20 Jul 2012 10:01:09 +0200	[thread overview]
Message-ID: <50091045.7060102@visionsystems.de> (raw)
In-Reply-To: <50090B30.3070206@visionsystems.de>

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 <paul@pwsan.com> 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

  reply	other threads:[~2012-07-20  8:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19  6:24 am3517: geting MMC working Yegor Yefremov
2012-07-19  6:34 ` Shilimkar, Santosh
2012-07-19  6:55   ` Yegor Yefremov
2012-07-19  7:07     ` Shilimkar, Santosh
2012-07-19  7:28       ` Yegor Yefremov
2012-07-19  7:43         ` S, Venkatraman
2012-07-19  8:15           ` Yegor Yefremov
2012-07-19  8:57             ` S, Venkatraman
2012-07-19 10:08               ` T Krishnamoorthy, Balaji
2012-07-19 13:45               ` Yegor Yefremov
2012-07-19 21:38               ` Paul Walmsley
2012-07-20  7:28                 ` T Krishnamoorthy, Balaji
2012-07-20  7:39                   ` Yegor Yefremov
2012-07-20  8:01                     ` Yegor Yefremov [this message]
2012-07-26 23:31                       ` Mark A. Greer
2012-07-19  8:46           ` Javier Martinez Canillas

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=50091045.7060102@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --cc=balajitk@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mgreer@animalcreek.com \
    --cc=mporter@ti.com \
    --cc=paul@pwsan.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=svenkatr@ti.com \
    /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