Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Ameya Palande <ameya.palande@nokia.com>
To: ext Jarkko Nikula <jhnikula@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	"Kristo Tero (Nokia-MS/Tampere)" <Tero.Kristo@nokia.com>
Subject: Re: CONFIG_CPU_IDLE broken for N900
Date: Tue, 10 Aug 2010 16:43:16 +0300	[thread overview]
Message-ID: <1281447796.17541.33.camel@chotu> (raw)
In-Reply-To: <20100810160324.8df82287.jhnikula@gmail.com>

Hi Jarkko,

On Tue, 2010-08-10 at 15:03 +0200, ext Jarkko Nikula wrote:
> On Tue, 10 Aug 2010 15:35:18 +0300
> Ameya Palande <ameya.palande@nokia.com> wrote:
> 
> > > 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?
> > 
> > Broken on linux-omap-pm as well!
> > 
> I'm able to reproduce with 2.6.35-rc1 but not with l-o head. It seems
> that the commit below fixes this.
> 
> commit c786bcf12e092802496f1bc440b2b189144612a5
> Author: Kevin Hilman <khilman@deeprootsystems.com>
> Date:   Thu Jun 3 17:13:22 2010 +0000
> 
>     OMAP3: PM: fix IO daisy chain enable to use PM_WKEN reg

Just tested it on linux-omap with omap3_defconfig and found that it is
broken. When kernel bootup is complete, and it switches to user space,
device hangs. When I disable CPU IDLE, it works..

Cheers,
Ameya.


  reply	other threads:[~2010-08-10 13:43 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 [this message]
2010-08-10 14:23       ` Jarkko Nikula
2010-08-10 23:21 ` Kevin Hilman

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=1281447796.17541.33.camel@chotu \
    --to=ameya.palande@nokia.com \
    --cc=Tero.Kristo@nokia.com \
    --cc=jhnikula@gmail.com \
    --cc=khilman@deeprootsystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox