From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: cpufreq problem wrt suspend/resume on Athlon64
Date: Thu, 3 Feb 2005 11:56:47 +0100 [thread overview]
Message-ID: <20050203105647.GA17526@isilmar.linta.de> (raw)
In-Reply-To: <20050203104126.GC1389@elf.ucw.cz>
Hi,
On Thu, Feb 03, 2005 at 11:41:26AM +0100, Pavel Machek wrote:
> Okay, you are right, restoring it unconditionaly would be bad
> idea. Still it would be nice to tell cpufreq governor "please change
> the frequency ASAP" so it does not run at 800MHz for half an hour
> compiling kernels on AC power.
It already does that... or at least it should. in cpufreq_resume() there is
a call to schedule_work(&cpu_policy->update); which will cause a call
cpufreq_update_policy() in due course. And cpufreq_update_policy() calls the
governor, and it is supposed to adjust the frequency to the user's wish
then.
Dominik
next prev parent reply other threads:[~2005-02-03 10:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 13:28 cpufreq problem wrt suspend/resume on Athlon64 Rafael J. Wysocki
2005-02-02 13:31 ` Pavel Machek
2005-02-03 0:08 ` Rafael J. Wysocki
2005-02-03 10:41 ` Pavel Machek
2005-02-03 10:56 ` Dominik Brodowski [this message]
2005-02-03 10:58 ` Pavel Machek
2005-02-03 11:01 ` Dominik Brodowski
2005-02-03 11:30 ` Rafael J. Wysocki
2005-02-03 12:40 ` Dominik Brodowski
2005-02-03 13:20 ` Rafael J. Wysocki
2005-02-03 14:22 ` Pavel Machek
2005-02-03 23:15 ` Rafael J. Wysocki
2005-02-03 23:34 ` Nigel Cunningham
2005-02-03 23:52 ` Rafael J. Wysocki
2005-02-07 12:38 ` cpufreq problem wrt suspend/resume on Athlon64 [update] Rafael J. Wysocki
2005-02-03 14:20 ` cpufreq problem wrt suspend/resume on Athlon64 Pavel Machek
2005-02-03 21:46 ` Rafael J. Wysocki
2005-02-03 22:00 ` Pavel Machek
2005-02-03 23:37 ` Rafael J. Wysocki
2005-02-03 22:01 ` 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=20050203105647.GA17526@isilmar.linta.de \
--to=linux@dominikbrodowski.de \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox