From: Thomas Renninger <trenn@suse.de>
To: Antti P Miettinen <amiettinen@nvidia.com>
Cc: davej@redhat.com, pavel@ucw.cz, rjw@sisk.pl, len.brown@intel.com,
khilman@ti.com, j-pihet@ti.com, markgross@thegnar.org,
cpufreq@vger.kernel.org, linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH] input: CPU frequency booster
Date: Fri, 20 Jan 2012 00:10:17 +0100 [thread overview]
Message-ID: <201201200010.18680.trenn@suse.de> (raw)
In-Reply-To: <201201192353.00761.trenn@suse.de>
On Thursday 19 January 2012 23:52:59 Thomas Renninger wrote:
> Hi,
...
> I'd also put this into drivers/cpufreq/cpufreq_input_boost.c.
>
> Find below a re-written version of the booster.
> Instead of pm_qos, it simply uses cpufreq interface:
> /sys/devices/system/cpu/cpufreq/input_boost_freq
> /sys/devices/system/cpu/cpufreq/input_boost_time
There was the same problem that scaling_max_freq showed a limit,
but one did not know whether it comes from:
- thermal
- PPC/BIOS
restrictions.
This got solved by introducing:
/sys/.../cpuX/cpufreq/bios_limit
which shows the PPC limitation
A file:
/sys/.../cpuX/cpufreq/input_boost_limit
could show the currently raised min_freq, caused by
the input booster.
Thomas
next prev parent reply other threads:[~2012-01-19 23:10 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 [this message]
2012-01-20 8:36 ` Antti P Miettinen
2012-01-20 10:50 ` Thomas Renninger
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=201201200010.18680.trenn@suse.de \
--to=trenn@suse.de \
--cc=amiettinen@nvidia.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--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 \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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.