From: Todd Poynor <tpoynor@mvista.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>,
Todd Poynor <tpoynor@mvista.com>,
cpufreq@lists.linux.org.uk,
Patrick Mochel <mochel@digitalimplant.org>,
linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>
Subject: Re: PowerOP 0/3: System power operating point management API
Date: Tue, 16 Aug 2005 18:52:38 -0700 [thread overview]
Message-ID: <43029866.8040605@mvista.com> (raw)
In-Reply-To: <20050816085740.GL9150@dominikbrodowski.de>
Dominik Brodowski wrote:
> A small add-on:
>
> We need to make sure that we're capable of handling smart CPUs like Transmeta
> Crusoe processors in a sane way. This means
>
>
>>b) Setting of "values"
>
>
> is optional if the hardware itself can be set to a min/max value (step a
> above in previous mail).
Although I haven't looked into the Crusoe processor support, it may be
that there is a different set of power parameters, not cpu speed
directly, that are appropriate to manage on these platforms (after a
brief look, seems to be a range of frequencies and some sort of flags)?
If so, these sorts of machine-specific power parameters are what
PowerOP is trying to address, allowing management of the underlying
machine-specific stuff to upper layers that may be presenting an
abstracted view of power/performance, such as CPU speed or speed ranges,
to the user. Thanks,
--
Todd
next prev parent reply other threads:[~2005-08-17 1:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 2:49 PowerOP 0/3: System power operating point management API Todd Poynor
2005-08-09 18:12 ` [linux-pm] " Patrick Mochel
2005-08-10 2:18 ` Todd Poynor
[not found] ` <20050809030000.GA25112@slurryseal.ddns.mvista.com>
2005-08-16 8:53 ` Dominik Brodowski
2005-08-16 8:57 ` Dominik Brodowski
2005-08-17 1:52 ` Todd Poynor [this message]
2005-08-17 1:39 ` Todd Poynor
2005-08-10 10:07 ` Pavel Machek
2005-08-10 22:02 ` 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=43029866.8040605@mvista.com \
--to=tpoynor@mvista.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=linux@dominikbrodowski.net \
--cc=mochel@digitalimplant.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