From: Mark Langsdorf <mark.langsdorf@calxeda.com>
To: Antti P Miettinen <amiettinen@nvidia.com>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>
Subject: Re: Using out of band messages to change min/max frequencies
Date: Tue, 20 Mar 2012 09:32:55 -0500 [thread overview]
Message-ID: <4F689517.8090809@calxeda.com> (raw)
In-Reply-To: <87y5qyt1uu.fsf@amiettinen-lnx.nvidia.com>
On 03/18/2012 09:34 AM, Antti P Miettinen wrote:
> Mark Langsdorf <mark.langsdorf@calxeda.com> writes:
>> On 03/16/2012 01:26 PM, Antti P Miettinen wrote:
>>> Mark Langsdorf <mark.langsdorf@calxeda.com> writes:
>>>> Is there some better way to approach this?
>>>
>>> PM QoS :-)
>>>
>>> http://thread.gmane.org/gmane.linux.kernel.cpufreq/7794
>>> http://thread.gmane.org/gmane.linux.kernel.cpufreq/7797
>>
>> Thanks, that looks like it could be useful.
>>
>> Is there a sample implementation of this in the context of
>> a cpufreq device driver?
>
> Hmm.. controlling cpufreq core from cpufreq driver? Nope, this input
> event booster is the only example I have:
>
> http://thread.gmane.org/gmane.linux.kernel.cpufreq/7801
Thanks. It wasn't exactly applicable, but it gave enough
hints that I got the QoS parts working for my driver.
--Mark Langsdorf
Calxeda, Inc.
prev parent reply other threads:[~2012-03-20 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 17:36 Using out of band messages to change min/max frequencies Mark Langsdorf
2012-03-16 18:26 ` 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 [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=4F689517.8090809@calxeda.com \
--to=mark.langsdorf@calxeda.com \
--cc=amiettinen@nvidia.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