From: Pavel Machek <pavel@ucw.cz>
To: Thomas Renninger <trenn@suse.de>
Cc: Antti P Miettinen <amiettinen@nvidia.com>,
davej@redhat.com, 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: Mon, 12 Jan 2015 14:32:48 +0100 [thread overview]
Message-ID: <20150112133248.GC15838@amd> (raw)
In-Reply-To: <201201192353.00761.trenn@suse.de>
Hi!
> I can't see why pm_qos is needed at all, better use cpufreq
> providing interface.
> PPC (BIOS request to cut max_frequency) in
> drivers/acpi/processor_perflib.c is a nice example
>
> 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
>
> I started with global cpufreq variables, they could also
> be declared per cpu like scaling_min_freq or others
> (at least input_boost_freq, input_boost_time should probably
> stay global). That would be:
> /sys/devices/system/cpu/cpuX/cpufreq/input_boost_freq
Going through old mails. This did not seem to go anywhere? Is it still
required? I don't see it in kernel. For some reason, it looks like it
has potential to help Nokia N900 a lot...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2015-01-12 13:32 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
2015-01-12 13:32 ` Pavel Machek [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=20150112133248.GC15838@amd \
--to=pavel@ucw.cz \
--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=rjw@sisk.pl \
--cc=trenn@suse.de \
/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.