From: Thomas Renninger <trenn@suse.de>
To: Antti P Miettinen <amiettinen@nvidia.com>
Cc: khilman@ti.com, len.brown@intel.com, markgross@thegnar.org,
cpufreq@vger.kernel.org, linux-pm@lists.linux-foundation.org,
j-pihet@ti.com
Subject: Re: [PATCH] input: CPU frequency booster
Date: Fri, 20 Jan 2012 11:50:22 +0100 [thread overview]
Message-ID: <201201201150.22950.trenn@suse.de> (raw)
In-Reply-To: <201201192353.00761.trenn@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]
On Thursday, January 19, 2012 11:52:59 PM Thomas Renninger wrote:
> Hi,
>
...
I forgot to activate the newly set limits:
> +/* sysfs stuff **************************/
> +
> +
> +static void cfb_boost(struct work_struct *w)
> +{
> + struct cpufreq_policy policy;
> + int ret;
> +
> + cancel_delayed_work_sync(&unboost);
> + ret = cpufreq_get_policy(&policy, 0);
> + if (ret)
> + return;
> + cpufreq_verify_within_limits(&policy, boost_freq,
> + policy.cpuinfo.max_freq);
cpufreq_update_policy(0);
> + queue_delayed_work(cfb_wq, &unboost,
> + msecs_to_jiffies(boost_time));
> +}
> +
> +static void cfb_unboost(struct work_struct *w)
> +{
> + struct cpufreq_policy policy;
> + int ret;
> +
> + ret = cpufreq_get_policy(&policy, 0);
> + if (ret)
> + return;
> +
> + cpufreq_verify_within_limits(&policy, policy.cpuinfo.min_freq,
> + policy.cpuinfo.max_freq);
cpufreq_update_policy(0);
Hope it works now?
Thomas
[-- Attachment #1.2: Type: text/html, Size: 7251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-01-20 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 12:53 [PATCH] input: CPU frequency booster Antti P Miettinen
2012-01-19 17:44 ` Pavel Machek
2012-01-22 10:55 ` Antti P Miettinen
2012-01-19 22:52 ` Thomas Renninger
2012-01-19 23:10 ` Thomas Renninger
2012-01-20 8:36 ` Antti P Miettinen
2012-01-20 10:50 ` Thomas Renninger [this message]
2015-01-12 13:32 ` Pavel Machek
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=201201201150.22950.trenn@suse.de \
--to=trenn@suse.de \
--cc=amiettinen@nvidia.com \
--cc=cpufreq@vger.kernel.org \
--cc=j-pihet@ti.com \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.