From: Tony Lindgren <tony@atomide.com>
To: Felix Xiaozhu Lin <xzl@rice.edu>
Cc: linux-omap@vger.kernel.org
Subject: Re: n8x0 idle power problem
Date: Tue, 3 Nov 2009 09:19:13 -0800 [thread overview]
Message-ID: <20091103171913.GK8981@atomide.com> (raw)
In-Reply-To: <f25d86460910231640i22e5da83q1094e60c2e4df05@mail.gmail.com>
* Felix Xiaozhu Lin <xzl@rice.edu> [091023 16:41]:
> I am trying to compile a linux-omap kernel for n810 that can do good
> idle power management.
>
> However, this seems to be harder than I expected. I've done all
> following measurements with /sys/power/sleep_while_idle set to 1.
> Compiler is arm-linux-gnueabi-gcc 4.2. I use n8x0_defconfig.
>
> * Maemo kernel (2.6.21) consumes ~0mA@3.8V when idle. This seems to
> be perfect. However, it has no pm regarding serial port. Whenever
> serial port is enabled, idle power is ~50mA@3.8V.
>
> * I've compiled 2.6.28/2.6.29 from l-o git. Serial port pm works
> fine. However the idle power is ~20mA@3.8V. That is quite strange.
>
> * For kernel >= 2.6.30 I didn't manage to boot my N810.
>
> I also dig out a thread discussing about N8x0 idle power:
>
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg11954.html
>
> where Kalle mentioned 2.6.29 idle power is OK. But I never get the same result.
>
> I'm wondering if I did something wrong in the measurement. Anybody did
> the same thing? You suggestion is highly appreciated.
It sounds like something is blocking the deeper idle states.
The way to debug is to see what clocks and domains are on
before entering idle.
Maybe do a register dump on a working system and compare that
to the current system?
Regards,
Tony
next prev parent reply other threads:[~2009-11-03 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 23:40 n8x0 idle power problem Felix Xiaozhu Lin
2009-11-03 17:19 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-03 17:30 xl6
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=20091103171913.GK8981@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=xzl@rice.edu \
/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