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: support for software direct frequency throttling?
Date: Wed, 07 Aug 2013 14:38:55 -0500	[thread overview]
Message-ID: <5202A24F.6040506@calxeda.com> (raw)

Is there an easy way to dynamically limit the maximum or minimum
frequencies available to a governor? I'm trying to support frequency
throttling in response to a thermal event (or theoretically to allow a
BMC to set a minimum frequency regardless of current load).

I looked into doing this last year and it required some QoS patches that
I don't think ever made it into the kernel.

Is there a straightforward way to do this right now? If not, is anyone
working on implementing this? If not, any preferences from the
maintainers on how I should implement?

Thanks,
Mark Langsdorf
Calxeda, Inc.

             reply	other threads:[~2013-08-07 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 19:38 Mark Langsdorf [this message]
2013-08-07 23:37 ` support for software direct frequency throttling? Rafael J. Wysocki
2013-10-17 17:39   ` Mark Langsdorf
2013-10-17 20:28     ` Rafael J. Wysocki

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=5202A24F.6040506@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