From: Igor Stoppa <igor.stoppa@nokia.com>
To: ext Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: cpufreq-set problems [Was: Re: Ottawa Linux Power Management Summit, June 25-26, 2007 - Minutes]
Date: Mon, 29 Oct 2007 15:26:00 +0200 [thread overview]
Message-ID: <1193664360.23273.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20071028135446.GG26943@isilmar.linta.de>
Hi,
On Sun, 2007-10-28 at 14:54 +0100, ext Dominik Brodowski wrote:
> Hi,
>
> On Wed, Sep 05, 2007 at 04:26:04AM -0400, Len Brown wrote:
> > cpufreq_set_policy() doesn't match Nokia's needs as it is a 1-way
> > notification, and there is no way to register constraints.
>
> Could you elaborate a bit on this? cpufreq_update_policy() and
> cpufreq_register_notifier() allows to register constraints, and then you can
> use cpufreq_update_policy().
we are using update policy, but the problem with the notifications as
cpufreq handles them, is that we wanted to have a specific sequence of
operations been done, while (if i'm not wrong) the cpufreq notifications
do not provide this feature.
Probably this is not really needed for traditional x86 systems, while
SoC allow to know at design time what sort of devices will be present in
the system.
--
Cheers, Igor
Igor Stoppa <igor.stoppa@nokia.com>
(Nokia Multimedia - CP - OSSO / Helsinki, Finland)
prev parent reply other threads:[~2007-10-29 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 8:26 Ottawa Linux Power Management Summit, June 25-26, 2007 - Minutes Len Brown
2007-09-09 12:26 ` Rafael J. Wysocki
2007-09-24 19:41 ` Dave Jones
2007-09-25 11:39 ` Rafael J. Wysocki
2007-09-25 12:00 ` Thomas Gleixner
2007-10-28 13:54 ` cpufreq-set problems [Was: Re: Ottawa Linux Power Management Summit, June 25-26, 2007 - Minutes] Dominik Brodowski
2007-10-29 13:26 ` Igor Stoppa [this message]
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=1193664360.23273.24.camel@localhost.localdomain \
--to=igor.stoppa@nokia.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux@dominikbrodowski.net \
/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