public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Todd Poynor <tpoynor@mvista.com>
To: Jordan Crouse <jordan.crouse@amd.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: Fri, 12 Aug 2005 16:13:28 -0700	[thread overview]
Message-ID: <42FD2D18.6080302@mvista.com> (raw)
In-Reply-To: <20050811150650.GG26524@cosmic.amd.com>

Jordan Crouse wrote:

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

It also occurs to me that another reason for the disconnect between x86 
desktop/server and embedded on this point is the lack of ACPI.  We want 
to do things analogous to the power management performed by ACPI, but 
entirely in Linux, so we need to expose some of those low-level machine 
resources to our power management software.  In many cases those power 
management decisions do not revolve around the question of the MHz at 
which the CPU is to run.  Embedded Linux system power management exists 
for many of the same reasons ACPI exists.


-- 
Todd

  reply	other threads:[~2005-08-12 23:14 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
2005-08-12 23:13           ` Todd Poynor [this message]
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=42FD2D18.6080302@mvista.com \
    --to=tpoynor@mvista.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=ducrot@poupinou.org \
    --cc=jordan.crouse@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.cz \
    /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