public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* n800 high idle power consumption
@ 2009-04-24  4:53 Kalle Valo
  2009-04-24  5:00 ` Kalle Valo
  2009-04-24 13:45 ` Kevin Hilman
  0 siblings, 2 replies; 4+ messages in thread
From: Kalle Valo @ 2009-04-24  4:53 UTC (permalink / raw)
  To: linux-omap

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?

-- 
Kalle Valo

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: n800 high idle power consumption
  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
  1 sibling, 0 replies; 4+ messages in thread
From: Kalle Valo @ 2009-04-24  5:00 UTC (permalink / raw)
  To: linux-omap

Kalle Valo <kalle.valo@iki.fi> writes:

> Hello all,

Hello again,

> 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?

Oh yeah, I forgot to mention that I have included Jarkko's patch "ARM:
OMAP: Fix tusb6010 init error and compilation warning" in my builds.
Otherwise usb won't work.

-- 
Kalle Valo

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: n800 high idle power consumption
  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
  2009-04-24 13:50   ` Kalle Valo
  1 sibling, 1 reply; 4+ messages in thread
From: Kevin Hilman @ 2009-04-24 13:45 UTC (permalink / raw)
  To: Kalle Valo; +Cc: linux-omap

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: n800 high idle power consumption
  2009-04-24 13:45 ` Kevin Hilman
@ 2009-04-24 13:50   ` Kalle Valo
  0 siblings, 0 replies; 4+ messages in thread
From: Kalle Valo @ 2009-04-24 13:50 UTC (permalink / raw)
  To: Kevin Hilman; +Cc: linux-omap

Kevin Hilman <khilman@deeprootsystems.com> writes:

> 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.

Ah, of course. I read about this but didn't understand the implications :)
Thanks for pointing this out to me.

> 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.

Ok. Please let me know when it's ready.

-- 
Kalle Valo

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-04-24 13:50 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2009-04-24 13:50   ` Kalle Valo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox