From: Thomas Renninger <trenn@suse.de>
To: Thomas Renninger <mail@renninger.de>
Cc: cpufreq@lists.linux.org.uk,
Dominik Brodowski <linux@dominikbrodowski.de>
Subject: Re: [PATCH 1/2] PPC frequency change issues
Date: Fri, 20 Jan 2006 11:49:32 +0100 [thread overview]
Message-ID: <43D0C03C.9000707@suse.de> (raw)
In-Reply-To: <43CFD67D.4080204@renninger.de>
[-- Attachment #1: Type: text/plain, Size: 34 bytes --]
and the other one...
Thomas
[-- Attachment #2: cpufreq_bios_ppc_change --]
[-- Type: text/plain, Size: 1099 bytes --]
Author: Thomas Renninger <trenn@suse.de>
BIOS might change frequency behind our back
when BIOS changes allowed frequencies via _PPC
in this case cpufreq core got out of sync.
-> ask driver for current freq and notify
governors about a change
cpufreq.c | 10 ++++++++++
1 files changed, 10 insertions(+)
Index: linux-2.6.15/drivers/cpufreq/cpufreq.c
===================================================================
--- linux-2.6.15.orig/drivers/cpufreq/cpufreq.c 2006-01-03 04:21:10.000000000 +0100
+++ linux-2.6.15/drivers/cpufreq/cpufreq.c 2006-01-20 11:11:55.000000000 +0100
@@ -1402,6 +1402,16 @@
policy.policy = data->user_policy.policy;
policy.governor = data->user_policy.governor;
+ /* BIOS might change freq behind our back
+ -> ask driver for current freq and notify
+ governors about a change
+ */
+ if (cpufreq_driver->get){
+ policy.cur = cpufreq_driver->get(cpu);
+ if (data->cur != policy.cur)
+ cpufreq_out_of_sync(cpu, data->cur, policy.cur);
+ }
+
ret = __cpufreq_set_policy(data, &policy);
up(&data->lock);
[-- Attachment #3: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
prev parent reply other threads:[~2006-01-20 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 18:12 [PATCH 1/2] PPC frequency change issues Thomas Renninger
2006-01-20 10:49 ` Thomas Renninger [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=43D0C03C.9000707@suse.de \
--to=trenn@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux@dominikbrodowski.de \
--cc=mail@renninger.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.