From: Kevin Hilman <khilman@deeprootsystems.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: linux-omap@vger.kernel.org
Subject: Re: n800 high idle power consumption
Date: Fri, 24 Apr 2009 06:45:08 -0700 [thread overview]
Message-ID: <87zle6xj17.fsf@deeprootsystems.com> (raw)
In-Reply-To: <877i1aejon.fsf@litku.valot.fi> (Kalle Valo's message of "Fri\, 24 Apr 2009 07\:53\:44 +0300")
Kalle Valo <kalle.valo@iki.fi> writes:
> Hello all,
>
> I was testing 2.6.30-rc3-omap1 on n800 and noticed that idle power
> consumption is very high, ten times compared to a 2.6.29 I tested few
> weeks back. I'm guessing that CPU doesn't sleep at all.
>
> Is this a regression? How should I debug this further?
Between .29 and .30, the PM code in l-o was dropped and re-sync'd to
kernel.org code. This is so that PM can be separated out into a
separate branch and submitted upstream independently.
The current PM branch is in the process of being re-based onto 2.6.30.
When it's ready, I'd appreciate any testing on n800.
Kevin
next prev parent reply other threads:[~2009-04-24 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 4:53 n800 high idle power consumption Kalle Valo
2009-04-24 5:00 ` Kalle Valo
2009-04-24 13:45 ` Kevin Hilman [this message]
2009-04-24 13:50 ` Kalle Valo
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=87zle6xj17.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=kalle.valo@iki.fi \
--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.