public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Govindraj <govindraj.ti@gmail.com>
Cc: Kevin Hilman <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>,
	t-kristo@ti.com,
	linux-omap mailing list <linux-omap@vger.kernel.org>,
	NeilBrown <neilb@suse.de>, Joe Woodward <jw@terrafix.co.uk>
Subject: Re: PM(?) problems on v3.3-rc1 on OMAP3
Date: Fri, 20 Jan 2012 13:07:24 +0200	[thread overview]
Message-ID: <1327057644.1921.59.camel@deskari> (raw)
In-Reply-To: <CAAL8m4xNj=-=tz7Fkv_MQzvQy5iNj9n10=00KAi0=ixtQ1GVVA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 655 bytes --]

On Fri, 2012-01-20 at 16:19 +0530, Govindraj wrote:
> On Fri, Jan 20, 2012 at 4:03 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > Hi,
> >
> > I'm testing v3.3-rc1 on OMAP3 overo, and I'm having problems probably
> > related to PM.
> >
> > First, when I boot up, the console (via USB serial) is very laggy, it
> > often takes many seconds until the key pressed appears so it's more or
> > less unusable.
> 
> can you try enabling CONFIG_CPU_IDLE ?

Enabling CPU_IDLE does remove the problems. I don't know what it's
supposed to do, but it seems to keep the MPU and DSS in ON state all the
time, so the problem disappears.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 10:33 PM(?) problems on v3.3-rc1 on OMAP3 Tomi Valkeinen
2012-01-20 10:49 ` Govindraj
2012-01-20 11:07   ` Tomi Valkeinen [this message]
2012-01-20 11:21     ` Govindraj
2012-01-20 12:32       ` Jean Pihet
2012-01-20 12:44         ` Govindraj
2012-01-21  7:39       ` Paul Walmsley
2012-01-21  7:38     ` Paul Walmsley
2012-01-20 11:56 ` Govindraj
2012-01-20 12:01   ` Tomi Valkeinen
2012-01-20 12:34     ` Jean Pihet
2012-01-20 12:40       ` Tomi Valkeinen
2012-01-20 13:36         ` Jean Pihet
2012-01-20 15:00           ` Tomi Valkeinen
2012-01-22 11:11             ` NeilBrown
2012-01-23  8:53               ` Tomi Valkeinen
2012-01-23  9:04                 ` Paul Walmsley
2012-01-23  9:24                   ` Tomi Valkeinen
2012-01-23  9:31                     ` Paul Walmsley
2012-01-23 10:48                       ` Tomi Valkeinen
2012-01-23 11:02                         ` Paul Walmsley
2012-01-23 11:06                           ` Tomi Valkeinen
2012-01-24 10:39                   ` Tomi Valkeinen
2012-01-20 12:45     ` Govindraj
2012-01-20 12:47   ` Shubhrajyoti
2012-01-21  7:35 ` Paul Walmsley
2012-01-21  7:47 ` Paul Walmsley
2012-01-21 15:57   ` Tomi Valkeinen
2012-01-21 20:46     ` NeilBrown
2012-01-23  8:25       ` Tomi Valkeinen
2012-01-21 20:47     ` Paul Walmsley
2012-01-22 11:11       ` Valkeinen, Tomi

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=1327057644.1921.59.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=govindraj.ti@gmail.com \
    --cc=jw@terrafix.co.uk \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=paul@pwsan.com \
    --cc=t-kristo@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