From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Len Brown <lenb@kernel.org>
Cc: linux-pm@lists.linux-foundation.org
Subject: cpufreq-set problems [Was: Re: Ottawa Linux Power Management Summit, June 25-26, 2007 - Minutes]
Date: Sun, 28 Oct 2007 14:54:46 +0100 [thread overview]
Message-ID: <20071028135446.GG26943@isilmar.linta.de> (raw)
In-Reply-To: <200709050426.04793.lenb@kernel.org>
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().
Best,
Dominik
next prev parent reply other threads:[~2007-10-28 13:54 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 ` Dominik Brodowski [this message]
2007-10-29 13:26 ` cpufreq-set problems [Was: Re: Ottawa Linux Power Management Summit, June 25-26, 2007 - Minutes] Igor Stoppa
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=20071028135446.GG26943@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=lenb@kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
/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