cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Langsdorf <mark.langsdorf@calxeda.com>
To: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>
Subject: Using out of band messages to change min/max frequencies
Date: Wed, 14 Mar 2012 12:36:28 -0500	[thread overview]
Message-ID: <4F60D71C.6070709@calxeda.com> (raw)

Does cpufreq currently support having an out-of-band agent
change the available minimum/maximum frequency and then
have the current frequency conform to the new values?

I experimented with a notifier routine (from an IPC
context) that used cpufreq_get_policy() and
cpufreq_update_policy(). I ran into two problems:
1) cpufreq_update_policy() would overwrite the
changes I made to the minimum/maximum settings
2) the driver->target call would be called within
the notifier context, and would explode when it
called its own notifiers.

driver->bios_limit doesn't seem like the right answer,
since it wouldn't be called if the current governor
has a static policy (ie performance, powersave).

Is there some better way to approach this? Ideally,
I'd like something like the ACPI _PPC concept, but
looking over that code I'm not sure it actually
limits the frequency correctly.

--Mark Langsdorf
Calxeda, Inc.

             reply	other threads:[~2012-03-14 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 17:36 Mark Langsdorf [this message]
2012-03-16 18:26 ` Using out of band messages to change min/max frequencies Antti P Miettinen
2012-03-16 20:56   ` Mark Langsdorf
2012-03-18 14:34     ` Antti P Miettinen
2012-03-20 14:32       ` Mark Langsdorf

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=4F60D71C.6070709@calxeda.com \
    --to=mark.langsdorf@calxeda.com \
    --cc=cpufreq@vger.kernel.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