From: Jarkko Nikula <jhnikula@gmail.com>
To: Ameya Palande <ameya.palande@nokia.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 17:23:03 +0300 [thread overview]
Message-ID: <20100810172303.31178f2f.jhnikula@gmail.com> (raw)
In-Reply-To: <1281447796.17541.33.camel@chotu>
On Tue, 10 Aug 2010 16:43:16 +0300
Ameya Palande <ameya.palande@nokia.com> wrote:
> > 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..
>
And I was too fast, problem is there in l-o head but it seems to hang in
different places for me. Above commit removed "Wake up daisy chain
activation failed." error that was slowing down the boot but this issue
seems to be different.
I can boot up to Debian console login but system hangs during user
space boot if I send something over serial. This happend with
omap3_defconfig in l-o head using N900. However, the same kernel works
fine on Beagle. Can this be some silicon dependent issue?
--
Jarkko
next prev parent reply other threads:[~2010-08-10 14:23 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 [this message]
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=20100810172303.31178f2f.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=Tero.Kristo@nokia.com \
--cc=ameya.palande@nokia.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