From: Igor Stoppa <igor.stoppa@nokia.com>
To: ext Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Woodruff, Richard" <r-woodruff2@ti.com>,
Koen Kooi <koen@beagleboard.org>,
"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>
Subject: Re: Beagle PM hangs
Date: Sat, 31 Jan 2009 13:18:32 +0200 [thread overview]
Message-ID: <1233400712.14037.34.camel@localhost> (raw)
In-Reply-To: <87pri4gz1m.fsf@deeprootsystems.com>
On Sat, 2009-01-31 at 00:21 +0100, ext Kevin Hilman wrote:
> CPUfreq policy is just as easily set in the kernel at init time. Then
> the default would be set right, and the rootfs would be left to change
> it if desired.
But in general the situation is more complex and knowledge about the
packaging and its thermal model is needed.
Note that with packaging i refer to both the omap package (does it use
stacked memory or not, is it a memory combo, etc) and the _device_
package.
Not getting errors is not a good indication that the system is really
operating in a safe mode; the device might be stable all the time but
its life be more than halved.
--
Cheers, Igor
---
Igor Stoppa
Maemo Software - Nokia Devices R&D - Helsinki
next prev parent reply other threads:[~2009-01-31 11:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <345163910901280814nb847b34pca50f4ee6e49929d@mail.gmail.com>
2009-01-28 16:28 ` Beagle PM hangs Kevin Hilman
2009-01-28 17:46 ` Kevin Hilman
2009-01-30 14:16 ` Sriram V
2009-01-30 14:34 ` Woodruff, Richard
2009-01-30 17:12 ` Kevin Hilman
2009-01-30 19:41 ` Pandita, Vikram
2009-01-30 19:53 ` Kevin Hilman
2009-01-30 21:31 ` Woodruff, Richard
2009-02-02 5:00 ` Nayak, Rajendra
2009-01-30 21:34 ` Koen Kooi
2009-01-30 22:03 ` Woodruff, Richard
2009-01-30 22:09 ` Koen Kooi
2009-01-30 22:39 ` Kevin Hilman
2009-01-30 22:49 ` Woodruff, Richard
2009-01-30 23:21 ` Kevin Hilman
2009-01-31 11:18 ` Igor Stoppa [this message]
2009-01-30 22:40 ` Woodruff, Richard
2009-01-29 17:20 ` Peter Reid
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=1233400712.14037.34.camel@localhost \
--to=igor.stoppa@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=koen@beagleboard.org \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@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