All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Ameya Palande <ameya.palande@nokia.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: CONFIG_CPU_IDLE broken for N900
Date: Tue, 10 Aug 2010 16:21:26 -0700	[thread overview]
Message-ID: <87zkwu3vgp.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1281442891.17541.26.camel@chotu> (Ameya Palande's message of "Tue, 10 Aug 2010 15:21:31 +0300")

Ameya Palande <ameya.palande@nokia.com> writes:

> When I enable CONFIG_CPU_IDLE and boot kernel, it hangs around the point
> when it switches to user space. I am able to reproduce this for 2.6.35
> on linux-omap and linux-2.6 trees.
>
> Has anyone else noticed the same thing for omap3 based boards?

I was able to reproduce on my n900 and found the problem.  I believe
this is the same problem that has been haunting the Overo folks in that
their console (on UART2 like n900) was not responding after suspend.

The patch below fixes the problem for me, and will post an official
version shortly.

Tested with l-o master (omap3_defconfig + CONFIG_CPU_IDLE=y) as well
with current PM branch.  PM branch (specifically pm-fixes sub-branch)
has been updated to include this fix.

Kevin


diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
index fb4994a..7b03426 100644
--- a/arch/arm/mach-omap2/pm34xx.c
+++ b/arch/arm/mach-omap2/pm34xx.c
@@ -480,7 +480,9 @@ void omap_sram_idle(void)
 	}
 
 	/* Disable IO-PAD and IO-CHAIN wakeup */
-	if (omap3_has_io_wakeup() && core_next_state < PWRDM_POWER_ON) {
+	if (omap3_has_io_wakeup() &&
+	    (per_next_state < PWRDM_POWER_ON ||
+	     core_next_state < PWRDM_POWER_ON)) {
 		prm_clear_mod_reg_bits(OMAP3430_EN_IO_MASK, WKUP_MOD, PM_WKEN);
 		omap3_disable_io_chain();
 	}
-- 
1.7.2.1




      parent reply	other threads:[~2010-08-10 23:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 12:21 CONFIG_CPU_IDLE broken for N900 Ameya Palande
2010-08-10 12:35 ` Ameya Palande
2010-08-10 13:03   ` Jarkko Nikula
2010-08-10 13:43     ` Ameya Palande
2010-08-10 14:23       ` Jarkko Nikula
2010-08-10 23:21 ` Kevin Hilman [this message]

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=87zkwu3vgp.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=ameya.palande@nokia.com \
    --cc=linux-omap@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 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.