From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Todd Poynor" <tpoynor@mvista.com>
Cc: "Dave Jones" <davej@redhat.com>,
"Bruno Ducrot" <ducrot@poupinou.org>,
"Pavel Machek" <pavel@ucw.cz>,
cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org,
linux-pm@lists.osdl.org
Subject: Re: PowerOP 2/3: Intel Centrino support
Date: Thu, 11 Aug 2005 09:06:50 -0600 [thread overview]
Message-ID: <20050811150650.GG26524@cosmic.amd.com> (raw)
In-Reply-To: <42FA8FC0.5000700@mvista.com>
> I've attempted to extoll the benefits of adding these interfaces in
> previous emails, and if after that it still seems mystifying why anybody
> would want to do this then I'll take the heat for doing a lousy job of
> extolling. I've also admitted that it is primarily of use in
> embedded-specific hardware, and of less use in x86 and in desktop/server
> usage for various reasons (unless it turns out there's some fantastic
> savings to be had in modifying common x86 bus speeds independently of
> cpu speed, which seems unlikely). In the case of x86, undervolting is
> in practice by some folks, but yes it is risky and support for it in the
> basic interfaces probably shouldn't be a high priority.
I would like to toss in my support to Todd, if he'll take it. When it comes
to embedded power management concepts, a consistant theme is that people
often question the usefulness, redundancy or complexity of a solution. This
is perfectly understandable, since such a huge majority of the power
management experts and users are concentrating intently on x86 desktops and
servers. Thats nobody's fault in particular, just a natural result of a
Wintel world gone mad.
At the PM BOF at OLS, when we started discussing runtime management, somebody
mentioned that one of the problems with RTPM is the complexity. As an
embedded Linux developer, I hope I speak for the entire embedded community
when I say that we welcome that complexity - we are willing to do anything
we can do to squeak every single millivolt out of our platforms.
But as a laptop owner, I can see the other side of the coin as well - I don't
know the specific voltages that my laptop uses, and I don't want to know.
In short, we have different goals, but our hearts are in the the same place.
These same concepts are going to show up more and more in the future, and
eventually somebody is going to start shipping less then optimal solutions,
just to get something to market. This list can either lend its expertise, or
complain when somebody else gets it wrong. The second one might seem more
fun, but I hope we can agree its far less productive.. :)
Jordan
--
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>
next prev parent reply other threads:[~2005-08-11 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 2:54 PowerOP 2/3: Intel Centrino support Todd Poynor
2005-08-09 7:59 ` Ingo Molnar
2005-08-10 10:01 ` Pavel Machek
2005-08-10 12:58 ` Bruno Ducrot
2005-08-10 18:44 ` [linux-pm] " Dave Jones
2005-08-10 23:37 ` Todd Poynor
2005-08-11 15:06 ` Jordan Crouse [this message]
2005-08-12 23:13 ` Todd Poynor
2005-08-12 12:38 ` [linux-pm] " Nikolay Pelov
2005-08-10 22:53 ` Todd Poynor
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=20050811150650.GG26524@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=ducrot@poupinou.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=tpoynor@mvista.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